CartVisualCreate account

Why can Claid return a white background when I request transparency, and which output format should I specify?

Set Claid’s background color to transparent and output.format to png for an async cutout. The async reference defaults to JPEG, which cannot carry alpha, so omitting the format can produce a white background. The Background guide lists PNG, WebP, and AVIF as alpha-capable, while the async schema describes its transparent setting as PNG-only.

Published · By CartVisual editorial team

Treat background removal, background color and output format as separate controls

A reusable product cutout needs three things to agree: the background must be removed, the replacement background must be transparent, and the encoded result must retain alpha. A request containing only a transparent color instruction should not be treated as proof that the original background was removed.

Claid's Background documentation places removal and color in operations.background. The removal setting supports true, false and advanced objects; false is the documented default. For a straightforward product cutout, the documented combination is background removal with color set to transparent.

The Background page explains an important fallback: when transparent is requested with a format that does not support alpha, the background becomes white. This is a representation consequence, not evidence that the product was incorrectly selected.

If the destination actually needs a finished white-background photograph, request that color deliberately. If it needs a reusable foreground layer, do not approve an opaque white file merely because the product silhouette looks clean.

Resolve the documented format conflict before building the request

The Background operations guide lists PNG, WebP and AVIF as formats that can carry alpha. The async API reference describes its transparent background setting as PNG-only. Use the references below to confirm the separate scopes.

Specify PNG for an async cutout that must preserve alpha. If the receiving system requires WebP or AVIF, verify that exact endpoint and format before relying on it, or plan to convert the delivered PNG and check that the exported file still contains alpha.

The following fragment illustrates the documented request structure. It is not an executed API request, and the source address is intentionally invalid.

{
  "input": "https://assets.example.invalid/product.png",
  "operations": {
    "background": {
      "remove": true,
      "color": "transparent"
    }
  },
  "output": {
    "format": "png"
  }
}

Diagnose white output without repeating the wrong operation

Check removal, color, and encoding in the actual request. If removal was off, enable it. If color was transparent and the format was omitted or set to jpeg, set output.format to png. The async schema’s documented JPEG default makes omission an actionable cause of white output.

If an alpha-capable format was requested but the delivered file appears white, inspect its actual decoded format and transparency. A viewer's white background is not necessarily part of the pixels. Conversely, a file extension that supports alpha does not prove that the particular image contains useful transparency.

Keep the format decision separate from clipping and resize behavior. The existing Claid clipping guide addresses why a tightly cropped product can be enlarged by the resizing defaults; changing output format does not resolve that geometry problem.

Illustrative decision: one product for two different handoffs

A designer needs a transparent cutout of a ceramic dispenser for several campaign backgrounds. The proposed Claid async request removes the background, requests transparent color and explicitly selects PNG. The review condition is an actual file containing usable transparent areas around the dispenser.

A second deliverable is a finished white-background listing photograph. That request instead specifies a white background and uses the destination's accepted opaque format. It does not need to preserve alpha.

If the transparent request produces white pixels in a JPEG, the next action is to correct the output-format choice. If the PNG has valid alpha but loses the dispenser's narrow handle opening, the problem is the cutout rather than the format. Keep the source and both proposed deliverables separate.

Where CartVisual fits

CartVisual offers a separate browser-local cutout workflow with transparent and filled-background presentations. It does not implement Claid's API, output schema or alpha-format contract.

See the current CartVisual workflow and its limitations

Source and evidence scope

Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.

Claid: Background

Official source snapshot checked .

Claid: Async API Reference

Official source snapshot checked .

The Background operations guide documents the white fallback and names three formats with alpha. The async schema narrows its transparent setting to PNG. PNG is the common documented option. The example describes a proposed request and file checks.

Related decisions

Browse ecommerce creative workflows