Cutmatte

The remove.bg API shuts down on 1 December 2026

remove.bg is moving into Canva. Its standalone website and self-serve API close on 1 December 2026. If your shop, app or script calls api.remove.bg, those calls stop working that day.

What is known

What happens to your integration

Requests to https://api.remove.bg/v1.0/removebg and /v1.0/account will fail. That includes the npm package remove.bg, the PyPI package removebg, remove.bg's command-line tool, and plugins for shops and CMSs that call the API for you.

Your options

  1. Rewrite for Leonardo.Ai. The successor remove.bg recommends. It has its own requests and keys, so plan for code changes and testing.
  2. Switch to a compatible API. Services such as Cutmatte accept remove.bg's requests unchanged: same endpoints, parameters, response formats, headers and error codes. You change the base URL and the key.
  3. Run a model yourself. Open models such as BiRefNet (MIT licence) do good cut-outs, but you build and run the API, the GPU servers and the edge cases yourself.

Keep your code: Cutmatte

See how to migrateGet a free API key

Checklist before 1 December

  1. Find every call to api.remove.bg: code, environment variables, CI secrets, Zapier or n8n flows, shop plugins.
  2. Use or record your remaining remove.bg credits. A screenshot of the balance is enough for our free credits.
  3. Download invoices and usage reports from your remove.bg account while you can still sign in.
  4. Point one environment at the new API and run your usual images through it before you switch production.

Cutmatte is not affiliated with remove.bg, Canva or Leonardo.Ai. Facts about remove.bg come from the sources linked above; last checked 21 November 2026.