Blog · Comparisons · September 24, 2026

I Switched Off remove.bg Before the Shutdown. Here's Why

remove.bg shuts down December 1, 2026. I migrated early. Here is the one question that matters when picking a replacement, plus my honest checklist.

In September 2026, remove.bg announced it was shutting down on December 1, 2026. I'd been using it for years — the tab was practically bookmarked into my muscle memory. Upload, wait three seconds, download, done.

Instead of waiting for the deadline, I migrated early. This is the honest story of how that went, including the part where I almost picked the wrong replacement, and the one question that actually matters when you're choosing where your workflow lives next.

What actually happened

The short version: remove.bg announced that its standalone site closes on December 1, 2026. Web users are being pointed toward Canva; API users toward Leonardo.Ai. Both are owned by Canva, which bought remove.bg. If you want the full timeline of how the shutdown unfolded, we've got it covered in our remove.bg shutdown timeline, and the shutdown announcement breakdown has the details that matter for regular users.

I'm not here to eulogize it. remove.bg was a genuinely good tool — fast, accurate, dead simple. That's exactly why its shutdown stings: when something that simple disappears, you realize how much of your workflow was balanced on it.

Why I didn't just follow them to Canva

The official guidance says web users should head to Canva. I tried. Here's my problem: I didn't want a design suite. I wanted a one-click cutout.

Canva's background remover is a feature buried inside an editor, and it requires a Pro subscription. So the "migration path" is: start paying monthly, open a design tool, and hunt for the feature that used to be a website. That's not a migration. That's a different product wearing my old tool's name.

Nothing against Canva — it's excellent at what it's built for. But if your workflow was "remove background, download PNG, get on with my day," being told to adopt an entire design platform feels like being told your favorite screwdriver is now only available inside a $200 toolkit.

This is the pattern worth noticing, by the way. Standalone tools keep getting absorbed into platforms. Adobe did the same thing moving background removal into Firefly. Every time it happens, the simple thing you relied on becomes a line item in someone else's subscription bundle. Which is exactly why the replacement you pick now should be chosen carefully — you don't want to do this migration twice.

The mistake I almost made

After rejecting Canva, I did what everyone does: I googled "remove.bg alternative" and clicked the result with the nicest landing page. Big friendly headline. "Free." "No watermark." "AI-powered." I was thirty seconds from making it my new default.

Then I actually read the pricing page. The free tier gave me a handful of credits, the downloads were capped at a resolution too small for real work, and the full version cost more per month than I'd ever paid remove.bg. The landing page wasn't lying, exactly — it was just describing the free tier the way a timeshare describes the free weekend.

That's when the real question clicked for me. It isn't "is it free." Every tool says it's free. The question is: where's the wall, and will I hit it on a normal Tuesday?

Every background remover has a wall. Some put it at the download button — process all you want, but the full-resolution file costs credits. Some put it at the resolution — free downloads come out at 625 pixels wide, which looks fine in the preview and falls apart everywhere else. Some let you do exactly one image before demanding an account. Some watermark the free tier, which isn't a free tier, it's an ad for the paid tier.

Knowing where the wall is, before you rebuild your workflow around the tool, is the entire decision. Everything else is decoration.

My checklist before switching

Once I started asking "where's the wall," picking a replacement got much easier. Here's what I actually checked, in order:

1. No account required. I'd spent years with remove.bg never knowing my name, and I liked it that way. An account means my uploads get tied to my identity, my work gets a paper trail, and someday there's a pricing email. Pass.

2. Full-resolution downloads on the free tier. This eliminated most of the field immediately. A cutout you can't actually use isn't free — it's a demo. I test this with a real photo, not the site's demo image, because demo images are chosen to make the tool look good.

3. No watermark. Non-negotiable. A watermarked "free" download is just a paid product with extra steps.

4. Batch processing. I don't need it every day, but when I need twenty product shots cut out, I need it badly. Single-image-only tools turn a ten-minute job into an hour of clicking.

5. Privacy. After years of uploading photos to remove.bg's servers without thinking about it, the shutdown made me think about it. Where do my photos go? Who keeps copies? I wanted the answer to be "nowhere," which meant a tool that processes on my device instead of a server.

That last one is what landed me where I am. Most alternatives I tested failed at least two items on this list. Usually the resolution cap got them, or the account wall.

Where Deback fits, and where it honestly doesn't

Full disclosure: I work on Deback. So take the recommendation with the appropriate grain of salt — but also know that I picked this checklist before I picked the tool, and the checklist is the part I'd defend to anyone.

Deback passes all five: no account, full-resolution transparent PNGs, no watermark, batch up to 20 photos per run, and everything runs in your browser on your device — your photos never touch a server. That last point is the architectural reason the rest is possible: no server GPUs to pay for means no credits to sell you.

Now the honest part — where it doesn't fit:

If you're a developer with remove.bg's API in your pipeline, Deback isn't your answer. It's a website, not an API. You need a real programmatic replacement, and our API migration guide walks through the actual options without pretending a browser tab can replace an endpoint.

If you want templates, backgrounds, and design around the cutout, Canva or PhotoRoom are genuinely better at that. Deback is a cutout tool. It makes clean transparent PNGs and gets out of your way. It doesn't pretend to be a design studio, and I'd rather tell you that than have you discover it mid-project.

If you need huge batch volumes — hundreds of images on a schedule — you probably want a paid API with SLAs, not any free web tool. Free tools are for humans clicking buttons, not for pipelines.

If you're migrating too, do this before December 1

Whatever you switch to, don't leave the remove.bg side of the move until the last minute. A few practical things:

• Download your past results. Anything sitting in a remove.bg library or history should be on your own drive before December.
• Export invoices. If you paid for credits or a subscription, grab your receipts for taxes now while the dashboard still exists.
• Use up paid credits. If the shutdown terms say anything about refunds or credit conversion, read them — and don't assume unused credits transfer anywhere.
• Test the replacement on your actual photos. Not the demo images. Your product shots, your lighting, your edge cases. Hair, fur, glass, and busy backgrounds are where tools differ, and you want to find out before you're on a deadline.
• Screenshot your settings. If you had default output formats or API keys configured, document them while you can still see them.

Our remove.bg alternative hub has the fuller comparison if you're still weighing options, and the credits explainer covers what we know about the paid side of the shutdown.

Frequently asked questions

When exactly does remove.bg shut down?

December 1, 2026. The standalone site closes and users are directed to Canva (web) and Leonardo.Ai (API).

What happens to my unused credits?

Honestly: remove.bg hasn't said publicly, as far as I've seen. Don't assume they transfer to Canva or Leonardo, and don't assume a refund. Check your account page and their announcements directly — anyone stating the answer confidently right now is guessing.

Do I have to move to Leonardo.Ai?

No. That's remove.bg's suggestion for API users, not a requirement. You're free to pick any tool, and for non-developers Leonardo.Ai is probably overkill — it's an AI platform, not a one-click cutout.

Is there a free replacement with no sign-up?

Yes — that's exactly the checklist above. No account, full-resolution downloads, no watermark. If a tool fails any of those three, keep looking.

What if I used the remove.bg API in my app or store?

You need a programmatic replacement, not a website. Start with our API migration guide — it covers the real options and what to test before December.

Can I process many images at once without paying?

Deback's batch mode handles up to 20 photos per run, free, no account. If you need hundreds on a schedule, that's API territory — see above.

I migrated in September and haven't thought about it since, which is exactly what you want from a tool like this. Pick the replacement with no wall in your way, test it on your real work, and get back to whatever you were actually doing. Try it at getdeback.com if my checklist matches yours.