CartVisualCreate account

How should I create a Photoroom Web App batch from loose images, one folder, or nested product folders?

Choose the import method from the structure you already maintain: individual images for a deliberate mixed selection, one folder for a single flat set, and a parent folder for multiple product groups that should remain separated in the Batch Editor. This is an intake decision, not an editing or export rule. Confirm the resulting sections before applying shared changes.

Published · By CartVisual editorial team

Decide From Your Source Structure

Photoroom’s Web App offers three distinct intake paths: selecting individual images, importing one flat folder, or importing a parent folder containing sub-folders. The practical choice is whether your existing file organization carries information you still need during editing.

Use individual selection when the batch should combine files from different locations or storage sources. Use a single-folder import when every image belongs to one undivided working set. Use a hierarchy import when the sub-folder names represent meaningful groups such as products, colors, or launch collections.

This guide concerns how images enter the batch and how groups are represented in the editor. It does not decide whether backgrounds should be removed; that is controlled separately by the batch background setting.

Use Grouping As A Control Boundary

A flat import gives you one working pool. That is efficient when the same edit should apply across the entire set and there is no reason to distinguish subgroups. It becomes risky when later review, selection, or handoff depends on knowing which files belonged together.

A hierarchy import preserves the source folder relationship as editor sections: images from child folders are placed in the appropriate section. Treat those sections as review boundaries. Apply a common edit only when it genuinely belongs to every section; otherwise, select or review sections independently.

Do not infer unsupported behavior from the folder structure. The supplied documentation does not establish file-type restrictions, duplicate-file handling, ordering rules, maximum folder depth, or export naming. Record those as unknowns rather than making them part of the operating contract.

Verify The Batch State Before Editing

After import, confirm that the batch contains the intended files and that any expected sections appear. The official sequence says Photoroom creates the batch and opens it in the Batch Editor after individual-image selection; folder imports likewise create a batch and import the folder contents.

A batch is saved automatically as a project through Save & Sync in the Web App, but the source specifically says batch images are not saved as designs. That distinction matters for handoff: reopening the batch is different from expecting each image to appear in the Designs area.

If the grouping is wrong, stop before making shared edits. Rebuild the intake from the appropriate source structure rather than treating an incorrectly flattened batch as evidence that the editor will reconstruct the missing groups.

Worked Example: Choose The Intake Path

Hypothetical example: a seller has 18 approved images for a spring launch. Six images are in a folder named Blue Bottle, six are in Red Bottle, and six are in Travel Set. The seller wants to review each product group separately while applying a common crop later.

The correct planning choice is to import the parent Spring Launch folder, because its child folders carry useful grouping information. Importing all 18 images as individual selections or importing a newly flattened folder would create a less informative working structure. This is a hypothetical workflow decision; no Photoroom batch was created for this guide.

Existing source stateBest intake choiceReason
Images selected from several unrelated locationsImport images and choose individualsThe intended batch is a deliberate mixed selection.
One flat folder with no meaningful sub-groupsImport folderThe complete folder is one working set.
Parent folder containing product sub-foldersImport folder and choose the parentChild folders can become separate editor sections.

Related questions

Should I import a parent folder if I only need one product group today?

Usually, no. Import the individual files or the specific product folder when the other sub-folders are outside today’s scope. Use the parent-folder method when preserving multiple child groups in one batch is part of the editing decision.

Where CartVisual fits

CartVisual can help create product-image assets, but it does not implement Photoroom’s batch import or folder-section behavior. Use this route only for new product-image creation, then manage any external batch intake separately.

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.

Photoroom: Create a batch of images (Web App)

Official source snapshot checked .

The documented behavior is for Photoroom’s Web App batch creation flow. The supplied source does not establish file-type limits, duplicate handling, ordering, maximum nesting depth, export naming, or equivalent mobile behavior. The workflow recommendations and hypothetical example are editorial guidance; Photoroom was not executed for this article.

Related decisions

Browse ecommerce creative workflows