What Remove.bg has officially confirmed
The official Remove.bg FAQ says Remove.bg became part of Canva in 2021 and that its background-removal functionality is now being migrated into the Canva platform. The wording matters: it confirms a product migration, but it does not justify inventing a more dramatic shutdown timeline beyond the dates Remove.bg publishes for specific products and credits.
The current pricing page states that credits expire on December 1, 2026 at 09:00 CET. If you have paid or unused credits, review the account and billing information early rather than waiting until the final day.
Developers have a separate path. The Remove.bg API documentation says that starting December 1, 2026, background removal moves to Leonardo.Ai, another Canva company. Teams should treat this as an integration migration: compare parameters, authentication, response formats, rate limits, billing, and output quality before changing production traffic.
What ordinary web users should do
Save finished assets and originals you still need. Review credit balances and subscription status. If your daily workflow depends on erase/restore brushes, bulk processing, a desktop application, or a particular maximum resolution, write those requirements down before choosing a replacement. “Removes a background” is not enough to prove that two tools fit the same job.
Canva is the most direct destination when a cutout is only the first step in a poster, presentation, product graphic, or social design. A focused alternative can be faster when you simply want a transparent PNG. Purgebg is built for that second case: open the free browser background remover, process one image locally, choose transparency or a solid color, and download without creating an account.
What developers should inventory now
List every endpoint, parameter, client library, callback, output format, and automation that currently relies on Remove.bg. Capture a representative image test set, including hair, fur, products, transparent objects, and busy scenes. A successful HTTP response is not a successful migration if the new mask changes the images your customers depend on.
Purgebg Phase 1 deliberately does not claim API compatibility. The current product is a private browser tool, not a drop-in server API. For hosted and developer options, use our Remove.bg alternatives comparison as a requirements checklist rather than accepting a one-size-fits-all ranking.
Why local browser processing is useful
Server tools can offer powerful models, batch queues, and APIs, but they require uploading an image. Browser processing trades some model and device constraints for a very clear privacy boundary. Purgebg downloads its Fast or Fine model, then performs inference on the device. It is a practical fit for sensitive drafts, quick portraits, and one-off product photos when no batch system is required.
A practical migration checklist before December 1
Start with ownership, not software. Download original images, finished transparent files, masks, invoices, and any records needed for accounting or licensing. Record the renewal date of an active subscription and the number of credits that remain. If several people share the workflow, assign one person to verify the official notices each month so a changed date or migration instruction is not missed.
Next, separate browser work from automated work. A person removing one background at a time can evaluate Canva, Purgebg, or another visual editor directly. A store, agency, or application calling the Remove.bg API needs a staged technical migration with representative inputs and a rollback plan. Do not route every production image to a replacement after testing only one portrait.
Finally, measure the downloaded result rather than the preview alone. Compare pixel dimensions, alpha edges, color fringing, hair and fur, processing time, and the steps required to correct a bad mask. Keep both the original and the accepted output until the transition is complete. This checklist remains useful even if Remove.bg publishes more detailed product timelines later.
Sources and update policy
This page was checked on September 5, 2026. Transition details can change. Before making billing or integration decisions, read the Remove.bg FAQ, pricing notice, and API migration documentation directly.