Localized App Store and Google Play screenshots from one English Maestro flow. Every language your app ships, captured in parallel, checked, and ready for fastlane. Free and open source.
$ shotfleet run shotfleet.toml
capturing 18 locales on 4 simulators...
ok ar 4/4 screenshots
ok de 4/4 screenshots
...
captured 18/18 locales in 534s on 4 simulators
checked 72 screenshots in 18 languages: 0 problem(s)
The review page from a real run on Quickspan (Android phone, en, de, ja, ko, es): 25 screenshots, 0 problems, 343 s to capture on one emulator. The text typed in the first column is the same in every language because Maestro 2.0.10 ignores per-language [inputs] on Android. A rerun on Maestro 2.11.0 (de, es, ko: 15 screenshots, 0 problems) typed the phrase in each language.
Localized screenshots often end up as the English set copied into every language folder. The UI script taps English buttons ("Next", "Settings"), so it can't run in German or Japanese without a separate copy per language, and nobody maintains 20 copies.
shotfleet reads the translations compiled into your app and rewrites your script for each language: "Next" becomes "Weiter", "次へ" or "İleri". Then it runs every language at once and checks the result, so a wrong-language, copied, blank or missing screenshot never reaches a store listing.
Doing this by hand is slow and it doesn't scale. When I captured the store screenshots for my own app by hand, 17 screenshots in 2 languages took about 1.5 hours, roughly 2.5 minutes per screenshot per language. At that rate 20 languages is around 15 hours of tapping, and it all repeats at every release. With shotfleet the flow is written once and each release is a single command.
It is for solo developers and small teams who ship an app in several languages and want store listings that look native in every one of them, without a localization agency or a week of manual work. Localized screenshots are one of the cheapest ways to make a store listing convert better in another country, and the part that was missing was a way to do it that doesn't fall apart on the second release.
- One flow, every language. Write the Maestro steps once in English; shotfleet translates the taps from your app's own strings.
- iOS and Android from the same file, in parallel on simulators and emulators.
- A check that catches real mistakes: screenshots in the wrong language, copies across languages, blank frames, missing screens, ambiguous translations before anything runs, and the size and count rules of both stores.
- A review page (
out/index.html): a grid with a row per language and a column per screen, problems outlined in red. - fastlane export:
shotfleet exportwrites the foldersdeliverandsupplyexpect, and skips any language that failed a check. - Works with native iOS and Android, Compose Multiplatform, Flutter, React Native, .NET MAUI and Unity (from your translation files), and with screenshots you already have (
shotfleet checkon a fastlane folder). - Made for AI agents too: an MCP server (
shotfleet mcp) and agent skills for Claude Code, Cursor, Codex, Gemini CLI and GitHub Copilot. - Signed, notarized, no account, no key, no telemetry service to sign in to. Everything runs on your Mac.
curl -fsSL https://shotfleet.com/install.sh | sh # Apple silicon Macs; or: brew install noloman/tap/shotfleet
shotfleet doctor --fix # checks Maestro, Java, Xcode, the Android SDK; fetches what is missing
cd path/to/MyApp # build the app once for the simulator or as a debug APK first
shotfleet init # writes shotfleet.toml and a starter flow.yaml
shotfleet run --locales en # try one language, then: shotfleet runThen edit flow.yaml (plain Maestro steps in English, a takeScreenshot: per store image), review out/index.html, and export with shotfleet export out --fastlane fastlane/. The guide has the details: install options, config, CI, tips for tricky screens and the honest list of limits.
- Write the flow once in English with Maestro: navigate by the text users see and add a
takeScreenshot:for each store image. - shotfleet translates it per language from the strings in your built app, runs all languages in parallel and takes the screenshots.
- It checks every screenshot against your app's own text and the store rules, then exports clean folders for fastlane.
shotfleet is built and maintained by one person and costs nothing to use. If it saves you or your team the tedious hours of hand-capturing screenshots in every language, please consider sponsoring it.
Sponsorship pays for the time that keeps it useful:
- keeping it working as Xcode, Android, Maestro and the store rules change,
- support for more frameworks and device types,
- testing on real simulators and emulators, which takes machine time,
- answering issues quickly.
Not ready to sponsor? Starring the repo, telling a teammate and filing a good bug report all help just as much.
- Guide: everything in detail, including what
checklooks at, config, CI and limits - Linux and CI
- shotfleet.com: docs, guides and what's new
- Agent skills
Contributions are welcome: see CONTRIBUTING.md. Bug reports and ideas go in GitHub issues.
MIT. Copyright (c) 2026 Manuel Lorenzo Parejo.
