Image background removal and classification

Which feed images Renable processes, how background removal and image categorization work, and how to correct the result. Also covers when to use Product image and when to use Image link.

Updated November 18, 2026

Renable can process the images in your product feeds in two ways: categorize them (sort each one into Product, Lifestyle, Information and so on) and remove their backgrounds. You decide which images get processed, per catalog and, with a rule, per product. An image that isn't processed is still in your feed: Image link and Additional image link always carry the feed's own images.

Feed images and processed images#

A product has two kinds of image, and they behave differently:

Feed imageProcessed image
What it isYour own image, at its place in your product feedA feed image that went through the catalog's Image processing settings or a Process images rule
PlaceholdersImage link for the main one, Additional image link for the others, for every productProduct image, Lifestyle image and the other category placeholders
In a channel fieldThe image's address as your feed lists it, from the moment the product is imported. Whatever your store's server sends for that address is what the destination gets.The image Renable prepared
In a template or promptRenable's own copy, which shows once Renable has fetched itThe image Renable prepared
Image cardNone. You can't approve, reject, categorize or tag it or make it primary, and nothing you do to a processed image changes it.Yes, on the product and on the project's Content page. Approve, reject, category, tags and primary act on it.

To send an image Renable prepared (background removed, cropped), bind a channel field to Product image with Image link as its fallback, so it reads "Product image, else Image link". A field bound to Image link alone always sends your own image, whatever Renable does to it elsewhere.

On a product's page, Product feed entries lists its feed images, read-only, under each catalog. The Media section shows its processed images, plus images you uploaded, images a prompt generated and images included from another catalog.

Which images are processed#

A catalog's settings decide. An image is processed when either of these holds:

  • Categorize images is on. Every image is then processed, because categorizing needs to look at all of them.
  • A background-removal step applies to it as a product image: a step whose Use for content types includes Product, or is left empty. A step set to Only apply this step to the main image covers only the main image.

So with Categorize images off and no steps, none of the catalog's images are processed. With it off and a main-image-only step, only each product's main image is.

An image that isn't processed uses no credits, has no image card and doesn't appear on the project's Content page. Product image and the other category placeholders stay empty for it, and it still reaches your channels through Image link and Additional image link.

If you change the settings so that an image stops being processed, it leaves the product's processed images after you publish. Your work on it is kept: a corrected category or a rejection comes back if the image is processed again later. An approval comes back only if the image is processed to the same result as before; otherwise it shows as unapproved.

Product image or Image link#

Product image and the other category placeholders show only images that went through your processing. They don't promise a transparent cutout: the background is removed only if a step removed it.

When a product has no processed image of the kind a placeholder asks for, that placeholder is empty. You can handle that in two ways:

  • Fall back to the feed's image. Add a fallback to the placeholder (the ⋮ menu, then Add fallback) and choose Image link, so it reads "Product image, else Image link". This works in templates and prompts as well as channel fields. The fallback also applies when you rejected the processed image or it's filed under another category, because rejecting a processed image doesn't remove the feed's original. See Placeholders.
  • Adapt the template. Give the image element a fallback element laid out for products without a processed image, or set it to hide when its content is missing. An automation whose condition is Product image is blank can also change the design for those products, for example to hide a background shape. See Automations.

Without either, an empty placeholder is missing content, and the channel treats the product the way its rules say. On a Meta or TikTok channel, for example, the built-in Status rule archives it. See Channel rules. Renable also says why a placeholder came up empty: see Why an image placeholder is empty.

Background removal#

You set up background removal on the catalog's Settings tab, under Image processing, as an ordered list of steps. Each step picks a model version, the content categories it applies to, whether it runs on the main image only, whether to crop, and an acceptable quality score. If a result scores below that, the image goes to the next step: for example, try v1 and fall back to v3 if the quality is too low.

A new catalog starts with one Make transparent (v3) step. With no steps, backgrounds aren't removed, and processed images stay as they came from the feed.

If no step scores high enough, Renable keeps the best result of all the steps and flags the image for review. Flagged content failed an automatic quality check. Approving it clears the flag. A flagged image is still used in your ads unless a placeholder is set to skip it: see Flagged content.

VersionBest forCost
v1Images with a clean, plain white background. Renable's original model.Fast and inexpensive
v2Almost anything. A premium third-party model and the highest quality option, but it can occasionally over-remove parts of product packaging or cartons.By far the most expensive
v3Colored or busy backgrounds, which it handles better than v1. The default for new catalogs.More than v1
v4-mediumRenable's newest model.About 1.4 times v3 per image

A step can also use No transparency, which skips background removal. The image is still cropped if the step's crop switch is on; with crop off as well, the step leaves the image as it came from the feed.

Removing the last step takes effect when you publish, after Renable asks you to confirm: backgrounds are no longer removed and images go back to their originals. With Categorize images off as well, the catalog's images aren't processed at all, and Product image is empty.

Different processing for different products#

The settings on the catalog are the default for every product in it. To process part of a catalog differently, such as the premium model on your best sellers, add a Process images rule on the catalog's Rules tab. Its dialog has the same two parts as the catalog's section: a Categorize images switch (on for a new rule) and the steps.

  • A rule replaces both parts for the products it matches. The catalog's own Categorize images switch no longer applies to them. Every other product keeps the default.
  • Categorize images on with no steps categorizes those products' images and removes no background.
  • With Categorize images off, a rule needs at least one step that applies to Product images, or it can't be saved.
  • If several rules set processing for the same product, the one lowest in the rule list wins.
  • A rule takes effect when you Publish, and only the products whose processing changed are processed again.

The same action is available inside a ruleset, so one decision can cover several catalogs.

Overriding the result manually#

On a specific product, open its image gallery and use Make transparent (v1 / v2 / v3 / v4-medium) on any image to force that version, whatever the catalog's steps chose. It doesn't work on an image that is only linked from another website. Each image also shows the model that produced it and an estimate, such as "Estimated background removal quality: 82%", to help you decide whether to override it.

To fix a batch, open the ⋯ menu on the project's Content page and use Make all images transparent (V1 / V2 / V3 / V4-MEDIUM) under Make transparent. It applies a version to every image shown and spends credits on each one. See Reviewing and approving content, and What uses my credits for the cost.

Image classification#

With Categorize images on, Renable sorts each image into one of three categories, so your templates and channels can target the right kind of shot:

  • Product: the item on a plain or neutral background.
  • Lifestyle: the item in a natural setting. Staged studio shots are sorted here too.
  • Information: badges, infographics and other non-product graphics.

To correct a category, or to use a finer one, use the category picker in the gallery, which offers Information, Product, Lifestyle, Staged and Feature. The Content page's bulk Change category action also offers Award and the text categories. You could mark a shot as Staged, for example, so the Staged image placeholder picks it instead of the general Lifestyle one. See Available placeholders.

With Categorize images off, the images a step processes aren't categorized: each counts as a Product image unless you've changed its category yourself. This suits a catalog whose feed only has product shots. A step that leaves Product out of Use for content types then runs only on images whose category you've changed.

Correcting a category fixes it across the whole project#

Many catalogs reuse one image on lots of products, such as a size guide or a brand banner. When you correct an image's category, every other product in the project showing that image gets the corrected category, and so do newly imported products with that image.

The image is also processed as if it had been classified that way from the start. Move it into a category your catalog makes transparent and its background is removed; move it out and it returns to the original picture. This happens at once on the image you corrected, and shortly after on the other products.

  • The image you corrected is approved for you, unless the new result is flagged. Copies on other products stay unapproved until you approve them.
  • A category you set directly on a product's image isn't changed by a correction made elsewhere.
  • An approved image isn't touched, because approval locks its category. To change one, change its category directly, or un-approve it and make the correction again: un-approving alone doesn't apply an earlier correction.

To undo a correction, correct the category again, anywhere in the project. The latest correction wins, and every automatically updated copy follows it.

To see every product that uses an image, open the image's ⋮ menu and choose Show all products with this image. The content view then lists those products with only that image on each, and bulk actions such as approve and change category apply to just these images. Clear the search box to go back. This works only for images from your feed, not for uploaded or AI-generated ones.

When does a change reach my images?#

Changes to the steps, Categorize images and the other settings on a catalog's Settings tab take effect when you Publish the catalog. They reach its products within minutes, without waiting for the next scheduled import. Images a changed step covers are processed again, approved ones included, and that spends credits: see What approving locks and What uses my credits. Images the change doesn't cover stay as they are and keep their approvals.

When a template or prompt first uses a feed image#

Templates and prompts use Renable's own copy of Image link and Additional image link. Renable keeps a copy of every image it processes, and fetches a copy of any other image the first time a template or prompt needs it. You don't need to do anything. A channel field bound to Image link never waits for this: it carries the address your feed lists.

  • A design in a channel waits for the image. Your live feed keeps its previous contents meanwhile. The channel's Preview tab fetches the image, shows the design's fallback or shows it as still being prepared, and fills in on its own. Trace only looks and fetches nothing, so until a preview or a run asks for the image it says "The image hasn't been fetched yet".
  • If the image hasn't arrived within an hour, the run publishes what's ready, as described in Publishing a channel. A design whose placeholder has a fallback goes out made with the fallback, with no warning. Without a fallback, the product goes out without that design for that run, like any other missing content, so on a Meta channel it goes out archived, and the channel shows a warning. A later run corrects the feed once the image arrives.
  • A prompt waits instead of skipping the product, and generates once the copy is there, usually within the hour after it arrives. A test in the prompt editor says "The image is being fetched so it can be used.", and a later test uses it.
  • If the image can't be fetched, the placeholder is empty. A design falls back if it has a fallback and is otherwise reported as missing content, and a prompt skips the product with the reason "The image could not be downloaded." Renable tries again automatically, and the design and the prompt update on their own when an attempt succeeds. If it keeps failing, see Product Images Won't Download.

A copy of an unprocessed image that no channel design or prompt has used for 45 days is removed, and fetched again the next time one needs it.

Related articles#