Remove.bg is shutting down: what it means for your pipeline

Remove.bg shuts down its standalone website and self-serve API on December 1, 2026, at 9:00 a.m. CET. Background removal moves into Canva, and API access moves to Leonardo.ai, which Canva also owns. From that moment, the self-serve API stops accepting requests, so every remove.bg API key stops working and unused pay-as-you-go credits expire.

On one login, that's a five-minute problem. Across a business, it's an inventory problem first and a purchasing decision second. A developer wired the API into the product pipeline. Someone in marketing connected it through Zapier. A storefront app calls it behind the scenes. Two colleagues have personal logins with credits on them.

So the question isn't which background remover is best. It's how many places yours is running right now. This guide covers where to look, what breaks on the day, what to save from your accounts, and how to test a replacement before the deadline.

This guide is for teams running an image pipeline or a shared image workflow. If you're a solo seller moving one account, read our seller switching guide instead.

Where remove.bg runs, and what happens to each on December 1

Remove.bg was never just an API. It shipped a Photoshop plugin, desktop and Android apps, design plugins, and apps on automation platforms like Zapier and Make. Remove.bg says its Photoshop plugin and its "other integrations and plugins" are discontinued on December 1. Any of these can live in your business without showing up in a code repository.

The dangerous rows are the ones nobody notices. A refused request in monitored code is the best case, because someone sees it. A Zapier API Request step marked successful, or a job that runs once a quarter, can push an unprocessed image into your catalog with no warning.

How to find every remove.bg dependency

1. Search code and config for X-Api-Key and api.remove.bg. Go beyond the main product repo: infrastructure config, scripts, serverless functions and environment variables.

2. Count keys, not accounts. One remove.bg account can hold up to 10 API keys, so a single account can stand for several teams or workflows. Map each key to its owner and what it does.

3. Check finance records. Look for remove.bg on invoices, card statements and expense reports. It's common to find more than one login, including personal sign-ups paid on company or team cards.

4. Check automation, creative and commerce tools. Look in Zapier, Make, Photoshop, Figma, Sketch, Adobe Creative Cloud, Shopify and Lightspeed.

5. Ask the teams that touch product images. That means merchandising, creative, photography, content operations and agencies. Don't stop at "do you use remove.bg?" Ask whether they have an account, an API key, a plugin, an automation or a subscription.

What happens to your credits, subscriptions and account data

From remove.bg's FAQ:

For every login you found:

• Record the plan type and the credit balance. Spend pay-as-you-go credits you can use before December 1.

• Download invoices and the credit usage report.

• Export any processed images you still need.

• List which API keys exist and which systems use them.

Three tests a replacement must pass

A replacement can produce a great cutout on one image and still be a poor production dependency. Test it on these three things before it goes live.

1. Edge quality on your hardest products

Average catalog images won't tell you much. Test the categories that have always caused trouble: reflective packaging, fine mesh, transparent bottles, dark products on dark backgrounds, hair and fine detail, and low-resolution supplier images.

Score each category separately. A 98% overall pass rate isn't reassuring if the 2% that fail are all in your highest-value category. Set a pass threshold per category, run the same images through remove.bg and the replacement while you still can, and decide which categories still need manual review.

2. A price that still works at your real volume

Price your actual volume, not an average month. Include peak months, the largest batch you run, retries and reprocessing, and every pipeline that calls the API.

What remove.bg charges today, per image, on monthly billing:

Yearly billing is about 10% lower ($0.065 an image at 75,000). Pay-as-you-go costs more: from $1.00 an image for 3 credits down to $0.21 for 8,000 credits ($1,699).

How we got these figures: read from remove.bg's pricing page on October 29, 2026. Cost per image is the plan price divided by its credits, at one credit per image.

A pipeline that processes 50,000 images in a seasonal refresh and 5,000 the next month needs a different plan from one that runs 50,000 every month. Model a full year, then model your peak month on its own.

Weighing Leonardo.ai against Photoroom at your volume? See the full cost comparison in Leonardo.Ai vs Photoroom.

3. A change small enough to ship before the deadline

The replacement has to fit how you operate: keys and permissions, usage reporting by team, monitoring and logging, and support. Ask three questions:

• Can you tell which request failed, which application sent it, and whether it hit ten images or ten thousand?

• Can you split usage and cost by team?

• Can you rotate keys without taking the pipeline down?

Then test the move itself. Run the replacement next to remove.bg on a small slice of production traffic. Compare outputs and failure rates, and check that downstream systems behave before you switch everything over. Keep the change small enough to roll back before December 1.

What to do this week, by mid-November, and before December 1

Three tips:

• Start finding now. Monthly and quarterly jobs only show up when they run. If time gets tight, shorten testing, not finding.

• Sort calls into standard and unusual. Standard calls can move quickly. Anything using less common parameters needs its own test.

• Leave buffer. Aim to finish by November 27, so a failed switch still has a day or two to roll back before 9:00 a.m. CET on December 1.

Moving to Photoroom

For the full tool shortlist, see our remove.bg alternatives and best background removers for e‑commerce.

Where Photoroom fits. Photoroom's Remove Background API takes the same argument names as remove.bg and returns the same response format. image_file, crop, bg_color, format and size carry over. A standard call moves by changing two things: the endpoint (api.remove.bg/v1.0/removebg becomes sdk.photoroom.com/v1/segment) and the API key. The code is on our developer migration page.

Before you switch, check two things:

• Less common parameters. The standard background-removal call moves as is. Test anything else on your own images first.

• A remove.bg Enterprise API contract. remove.bg says those continue as normal, so you can plan the move on your own timeline.

If you need more than cutouts. Photoroom's Image Editing API (Plus plan) adds AI Relighting, AI Expand, AI Ironing, Ghost Mannequin and Flat Lay to the same pipeline, at $0.10 an image whatever edits a call combines.

Testing on your own images. New API accounts get 10 free production calls without a watermark. A sandbox key adds watermarked test calls for checking output. Both are for testing, not for production volume.

To weigh the two products in detail, see Photoroom vs remove.bg.

Migrate the pipeline, not just the endpoint

Treat December 1 as a forced pipeline audit. Find every place remove.bg is called, name an owner for each, know what happens when it stops, save your account records, and test the replacement on your real workload before you switch.