What is the simplest remove.bg API replacement?

One that accepts the same requests. With NukeBG you change https://api.remove.bg/v1.0/removebg to https://api.nukebg.com/v1.0/removebg, use your NukeBG key in the same X-Api-Key header, and keep the rest of your code.

Do I have to rewrite my integration?

No. The /v1.0/removebg and /v1.0/account endpoints take remove.bg's parameters (size, roi, crop, crop_margin, scale, position, bg_color, bg_image_url, bg_image_file, format, channels) and return its headers, JSON shape and error format.

What is the best remove.bg alternative?

If you call the remove.bg API, the best alternative is one you can switch to without rewriting code. NukeBG accepts the same requests, keeps full resolution on paid credits, processes batches of up to 500 images, and its credits never expire. If you only use the website, the NukeBG Studio removes backgrounds in the browser and exports Amazon, Shopify and Etsy sizes.

Is there a free remove.bg alternative?

Yes. NukeBG gives every new account 50 free credits plus 20 a month, with no watermark. Free cutouts go up to 2 MP; full resolution (up to 25 MP, or 50 MP) uses paid credits from $15.

A warm GPU cuts out a typical image in under a tenth of a second; including upload and download, most API calls finish in one to two seconds.

Does it work with Zapier, Make or n8n?

Yes. In the HTTP step that calls remove.bg, change the URL to the NukeBG one and the X-Api-Key value to your NukeBG key. Leave every other field as it is.

How much does it cost?

Each successful image costs 1 credit (2 for size=50mp). Failed images are free. New accounts get 50 free credits; packs start at $15 for 4,000 credits, and paid credits never expire.

Can I check my balance like before?

Yes. GET https://api.nukebg.com/v1.0/account returns remove.bg's account shape, with your credits under data.attributes.

What happens to my remove.bg key and credits?

Your remove.bg key stops working for the self-serve API on 1 December 2026. Check remove.bg's own FAQ for what happens to any unused credits. NukeBG uses its own API keys and credits, and paid NukeBG credits never expire.

remove.bg migration

The drop-in remove.bg API alternative. Change one line, keep your code.

remove.bg's standalone website and self-serve API end on 1 December 2026, 09:00 CET, and API access moves to Leonardo.Ai, which needs a different integration (Leonardo.Ai's announcement). NukeBG accepts the same requests: point your code at our URL, use our key, and you're done.

Get your API key Migration checklist

remove.bg's self-serve API ends 1 December 2026, 09:00 CET

days

hours

minutes

seconds

Is remove.bg shutting down?

Yes, the self-serve part. remove.bg's standalone website and self-serve API stop on 1 December 2026, 09:00 CET. Background removal moves into Canva, and API access moves to Leonardo.Ai, a different API that needs code changes. Enterprise contracts continue. If your app, plugin or Zapier flow calls api.remove.bg, it needs a new provider before that date.

Move to Leonardo.Ai
A different API: plan time to rewrite and retest your integration.
Switch to a drop-in API
Keep your code. Change the URL and the key, test one image, deploy.

The one line that changes

Before https://api.remove.bg/v1.0/removebg

After https://api.nukebg.com/v1.0/removebg

Same X-Api-Key header with your NukeBG key. Same parameter names, same response headers, same {"errors": [...]} error format.

Before and after

A typical integration in four languages. Only the URL and the key change.

Before: remove.bg

curl -f -H "X-Api-Key: $REMOVEBG_API_KEY" \
  -F image_file=@photo.jpg \
  -F size=auto \
  -o no-bg.png \
  https://api.remove.bg/v1.0/removebg

After: NukeBG

curl -f -H "X-Api-Key: $NUKEBG_API_KEY" \
  -F image_file=@photo.jpg \
  -F size=auto \
  -o no-bg.png \
  https://api.nukebg.com/v1.0/removebg

Using Zapier, Make or n8n?

Open the HTTP step that calls remove.bg (Zapier Webhooks, Make HTTP, n8n HTTP Request), change the URL to https://api.nukebg.com/v1.0/removebg and the X-Api-Key value to your NukeBG key. Keep every other field as it is.

Parameter compatibility

Everything your remove.bg request sends is accepted. A few cosmetic options have no effect here, and the table says so.

Parameter	Status	Notes
image_file / image_file_b64 / image_url	Supported	Multipart, urlencoded or JSON bodies. JPG, PNG or WebP up to 25 MB; image_url must be a public http(s) address.
size	Supported	preview, small, regular ≈ 0.25 MP · medium 1.5 MP · hd 4 MP · auto, full, 4k up to 25 MP · 50mp up to 50 MP. Free credits return up to 2 MP; full resolution uses paid credits.
format	Supported	auto (PNG if transparent, otherwise JPG), png, jpg, webp, and zip (color.jpg + alpha.png).
crop / crop_margin	Supported	Trim to the subject, with 1–4 CSS-style margins in px or % of the subject ("10% 20%" = vertical, horizontal); up to 500px or 50% per side.
roi	Supported	"x1 y1 x2 y2" in px or %: only the subject inside that region is kept.
scale / position	Supported	scale 10%–100% or original; position center, original or "x% y%" (0% 0% = top left).
channels	Supported	rgba (cutout) or alpha (grayscale mask).
bg_color	Supported	Hex with or without # (3, 6 or 8 digits; 8-digit colours drop their alpha) or a colour name such as white, black or navy.
bg_image_url / bg_image_file	Supported	The cutout is composited over your background image, cover-fitted to the output size.
Accept: application/json	Supported	Returns { data: { result_b64, foreground_top, foreground_left, foreground_width, foreground_height } }.
type / type_level	Accepted, ignored	The subject is detected automatically.
semitransparency	Accepted, ignored	Soft and semi-transparent edges come straight from the matte.
shadow_type / shadow_opacity / add_shadow	Accepted, ignored	No shadow is added on this endpoint (use shadow on /v1/cutouts).

Response headers

A successful call returns the image bytes (or a ZIP) with these headers. Send Accept: application/json for result_b64 instead.

X-Width / X-Height: Size of the result in pixels.
X-Credits-Charged: Credits this image used: 1 (2 for size=50mp). Failed images cost 0.
X-Credits-Remaining: Your balance after this call (extra).
X-Type: Always "product" (subject detection is automatic).
X-Foreground-Top / -Left / -Width / -Height: Bounding box of the subject in the result, in pixels.
X-Request-ID: Echoes your X-Request-ID, or a generated id. Quote it if you contact support.

Errors

Same shape as remove.bg: {"errors": [{"title", "code"}]}.

400: Invalid parameter or image: invalid_size, invalid_format, invalid_bg_color, missing_image, invalid_image_url.
402: insufficient_credits: top up on the pricing page (or free_tier_limit for sizes that need paid credits).
403: auth_failed: missing or invalid X-Api-Key.
413 / 415: file_too_large (over 25 MB) / unsupported_image (not JPG, PNG or WebP).
429: rate_limit_exceeded: see the Retry-After header.
500 / 503: Processing failed or the engine is briefly unavailable. Retry; failed images are never charged.

Check your balance with GET https://api.nukebg.com/v1.0/account (remove.bg's account shape). Full details in the API reference.

1 credit per image. Credits never expire.

Every successful image costs 1 credit on the remove.bg endpoint (2 for size=50mp). Failed images are free, and new accounts get 50 free credits to test with.

Starter

$15

4,000 credits

$0.38 per 100 images

Pro

$45

15,000 credits

$0.30 per 100 images

Scale

$89

40,000 credits

$0.22 per 100 images

Volume

$199

100,000 credits

$0.20 per 100 images

Credits never expire. Top up once, use them next week or next year.
No subscription. One-time packs. Nothing renews.
Failed images are free. A credit is used only when the background is removed.

See pricing

Migration checklist

1
Get a NukeBG API key
Sign up (50 free credits) and create a key on your account page.
2
Change one line
Point your code at https://api.nukebg.com/v1.0/removebg and put the new key in the same X-Api-Key header.
3
Test one image
Send one real request and compare it with the result you get today.
4
Switch your traffic
Deploy before 1 December 2026, 09:00 CET. Top up once; paid credits never expire.

remove.bg migration FAQ

remove.bg has announced that its standalone website and self-serve API end on 1 December 2026, 09:00 CET. Self-serve API access moves to Leonardo.Ai (also part of Canva), which uses a different integration. Existing Enterprise API contracts are not affected, according to remove.bg.

Switch before 1 December 2026, 09:00 CET

Create a key, change one line, test one image. 50 free credits included.

Get your API key API reference

remove.bg's self-serve API ends in