ItemlumePRODUCT CREATIVE / PRODUCTION AND HANDOFF
Why Does Claid Enlarge My Product After Clipping Away the Background?
Claid background clipping and final resizing are separate decisions. Its API documentation says that with clipping enabled, crop or unspecified fit and no width or height, the clipped image is scaled to the input dimensions. To keep the clipped region unchanged, it documents bounds with both dimensions unspecified.
Locate the size change in the processing chain
A tightly bounded cutout and an object preserved at its original pixel scale are different deliverables. Removing empty background can leave fewer pixels around an object, while a later resize can enlarge that remaining content. Before blaming the cutout detector, record both the clipping decision and final-size instructions.
Inspect the complete settings submitted by your connector, including defaults that it may add. A user-facing label such as automatic size does not establish which fit value reached the API. Preserve the source and examine the actual downloaded result rather than a browser preview that fits every file into one box.
Choose between a clipped asset and a normalized canvas
For the documented unchanged-region branch, bounds is paired with omitted width and height. Merely changing the fit label while retaining explicit dimensions does not reproduce that condition. Conversely, a normalized catalog canvas may deliberately require a later scaling operation.
Tell the integration maintainer which output you need. Do not remove all resizing globally because one asset needs its native clipped size; other placements may depend on the existing output contract. This article describes an external API behavior and does not execute or configure an Itemlume connection.
| Required deliverable | Decision to inspect | Acceptance observation |
|---|---|---|
| Tightly bounded cutout at retained pixel scale | Clipping plus bounds; width and height omitted | Actual cutout dimensions and product scale |
| Product standardized for an agreed canvas | Explicit documented sizing workflow | Canvas dimensions and product landmarks together |
Illustrative exercise: the bottle grew after clipping
Illustrative exercise: a fictional 1600 by 1600 source contains a bottle occupying a much smaller foreground region. The team requests a tightly bounded reusable cutout, but its connector keeps the default crop behavior with no target dimensions. This is a planning example, not a measured Claid response.
Ask the maintainer to compare the documented fit branches on an authorized copy while leaving the product source unchanged. Record the returned pixel dimensions and apparent bottle scale for each result. Do not predict an exact cutout width: foreground detection and the actual source determine the retained region.
Accept the output at its intended downstream scale
If the correct cutout is delivered but looks too large only inside a layout, inspect that layout separately. If the file itself was scaled, retain its processing record and correct the intended sizing branch. Neither observation proves the product shape or label survived accurately.
Keep the clipped source, final output and placement requirement distinct in the handoff. This prevents the next designer from undoing an intentional catalog normalization or treating an enlarged cutout as newly captured product detail.
Illustrative exercise: clipped region and final-size contract
These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.
| Fictional task | Required size behavior | Settings to inspect | Record after evaluation |
|---|---|---|---|
| Reusable bottle cutout | Keep clipped region unchanged | Clipping, bounds, omitted dimensions | Actual dimensions and product boundaries |
| Catalog-ready bottle image | Use agreed final canvas | Separate explicit sizing requirements | Canvas size, object scale and label accuracy |
Sources and further reading
Recorded source-review dates are listed individually below. An undated source does not inherit the article’s publication date. Software and platform rules can change; check the current original before acting.
- Background operations — Claid API · Reviewed
Frequently asked questions
Is clipping alone a promise that the returned file keeps the retained pixels at the same scale?
No. The documentation makes the final canvas depend on resizing. Review the fit and dimensions together.
Will clearing a virtual canvas offset undo this rescaling?
No. Position metadata and image resampling are different operations. Diagnose the actual file and processing chain.
PREPARE ASSETS FOR YOUR NEXT STEP
Create supporting product assets in Itemlume.
Create new product creative assets in the workspace, then continue in your chosen tools. Third-party software procedures described in this guide take place in those applications; this workspace link does not imply an integration. Check current capabilities, account access and credit quotes.
Explore asset creation tools Check pricing and credits