Screenshotify
For Expo developers

For Expo and EAS Submit workflows.

TL;DR. Browser-based tool — no Mac required to design (unlike Fastlane on iOS). Export App Store and Play Store sizes from one design. Drop the result into EAS Submit, App Store Connect, or Play Console manually. No setup, no Snapfile.

Expo's selling point is shipping iOS apps without a Mac. Most screenshot tooling breaks that promise — Fastlane snapshot needs Xcode, the simulator's screenshot keybind needs a Mac, and AppCenter screenshot uploaders need a build from Mac infrastructure. Screenshotify runs entirely in the browser, so the no-Mac story stays intact through the marketing-asset step.

Where Screenshotify fits in EAS Submit

EAS Submit handles the upload-binary part of App Store / Play Store deployment. It does not handle screenshot creation — you provide those separately. Workflow:

  1. Capture source frames from npx expo start on a real device or simulator. Expo Go works for this.
  2. Open Screenshotify in the same browser, paste or drop the screenshots. WebRTC pairing connects your phone for direct transfer if you don't want to AirDrop.
  3. Design the marketing carousel — captions, device frames, locale variants.
  4. Export the ZIP at App Store + Play Store sizes.
  5. Upload manually to App Store Connect (under Screenshots per locale) and Play Console (under Store Listing → Graphic assets). EAS Submit itself only handles the binary, not the marketing assets.

What about Expo's screenshot APIs?

expo-screen-capture blocks screenshots at runtime (security feature for sensitive apps), not a generator. There's no Expo-native equivalent of Fastlane snapshot or a marketing-composer. Screenshotify fills that gap from the browser side.

Tips for Expo apps specifically

Open the editor →