Same artwork.
Next week's offer.

First, choose the simpler workflow

One prepared template with variable text or images: try Photopea Variables. Its documented workflow already accepts CSV data, changes text, visibility or pixel content, and exports a batch ZIP. Batch text replacement alone is not unique to this experiment.

Different named groups across a few older files: Campaign Reuse tests an explicit connection list. Each alias points to one source file, either its full template or a selected group, and one text layer. Full-template mode keeps the original dimensions. This may save repeated selection work; whether it saves enough time in real work is still being tested.

Large PSB files or edits to smart objects: these edits are not supported. Keep those files in an editor that supports their structure. It is not a Photoshop replacement.

A concrete weekly example

A fictional shop has square and landscape offer groups in three PSD files. Six connections select those exact groups and their discount text. This week's list contains an output name, connection and new offer for each graphic.

1. Select your source PSDs. Eligible groups appear in the connection list.
2. Choose Entire template to retain the original design, or choose a specific group. Then select the editable text layer. In group mode, that group must contain everything you want in the result, including any background.
3. Enter offers in the on-page table or import a CSV with output,alias,text columns.
4. Enable the embedded Photopea renderer. Review each generated preview.
5. Download PNGs, editable PSDs or the complete ZIP. Save connections for the next batch.

Next week, select the same source files and restore the saved connections. The mapping file contains filenames and layer paths, not artwork. Renamed or missing layers need to be mapped again.

The built-in designs are fictional demonstrations. They are not customer work, testimonials or evidence of revenue.

What is preserved—and what needs review?

Full-template mode passes the original PSD to Photopea and changes only the selected text. Group mode keeps the chosen group’s coordinates on a new fixed-size canvas. In group mode, other source groups are not included. There is no automatic resizing, layout adaptation, line fitting or font substitution guarantee.

The app checks output dimensions, updated text and whether the PNG has visible pixels. It flags target text outside the canvas. These checks do not establish visual correctness: you still need to inspect fonts, clipping, overlap and background coverage before delivery.

Parent effects, masks and non-default parent opacity can change a nested group's appearance. Group mode rejects those inherited structures rather than silently discarding them. Full-template mode delegates preservation to Photopea, which still requires visual review.

Accepted files and current limits

• 8-bit RGB PSD; at most 3 sources, 20 MB each, 24 MB combined and 6 million pixels per source.
• A selected horizontal text layer with one style. Group extraction additionally requires simple pixel/text layers, up to 50 layers and 8 levels.
• Up to 12 outputs; native canvas dimensions for full templates, 1080 × 1080 or 1400 × 854 for groups. One text replacement per output.
• No PSB, actual text-on-path or mixed-style text editing. Group extraction rejects smart objects, adjustments, masks, artboards and effects. Full-template mode does not edit those features and does not certify all of them.

If your recurring task falls outside these limits, describe the exact file structure and desired result. Please do not send confidential client artwork in a feedback message.

Where are files processed?

Source parsing happens in your browser. Rendering starts only after you enable the embedded Photopea editor; that editor is a third-party dependency with its own privacy policy. Artwork is not uploaded to Supplier Desk. Feedback text you choose to submit and basic usage events are handled separately.

No AI model is used to parse, map or render your files. Keeping a browser-based editor available is still necessary for rendering.

What has been verified?

The prototype has been exercised with synthetic PSDs through source selection, saved mappings, offer changes, PNG/PSD export and ZIP download. Separate inspection of public design templates found major compatibility gaps, including root-level text, common text metadata and complex layer styles. The strict group-extraction workflow did not accept them. A separate full-template mode was then checked with one publicly available hiring PSD: the selected text survived PSD export and reopening, with PNG changes confined to its text region. This one example does not establish broad compatibility. This does not certify Photoshop compatibility or prove that real client projects will work.

We publish limitations alongside the workflow so you can decide whether trying a non-confidential file is worthwhile. Public test source: hiring template by PsFiles (author attribution required; source artwork is not distributed here). No paid service is purchased by submitting feedback.