Switch Your Background Removal API to bgfree.app
Compare the implemented request contract and plan a measured migration.
A safe migration starts with the actual contract
bgfree.app is an independent service and is not affiliated with remove.bg. Update your endpoint and key, then check each field your integration sends against the documented compatibility list. The API accepts image_file or image multipart uploads, image_url or image_base64 and the size, format and bg_color options. Unknown request fields are rejected.
Frequently asked questions
Practical answers about this workflow and bgfree.app.
Which endpoint should I use?
Send POST requests to https://api.bgfree.app/v1.0/removebg and authenticate with a bgfree.app key in X-Api-Key.
Which common fields are supported?
The API accepts image_file or image multipart fields, image_url, image_base64, size, format, and bg_color. Unsupported fields are rejected explicitly.
Does the response match the previous provider exactly?
No exact response compatibility is promised. A successful bgfree.app request returns binary image data; failures return JSON errors. Update your response handling accordingly.
How are credits and rate limits handled?
Each successful request uses one image credit. API key and organization rate limits, concurrency limits, and balance checks may also affect requests.
How should I test before migrating?
Use a staging key and representative images, then test success, invalid input, insufficient balance, rate limits, and unsupported parameters before gradually routing traffic.