Why does reopening my Photopea batch-poster PSD still require source images for the next export?

Separate the reusable template from batch inputs

A merchant may reopen a PSD used for last month's product posters and see the previous product photograph still on the canvas. That visible image does not prove that Photopea has the Source images collection required for the next batch export.

Photopea Variables supports three different responsibilities: text content, pixel content, and layer visibility. Data Sets provide the values used to produce individual versions.

The PSD retains the variable configuration and Data Sets settings, but not the Source images collection needed for pixel replacement during a later export.

This does not mean that PSD files contain no image pixels or that every image must always remain externally linked. The distinction concerns the batch replacement source collection.

Before repeating a campaign, inventory the editable PSD, the corresponding data, and the approved product photographs as separate handoff materials.

Match source photographs to the correct product records

When preparing the next batch, reload the source photographs and verify that their filenames correspond to the references in the data table.

A poster can contain correct promotional text but the wrong product image if the image-source mapping is confused. Matching by casual visual inspection is particularly risky for similar product variants.

Use a stable internal SKU-to-filename checklist. For example, distinguish two bottle variants with unambiguous source names rather than relying on generic filenames such as product-final.

Keep approved photographs in the authorized production handoff. Do not delete original images merely to test whether Photopea remembers them.

The stopping condition is any unresolved filename-to-product mismatch. Resolve it before preparing the complete batch.

Illustrative exercise: missing sources and persistent badges

Illustrative exercise — fictional merchant scenarios, not executed Photopea exports, PSD edits, or software tests.

Input A is a cosmetics poster template reopened for a new seasonal campaign. The PSD displays last month's product image, but the next campaign's Source images collection has not been loaded.

The merchant should reload the approved source photographs and compare filenames with the current Data Sets before evaluating export.

Input B is a discount-poster series. Some products have no promotion. The merchant leaves the promotional text value empty, but the decorative badge background remains visible.

This is a different variable responsibility. The team should evaluate a visibility variable for the badge layer rather than assuming blank text hides the entire graphic.

Both cases belong to one repeatable batch workflow, but they require different corrections.

Package the next production cycle correctly

For handoff, provide the editable PSD, the corresponding Data Sets information, and the approved Source images collection. Record the expected relationship between product identifiers and source filenames.

Review text, pixel replacement, and visibility as separate acceptance conditions. A correctly updated price does not establish that the product photograph is correct, and an empty badge caption does not establish that its background is hidden.

Use a working copy for manual checks before preparing the full export. Confirm representative products with and without promotions.

If a source photograph is missing or its filename conflicts with another product, stop the batch preparation rather than substituting an unverified image.

This workflow preserves the distinction between reusable template configuration and the external source collection required for future pixel-variable exports.

Illustrative exercise — Photopea batch-poster handoff checklist

These are illustrative exercise rows. Save a copy and record your own observations; the example is not an executed acceptance test.

Download review worksheet (CSV)