Replace the remove.bg command-line tool
The remove.bg CLI calls the remove.bg API, which closes on 1 December 2026. The lassocut CLI is a drop-in replacement: same flags, same -removebg file names, same behaviour on folders. Your scripts only need a new command name and a new key.
1. Install it
Needs Node.js 18 or later. One file, no dependencies.
npm install -g lassocut-cli
Or run it once without installing: npx lassocut-cli photo.jpg.
2. Get a key
Sign in with GitHub or Google in your account and create a key. Every account gets 50 free previews per month.
export LASSOCUT_API_KEY=your-key
If your environment already sets REMOVE_BG_API_KEY, the CLI reads it too: put your lassocut key in it and nothing else changes. --api-key also works.
3. Change the command name
- removebg --size full --output-directory out/ photos/*.jpg + lassocut --size full --output-directory out/ photos/*.jpg
In a shell script with many calls, an alias is enough: alias removebg=lassocut.
Flags
| Flag | Status | Notes |
|---|---|---|
--api-key | Same | Or LASSOCUT_API_KEY, or REMOVE_BG_API_KEY |
--size, --type, --format, --channels | Same | Same values as the API |
--bg-color, --bg-image-file | Same | |
--output-directory | Same | Results keep the -removebg suffix |
--reprocess-existing | Same | Without it, images already done are skipped |
--confirm-batch-over | Same | Asks before a large batch |
--extra-api-option | Same | Any other API parameter |
--api-url, --output-suffix, --concurrency | New | Default concurrency is 4; 429 and 503 answers are retried automatically |
Full list: lassocut --help, or the source on github.com/jaupin94/lassocut-cli (MIT licence).
Questions
Is it a copy of the remove.bg CLI?
No. It is written from scratch by lassocut and only follows the same flags, so your scripts keep working.
Can I keep calling remove.bg with it?
Yes, until the API closes: --api-url https://api.remove.bg/v1.0. Handy to compare results on your own images.
No Node.js on the machine?
Use the batch tool in the browser, or call the API directly with curl as shown in the API migration guide.