LassoCut for n8n: remove image backgrounds

What happens to remove.bg workflows on 1 December

Any n8n workflow that calls api.remove.bg, directly with an HTTP Request node or through a community node, stops returning results on 1 December 2026, when remove.bg's self-service API stops accepting requests (announced in early September 2026). There is no official n8n node for remove.bg, so every workflow that uses it is a custom HTTP call that needs the same two changes described below. See the shutdown guide for every date and source.

Switch to LassoCut in 3 steps

1. Install the LassoCut community node, or keep your existing HTTP Request node.
2. Create a LassoCut credential (a key from your account), or update the URL and the X-Api-Key header.
3. Run the workflow the same way as before; the output fields keep the same names.

Option A: the LassoCut node

1. The node is verified by n8n. On n8n Cloud, search for LassoCut in the nodes panel. On self-hosted n8n, open Settings → Community nodes → Install and enter n8n-nodes-lassocut.
2. Add the LassoCut node to your workflow (search for remove background) and choose Remove Background.
3. Create the LassoCut API credential with a key from your account.
4. Set Input to a binary file from a previous node, or to an image URL.

The node returns the cut-out as a binary file (field data by default, named <name>-removebg.png) with credits_charged, width, height and detected_type in the JSON. Options: size, subject type, format, background colour, crop to subject, crop margin. Errors are readable, and Continue On Fail works per item.

Ready-made workflows in the n8n template library:

• Remove WooCommerce product image backgrounds with LassoCut: new products get a white-background main image, the original stays in the gallery, and products already processed are skipped.
• Remove Google Drive photo backgrounds and log results to Google Sheets: photos dropped in a Drive folder are cut out into another folder, originals are moved to a done or failed folder, and each photo gets a row in a Google Sheet with its links and credits.

Source: github.com/jaupin94/n8n-nodes-lassocut (MIT), published on npm with provenance.

Option B: keep your HTTP Request node

If your workflow calls the API with an HTTP Request node, change the URL and the key. Everything else stays: the image_file or image_url field, the options, and Response Format: File.

- URL: https://api.remove.bg/v1.0/removebg
+ URL: https://api.lassocut.com/v1.0/removebg
- Header X-Api-Key: your remove.bg key
+ Header X-Api-Key: your LassoCut key

If you want the image itself, send Accept: image/* or no Accept header at all: with Accept: application/json the API answers JSON with the image in base64, exactly like remove.bg.

Marketplace presets and cast shadow

From node version 0.2.0, the options of the Remove Background operation include Preset (Amazon, eBay, Etsy, Shopify, Zalando or Instagram), Shadow (None or Cast Shadow), Light Direction, Shadow Length and Shadow Strength. With a preset, the node returns a .jpg framed to that marketplace's image rules, and the Format, Background Colour and Crop options are ignored. Zalando allows no shadow. See marketplace presets.

Error messages

Both options surface the API's JSON error body, {"errors":[{"title": "…"}]}. What each title means and what to do:

Questions