What Devices, Orientations, and Languages Does Screenshots Pro Support?
Updated
Screenshots Pro supports 23 device frames across Apple and Android, both portrait and landscape orientations, and translation into any language the App Store and Google Play support. It also offers a REST API for CI/CD automation. If you need to produce one design and export it across multiple device sizes and languages, the platform is built for exactly that. The details below cover what's confirmed on the site and where you'll need to verify specifics yourself.
Device support: Apple and Android
Screenshots Pro provides 23 pixel-perfect device frames, covering the latest Apple and Android hardware. The site specifically names:
| Platform | Devices mentioned |
|---|---|
| Apple | iPhone 16 Pro Max, iPad M4, iPhone and iPad (latest iOS devices) |
| Android | Google Pixel 8, Google Pixel 8 Pro, Android phones and tablets |
Frames come in two styles: clay (a neutral, colored mockup look) and real device frames, and the site states you can apply any color you need. Devices can also be shown at 3D angles with perspective, which the site markets as giving screenshots a "premium feel."
If your target device isn't in the named list, the practical move is to open the editor and check the full device picker — the site says 23 devices total but only names a subset.
Orientation: portrait and landscape
Both orientations are supported natively. This matters because App Store and Google Play accept different aspect ratios depending on orientation, and a tool that only handles portrait forces manual workarounds for landscape layouts (games, video apps, tablet-first designs).
Multi-device export
You design once, then export for every device. Screenshots Pro automatically resizes your screenshots to the sizes required by the App Store and Google Play. This is the core workflow benefit: instead of rebuilding a screenshot set per device class, you maintain one design and let the export step handle the resizing.
Language and localization
Screenshots Pro can translate your app screenshots into different languages and supports distribution across multiple regions. The site states:
- All languages — translate screenshots to any language supported by the App Store and Google Play Store.
- International growth — create a native experience for local speakers and gain larger local market share.
The site's own example scenario is localizing into 20 languages while releasing for multiple devices, with the pitch that you only need to design once. Note that the site describes automatic translation of screenshots; if your screenshots contain brand-specific copy or legal text, review translated output before publishing.
Automation via REST API
For teams running CI/CD pipelines, Screenshots Pro offers a REST API to auto-generate App Store screenshots. The site lists three API-related capabilities:
- CI/CD automations — auto-generate screenshots using the REST API.
- Scale to 1000s of apps — create personalized screenshots for multiple apps.
- Documentation — the site points to its docs for automating marketing efforts.
If automation is your deciding factor, check the documentation for rate limits, authentication method, and whether the API covers localization and multi-device export or only base generation.
Quick fit check
Use this to decide whether Screenshots Pro matches your requirements:
- Need iPhone 16 Pro Max, iPad M4, or Pixel 8 frames? Covered.
- Need both portrait and landscape? Covered.
- Need one design exported to many device sizes? Covered via automatic resize.
- Need 20+ language variants? Supported, with automatic translation.
- Need pipeline automation? REST API available; verify scope in the docs.
- Need a device not named on the site? Check the editor's device list before committing.
The site also states no account is needed to create screenshots, and describes the editor as drag-and-drop. For pricing, API access tiers, or limits on the number of exports, the provided page content doesn't specify — confirm those directly on the site before relying on them for a production workflow.