remove.bg shutdown · December 1, 2026

A two-value API migration

Keep your background removal pipeline running.

For the standard request in remove.bg’s API docs, your multipart form, field names, and response handling can stay put. Change the URL. Change the key. Ship.

2 values to change
1,000 trial API calls included
$0.01 per API image on Business
migration.patch READY
2 changes 0 request fields rewritten
−
ENDPOINT https://api.remove.bg/v1.0/removebg
+
ENDPOINT https://api.backgrounderase.com/v2
−
X-API-KEY rbg_live_••••••••••••
+
X-API-KEY be_live_•••••••••••••
UNCHANGED image_file · size=auto · image/png

remove.bg says its background removal service is moving after December 1, 2026. Read their shutdown FAQ.

Keep your existing
  • POST request
  • multipart form
  • image field
  • binary output handling

The exact change

Your request, before and after.

The request body below is identical. Only the highlighted service URL and API-key value move to BackgroundErase.

BEFORE

remove.bg

curl -H 'X-Api-Key: $REMOVE_BG_API_KEY' \
  -F 'image_file=@/path/to/file.jpg' \
  -F 'size=auto' \
  -f https://api.remove.bg/v1.0/removebg \
  -o no-bg.png
AFTER

BackgroundErase

curl -H 'X-Api-Key: $BACKGROUNDERASE_API_KEY' \
  -F 'image_file=@/path/to/file.jpg' \
  -F 'size=auto' \
  -f https://api.backgrounderase.com/v2 \
  -o no-bg.png
01

Replace endpoint https://api.backgrounderase.com/v2

02

Replace secret value BACKGROUNDERASE_API_KEY

That’s the standard migration.

A calm rollout

Move before the deadline without turning it into a rewrite.

Make the small code change, then give it the same staged rollout you would any production dependency.

Review the API reference
  1. 01

    Create a BackgroundErase API key

    Start the Business trial, then generate a key from API access in your account. Keep it in your server-side secret store.

    Start Business trial
  2. 02

    Change two values

    Replace the remove.bg endpoint and the secret value. Keep the X-Api-Key header name, multipart body, file field, and binary response handling.

  3. 03

    Send one production-shaped test

    Use a representative image and your existing request options. A successful cutout returns image bytes with a 200 response.

    Open API docs
  4. 04

    Roll out with your normal guardrails

    Deploy through staging, compare a small batch of outputs, then switch production traffic and watch status codes and latency.

Standard REST compatibility

Keep the request shape you already know.

BackgroundErase accepts the common multipart fields used in direct remove.bg calls and returns binary image data for the same simple write-to-file flow.

200 OK · image/png
✓image_file✓image_url✓image_file_b64✓size✓format✓channels✓crop✓bg_color✓bg_image_url✓bg_image_file
Using advanced remove.bg behavior?

The two-value swap is for standard direct REST cutout requests. If your integration depends on ZIP output, OAuth, ROI, positioning, generated shadows, or a remove.bg-specific SDK, map those parts before switching production traffic.

BackgroundErase Business

Simple migration. Simple bill.

Start with a 7-day trial and 1,000 API calls. Then pay a flat Business subscription plus the images you process.

  • Production API access
  • API keys and usage dashboard
  • Email support

Business

$20/ month
+ $0.01/ API image
Start 7-day free trial First 1,000 API calls included in the trial.

Migration FAQ

What stays the same?

Do I need to rename X-Api-Key?

No. HTTP header names are case-insensitive, and BackgroundErase accepts x-api-key. You can leave X-Api-Key exactly as it appears in the remove.bg example and replace only the key value.

Can I keep image_file and image_url?

Yes. Standard multipart requests can keep image_file or image_url, along with common options such as size, format, channels, crop, and bg_color.

Does the response still contain the image bytes?

Yes. A standard multipart request returns binary image data, so existing code that writes response bytes to a file can stay in place.

What if I use a remove.bg SDK or advanced options?

Call BackgroundErase over HTTP rather than through a remove.bg-specific SDK. ZIP output, OAuth, ROI, positioning, and generated-shadow options are not part of the two-value swap; map or remove those before rollout.

Before December 1, 2026

Change the endpoint. Keep shipping.

Get a BackgroundErase key, copy the request above, and test your production-shaped call today.

BackgroundErase is not affiliated with remove.bg, Canva, or Leonardo.Ai.