Product images / MERCHANT WORKFLOW
Should You Remove a Product-Photo Prop Together With Its Reflection and Shadow?
Use Photoshop's Remove related elements workflow when the unwanted object has associated visual effects that should disappear with it. Adobe documents removal of related shadows, reflections, smoke, steam, and similar effects. However, the tool cannot independently certify which reflection belongs to a styling prop rather than the product. Preserve the original photograph and review the resulting new layer against the actual product.
Decide which visual effects belong to the unwanted object
A prop can leave more evidence than its visible silhouette. A red styling cube beside a chrome bottle may cast a red reflection onto the bottle and a separate shadow across the tabletop. Removing only the cube can leave those effects behind, producing a photograph with an unexplained colored patch or shadow.
Adobe's Remove objects and related elements instructions document an option designed to remove an object and associated effects. The documented procedure uses the Remove tool, Generative AI on, Cloud generative AI processing, and Remove related elements. The operator draws a loop around the object and applies the removal. Adobe states that the edit is created on a new layer.
This mechanism differs from Content-Aware Fill with protected sampling. That guide addresses removing a stand while keeping the product's contact shadow. Here, the editing request explicitly includes some related effects, while other effects must remain.
| Visible feature | Ownership question | Proposed treatment |
|---|---|---|
| Red styling cube | Is it merchandise? | Remove if decorative and unwanted |
| Red reflection caused by cube | Would it exist without the cube? | Candidate for related removal |
| Bottle's base contact shadow | Does it describe real grounding? | Preserve |
| Chrome highlight from studio lighting | Does it describe the material? | Preserve unless independently approved for change |
Understand the processing and credit boundary
Adobe currently instructs the operator to select Cloud generative AI processing for Remove related elements. The feature uses generative credits. Its optional Enhance operation consumes additional credits according to output-image size; Adobe documents 10 credits for images up to 25 megapixels and 20 credits for images from 25 to 67 megapixels.
Those numbers concern the documented Enhance operation, not a universal price for every Photoshop removal. Inspect the current account's entitlement and any displayed cost before using a credit-consuming operation.
Adobe describes an optional Enhance step for refining the removal. Its Contextual Task Bar availability is tied to images at least 2K × 2K. The presence of Enhance does not guarantee that a chrome reflection will be physically accurate after reconstruction.
Before submitting, retain the untouched photograph, identify the prop's approximate reflection and shadow regions, and mark the product features that must remain. The selection gesture targets the object; the tool's related-effects processing may change a wider area. That broader change is precisely why a source comparison is necessary.
Hypothetical chrome-bottle cleanup
Hypothetical CartVisual editorial exercise. No Photoshop removal or credit-consuming operation was performed. Fictional source CHROME-BOTTLE-R7.jpg shows one chrome bottle, a red decorative cube at its right, a red reflection on the bottle's lower-right side, and the bottle's own dark contact shadow.
The requested product photograph is CHROME-BOTTLE-CLEAN-C01. The approved source facts are a narrow silver cap, an uninterrupted chrome body, and a single bottle resting on a pale tabletop.
| Region | Required result | Failure response |
|---|---|---|
| Red cube | Absent | Repeat or refine the object-removal request |
| Cube-caused red reflection | Absent if source ownership is established | Review a separate localized correction |
| Bottle contact shadow | Continuous and source-consistent | Reject if erased or invented |
| Silver cap and label | Unchanged | Reject product alteration |
The exercise assumes the merchant has determined that the cube is not included in the sale. It does not assume that Photoshop will automatically identify every reflection correctly.
Choose the next edit from the observed defect
If the cube disappears but a distinct red reflection remains, inspect whether the reflection is genuinely associated with the removed prop. A targeted follow-up edit may be appropriate. Do not remove every warm highlight from the chrome surface merely because one red object was removed.
If the cube and reflection disappear but the bottle's contact shadow is also erased, reject the result. Return to the original source and consider a narrower operation or a different photograph. An image that appears cleaner but makes the bottle float has not met the product brief.
If the bottle label, cap, or silhouette changes, treat that as a merchandise-identity failure. A generated correction is not evidence of the physical product's geometry.
If the operator cannot use the documented cloud processing or credit-consuming workflow, do not describe ordinary local removal as an equivalent implementation of Remove related elements. Evaluate a separately documented retouching route with its own limits.
Keep the original and the proposed correction as distinct files. CartVisual can help prepare creative product scenes, but the described related-elements control belongs to Photoshop and is not a CartVisual integration.
Use the example with your own product records
The filled records are hypothetical editorial examples. The entry-template row is for your own files, settings and observations; it does not connect to another application.
| Source | Region | Effect owner | Requested change | Preserve | Proposed output | Actual observation | Next action |
|---|---|---|---|---|---|---|---|
| CHROME-BOTTLE-R7 | Red cube | Decorative prop | Remove | Bottle silhouette | CHROME-BOTTLE-CLEAN-C01 | Not generated | Inspect object disappearance |
| CHROME-BOTTLE-R7 | Lower-right red reflection | Prop, hypothetical | Remove related effect | Chrome curvature | CHROME-BOTTLE-CLEAN-C01 | Not generated | Compare against source |
| CHROME-BOTTLE-R7 | Base contact shadow | Product | No removal | Grounding | CHROME-BOTTLE-CLEAN-C01 | Not generated | Reject if shadow disappears |
What the sources establish
- Adobe Photoshop — Remove objects and related elements: Primary procedure, related-effect scope, new-layer result, cloud processing requirement, generative credits, and Enhance conditions.
- Adobe Photoshop — Remove objects from images: Documents the general Remove tool and its distinct processing modes; does not establish equivalent behavior for Remove related elements.
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.
- Adobe Photoshop — Remove objects and related elements · Review date not separately recorded
- Adobe Photoshop — Remove objects from images · Review date not separately recorded
Frequently asked questions
Does Remove related elements always know which shadow belongs to a prop?
No. Adobe documents the capability to remove related effects, but the merchant must review whether legitimate product shadows and reflections were preserved.
Can I use the same related-elements workflow entirely on-device?
The cited Adobe procedure specifically requires Cloud generative AI processing. Photoshop's separate on-device Remove tool option does not establish an on-device equivalent for this feature.
YOUR NEXT CAMPAIGN
Create assets from a clear source
Bring your reviewed source photo or brand brief to CartVisual. Check the current tools, account access and credits before generating, then compare every result with your source.
Create a CartVisual account Open the workspace Check access and credits