Workflow operations

Copy import, multi-language translation and copy preview

Feed the title and subtitle of each locale / shot into the project, and try to standardize the translation work.

Project and language settings Automatic capture and footage Preview / Export

`Import Copy`: Use | as delimiter with standard quoting

The most important input area of the Copy page is Final copy input. Use | as separator with columns in order: locale, shot, title, subtitle. As long as the shot name and locale match, Parse and apply will write the content into the project.

Minimal usable example

text

locale|shot|title|subtitle
en-US|home|Welcome to Store Screenshot Studio|Create store screenshots faster
en-US|paywall|Ship polished visuals|
es-MX|home|Bienvenido a Store Screenshot Studio|Crea capturas para tu tienda mas rapido

Prepare shot column

shot must be consistent with the display label of the current screen in the project.

The safest way is to name the Screens in the project first, then derive shot names directly from those screen labels.

Paste or import text file

Can be pasted directly into Final copy input.

You can also click Import copy file to read a local text file.

Click `Parse and apply`

Copy Preview will be unlocked after success.

If the locale or shot does not match, the app will try its best to give a fallback prompt; but in terms of operational efficiency, it is best to keep your table fully aligned with project fields from the start.

subtitle is allowed to be empty

If you only need the main title for a certain screen and no subtitle, leave the subtitle column blank and do not delete the column. The header structure must remain unchanged.

External translation workflow: generate table outside the app, then paste back

The app no longer has a built-in translation helper panel. Recommended approach: keep your source rows in locale|shot|title|subtitle format, run translation in your preferred external tool (AI or human workflow), then paste/import the returned table and click Parse and apply.

Reusable prompt template (external AI)

text

You are a professional App Store screenshot copy localizer.

Translate the source copy into the target locale and return ONLY valid pipe-separated rows.
Do not add explanations, markdown, or extra text.

Output requirements:
1. Keep this exact header and order: locale|shot|title|subtitle.
2. Use a literal | character between columns.
3. If a field contains |, newline, or double quote, wrap that field in double quotes and escape internal double quotes as "".
4. Keep shot names unchanged.
5. Keep one row per shot.
6. subtitle is optional; leave it empty if not needed.
7. Preserve product names and glossary terms exactly: <Glossary or None>
8. Use natural, concise, marketing-friendly language for the target locale.
9. Translate into every target locale listed below.
10. Include source-locale rows unchanged in the same output.
11. Return a single pipe-separated table with rows for source + all target locales.
12. Do not wrap output in code blocks.

Source locale: <Source locale>
Target locales:
- <Locale A>
- <Locale B>

Source rows:
locale|shot|title|subtitle
<your rows>

After AI returns the result, paste it back into Final copy input and click Parse and apply.
For iterative optimization, edit your source rows/glossary externally and rerun translation.
If the team has a need to separate iOS and Android copywriting, keep separate source tables in your external workflow and import per release branch.

`Copy Preview`: proofread the final copy language by language and screen by screen

After the table is parsed successfully, Copy Preview will display all screens according to locale. You can change a single title/subtitle directly here without having to regenerate the whole table.

Top locale tabs: Switch the language currently being checked.
Each screen has two input boxes: Primary copy and Supporting copy (optional).
This is suitable for manual polishing, but not suitable for large-scale modifications. For bulk changes, go back to table input.

Why sometimes I can’t see Copy Preview

There are usually only three reasons: 1. No locale has been enabled yet. 2. There is no screen yet. 3. Haven’t successfully Parse and apply a copy table yet.

Current copy model: shared copy across App Store and Google Play

In the current app flow, copy editing is centered on shared project copy. Final copy input + Copy Preview applies to the active project and is used by both App Store and Google Play outputs.

There is no longer a documented in-app toggle flow for Only this platform uses independent copy in current builds.
If your team needs long-term per-platform copy divergence, use separate project/release branches and maintain copy tables externally.
For most teams, shared copy keeps Preview/Render/Export maintenance simpler and avoids dual-tree drift.

Keep one copy tree unless you truly need two

If differences are only occasional wording tweaks, keep one shared copy table and adjust visuals in Preview. Split copy trees only when App Store and Google Play need long-term, structurally different messaging.

Auto capture, Deep Link and material input

This step determines how to get the original screenshot, and it is also the easiest place to get stuck. Explain deep link, capture set, upload rules and special branches in one go.

Preview, template adjustment, rendering and export

After the original screenshots and copy are in place, this final step determines the quality of the finished film and the delivery catalog.