Dev.to WebDev 🛠 Dev 👁 0 📖 3 min read

remove.bg's API shuts down on 1 December 2026: how to migrate in one line

remove.bg has announced that its standalone website and self-serve API end on 1 December 2026. Background removal moves into Canva, and self-serve API access moves to Leonardo.Ai, which is a different API with its own in

remove.bg has announced that its standalone website and self-serve API end on 1 December 2026. Background removal moves into Canva, and self-serve API access moves to Leonardo.Ai, which is a different API with its own integration. Enterprise contracts continue.

If your app, a Shopify plugin, a Zapier flow or a cron job calls api.remove.bg, it needs a new home before that date. Here are your options and the smallest possible migration.

Your three options

  1. Move to Leonardo.Ai. It's the official path, but it's a different API, so plan time to rewrite and retest your integration.
  2. Self-host an open-source model (rembg, BiRefNet and friends). No per-image cost, but you run the GPUs, the queue and the edge cleanup yourself.
  3. Switch to a drop-in compatible API. Keep your code, change the URL and the key.

Disclosure: I work on NukeBG, which takes option 3, so the examples below use it. The same checklist applies to any compatible provider.

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 the new key), same parameter names, same response headers and the same {"errors": [...]} error format.

cURL

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

Python

import os, requests

r = requests.post(
    "https://api.nukebg.com/v1.0/removebg",
    headers={"X-Api-Key": os.environ["NUKEBG_API_KEY"]},
    files={"image_file": open("photo.jpg", "rb")},
    data={"size": "auto"},
)
r.raise_for_status()
open("no-bg.png", "wb").write(r.content)

Node

import { openAsBlob } from "node:fs";
import { writeFile } from "node:fs/promises";

const form = new FormData();
form.append("image_file", await openAsBlob("photo.jpg"));
form.append("size", "auto");

const res = await fetch("https://api.nukebg.com/v1.0/removebg", {
  method: "POST",
  headers: { "X-Api-Key": process.env.NUKEBG_API_KEY },
  body: form,
});
await writeFile("no-bg.png", Buffer.from(await res.arrayBuffer()));

What carries over

  • Inputs: image_file, image_file_b64 or image_url, as multipart, urlencoded or JSON.
  • Parameters: size, format (including zip), crop and crop_margin, roi, scale and position, channels, bg_color, bg_image_url and bg_image_file.
  • JSON responses: send Accept: application/json to get result_b64 plus the foreground box.
  • Headers: X-Width, X-Height, X-Credits-Charged, X-Type and the X-Foreground-* bounding box.
  • Balance check: GET /v1.0/account returns the same account shape.

A few cosmetic options (type, semitransparency, shadow_type) are accepted but have no effect, so old requests don't break.

Zapier, Make or n8n

Open the HTTP step that calls remove.bg, change the URL to https://api.nukebg.com/v1.0/removebg and the X-Api-Key value to your new key. Leave every other field alone.

Migration checklist

  1. Create an API key (new accounts get 50 free credits, no watermark).
  2. Change the URL and the key.
  3. Send one real image and compare it with today's result.
  4. Deploy before 1 December 2026.

Pricing, if it matters for your volume: one successful image is one credit, failed images are free, monthly plans start at $9 for 1,500 credits, and one-off packs (from $25) never expire.

The full parameter table, error codes and FAQ are on the migration guide, and the API reference is at nukebg.com/docs.

If you're running a different migration path, self-hosted or otherwise, I'd like to hear how it went in the comments.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.