fastlane snapshot alternatives, and when not to use shotfleet
There are a few good tools for localized store screenshots, and some of them are free. This page shows how shotfleet compares, and when you should use something else.
Feature comparison
| Tool | Takes the screenshots from your running app | One flow for every language | Checks the language of the result | iOS and Android | Price |
|---|---|---|---|---|---|
| shotfleet | Yes | Yes | Yes | Both | Free and open source (MIT) |
| fastlane snapshot and screengrab | Yes | Yes (UI-test code in your app, one per platform) | No | Both (two tools) | Free |
| simshot | Yes | Yes (a few lines added to your app) | No | iOS only | Free |
| ButterKit | Yes (from the Simulator) | Not stated on its pricing page | Not stated | Not stated | Free (watermarked), Pro $99 once |
| AppScreens | No (mockups from screenshots you upload) | No | No | Both | Pro $99/yr, Scale $180/yr |
Checked on 2026-10-02 from each tool's own pages and docs. "Not stated" means the page doesn't say, not that the answer is no. If I got something wrong, tell me and I'll fix it the same day.
What each tool does
shotfleet
It takes one English Maestro flow and rewrites it for every language your app has. It uses the translations built into your app to do that. Then it runs the flow on several simulators and emulators at the same time. It checks each screenshot for the wrong language, copies, missing screens and store size rules. Last, it exports the screenshots to fastlane's folders.
Setup is one command, a two-line config and a Maestro flow in English. Measured once on my M1 Pro, with my app, on Maestro 2.0.10: 18 languages x 4 screens, 9 minutes on iOS and 15 on Android. Your Mac and your app will give other times. You can watch the main commands in the clips on See it work.
fastlane snapshot / screengrab
This is the one most people use. You write UI-test code (XCUITest on iOS, Espresso on Android) that taps buttons and takes screenshots, and it runs once per language. You add a test target to your app, and iOS and Android need separate code. It's free, lots of people use it, and it works in CI.
If you already have UI tests that run in every language, you may not need shotfleet. shotfleet is for when you don't want test code in your app, or you want one flow for both platforms and a check of the results. fastlane still does the upload and the framing.
You don't have to pick one. If your fastlane UI tests already run in every language, keep them and run shotfleet check on the folder they write (snapshot or screengrab). It's free. It tells you which languages show the wrong strings, which are copies and which miss a screen. I ran it on a real fastlane snapshot set and it found a German listing whose app was still in English.
simshot
Free, MIT-licensed, iOS only. It opens the app in each language with launch arguments and takes the screenshots. You need to add a few lines to your app. It's a very new project.
ButterKit
A Mac app that takes screenshots from the iOS Simulator, adds device frames and captions, translates the text with AI and uploads to App Store Connect. Its pricing page lists a free tier (watermarked exports, 50 languages, on-device translation) and Pro at $99 once, with free updates, 5 Macs and a 14-day refund. It doesn't say whether it re-captures your app in each language.
Using the two together: run shotfleet to get the raw localized screenshots into fastlane's folders. Then point ButterKit at them for frames and captions, and upload. shotfleet's check tells you whether the language inside the app matches the language on the listing.
AppScreens
A web editor. You upload screenshots and add device frames, text and backgrounds, for iOS and Android. Free covers one project with no localizations; Pro is $99 a year (10 languages) and Scale $180 a year (80+ locales). It makes marketing images from what you upload. It doesn't take screenshots from your app.
When you shouldn't use shotfleet
Skip it if one of these sounds like you
- Your app has one or two languages. fastlane snapshot or simshot (both free) will do the job.
- Your fastlane UI tests already work well, and you don't mind running them once per language.
- You want frames, captions, or store upload. ButterKit and AppScreens are made for that; shotfleet doesn't do it.
- Your app is Flutter or React Native. shotfleet reads translation files from those stacks and has been run end to end on one real Flutter app (wger) and one real Expo app (the obytes template), not on other apps or on bare React Native.
- You don't have an Apple silicon Mac. shotfleet runs on macOS on Apple silicon only, and needs Maestro and Java 17 or newer (on iOS, your own XCUITest tests can stand in for Maestro, but that part is new in 0.1.6). Built to run on macOS 13 or later on Apple silicon (the build declares 13.0 as its minimum), but I haven't run it on macOS 13. My full runs, with simulators and emulators, were all on macOS 27. On macOS 14 and 15 I ran the installer, doctor and check for version 0.1.6, and on macOS 26.2 in a virtual machine for 0.1.2. Other macOS versions are not tested yet.
The story
I have a workout app in 18 languages. A Maestro flow finds buttons by the text on them, so every flow I wrote only worked in English.
So I wrote shotfleet. My flow stays in English, and shotfleet changes it for each language, on both platforms, then checks what comes out. On the first full run, the onboarding button was out of reach in Japanese, Korean, Chinese and Arabic on small phones. The text was taller and the page didn't scroll. The fix in my app was small: I made two pages scroll. Nobody had noticed, because the English screenshots fit fine.
ButterKit, AppScreens and fastlane do other jobs: frames, mockups and UI tests. shotfleet does one smaller job. It makes sure the raw screenshots of your app are really in the right language.