remove.bg Shutdown Countdown: What to Do Before 1 December 2026

What is actually happening on 1 December 2026

On 1 December 2026 at 09:00 CET, the standalone remove.bg website closes. The background-removal feature itself does not vanish from the world: it moves inside Canva, which requires an account, and the self-serve API moves to Leonardo.Ai. What ends is the simple, standalone remove.bg website that many people have bookmarked for years.

That distinction decides what you need to do. One-off cutouts need a new manual tool — a free remove.bg alternative like BGone covers that. API users need a new integration on the official Leonardo.Ai path. Credit holders should check remove.bg's own terms and use credits on real work before the deadline.

The biggest risk is waiting. Migration always takes longer than expected: a replacement tool behaves slightly differently on tricky images, an API integration needs testing, and a team needs time to learn a new step.

The countdown: your week-by-week checklist

Counting from mid-October, you have roughly seven weeks. Each week below has one main job.

• Week 1 — 14 to 20 October: pick your alternative and test it on real images. Do not judge a replacement on a single easy photo. Run it on your five hardest real images: wispy hair, fur, glass, jewellery chains, and a busy product shot. Compare the results side by side with remove.bg while you still can. If the alternative handles your real work, commit to it this week.
• Week 2 — 21 to 27 October: move your everyday manual workflow. Bookmark the new tool, update any saved links or browser shortcuts, and use it for all new images from this week onward. If you work in a team, show everyone the new steps once, in a short walkthrough, so nobody is still opening remove.bg out of habit.
• Week 3 — 28 October to 3 November: use up credits on real work. If you hold remove.bg credits, spend them on images you genuinely need — back-catalogue product photos, profile pictures, or assets you have been postponing. Check remove.bg's own announcements for what happens to unused credits, and do not leave this to the last week.
• Week 4 — 4 to 10 November: move API and automated workflows. This is the week for developers and store owners. Move programmatic background removal to the official Leonardo.Ai path — see our API migration guide for the shape of that move. Test the new integration on real traffic, not just a single sample image, and keep a manual fallback ready for one-off images.
• Week 5 — 11 to 17 November: re-do your most important images. Rebuild the assets that matter most — best-selling product photos, homepage images, profile pictures — in the new tool. Check edges at full zoom, and re-export anything that looks rough. This is also the week to standardise: one background style, one framing habit, one filename pattern.
• Week 6 — 18 to 24 November: tell your team and update your docs. Tell clients, teammates, and any freelancers who touch your images that remove.bg closes next week. Update internal guides, onboarding notes, and any help-centre article that still points at remove.bg. Remove the old bookmark from shared machines so nobody discovers the shutdown mid-task.
• Final week — 25 November to 1 December: verify, then stop using remove.bg. Do a last check: open every workflow that once used remove.bg and confirm it now runs without it. Export or save anything you still need from your remove.bg account. Then stop. By 09:00 CET on 1 December, the standalone site closes, and your work should already be running somewhere else.

If you are starting late, do not try to follow the calendar day by day. Do the weeks in order, compressed: test the alternative today, move the manual workflow tomorrow, and give the API move the time it needs. The order matters more than the dates.

Manual users: the simplest switch

If you only ever used the remove.bg website by hand, the switch is small. BGone's Background Remover is free, needs no signup, adds no watermark, and processes images in your browser — so your photos never leave your device. Open the tool, upload one image, remove the background, and download a clean white or transparent version. The honest comparison with remove.bg, including where remove.bg's larger server models still win on tricky edges, is in our remove.bg vs BGone guide.

Two habits make the switch stick. First, judge the new tool on your real images, not on a demo photo — your product shots, your portraits, your trickiest edges. Second, change the bookmark. As long as remove.bg is still the easy click, it stays the default.

API and automation users: do not leave this to the final week

Manual users can switch in an afternoon. API users cannot. If an app, store, or script calls remove.bg automatically, that integration needs a new home before 1 December — and it needs testing under real conditions, not just a single successful test call.

• Move to the official path. The self-serve API moves to Leonardo.Ai. Start there, on Leonardo.Ai's own documentation, rather than trusting a third-party wrapper you have not vetted.
• Test with your real images. Run your hardest production images through the new integration — the ones with hair, fur, glass, and busy backgrounds — and compare the outputs against what remove.bg produced.
• Watch for edge cases. Check file sizes, formats, error handling, and what happens when an image fails. A migration that works on ten test images can still break on the eleventh.
• Keep a manual fallback. For one-off images, a free manual tool like BGone covers the gap while the integration is being finished. It has no API, so it is a fallback, not a replacement, for automation.

For the full shape of the API move, see our API migration guide and the general shutdown guide, which covers the broader checklist this countdown builds on.

Honest limits

• BGone processes one image at a time and has no API or bulk mode. It is a manual replacement for the remove.bg website, not for the remove.bg API.
• The in-browser model is smaller than remove.bg's server models. Always zoom in on tricky edges — hair, fur, glass — before using a result professionally.
• Credit and account questions are decided by remove.bg's own terms and announcements. Check them directly rather than assuming credits, history, or settings transfer automatically.

Related tools & guides