How it works
Four steps from capture target to store-ready files.
Choose screenshot states
Prepare data and flags
Capture target screens
Export final assets
App state capture
The screenshot is only right when the app state is right
Define the target state
Decide whether each screenshot needs onboarding, logged-in content, a paywall, empty state, or filled sample data.
Prepare it before capture
Use setup links, demo accounts, or app-specific parameters to put the app into the right condition.
Reuse it later
Keep state definitions with the project so launches, updates, and localized variants do not start from scratch.
Demo
See app states captured without repeating setup by hand
FAQ
Questions before you download.
Can I capture logged-in screenshots?
Yes, if your app can prepare the logged-in state through a demo account, setup link, or other repeatable state setup before capture.
Can I capture paywalls or onboarding?
Yes. These are good examples of screens that benefit from saved routes and predictable app state.
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.
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.
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.

