Remove.bg Is Moving to Canva: What Changes in 2026
Remove.bg has confirmed that its background-removal functionality is moving into Canva. A separate transition moves API background removal to Leonardo.Ai on December 1, 2026. Here is what is confirmed, what is not, and how to choose your next workflow.
1. What is happening
Remove.bg’s official FAQ says the company is migrating its background-removal functionality into Canva, which has owned remove.bg since 2021. The wording matters: the announcement describes a product move into Canva. It does not say that the remove.bg website will definitively close on December 1.
According to the currently published information, users should expect the familiar capability to sit alongside Canva’s broader design tools. The final details of every user journey may still change, so check the vendor’s own pages before making a long-term workflow decision.
2. The API transition to Leonardo
The API path has a specific date. Remove.bg’s API page and Leonardo’s migration guide say background removal moves to Leonardo.Ai on December 1, 2026. Leonardo documents a synchronous endpoint intended for remove.bg migrations and an asynchronous option for larger pipelines.
For developers, this is not merely an endpoint rename. Authentication changes to a bearer token, requests become JSON, and results are returned as JSON rather than raw image bytes. Leonardo also recommends setting ephemeral: true when you do not want results saved to a Leonardo library.
3. What this means for remove.bg users
- Occasional users: decide whether a Canva-based workflow still feels direct enough for a one-step cutout.
- Teams: review account, privacy, and asset-management requirements before migrating stored workflows.
- API users: plan for the request, authentication, response, retry, and storage differences documented by Leonardo.
- Automation owners: benchmark output quality and total cost with your own image mix rather than relying on one vendor demo.
4. Canva and a standalone tool solve different jobs
Canva is useful when background removal is one step in a larger design process: layout, text, templates, collaboration, and publishing can all live together. A standalone background remover serves a narrower intent. You upload, create the cutout, and download it.
Neither shape is universally better. The right choice depends on whether the next action after removal happens inside an editor or outside it.
5. Remove.bg alternatives compared
| Option | Best fit | Important check |
|---|---|---|
| NoBGNow | A focused upload → remove → download workflow | Production engine, pricing, and output limits are still being evaluated |
| Canva | Background removal inside a wider design workflow | Confirm the account and export path that fits your use |
| Photoroom API | Developers who need a managed removal endpoint | Benchmark your image categories and expected monthly volume |
| Leonardo API | Remove.bg API migrations and broader creative pipelines | Update authentication, JSON requests, result handling, and storage settings |
| Browser-side model | Local processing and predictable infrastructure cost | Confirm model licence, download size, device support, and non-portrait quality |
6. How to choose the right alternative
- Collect representative portraits, logos, product photos, hair detail, and difficult edges.
- Score edge quality and failure cases before comparing average latency.
- Calculate cost at your expected volume, including retries and infrastructure.
- Review licence and image-retention terms.
- Count the user steps from upload to saved result.
If the last point is your priority, try the focused remove.bg alternative or go directly to the NoBGNow background remover.