Migrate from remove.bg with a clear plan.

01 · EXISTING WORK

Export the files you cannot recreate quickly.

• ✓
  List the important assets.

  Start with product listings, campaign files, profile images and transparent overlays that are still in use.

• ✓
  Download the finished PNGs.

  Do not rely on an account or credit balance being available after the published expiry time.

• ✓
  Keep the originals.

  Store the source image beside the cutout and preserve the filename or internal asset ID.

• ✓
  Check the edge.

  Open a sample on a light and dark background so you know which assets are ready to ship.

Credit expiry is a reason to make an inventory, not a reason to download every possible variation. Keep what has a real job and leave the rest as source material.

02 · CREDITS AND BILLING

Separate credits from subscriptions.

The current remove.bg pricing page says credits expire on December 1, 2026 at 9:00 AM CET. That is the operational fact to plan around. It does not answer every question about refunds, subscriptions or account transfer, so use the current account and support channels for those cases.

Record the balance and renewal state for any account that matters to your workflow. If a team shares a process, record who owns the account and where the downloaded assets should live. A migration is easier when the person who can access the old work is known before the deadline.

03 · CONSUMER WORKFLOW

Decide whether you want the suite or the single task.

Canva is the destination remove.bg names for the consumer background-removal experience. It is the sensible choice if the next step is a design: add the cutout to a presentation, post, page or template and continue editing there.

A standalone-style remover is the better fit when the next step is already decided elsewhere. You do not need a new design canvas for a product image that is going straight into a shop, or a portrait that is going into an existing layout. The fewer decisions between upload and download can be the point.

04 · DEVELOPER PATH

Leonardo.Ai is a migration, not a drop-in clone.

remove.bg’s API documentation directs developers to Leonardo.Ai from December 1, 2026. Leonardo’s official migration guide documents the changes: a new endpoint, Bearer authentication, JSON instead of the old multipart or JSON shape, an explicit remove-bg model and a different response structure.

Plan a real integration change. Update secrets handling, request construction, error handling, response parsing, test fixtures and result storage. Leonardo’s guide also notes differences in input limits, output formats, URL storage and cost reporting. Test the exact options your product uses before switching production traffic.

PoeysiaPRO Cutout is not the answer to this developer path. It has no public API, no API keys and no enterprise surface. It is a simple web alternative for people who want to remove a background manually.

05 · SIMPLE WEB PATH

Use Cutout when there is no integration to migrate.

PoeysiaPRO Cutout is designed for the everyday case: choose a JPG, PNG or WebP in your browser, remove the background on your device, inspect the transparent preview and download a PNG. Your original is not uploaded to PoeysiaPRO.

The free preview works without an account. Sign in with a free PoeysiaPRO account when you need the full-size download path on supported devices. If the image is part of a larger content job, continue with Carousel Composer for a branded set or Clips for a video-first workflow.

06 · THE HANDOFF

Test the new path with one real asset.

Pick a representative image rather than a perfect demo. Check the edges, dimensions, file format, download behavior and where the asset goes next. For an API, run the same test through the new endpoint and compare the actual response your software consumes.

Once the test works, write down the new owner, URL, account and storage location. The best migration document is short enough to use when the next person has to repeat the job.