remove.bg shutdown

LassoCut guide: remove.bg shuts down on 1 December 2026

The standalone remove.bg service closes on 1 December 2026 (website and accounts at 09:00 CET). The self-service API stops accepting requests from 1 December 2026, and the plugins are discontinued on 1 December 2026.

Dates and Enterprise contracts (which continue): remove.bg FAQ, read on 27 September 2026. Reported in early September 2026 (Bitvoxy, 3 September 2026).

This page sums up what the official remove.bg FAQ and Leonardo.Ai's migration guide say, with a link to the source for each point, and what you can do before the date.

Updated on 27 September 2026.

What stops, and when

All dates below come from the remove.bg FAQ.

Part of remove.bgWhat happensDate
Website and accountsNo longer available; background removal moves to Canva1 Dec 2026, 09:00 CET
Self-service APIStops accepting requests; API access moves to Leonardo.Ai1 Dec 2026
Enterprise API contractsNot affected, continue as normalNo change
Photoshop pluginNo longer availableAfter 1 Dec 2026
Other plugins and integrationsDiscontinued1 Dec 2026

Where the FAQ points people instead:

  • Single images and bulk batches: background removal inside Canva.
  • Larger volumes and automated use: Leonardo.Ai's APIs. Canva owns both.
  • Photoshop users: Affinity. The FAQ notes that its background removal runs on Canva AI and needs a Canva Pro subscription.
  • Other plugins: the apps in Canva's App Marketplace.

Your credits and subscriptions

What the remove.bg FAQ says, by type of plan:

  • Pay-as-you-go credits: unused credits expire on 1 December 2026. The FAQ recommends using them before that date.
  • Annual subscriptions: they work until 1 December 2026 at 09:00 CET, then end without further charges. Unused time after that date is refunded pro rata to the original payment method, with nothing to do.
  • Monthly subscriptions: they work until the same date and then end. A final renewal on or after 1 November 2026 is free. You can also cancel earlier from the remove.bg dashboard.
  • Invoices and usage reports: export them from your remove.bg Account page before 1 December 2026. The FAQ says they cannot be downloaded afterwards.

Neither the remove.bg FAQ nor Leonardo's migration guide mentions moving remove.bg credits to Leonardo. remove.bg credits cannot be used on LassoCut either.

The API moves to Leonardo.Ai

For self-service API customers, the FAQ points to Leonardo.Ai, also part of Canva, and says its API uses the same background-removal technology. Leonardo's own migration guide (read on 27 September 2026) lists what changes for existing code:

  • Endpoint: POST https://cloud.leonardo.ai/api/rest/v2/generationssync instead of /v1.0/removebg.
  • Authentication: Authorization: Bearer instead of the X-Api-Key header.
  • Requests: JSON only, with no multipart upload. The input image goes under guidances (a URL or base64).
  • Parameters: size, type, bg_color, crop, crop_margin, scale, position and channels are kept, inside a JSON parameters object.
  • Not supported: format=zip, format=auto, bg_image_file and raw image bytes in the response, which is always JSON (a URL or base64).
  • Headers: the cost is in a cost object in the body instead of X-Credits-Charged.
  • Storage: results are kept in your Leonardo library unless you set "ephemeral": true.

Leonardo.Ai charges $0.1047 per image for background removal, according to the same guide.

LassoCut sells credit packs with no subscription: the pricing page compares the cost of 1,000 to 100,000 images.

The compatibility table on the migration guide compares the remove.bg API, LassoCut and Leonardo.Ai parameter by parameter.

What to do before 1 December

  1. Export your invoices and usage reports from your remove.bg Account page.
  2. Use your remaining pay-as-you-go credits, since unused ones expire on 1 December.
  3. List what calls the remove.bg API: your own code, libraries, the command-line tool, plugins and automations (Zapier, Make, n8n).
  4. Choose where each one goes and test it on a sample of your own images before switching production traffic.

LassoCut is compatible with the remove.bg API: change the base URL and the key, and existing requests keep working. The migration guide has before/after code, and the platforms page lists the LassoCut plugins and integrations for Photoshop, Figma, WordPress, Zapier, Make, n8n and GIMP.

Questions

Is remove.bg really shutting down?

Yes. According to the remove.bg FAQ, the standalone website is no longer available from 1 December 2026 at 09:00 CET, and the self-service API stops accepting requests from that date. The closure was reported in early September 2026 (Bitvoxy, 3 September 2026).

Do my remove.bg credits expire?

Unused pay-as-you-go credits expire on 1 December 2026, according to the remove.bg FAQ, which recommends using them before then. The FAQ does not mention a refund for them.

Will I get a refund on my subscription?

Annual plans get a pro-rata refund for unused time after 1 December 2026, with no action needed. For monthly plans, a final renewal on or after 1 November 2026 is free. Source: remove.bg FAQ.

Does the remove.bg Enterprise API stop too?

No. The remove.bg FAQ says Enterprise API contracts are not affected and continue as normal. Only the self-service API stops.

What happens to the Photoshop plugin and other integrations?

The remove.bg Photoshop plugin is no longer available after 1 December 2026, and the other plugins and integrations are discontinued on that date (remove.bg FAQ). LassoCut has its own plugins and integrations for Photoshop, Figma, WordPress, Zapier, Make, n8n and GIMP: see the platforms page.

Do I have to rewrite my API code?

For Leonardo.Ai, yes: its migration guide uses a different endpoint, a Bearer token and JSON-only requests. With LassoCut, you change the base URL and the key, and existing requests keep working with the same paths and parameters. See the migration guide.