BUILT FOR YOUR WORKFLOW

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

ONE REQUEST

POST /api/v1/remove-background

X-Api-Key: <your-secret-key>

image_file: photo.jpg

ONE CLEAN RESULT

cutout.pngTransparent. Full dimensions. Ready.

Fits 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.

UP AND RUNNING

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://clearcut-orcin.vercel.app/api/v1/remove-background \
  -H "X-Api-Key: $CLEARCUT_API_KEY" \
  -F "image_file=@photo.jpg" \
  --output cutout.png

These are server-side examples. Never include a secret API key in frontend JavaScript or a public repository.

THE ENDPOINT

Send your image.

POST/api/v1/remove-background

Send a multipart/form-data request with the original image. Your HTTP client will set the multipart boundary automatically.

Request parameters
Parameter	Location	Description
`X-Api-Key`Required	Header	Your secret BackdropZap API key.
`image_file`Required	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.

WHAT COMES BACK

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.

Response status codes
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	Add credits in your account.
`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.

KEYS & PRIVACY

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.
API images are sent to BackdropZap and its processing provider. Standard browser editing stays on your device unless you choose Save to my images or confirm HD processing. See our Privacy policy for temporary storage and retention.

A FEW MORE DETAILS

Developer FAQs

Where do I see my usage?

Your account shows your credit balance, API keys, and usage history. You can buy more credits or manage your monthly plan from the same dashboard.

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.

Does the API use the same removal engine?

The standard browser editor processes images on your device. The paid API and HD option use server-side processing selected for detailed subjects. 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 bulk editing in your browser.

Your images.One API call.Background, gone.