2026-09-20

Remove.bg's standalone site closes December 1, 2026 — what the move into Canva changes

Remove.bg's own FAQ page confirms the headline in four words — "remove.bg is moving to Canva" — and explains why: the company is "migrating remove.bg's background removal functionality into the Canva platform, where it'll sit alongside everything else Canva has to offer." What that page alone doesn't spell out is exactly when, or what happens to a paid plan or an API integration in the meantime. Multiple independent reports on the transition converge on the same specifics — Nero's coverage and PurgeBG's writeup both give the same cutoff, and Android Branch's report independently states the same closure date: the standalone remove.bg website stops working on December 1, 2026, at 9:00 AM CET, any paid or unused credits expire at that same moment, and the developer API moves to a separate Canva-owned company, Leonardo.Ai. If "remove background from a photo" has been a bookmark for you, here's what that migration actually changes — and what it never touched in the first place.

What's actually changing, fact by fact

remove.bg was already a Canva-owned product going into this — Canva acquired Kaleido AI, remove.bg's maker, back in 2021 — so this isn't a change of ownership. It's the step after that: folding a tool that used to work as its own standalone destination into the destination it was bought into, on a fixed calendar date rather than gradually.

This isn't hypothetical — someone already reacted to it

Within days of the announcement, a developer wrote up, in public, the exact reasoning that a move like this puts back on the table. In a post explaining why she built a browser-only alternative after seeing the shutdown notice, she names the mechanic directly: "most background removers (remove.bg included) upload your photo to their servers, run inference there, and send back the result." Her stated fix was to process the image "entirely in the browser using WebAssembly," so that, in her words, "your images never touch a server" — no signup wall, no credit system, no resolution cap tied to a paid tier. That's an independent developer's reaction to this specific news, not an argument this post is constructing after the fact; the shutdown notice made "does this tool need an account, and where does my photo actually go" a live question for real people this month, not a hypothetical one.

The tradeoff this migration exposes, not just a UI change

A cloud background remover's economics have always run through a server: someone's GPU has to load a model and run inference on every photo a visitor submits, and that compute costs the operator money per image, at scale. remove.bg's own product has priced around that reality for years — a free preview, with paid credits required to unlock a full-resolution download — because giving away unlimited full-resolution server-side processing for free was never the economics on offer. Moving the tool into Canva doesn't remove that underlying server cost; it just changes who operates the servers and what you now need — a Canva account — to reach them. The tradeoff was always structural, not a Canva-specific decision: any tool that processes your photo on someone else's computer has to recoup that computer's cost from someone, and an account plus a subscription is one of the more common ways to do that.

What NearBG does and doesn't do here

• No account, before or after this news. NearBG never asked for a sign-in to begin with, so there's no migration deadline, no expiring credits, and no new account wall to run into — not because of a policy decision made in response to remove.bg, but because there's no server behind it to gate access to.
• No per-image cost to recoup, so no resolution cap tied to a plan. The trade-off section above is specific to tools whose economics run through a server per image; NearBG's cutout runs on the visitor's own device, so there isn't a compute bill per photo driving a paid tier.
• Still one job, not a design suite. This is a real difference, not just a marketing angle: Canva is a full design platform with templates, layouts, and generative tools built in. NearBG does exactly one thing — isolate the subject of a photo from its background — and stops there. If you want to place that cutout onto a new background, a template, or a composed scene afterward, that's a separate step in a separate tool, same as every other post on this blog says.
• No batch mode, no API of its own to migrate. One photo at a time, run in the tab you're already in — there's no developer integration here to reroute the way remove.bg's API customers now have to reroute to Leonardo.Ai.

Honest summary

The facts here are sourced, not assumed: remove.bg's own FAQ confirms the migration into Canva, and independent reporting on the transition (Nero, PurgeBG, Android Branch, and a developer's own account of building an alternative in reaction to the news) converges on the same December 1, 2026, 9:00 AM CET cutoff, the same credit-expiry mechanic, and the same API move to Leonardo.Ai. None of that makes remove.bg's underlying tool worse at what it does, and switching tools isn't a requirement just because one changed hands administratively. What the news does surface, honestly, is the one question worth asking about any background remover, cloud or otherwise: where does the photo actually go while it's being processed, and what has to exist — an account, a credit balance, someone else's server — for you to get it back. For a tool that never sent the photo anywhere in the first place, that question has had the same answer the whole time.