Your images.
One API call.
Background, gone.
Bring automatic background removal to your app, product catalog, or next great idea.
10 trial images for eligible verified accounts
backdropzap-api
POST /api/v1/remove-background
X-Api-Key: <your-secret-key>
image_file: photo.jpgFits your stack
A standard HTTP endpoint. Use the language and tools you already know.
Ready-to-use PNGs
Send a JPG, PNG, or WebP. Get back a transparent PNG at the dimensions after EXIF orientation is applied.
Simple credit usage
One credit per successfully processed image. Failed processing jobs are refunded.
A few lines. A clean cut.
Create an account, verify your email, and generate an API key in your account dashboard. Keep it in the CLEARCUT_API_KEY environment variable on your server.
curl --fail --show-error \
https://backdropzap.com/api/v1/remove-background \
-H "X-Api-Key: $CLEARCUT_API_KEY" \
-F "image_file=@photo.jpg" \
--output cutout.pngThese are server-side examples. Never include a secret API key in frontend JavaScript or a public repository.
Send your image.
/api/v1/remove-backgroundSend a multipart/form-data request with the original image. Your HTTP client will set the multipart boundary automatically.
| Parameter | Location | Description |
|---|---|---|
X-Api-KeyRequired | Header | Your secret BackdropZap API key. |
image_fileRequired | Form data | A JPG, PNG, or WebP file. Maximum 3 MiB (3,145,728 bytes) and 4 megapixels. |
Send one image per request. Each account can make 10 requests per minute with up to 2 processing concurrently. URL-based input, animated images, SVGs, and generated backgrounds are not supported by this endpoint.
Image in. Transparent image out.
A successful response returns HTTP 200 with Content-Type: image/png. Save the response body as a PNG file. The output keeps the dimensions after EXIF orientation is applied and must be no larger than 4 MiB. The X-Request-Id header identifies the request; X-Credits-Remaining reports the remaining balance.
| Status | Meaning | What to do |
|---|---|---|
200 | Image processed | Save the PNG response. One credit is used. |
400 / 413 / 415 / 422 | Invalid or unsupported image | Check the file type, file size, dimensions, and form field. A result above 4 MiB also returns 413 and is refunded. |
401 / 403 | Authentication required | Check your API key and verify your account email. |
402 | No credits available | Paid plans open soon. Join the purchase notification list. |
408 | Upload timed out | Check your connection and upload a smaller file. |
429 | Too many requests | Wait at least 60 seconds, as indicated by Retry-After, then reduce concurrency. |
500 / 503 / 504 | Processing unavailable | Try again later. Failed jobs are refunded; an interrupted job may need reconciliation. |
Error responses use JSON. Check the HTTP status before saving the response so that an error is not mistaken for an image. Interrupted pending jobs are reconciled automatically by a scheduled service. You do not need to send another request to recover a reserved credit.
Automatic retries after a lost connection can create a second request and spend another credit. Check whether your original request completed before resending.
Keep your automation secure.
- Store API keys in environment variables or your platform’s secret manager.
- Use a separate key for each integration so you can revoke one without interrupting the others.
- Revoke an exposed or unused key immediately from your account.
- Images are sent to BackdropZap and its cloud processing provider. Guest previews use cloud processing with Cloudflare Turnstile verification. Signed-in editor uploads are automatically processed at full resolution, with one credit per successful image. Background removal is not performed on your device. See our Privacy policy for temporary storage and retention.
Developer FAQs
Where do I see my usage?
Your account shows your credit balance, API keys, and usage history. Purchases are coming soon; join the notification list on the pricing page.
Can I use this in a browser app?
Call the API from your own backend to keep your key private. Your frontend can upload to your backend, which forwards the request to BackdropZap and returns the result.
How are images processed?
Guest previews, signed-in editor uploads, and API requests use cloud processing. Signed-in editor uploads are processed at full resolution, with one credit per successful image. If processing is unavailable, the request returns an error; there is no on-device fallback. Results vary; fine hair, glass, and busy backgrounds can still need touch-ups.
Can I process an entire folder?
Send one image per API request and process your queue sequentially to start. For a manual workflow, use the editor one image at a time. Guest previews have daily limits; signed-in processing uses credits. Batch editing is coming later.