Check whether the upload is behaving as designed
A seller uploads a dozen approved catalog photos into Photoroom Batch and sees the original room or tabletop behind every item. That alone is not a failed cutout. Photoroom's October 2026 help explicitly describes original-background retention as the default on Web, iOS and Android. Older tutorials describe automatic cutouts at intake, so first establish which workflow version the operator expects.
Record the client, browser, batch identity, source file and intended outcome. A product photo with its original background is not necessarily a defective segmentation result: segmentation may not have been requested at all. Do not open every image to repair a nonexistent mask before inspecting the batch background setting.
Set the next Web batch deliberately
In the Web App, open a batch, select Background, and inspect Auto-remove background on upload. Check the box if new batches should start with removal; clear it if product backgrounds must remain. The documented default is off. The setting applies when the next batch is created. Changing it does not retroactively remove backgrounds from the batch currently open, including images subsequently added to that existing batch.
Photoroom stores the Web preference in the browser. A colleague using another browser or device, or a browser whose data was cleared, should not assume the previous operator's choice persists. The all-platform default is documented, but this particular preference procedure is for Web; do not invent equivalent mobile labels. The existing single-cutout exception guide begins after a removal has actually been attempted.
Use an intake-state decision matrix
| Observed intake | Diagnosis | Action | Release condition |
|---|---|---|---|
| New batch, originals remain | Default retention may be intended | Inspect Background setting | Record intended batch mode |
| Preference switched on in an existing batch | Not retroactive | Create a new batch for future intake or edit existing backgrounds separately | Do not claim current files were cut out |
| New browser, automatic removal absent | Browser-local preference may have reset | Inspect preference in that browser | Confirm before next intake |
| Removal was applied but one edge is damaged | Actual cutout defect | Isolate affected product | Review edge and merchandise |
Fictional two-batch handoff
In an illustrative kitchenware launch, BATCH-A contains six jars with their original countertops. The operator checks the Web preference, turns on automatic removal, and creates BATCH-B from separate approved source copies. The proposed expectation is that BATCH-B follows the newly chosen intake behavior; BATCH-A is not silently modified. No Photoroom batches were created in this exercise.
The merchant records which set is intended for white-background listing images and which set retains the lifestyle source. If a jar in the removal set loses its transparent rim, route that jar to an individual edge review; do not assume that the new intake preference repairs quality. For a different question about making backgrounds identical across products, see static background reuse.
Close on a verified state, not a remembered default
Before delivery, inspect an actual newly created batch and the resulting files. Record whether original backgrounds were kept, whether removal was deliberately requested, and whether each cutout preserves handles, labels, translucent parts and contact edges. Hold export when the operator cannot identify the active intake mode or has only inspected a setting without reviewing images. This is an external Photoroom workflow, not a CartVisual setting.