Migrating off the remove.bg API: a field-by-field compatibility audit
TL;DR The remove.bg standalone site — and its self-serve API — retires on 1 December 2026, 9:00 CET . The official landing spot for API users, Leonardo.Ai, is a capable platform but not a drop-in replacement: it means async jobs, polling loops, presigned S3 URLs and JSON image payloads where you currently have one synchronous function call. This post is the field-by-field audit I did while wiring…
The remove.bg standalone site and self-serve API are set to retire on December 1, 2026, at 9:00 AM CET. The official landing spot for API users, Leonardo.Ai, offers a platform but is not a drop-in replacement for the existing API. This post provides a field-by-field audit of the compatibility between the two APIs, revealing which request parameters behave identically, which are silently ignored, and how your error handling might be affected.
Half of the parameters have full support, while others are accepted without any action. Parameters such as image_file, image_file_b64, image_url, type, and bg_color are either fully supported or silently ignored. The binary PNG response body, X-Width, X-Height, X-Credits-Charged, and X-Processing-Time-Ms headers remain fully supported, aiding in server-disclosed timing and billing reconciliation.
Error handling varies between the two APIs. The new Leonardo.Ai platform uses a specific error body shape, while the existing API allows for more flexibility. This difference can lead to issues in error handling and retry logic. HTTP status codes remain consistent, but the code strings used to represent errors differ. Monitoring these codes is crucial to ensure proper functionality after migration.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
