← App Store Screenshot Studio한국어로 읽기 →
How to use App Store Screenshot Studio
The studio takes you from raw simulator screenshots to a complete, multi-language, App-Store-Connect-ready PNG set in four steps — entirely on your Mac, no account, no upload. This is the full walkthrough, including the file-based pipeline that lets an AI assistant do most of it for you.
Step 1 — Set up the project
Download the studio for macOS, open it, and pick a device type (iPhone or iPad — each slide's type is later auto-detected from its screenshot anyway), a slide count, and a theme. Or skip the blank start:
- Start from a template — a designed multi-slide starter set that drops you straight into the editor.
- Import a project — select an AI-drafted file set (manifest + captions + screenshots, see below) and get a ready-to-review project in one pick.
- Open a project you already have — pick a
.studio.zip, or one of the recent projects (⌘O).
However you start, the project becomes a file right away —
~/Documents/Screenshot Studio/ unless you save it elsewhere — so
⌘S, ⇧⌘S and the File menu work the way they do in any Mac app. The window
title is the file name, with a dot in front while there is something unsaved. Everything stays on
your Mac; nothing is sent anywhere.
Step 2 — Design in the editor
- Screenshots — upload one per slide; it's framed in the device automatically. Rotate, crop by edge-drag, or let the device bleed off the canvas for hero layouts.
- Text — headline and subheadline per slide with full typography control; drag to place, double-click to edit.
- Highlights — draw a dashed source region on the screenshot and a magnified loupe card floats above the bezel.
- Extras — badges, emoji ornaments, gradient/image backgrounds, and App-Store-style 2-page panoramas that span two slides.
- Your slide set can be saved as a reusable template from the header.
Step 3 — Localize
Captions live in a slide × language table. Three ways to fill it:
- Type translations directly into the grid.
- Export the template (CSV or JSON, one labeled column per language), fill it in a spreadsheet or hand it to a translator, re-import. Empty cells are skipped, so partial files are fine.
- Copy the built-in translation prompt, paste it into ChatGPT / Claude / Gemini together with the exported template, and re-import the filled file. No API keys involved.
If your app's UI is localized, bulk-add per-language screenshots named
01-home.en.png, 01-home.ko.png, … — leading digits pick the
slide, the suffix picks the locale. Languages without an override fall back to the base
screenshot. A preview dropdown in the editor shows any locale on the canvas before you
export. Full strategy in
the localization guide.
Step 4 — Export
One click renders every slide × language at the
exact App Store Connect resolution,
alpha-stripped so uploads never bounce, zipped as locale/device/NN.png.
The “ZIP for fastlane” button instead produces a ready-to-run
fastlane deliver folder —
unzip, set your bundle id and API key, run ./upload.sh.
The AI-agent pipeline (zero clicks)
Everything above also works without a human at the keyboard, because the studio's input and output are both files. An AI assistant (Claude Code, Cursor, etc.) drafts an import folder:
launch-screenshots/
├── manifest.json # device, locales, per-slide layout & text-block count
├── captions.csv # slide × language caption table
├── 01-home.en.png # screenshots: {slide}[-desc].{locale}.{ext}
├── 01-home.ko.png
└── 02-add.en.png
A human can drop that folder into step 1's “Import project”. Or skip the browser entirely with the headless pipeline from the repository:
npm run headless:export -- launch-screenshots/ out/ --report
# → out/en-US/iphone/01.png … every locale, exact sizes
# → out/layout-report.json + out/layout-summary.json
npm run layout:loop -- launch-screenshots/ out/ --write --max-runs 3
# render → apply conservative manifest fixes → re-render until clean
The agent loop is: edit the manifest or captions → render → read the layout summary
and PNGs → apply safe manifest fixes → repeat until it converges. The manifest schema,
naming rules, and layout autofix commands are documented in
docs/project-import.md.
Requirements on the machine running it: Node, @playwright/test + Chromium, and
either a local checkout or BASE_URL pointed at the hosted studio.
FAQ
Where is my project stored?
In a .studio.zip file you own — by default under
~/Documents/Screenshot Studio/. It holds the project and every screenshot in it, so
you can move it, back it up, or hand it to someone else. Work you have not saved yet is also
mirrored inside the app's own folder, and the app offers it back if it was quit unexpectedly.
Does it cost anything or need an account?
No. It's MIT-licensed open source released on GitHub; there is no backend at all.
Which sizes does it export?
The App Store Connect upload slots: iPhone 6.9″ (1320×2868), iPhone 6.5″ (1242×2688),
iPad 13″ (2064×2752), iPad 11″ (1668×2388) — see
the size guide for which you actually need.
Related guides
- Let an AI agent edit your screenshots — MCP setup
- App Store screenshot sizes 2026 — every required resolution
- Localizing App Store screenshots — a workflow that scales past 3 languages
- Upload App Store screenshots with fastlane deliver
- How to take iOS Simulator screenshots for the App Store
- App Store screenshot captions that convert