Switch image workflows with confidence
Keep the basic request shape while changing your endpoint and API key.
A migration should be predictable
The API supports multipart image uploads, image_url, image_base64, size, format and bg_color. It returns a binary image with request and image usage headers. Crop, positioning, type, scale, source image URL response mode and other undocumented parameters return an explicit unsupported-parameter error. Input accepts PNG, JPEG and WebP up to the configured upload limit.
curl -X POST \\ https://api.bgfree.app/v1.0/removebg \\ -H "X-Api-Key: YOUR_API_KEY" \\ -F "image_file=@photo.jpg" \\ -o cutout.pngUse a server-side API key. Success returns binary image data; errors return JSON. Each successful API request uses one image credit.
See request fields, limits, and errors ↗Frequently asked questions
Practical answers about this workflow and bgfree.app.
Is bgfree.app affiliated with remove.bg?
No. bgfree.app is an independent service and is not affiliated with remove.bg.
Is the API a drop-in replacement?
No. It supports a subset of similarly shaped requests. You must replace the endpoint and API key and confirm that your parameters are supported.
Which fields are supported?
The API supports image_file or image multipart uploads, image_url, image_base64, size, format, and bg_color. Other fields return an unsupported_parameter error.
How should I compare services?
Test representative images, compare results against your own quality needs, and review current pricing, usage limits, and error handling before switching.