Lilacpane01 / Why batch deserves its own workflow
One image feels fast, but ten means ten rounds of open canvas, import capture, adjust copy, set size, export, rename. Any inconsistency shows up visually: the second image has slightly smaller type, the fifth uses a different background depth.
Batching is not laziness — it turns consistency from a steady hand into a structural guarantee.
02 / Order matters: template first, batch second
There is only one correct order, and reversing it guarantees rework:
- Build the first image as the template: frame position, background, type size, weight, spacing, and canvas size all locked.
- Verify how it actually reads at target size — especially at 25% scale.
- Duplicate the template and swap capture and copy one by one. Change content, nothing else.
- Export everything at the end, not as you go.
Step two is the one people skip, and it is the quality gate for the whole set. If the first image is wrong, the other nine inherit it.
03 / Get export parameters right once
Confirming these before export is far faster than fixing them after:
- Canvas size equals the target bucket (iPhone 6.9-inch or iPad 13-inch)
- PNG or JPEG for submission; keep transparent PNGs as a separate set for design work
- Solid background with no alpha channel
- Scale as needed: 1× for web, 2× / 3× where images get enlarged
04 / Naming rules your future self will thank you for
A batch run produces dozens of files, and without naming rules that is not file management. A structure that works:
- Folders by language / device / size, like en / iPhone / 6.9
- Filenames with order, content, and format, like 01-home-PNG, 02-search-PNG
- A suffix for transparent versions, like 01-home-transparent
- Version at the folder level, like v4-1-0, so you can roll back and compare
The sequence number matters: App Store shows screenshots in upload order, so numbered filenames prevent mistakes.
05 / The last check before exporting
Clear this list and the set is ready to upload. Localized versions follow the same flow — swap copy, change folder, export again.
FAQ
How many should I export at once?
It depends on the channel. App Store allows up to 10 per device size per language, and a set of 5 to 8 usually covers the core features. Website and social images have no such limit, so export as many as you need there.
Should I export at 1×, 2×, or 3×?
Match the destination. 1× corresponds to logical resolution and is fine for small web images and quick sharing; 2× and 3× carry more pixels for enlarged or high-density displays. For App Store submission, export at the target bucket’s native pixels — no extra upscaling needed.
Do transparent and flattened versions need separate exports?
Yes. App Store rejects images with alpha channels, so submission must be flattened, while transparency suits Figma, Notion, your website, and decks. Keep two folders and distinguish them by filename suffix.
Can I still edit one image after a batch export?
Yes, but re-export with identical parameters. The safest route is to change it inside the template and re-run the batch, so the edited image does not drift from the rest.
