How to use 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 — Start a project
Download the studio for macOS and open it — the home screen is a launcher, not a form. Nothing to configure up front: the device type is auto-detected from each screenshot you upload, and sizes live in the editor header. Or skip the blank start:
- Start from a template — a designed multi-slide starter set that drops you straight into the editor.
- Import files — the card next to Open 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). Your projects also sit as thumbnails under the start cards, and a.studio.zipdragged onto the window opens in place.
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. Your screenshots and
projects stay on your Mac; the only network request is a check for a newer version at launch, which
you can switch off with Check at Launch in the header's ⋯ menu.
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. Wrap words in
==double equals==to draw just those in the emphasis style — the markers live in the text, so they survive translation. - Highlights — draw a dashed source region on the screenshot and a magnified loupe card floats above the bezel.
- Extras — badges (including laurel rating badges), vector ornaments like sparkles and hand-drawn circles and arrows, gradient/image backgrounds, and App-Store-style 2-page panoramas that span two slides.
- Save Design as Template in the header's ⋯ menu keeps the design without the screenshots as a new start card on the home screen.
Step 3 — Localize
Captions live in a slide × language table. The fastest way to fill it: with the MCP agent connected, ask it to translate every missing caption — it writes into the table live and adds new languages itself. By hand, three ways:
- 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. Pick a language from the editor's edit-language menu to see it on the canvas
before you export, and adjust position, size, background or device for that language
only — anything you don't touch follows the shared layout. 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, and writes them into a folder you choose as
locale/device/NN.png. The “fastlane folder” button instead
writes a ready-to-run fastlane deliver
folder — 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
In the app, select those files together with step 1's Import files — it
takes the files, not the folder, and the window itself only accepts a dropped
.studio.zip. Or render them with no window at all, using 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: a checkout of the repository with
npm install done (Node, plus Playwright's Chromium). The script starts the dev
server itself; BASE_URL only points it at another build.
An AI agent can also drive the project you have open in the app instead of files — see the MCP guide.
Download Screenshot Studio for macOS — free, open source, fully client-side. Your screenshots never leave your Mac. →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