How to Migrate from the remove.bg API Before December 1, 2026: Checklist, Cost Comparison & Code Examples
A practical developer guide for migrating background-removal pipelines off remove.bg before the December 1, 2026 Leonardo.Ai transition, including endpoint changes, parameter differences, and pricing comparisons.
Why teams are migrating before December 1, 2026
According to remove.bg's official announcements, its web workflow has been transitioning into Canva while its standalone API transitions toward Leonardo.Ai on December 1, 2026 (with published credit expiry listed for December 1, 2026 at 9:00 AM CET). If your ecommerce pipeline, SaaS app, or CMS calls https://api.remove.bg/v1.0/removebg, switching endpoints early prevents production failures and gives you time to verify edge quality and billing behavior on your own image set.
RemoveBGTool (https://removebgtool.net) is an independent background removal platform and developer API—not affiliated with remove.bg, Canva, or Leonardo.Ai. Below is the exact migration checklist, parameter compatibility matrix, and pricing comparison to evaluate switching cleanly.
Pricing & workflow comparison (reviewed November 21, 2026)
| Dimension | remove.bg (published snapshot) | RemoveBGTool (removebgtool.net) |
| ------------------------- | ------------------------------------------ | ----------------------------------------------------------------------- |
| API Endpoint | POST https://api.remove.bg/v1.0/removebg | POST https://removebgtool.net/v1.0/removebg |
| Auth Header | X-API-Key | X-API-Key |
| Entry Monthly Plan | $9 / month (40 credits) | $8.10 / month (40 credits) |
| Mid / Volume Monthly | Tiered subscriptions | $35.10 / mo (200 credits), $80.10 / mo (500 credits) |
| Pay-As-You-Go Starter | $3 / 3 credits | $2.70 / 3 credits, $8.10 / 10 credits, $44.10 / 75 credits |
| Credit Sharing | Account balance | Shared across web full-size, batch ZIP, and API |
| Max API Upload | Up to 22 MB | Up to 22 MiB (file, HTTPS URL, or base64) |
| Free Web Testing | Preview | 3 guest / 5 signed-in watermark-free previews daily (up to 0.25 MP) |
Always verify current third-party terms directly on remove.bg pricing and remove.bg API docs. Accounts, keys, and remaining balances from remove.bg do not transfer to RemoveBGTool.
Step 1: Audit which parameters your integration actually sends
Before changing any production URL, log the exact multipart or JSON fields your app sends today. RemoveBGTool supports the core request structure (POST /v1.0/removebg with X-API-Key), while explicitly separating supported parameters from unsupported layout flags so you avoid silent surprises.
| Parameter | Status on RemoveBGTool API | Notes |
| ---------------------------------------------------- | -------------------------- | ---------------------------------------------------------------------------------------------------- |
| image_file, image_url, image_file_b64 | Supported | Send one input per request (up to 22 MiB). |
| size | Supported | Defaults to preview; pass full / auto according to your workflow and verify output dimensions. |
| format | Supported | PNG (default transparent), JPG, WebP (zip output is not supported via API; use web batch for ZIP). |
| bg_color, crop | Check docs | Verify exact supported values in the API Reference and OpenAPI spec. |
| shadow, roi, scale, position, bg_image_url | Not drop-in identical | Test in staging or apply compositing in your own image service after receiving the transparent PNG. |
Step 2: Update the endpoint and API key (cURL & Node.js)
Generate a new API key in your RemoveBGTool account settings, then test against 10–20 representative production images (white products, portraits with hair, dark objects, and high-res catalog photos).
cURL example
curl -X POST "https://removebgtool.net/v1.0/removebg" \
-H "X-API-Key: YOUR_REMOVEBGTOOL_API_KEY" \
-F "image_file=@product.jpg" \
-F "size=full" \
-F "format=png" \
-o product-cutout.png
Node.js / TypeScript example
import { readFile, writeFile } from 'node:fs/promises';
const form = new FormData();
const bytes = await readFile('product.jpg');
form.append(
'image_file',
new Blob([bytes], { type: 'image/jpeg' }),
'product.jpg'
);
form.append('size', 'full');
form.append('format', 'png');
const res = await fetch('https://removebgtool.net/v1.0/removebg', {
method: 'POST',
headers: { 'X-API-Key': process.env.REMOVEBGTOOL_API_KEY! },
body: form,
});
if (!res.ok) {
const err = await res.text();
throw new Error(`RemoveBGTool API error ${res.status}: ${err}`);
}
const buffer = Buffer.from(await res.arrayBuffer());
await writeFile('product-cutout.png', buffer);
Step 3: Validate edge quality, latency, and error handling
- Test failure-prone image classes: include pale/white packaging on white studio backdrops, curly or low-contrast hair, reflective cars/glass, and thin straps or handles.
- Handle HTTP errors cleanly: inspect
401(invalid key),402(insufficient_credits),413(payload too large), and429(rate limit) with bounded retries only on transient5xxresponses so you never double-spend credits. - Check credit deduction: verify that failed requests do not consume credits and confirm your monthly or pay-as-you-go volume matches your peak traffic.
Step 4: Dual-run in staging before cutting over production
Keep your old client behind an environment flag (BG_REMOVER_PROVIDER=removebgtool) and run a small percentage of traffic or a shadow batch first. Once output dimensions, alpha transparency, and response times pass your QA threshold, switch 100% of traffic well before December 1, 2026.
Next steps
- Read the full remove.bg API Migration Guide and API Documentation.
- Need browser editing instead of code? Try the remove.bg Alternative Editor, Batch Background Remover, or compare plans on remove.bg Pricing Alternative.