remove.bg stops being a standalone product on 1 December 2026 at 09:00 CET. The website and accounts are gone, the self-service API stops accepting requests, unused pay-as-you-go credits expire, and the Photoshop plugin and the other integrations are discontinued. Background removal is not disappearing — it moves into Canva, and the API moves to Leonardo.Ai — but the thing you built your workflow around does.
If you remove a background once a week, this is a fifteen-minute job. If your product calls the API, it is a week of testing: new credentials, a lower standard rate limit, and a different billing model.
The short version
- The site and accounts close on 1 December, 09:00 CET. Subscriptions end on their own; annual plans get unused time refunded pro rata.
- Pay-as-you-go credits expire with no refund. Spend them first. Export your invoices and credit usage report while you still can download them.
- The API moves to Leonardo.Ai. Your remove.bg credentials do not carry over, so you create an account and a new key.
- The standard rate limit drops from 500 images per minute to 100, and billing changes from one credit per image to a USD credit balance that varies by capability.
- On Canva, Background Remover is paid-plan only: up to 50 images per folder, one folder at a time; free users get a limited number of HD downloads.
What ends, and what you should do about it
remove.bg has been part of Canva since 2021. Its homepage, pricing page and FAQ all carry the same banner: the standalone site is gone after 1 December. What matters is which row you are in.
| If you… | On 1 December | Do this before then |
|---|---|---|
| Use the site now and then | Canva’s Background Remover, paid plans only | Use the free HD trial, then decide on a plan |
| Pay monthly | Ends; a final renewal on or after 1 November is free | Cancel earlier if you want it to stop sooner |
| Pay annually | Ends; unused time refunded pro rata | Nothing to do; check the refund arrives |
| Hold pay-as-you-go credits | Expire, no refund | Spend the balance on the backlog you keep postponing |
| Call the self-service API | Stops accepting requests | Open a Leonardo.Ai account, issue a new key, retest |
| Use the plugin or another integration | Discontinued | Photoshop, Figma and PowerPoint have their own remover |
The twenty-minute version for everyone else
Most people do not need a project plan. They need to stop losing things that cannot be recovered afterwards.
- Export the paperwork. Invoices and the credit usage report are downloadable from the account page today and not after the shutdown. If you expense this tool, do it now.
- Spend the credits. Run every half-finished product shot, headshot and thumbnail through while the account works. Future-you will not remember the credits were about to vanish.
- Test a replacement on your hard images. Every remover looks clever on a clean studio photo. Test the three that break them: hair, transparent or mesh fabric, and a product edge against a similar-coloured background.
- Keep private images local if that matters. Several browser-based removers that run the model on your machine, with no upload, launched on Show HN this month. For client material under an NDA, on-device processing is the difference between usable and not.
- Update your own instructions. Bookmarks, the checklist in your notes app, the “how we prepare images” line in a client document. A dead link in your own process costs more than the tool did.
If your product calls the API, this is the real work
The endpoint move is the small part. Start by finding every place you talk to it, because abandoned call sites are how you discover a problem three weeks after launch.
# every call site in the repo
grep -rn "api.remove.bg" . --include="*.js" --include="*.php" --include="*.py"
# credentials and config that must move, not the code around them
grep -rn "REMOVE_BG\|removebg" . --include="*.env*" --include="*.yml" --include="*.json"
Then work through the differences that will actually break something:
- New account, new key. remove.bg credentials do not carry over. The change belongs in configuration, not logic, which is why the endpoint and key should live in one adapter function and one config value.
- Rate limit. remove.bg allows up to 500 images per minute; Leonardo’s standard limit is 100, with higher limits on request. A batch job that fired everything at once will now start returning errors, so add a queue and backoff before you notice it in production.
- Billing shape. One remove.bg credit meant one image. Leonardo bills in USD from a prepaid balance, and the rate depends on which capability you call. If you resell image processing at a fixed price, redo that arithmetic.
- Plan coverage. Background removal is not included in Leonardo’s unlimited web plans, and API access is separate from the web subscription. A web plan is not a substitute for API credits.
- What does not change. Both APIs are synchronous, both accept a file upload or an image URL, and neither stores your images. That part of your code stays as it is.
What this teaches anyone running a free tool
The obvious lesson is that a free tool you do not control can end on a date you do not choose. The useful lesson is about where the demand goes when it does.
When a tool this well known closes, search demand for “remove.bg alternative” does not trickle — it spikes, with a deadline attached. The pages that win it are not listicles with eleven logos. They answer the dated questions: what ends on which day, what happens to my credits, which replacement does bulk, what breaks in my integration. remove.bg’s notice is a banner; the specifics are spread across an FAQ, a help-centre article, a vendor post and a terms update. Someone has to put them on one page with dates, and that someone can be a small site.
Which is the honest version of the strategy: publish the thing only you will bother to publish. A single-person site cannot beat a platform on features or on price, but it can be the clearest page on the internet about one dated change, and it can keep it current. That is also what keeps a page worth linking to after the deadline passes — the migration is over, the record stays.
Two cautions. The gap is real but crowded: this shutdown has already produced a wave of alternative pages from free browser removers, many of them decent, some of them thin. If your page is the same list as everyone else’s, you are not filling the gap, you are adding to the noise. And do not let one vendor own your product. One function that takes an image and returns a cutout, an endpoint in configuration, a tested fallback, and a note of the date on which your provider could disappear.
The five checks I would run this week
- List every tool in my stack that depends on a single third-party API, and note which ones I could not replace in a day.
- For each one, does the endpoint live in configuration or scattered through the code?
- Does each have a tested second option — not a bookmark, a tested option?
- Do I have a page that answers “this tool is closing” for my own niche before the news hits? The deadline is the best traffic a small site gets for free.
- Is there a path that removes the dependency entirely? For background removal that is on-device processing; for other tools it may be a script I run locally.
So do the boring part today: open the account page, export the invoices and the usage report, spend the credits on the backlog, and pick your replacement before 1 December rather than the morning you need it. If you run a small site, write the migration page while the searches are happening. Judge it with a clear head: Google’s November core update is still rolling out, so the week you publish is not a fair baseline, and the queries are worth checking in Search Console rather than guessing.
The tools that end on a schedule are also a reminder of the opposite: a page you publish on your own domain does not send you a shutdown notice.

Leave a Reply