remove.bg to shut down its website and self-service API on December 1
remove.bg’s website and self-service API will shut down on December 1, 2026. Users are being directed to Canva and Leonardo.Ai; unused credits will expire.
remove.bg will shut down its website and self-service API on December 1, 2026, at 9:00 CET, according to APIC STUDIO’s developer writing on DEV.to. Website users are being directed to Canva’s Background Remover, while API users are being directed to Leonardo.Ai. Unused pay-as-you-go credits will expire, and the Photoshop plugin and other integrations will stop working.
How to test a remove.bg replacement
When choosing a new tool, the quality of the cutout isn’t the only thing that matters. You also need to know whether the original photo leaves your browser, whether the output retains its resolution, and what it takes to download the result. Free processing isn’t much use if all you get is a thumbnail or you have to sign up to download a transparent PNG.
The author suggests a quick test for any candidate. Open DevTools → Network, clear the request log, add a photo, and remove its background. Check whether a request containing image data appears. Then download the file, compare its pixel dimensions with the original, and count the steps it took to get a finished PNG. That lets you test how the service behaves in normal use, rather than relying on the promises on its website.
Look at the manual edge-refinement tools, too: hair and translucent fabric may need touching up. Check for watermarks, limits on free uses, per-image charges, and mandatory subscriptions. One test photo is better for this than a batch of images you already need to publish.
The author’s browser-based tool: capabilities and caveats
The author applies this test to his own product, APIC STUDIO. His assessment should be read with that interest in mind: this is not an independent comparison of services. He says background removal happens in the browser without uploading the photo itself. On first use, though, the model has to download: about 5 MB for Lite, 44 MB for Fast, or 176 MB for Maximum. It is cached after that.
Object segmentation is handled by a model running through ONNX Runtime Web. It uses WebAssembly and, where available, WebGPU. The tool then cleans small defects from the mask, refines the edges against the photo at its original resolution, and reduces color fringing around hair. The author says the result isn’t simply a downscaled version of the original. Mistakes can be corrected with a Restore/Erase brush, and the background can be replaced.
Performance depends on the device. The first run takes longer because the model has to download; an older phone will be slower than a cloud GPU; and fine hair or transparent fabric may need manual work. On devices with limited memory, the Remove Object feature has a restricted working area.
You can edit without an account, but exporting requires a free Google sign-in. According to the author, there are no credits, paid plans, or watermarks. He also lists resizing for social media formats, compression to a target file size, and batch export as a ZIP among the additional features. When choosing a replacement, testing the operation you need is more useful than being impressed by the number of buttons.
What website owners and developers should do
Before December 1, finish any work you still have in remove.bg and use up your remaining credits. Then check your automations: calls to the service may be in Zapier, scripts, and plugins, not just your website code. Searching the repository won’t necessarily find them. Automations that call remove.bg will stop working when the API shuts down.
Next, separate your use cases. For manually processing individual photos, the browser-tool test above is a good starting point. If background removal is built into an API-driven processing workflow, you need a tool designed for that. The author points to Leonardo.Ai as remove.bg’s successor for API use and says plainly that his own product is not intended for production pipelines. A browser-based editor may be convenient for a person, but it cannot replace API calls.
My take: find the dependencies first
I wouldn’t choose a replacement from a list of “best alternatives,” especially when its author is showcasing his own product. At least that interest is disclosed here, as is the Google sign-in requirement for exporting. Checking Network is useful, but you’ll still need to judge the output quality using your own photos and the device you normally work on.
If you only have a few images, a local tool may be more convenient than connecting a new API. If your workflow depends on the API, a collection of features in another tab won’t restore it. I’d first find every call to remove.bg—including those hidden outside the repository—and only then compare how cleanly the alternatives cut out hair.
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.
technical architect
I design platforms and periodically clean up after “the simplest solution.” I respect CMSs, as long as nobody makes them pretend to be a distributed system.
All posts by the authorRelated articles
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.
Blog Author Drops Next.js and Scores 100 in Every Lighthouse Category
Bloffy’s creator replaced Next.js with Hono for the public-facing blog and scored 100 in every Lighthouse category. Here’s why caching and image optimization weren’t enough.
Adaptive Dark Mode arrives in Safari 27.3 beta for light-themed sites
WebKit has added Adaptive Dark Mode to Safari 27.3 beta. When users choose it, the browser adapts light-themed sites for dark mode. Here’s what site owners should check.
Discussion 4
Azamat Toktosunov
On a small image-upload feature I built, we tested replacements by checking the Network tab and comparing the downloaded PNG dimensions, not just the preview. One candidate looked fine in the browser but returned a reduced-size image unless we used a paid tier, so the thumbnail test would have missed the main issue. I’d also check whether the tool has a stable API before wiring it into a site; swapping a background remover later is more work once its output and billing assumptions are baked into the flow.
Elchin O.
Did you also verify whether the candidate’s API returns full-resolution output on the same plan as the browser tool?
Jan K. Post author
Not in the same run yet; I’d compare the API and browser output dimensions on the same plan, since a polished preview can hide a paid-tier cap.
Ali Jafarov
Could you include whether the API and browser tool preserve the original image dimensions on the same plan? That seems like an easy detail to miss when comparing previews.