Expo screenshot generator
Store screenshots from your Expo screens.
Capture the UI from a development build or Simulator, then upload those images. Screenies builds the listing set around that UI. EAS Submit sends the binary to Apple or Google. It does not upload App Store or Play screenshots.
1 credit per phone slide. Credits do not expire.
Capture the build store visitors will see
- 01
Use a development build when the UI needs native modules
Expo Go omits custom native code. If a screen depends on a native module, run a development build and capture that, not Expo Go.
- 02
Screenshot from Simulator or a device
Start the project with npx expo start, open iOS or Android, and capture the flows for the listing. Keep source images free of debug banners when you can.
- 03
Generate the set, then submit the binary separately
Create the screenshot batch in Screenies. Use EAS Submit or Xcode for the build. Upload listing images in App Store Connect, Play Console, or the Screenies upload for a linked iOS app.
EAS Submit and listing images are different jobs
eas.json and EAS Submit handle the IPA or AAB. Screenshot files still go to the store listing. Screenies does not talk to EAS and does not read your project config.
React Native CLI projects without Expo should use the React Native screenshot generator. Flutter projects use the Flutter screenshot generator.
iPad and Play still need their own captures
If the Expo app runs on iPad, capture iPad Simulator and generate a 13-inch set with the iPad screenshot generator. Google Play sets download for manual upload in Play Console.
Credits cover generation, not EAS
Each phone slide costs 1 credit. Localization is 0.10 credits per slide, per locale. Credit packs are one-time purchases.
Upload the listing after the set is ready
Check exports with the size checker. Follow the upload guide for App Store Connect. Translate headlines with screenshot localization.