remove.bg to shut down its standalone site on December 1; APIC creator offers a browser-based alternative

The standalone remove.bg site will close on December 1, 2026. Background removal is moving to Canva, while API users are being directed to Leonardo.ai. APIC Web’s creator offers a browser-based alternative.

· 5 min read · 4 comments

The standalone remove.bg site will shut down on December 1, 2026, at 9:00 a.m. Central European Time, APIC Web developer Akhouri Anmol Kumar writes in a DEV.to article. Background removal is moving to Canva, while API users are being directed to Leonardo.ai. Anyone who relies on the feature should test another tool ahead of time; API users should check the migration terms. Kumar offers his own browser-based editor, which he says does not upload photos to a server.

What’s changing for remove.bg users

It’s the standalone site that’s closing, not the background removal feature itself: it will be available with a Canva Pro subscription. The article’s author points to a notice on remove.bg’s pricing page. For API users, he identifies a different destination: Leonardo.ai, where they are being moved to new pricing terms.

Free access to remove.bg never meant free full-resolution exports. Without paying, users could download a preview-resolution result; full-resolution images required credits. The article gives a ballpark price of around $9 a month for 40 images. So the change affects more than people who are used to keeping the site bookmarked: teams that regularly need finished files will have to rethink their workflow.

The article does not explain what will happen to existing credits or previously prepared files after the site closes. It offers no basis for assuming they will automatically appear in Canva or Leonardo.ai.

How APIC Web works

APIC Web is the article author’s own project. According to his description, models are downloaded in the browser, cached and run on the user’s device via WebAssembly. An internet connection is needed for the initial download, but the photos themselves, Kumar says, are not sent to a server. The article provides no independent verification of that claim: the account of how the service works comes from its developer.

The editor is said to export full-resolution transparent PNG and WebP files, with edge refinement and color-fringe removal. The author writes that APIC Web has no credits, watermarks or paid plans. No account is needed to edit, export or batch-download files as a ZIP. Google sign-in is optional; it is there for the community counter and update emails.

There are three modes for different hardware. Light requires an initial model download of about 5 MB and is intended for phones. Fast is about 44 MB for everyday tasks; Maximum is about 176 MB and is recommended for computers. Local processing does not mean working entirely without an internet connection: the browser still has to download the model first.

APIC’s features go beyond background removal. The author lists object removal, 2× or 4× image upscaling, color correction, resizing, compression to a target file size and batch processing. It also claims to offer color-setting exports as .cube LUT files and templates for 15 social platforms. A separate Windows app is available and, according to the developer, works offline. This is a list of features from the announcement, not a guarantee that they will run equally fast on phones and computers.

What to check in your workflow

If background removal is part of preparing product images, banners or social media assets, start by working out how many files the team processes at once. APIC offers batch processing with ZIP downloads and no account, but the processing happens on the user’s device. For a large volume of images, processing time on work computers and phones becomes part of the tool decision.

Before December 1, you can run a few typical and a few difficult images through APIC. Compare edge quality and color fringing, make sure the result saves at the resolution you need, and time a batch. For client assets you would rather not send to a third-party server, the stated approach to file processing matters in its own right; with sensitive images, a claim in an announcement is no substitute for verification.

Developers with a remove.bg integration have a different set of questions. The author describes APIC as a browser-based editor and a Windows app, but does not claim they can replace the API. The move to Leonardo.ai and its pricing should therefore be assessed separately from the choice of a tool for editing images manually.

My take: changing a button is easier than changing a habit

I like the idea of an editor that doesn’t demand an account just to produce one transparent PNG. When you’re building your first websites, little tasks like that pile up without you noticing, and paying a subscription for a single button feels slightly comical. Batch downloads sound more useful to me than another showcase of effects: process the files, grab the ZIP, get back to the design.

But I wouldn’t move the whole workflow on the strength of one announcement. I’d test tricky edges on both a phone and a computer first, then check the speed across a batch of files. Local processing seems like a reasonable trade-off: less reliance on server-side processing, but more work for your own device. Free is nice; nicer still if you don’t have to rescue the cutout by hand on every screen.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. remove.bg Is Shutting Down — Here's a Free, No-Upload Alternative dev.to

About the author

Rūta from Kaunas

Aspiring web designer

I’m building my first websites for my portfolio while learning not to turn every screen into a showcase of effects. So far, I mostly design for people I know and argue with myself about button sizes.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. On a small site I maintain, we replaced a background-removal API call with a browser-side tool after the pricing changed; it took longer to check export quality and permissions than to swap the button.

    1. Was the browser-based option usable without uploading files, or did privacy checks rule it out?

      1. @yernur.khol i’ve tried a browser-side background remover on a little project of mine, and keeping the image local was the main appeal — though i still had to check what the tool does with exports and permissions, because “runs in the browser” isn’t a complete privacy policy. i’m still learning this stuff, but that check took longer than the code change, naturally.

        1. The other practical check is who on the team will handle the new workflow. In a small learning center, if staff need to prepare images between classes, a local browser tool is only useful if exports are predictable and the steps are simple enough to repeat without extra help.