How it works
Four steps from capture target to store-ready files.
Add screenshot languages
Open target screens
Capture each locale
Export localized folders
Localized capture
Treat language as a screenshot input, not a manual device setting
Add target locales
Define the languages your store listing needs before capture starts.
Open the same screen
Use capture targets so each locale starts from the same app page, state, and data setup.
Review before export
Check localized copy, wrapping, layout balance, and final store output while the set is still editable.
Demo
See language, screen, and state capture in one project
FAQ
Questions before you download.
Can this avoid changing simulator language manually?
Yes. The goal is to make locale part of the capture target so you can run localized screenshot sets without manually changing global simulator or device language each time.
Can I use my own translations?
Yes. You can paste TSV/CSV copy and review every localized screenshot before export.
Do I need deeplinks?
Automatic capture works best when your app can open the screens you want through deeplinks, routes, or intent URLs. You can also use manual uploads for screens that cannot be automated yet.
Can it prepare sample data?
You can run setup links before capture, use demo accounts, or pass state through your capture links so screenshots use stable sample data instead of live user data.
Does it support App Store and Google Play?
Yes. You can create screenshot projects for iOS, Android, or both, then export complete store-ready screenshot sets.

