Home / Migration Guide
Protocol Retiring: Dec 1, 2026 (09:00 CET)

How to Migrate from remove.bg® API in 60 Seconds

With the upcoming retirement of the standalone api.remove.bg endpoint on December 1, 2026, self-serve users are being directed to Leonardo.Ai. Here is how to retain seamless synchronous PNG output without rewriting your backend.

The Migration Problem: Why Leonardo.Ai Requires a Complete Rewrite

When Canva (owner of remove.bg) announced the consolidation of API services, developers were instructed to migrate to Leonardo.Ai. However, Leonardo's API is fundamentally engineered for generative AI generation, not synchronous pipeline utility:

❌ Leonardo.Ai Official Path
  • • Asynchronous only: Returns a job_id. Requires polling loops.
  • • S3 presigned URLs: Must fetch raw image, convert to Base64 JSON, and fetch from temporary AWS buckets.
  • • Token credit math: 1 image = variable token burn rates based on resolution.
  • • Refactor cost: Complete overhaul of existing SDKs, queues, and webhook listeners.
✅ BGRemover Drop-in API
  • • 100% Wire-compatible: Same POST /v1.0/removebg path and parameters.
  • • Direct Binary PNG: Instant raw HTTP stream response. Zero S3 storage hops.
  • • Zero code rewrite: Just change 1 line of configuration (baseURL).
  • • Zero Retention: Images processed in RAM and discarded immediately.
Protocol Specification & Migration Mapping Matrix 0 Lines Code Refactor
Specification Dimension remove.bg® Standard Leonardo.Ai (Official Route) BGRemover Drop-in API
Target Endpoint POST /v1.0/removebg POST /api/rest/v2/generationssync POST /v1.0/removebg (Identical)
Auth Header X-Api-Key: <KEY> Authorization: Bearer <KEY> X-Api-Key: <KEY> (Identical)
Request Encoding multipart/form-data JSON only (application/json) multipart/form-data (Identical)
Image Upload Mechanism Raw binary file stream Base64 encoded string or S3 URL Raw binary file stream (Identical)
Delivery Payload Direct binary PNG stream (200 OK) Nested JSON response object Direct binary PNG stream (Identical)
Telemetry Headers X-Width, X-Height, X-Credits No compatible headers X-Width, X-Height, X-Credits-Charged
Developer Refactor Work 0 (Existing stack) Rewrite network client & response parser Update 1 line: baseUrl host only
🎁

Unused remove.bg Credits Match Guarantee

Official PAYG credits expire permanently on Dec 1, 2026. Forward a screenshot of your previous account balance to [email protected] to receive an immediate complimentary balance injection (up to 500 free production credits) into your developer account.

Create Account →

The 3-Step 60-Second Migration Process

1

Get Your API Key

Obtain your drop-in API credentials from the dashboard or use our sandbox testing key during local staging development.

2

Replace the Endpoint URL in Your Config

Locate your application's remove.bg client configuration. Change the base URL:

config.env (or your HTTP client URL)
- REMOVEBG_ENDPOINT="https://api.remove.bg/v1.0/removebg"
+ REMOVEBG_ENDPOINT="https://backgroundremoverapi.com/v1.0/removebg"
3

Run Your Test Suite

Execute your existing test cases. Because response headers (X-Width, X-Height, X-Credits-Charged) and image streams are identical, your assertions will pass without modifications.

# Test with cURL
curl -H "X-Api-Key: YOUR_KEY" -F "[email protected]" https://backgroundremoverapi.com/v1.0/removebg -o result.png

Frequently Asked Migration Questions

What happens to my unused remove.bg credits?

According to official announcements, unused credits do not automatically transfer to Leonardo.Ai tokens. We recommend exhausting your remaining balance before December 1, 2026, while running our endpoint in canary mode.

Are there any parameter differences?

No. Standard parameters including image_file, image_url, size, and format are supported natively.

Ready to migrate your pipeline?

Test our endpoint with your production images in real time using our interactive benchmark studio.