For a quick web cutout, keep your original, upload a supported image and inspect the free preview. For an integration, validate a new API key, endpoint and request contract separately. Your remove.bg account, credit balance and key are not imported into RemoveBGTool.
1. Keep your originals and finished work
Save the source photo as well as any cutout you still use. A transparent export cannot reveal pixels that were already removed, and a small preview is not a substitute for a higher-resolution original. Keep originals separate from new tests so an export never silently overwrites your only copy.
For remove.bg invoices, subscription details or existing credits, consult your account and the official FAQ. This independent guide cannot transfer balances, cancel the old service or promise refunds.
2. Choose the output, not just a familiar button
Use a transparent PNG when the cutout will be placed in several designs. Use the white-background workflow when you need a white image, and the background changer when you already have a replacement scene. Make that choice before judging edges: a halo may be visible on one background and hidden on another.
The web editor accepts JPG, PNG, WebP and BMP, up to 3 MB per image. Keep a copy of a larger original when preparing an upload. Do not assume a competitor’s upload limit or output setting applies here.
3. Test the difficult images you actually use
Try a portrait, a pale product and any image with fine gaps or thin edges that is representative of your work. Review the result on light and dark backgrounds, then use erase and restore only where needed. A polished demonstration is not evidence that every image will behave the same way.
The comparison checklist below separates visual quality from file size and workflow. Record what needed correction rather than giving the whole tool a single unsupported accuracy score.
4. Check preview size before paying
Uploading, editing and a watermark-free PNG preview up to 0.25 MP are free in the web editor. A full processed-size download requires an account and 1 credit. The output is not advertised as an upscale of the source, and “full processed size” should not be read as a guarantee that every provider returns the original dimensions.
Inspect the preview first. Check the available output dimensions and the current purchase options before using paid downloads for a large collection. API-enabled plans and API billing have their own rules; do not infer them from the web download button.
5. Plan how you will handle several photos
The existing browser workflow accepts multiple images for sequential processing and individual downloads. It is useful when you want to inspect each result, but it is not an unattended production queue or an automatic ZIP exporter.
For a repeated catalog workflow, test whether the manual review and download steps fit your volume. Teams needing automation should evaluate the API separately rather than expecting the browser tool to be a desktop-plugin replacement.
6. Keep API migration separate from browser editing
An API integration needs a new RemoveBGTool key and an endpoint change, but that is only the beginning. Some request fields and output formats differ; the current API rejects unsupported options instead of silently claiming full compatibility.
Use the developer migration guide for parameter mapping, error handling, billing checks and a small controlled rollout. Keep the previous route available only while that provider still supports your contract; do not assume an old endpoint will remain a permanent fallback.
What to compare in your own test
This is a testing checklist, not a claim that we have measured a winner. Use images you own or have permission to process.
| Test image or workflow | Inspect | Decision |
|---|---|---|
| Portrait with fine hair | Check wisps and gaps against both white and dark backgrounds. | Use the restore brush for missing visible strands; do not expect recovery of detail absent from the source. |
| Product with a pale edge | Inspect labels, white packaging and holes in handles. | Choose the required final background, then review the actual exported file. |
| Several images | Check per-image upload limits, order and the download workflow. | Browser processing is sequential with individual downloads, not a one-click ZIP export. |
| Full-size download | Compare the file dimensions with the original and the free preview. | Full processed size costs 1 credit and does not promise upscaling. |
Questions before switching
Can I bring my remove.bg credits with me?
No. RemoveBGTool is a separate service and does not import remove.bg accounts, balances or API keys. Check remove.bg’s official pages for the treatment of your existing credits.
Do I need a Canva account to use this editor?
No Canva account is required. The free web preview does not require a RemoveBGTool account either; a paid full processed-size download does.
Will the replacement produce exactly the same cutout?
Do not assume identical masks across providers. Compare representative images, especially hair, pale edges and narrow gaps, before switching a production workflow.
Official sources and scope
The FAQ confirms the move into Canva. The API page names December 1, 2026 and Leonardo.Ai. These are distinct statements: this guide does not claim a separately verified website shutdown time, subscription refund policy or credit-expiry rule. Recheck the linked official pages for account-specific instructions.
Choose your next step
Try a free background-removal preview →Website preview: up to 0.25 MP free. Full processed-size download: account + 1 credit. No upscaling is promised.
Independent service; not affiliated with remove.bg or Canva. Existing accounts, credits and API keys do not transfer to RemoveBGTool.