remove.bg is shutting down its self-service API on December 1, 2026, at 9:00 AM CET. Its background removal is moving into Canva, and API users are being directed to Leonardo.Ai.
If you have code calling api.remove.bg, the real question isn't "which background removal API is best?" It's "how much of my integration do I have to rewrite?"
So instead of a classic top 5, this article groups the alternatives by migration effort, from "change the URL and key" to "run it yourself."
Quick comparison
| Category | Service | What you change | Pricing* |
|---|---|---|---|
| Drop-in compatible | ShortPixel AI Background Removal | Base URL + API key | Free plan with 100 AI Credits/month and Unlimited AI plan for $13.33 per month |
| Drop-in compatible | Photoroom | Endpoint URL + API key | $20/month for 1,000 images (Basic plan) |
| Official migration path | Leonardo.Ai | Endpoint, auth, request and response format | About $0.10 per image, prepaid |
| New API integration | Slazzer | Endpoint, auth header, request handling | Credit packs, on-premise option |
| Self-hosted | rembg | Your own service and integration | Free, runs on your hardware |
*Prices as of November 2026. They can change, so check each provider's official pricing page before deciding.
Drop-in compatible APIs
Both services in this group accept remove.bg's parameter names and return the processed image the way remove.bg does. For a standard request, you change the URL and the API key, and the rest of your code stays the same.
They differ in the details, though:
| ShortPixel | Photoroom | |
|---|---|---|
Keeps the /v1.0/removebg path |
Yes | No (/v1/segment) |
image_url input |
Yes | No, upload the file (Basic plan) |
image_file_b64 input |
Yes | Upload the file |
crop |
Not yet | Yes |
| HEIC input | Yes | Yes |
| Account/credits endpoint |
GET /v1.0/account or dashboard |
Separate dashboard |
So before choosing, check which parameters and input methods your integration actually uses.
1. ShortPixel
ShortPixel's background removal API is built as a drop-in replacement for remove.bg. It preserves the remove.bg endpoint structure, authentication method, response format, and error handling for supported requests.
Before (remove.bg):
curl -H "X-Api-Key: YOUR_REMOVEBG_KEY" \
-F "[email protected]" \
-F "size=auto" \
-f https://api.remove.bg/v1.0/removebg \
-o no-bg.png
After (ShortPixel):
curl -H "X-Api-Key: YOUR_SHORTPIXEL_KEY" \
-F "[email protected]" \
-F "size=auto" \
-f https://remove-bg-di.shortpixel.com/v1.0/removebg \
-o no-bg.png
Because the path stays the same (/v1.0/removebg), only the base URL changes: https://api.remove.bg becomes https://remove-bg-di.shortpixel.com. That matters for plugins and SDKs that let you configure the API base URL but not the full path. Set it to https://remove-bg-di.shortpixel.com/v1.0 and use your ShortPixel key.
What carries over:
| Parameter | Values |
|---|---|
| Image input |
image_file, image_file_b64, image_url
|
size |
preview (default), full, 50MP, auto, plus older values small, regular, medium, hd, 4k
|
format |
auto, png, jpg, webp, zip
|
type, type_level, channels
|
Same values as remove.bg |
| Background |
bg_color, bg_image_url, bg_image_file
|
The response headers (X-Credits-Charged, X-Width, X-Height, X-Type) and the JSON error format with its HTTP status codes also match remove.bg.
Differences to check:
-
crop,roi,scale,position, and shadow parameters aren't in the supported list. - Input is limited to JPG, PNG, and WebP, up to 22 MB and 50 megapixels.
- If you don't send
size, you getpreview(up to 0.25 megapixels). Sendsize=autoorsize=fullfor full resolution.
Pricing: a free plan with 100 credits per month and an Unlimited AI option that costs $13.33 per month. Check the current pricing and usage terms for your volume. ShortPixel's broader API also handles compression and WebP/AVIF conversion, and there's a WordPress plugin, which can help if your images end up on a website.
Best for: existing integrations, plugins, and SDKs where you want to change as little as possible, including workflows that send image URLs or base64 data.
๐ API documentation ยท Migration guide
2. Photoroom
Photoroom's Remove Background API has built-in remove.bg compatibility. It accepts the same argument names and returns the same result format.
Before (remove.bg):
curl -H "x-api-key: YOUR_REMOVEBG_KEY" \
-F "[email protected]" \
-F "crop=true" \
-F "bg_color=FFFFFF" \
-F "format=jpg" \
-f https://api.remove.bg/v1.0/removebg \
-o result.jpg
After (Photoroom):
curl -H "x-api-key: YOUR_PHOTOROOM_KEY" \
-F "[email protected]" \
-F "crop=true" \
-F "bg_color=FFFFFF" \
-F "format=jpg" \
-f https://sdk.photoroom.com/v1/segment \
-o result.jpg
Here the full URL changes, path included: /v1.0/removebg becomes /v1/segment. In your own code that's a one-line change. In a plugin or SDK, check whether you can set the full endpoint and not just the base URL.
What carries over: image_file, crop, bg_color, format, and size, plus the result format.
Differences to check:
- The Remove Background API (Basic plan) requires uploading the image file. If you currently send
image_url, you'll need to download the image first, or use the Image Editing API (Plus plan), which accepts URLs but costs more per image. - Photoroom recommends testing less common parameters on your own images before switching.
- Input supports PNG, JPEG, WebP, and HEIC. Very large images are resized down, so check the resolution limits in the docs.
- Background replacement with images, shadows, and relighting are part of the separate Image Editing API (Plus plan).
Pricing: the Basic plan is $20/month for 1,000 images, about $0.02 per image. Check the current pricing.
Best for: e-commerce and product photography, especially if you rely on crop or plan to use Photoroom's editing features later.
๐ remove.bg compatibility docs
Switching between drop-in providers in code
If your requests use image_file, you can keep the endpoint in config and test both providers side by side:
import os
import requests
ENDPOINTS = {
"removebg": "https://api.remove.bg/v1.0/removebg",
"shortpixel": "https://remove-bg-di.shortpixel.com/v1.0/removebg",
"photoroom": "https://sdk.photoroom.com/v1/segment",
}
provider = os.environ.get("BG_PROVIDER", "shortpixel")
with open("photo.jpg", "rb") as image:
response = requests.post(
ENDPOINTS[provider],
files={"image_file": image},
data={"size": "auto"},
headers={"X-Api-Key": os.environ["BG_API_KEY"]},
timeout=120,
)
response.raise_for_status()
with open("no-bg.png", "wb") as out:
out.write(response.content)
This also makes the next migration a config change instead of a code change.
Official migration path
3. Leonardo.Ai
Leonardo.Ai is where remove.bg is directing its API users. It's part of Canva, like remove.bg, and offers a synchronous API that returns the result in a single request.
What changes:
-
Endpoint:
POST https://cloud.leonardo.ai/api/rest/v2/generationssync -
Auth:
Authorization: Bearer <key>instead ofX-Api-Key -
Request: JSON with
"model": "remove-bg". Your options keep their names but move under aparametersobject, and file uploads are sent as base64. -
Storage: set
"ephemeral": trueto match remove.bg's behavior of not storing your images. - Account: remove.bg keys and credits don't carry over.
Pricing: about $0.10 per image, from a prepaid balance.
Best for: teams that want the official successor or plan to use Leonardo's other image APIs.
๐ Leonardo.Ai migration guide
New API integration
4. Slazzer
Slazzer has its own background removal API, plus a desktop app and an on-premise option for unlimited processing on your own servers.
What changes:
-
Endpoint:
POST https://api.slazzer.com/v2.0/remove_image_background -
Auth:
API-KEYheader - Request and response handling: different from remove.bg, so plan for integration work
Pricing: credit packs, with an on-premise license for high volumes.
Best for: agencies and businesses with bulk processing needs, or ones that can't send images to a third-party cloud.
๐ Slazzer API
Self-hosted
5. rembg
rembg is an open-source Python tool you can run as a CLI, a library, or an HTTP server.
pip install "rembg[cpu,cli]"
rembg i input.jpg output.png
What changes: everything. You run and maintain the service yourself, and it doesn't expose a remove.bg-compatible API out of the box.
Pricing: free, but you pay in hardware and maintenance. Large volumes need a GPU.
Best for: privacy-sensitive workloads and teams that already run their own image processing. Quality on hair, fur, and glass is usually behind the commercial APIs, so test first.
Migration checklist
- Search your code, workflows (n8n, Make, Zapier), and plugins for
api.remove.bgandremovebg. - List the parameters and input methods you actually use. This decides which drop-in fits: some integrations depend on
crop, others onimage_urlor base64 input. - If remove.bg is called from a plugin or SDK, check whether you can change the base URL, the full endpoint, or neither.
- Test 10โ20 of your hardest images (hair, fur, glass, low contrast) with your top candidates.
- Check output resolution, error handling, and rate limits.
- Deploy before December 1, not on it.
Final thoughts
For existing remove.bg integrations, ShortPixel and Photoroom are both worth considering as drop-in alternatives.
ShortPixel preserves the original /v1.0/removebg endpoint path and supports image uploads, image URLs, and base64 input, so it's the easiest solution to switch to. This can make migration especially straightforward for existing plugins and integrations where only the API base URL can be configured.
Photoroom also offers remove.bg compatibility and is particularly relevant for product photography, although its supported input methods and parameters differ.
For workflows that require a different approach, Leonardo.Ai, Slazzer, and rembg are worth exploring.
Whichever option you choose, test your existing requests before the December 1 shutdown.
Are you migrating away from remove.bg? Which alternative are you considering?
Top comments (0)