What screenshot inputs are required?

Clean simulator captures in PNG format are required. The studio composites each capture into the chosen device frame and applies your typography, layout and theme.

Can a project be saved and resumed later?

Yes. Authenticated users can save projects to the cloud, name them, and open them again from any device. Autosave runs every 30 seconds during an active session and uploads only the screenshot bytes that have actually changed. The Free tier supports one saved project; the Pro tier supports twenty.

Is the export compatible with fastlane?

Yes. The export bundle uses the exact directory layout expected by fastlane deliver and supply, including locale and device folders. iOS and Google Play screenshots may be mixed within a single bundle without further reorganisation.

Can multiple device sizes be rendered together?

Yes. Any combination of iOS 6.9, 6.7, 6.5 and Google Play may be selected. A single render produces every selected size and packages them in one bundle.

How customisable is the typography?

Each project supports an arbitrary number of named text fields. Within each field, individual character spans may be styled with their own font, size, weight, colour, italics, underline and alignment. More than 30 Google Fonts are available out of the box.

Is there a way to translate screen text into other languages?

Yes. Pro accounts auto-translate every text field on every screen into every selected language in one click. Translation runs on a self-hosted LibreTranslate instance, not a third-party API. Proposals appear in a review panel and the originals stay untouched until you approve them.

Where is data stored?

Render output and project assets are stored in Cloudflare R2 under the European Union jurisdiction (primary copy in Western Europe). Accounts, render history, and billing data sit in Postgres on a Contabo VPS in Düsseldorf, EU. Render outputs are removed after 24 hours; screenshots associated with saved projects are retained for the lifetime of the project. No training is performed on customer data, and the studio interface uses no tracking cookies.

mcp · options gallery

Every option, with a preview

When you render through the AppScreen MCP server, the agent should show you this menu and let you pick. Each option below is rendered with the same placeholder so you can compare them directly.

Background effects

Use this screen's own screenshot as a processed backdrop (bg.kind = effect).

Blur example — `blur`
Blur
The screenshot itself, heavily blurred, as the backdrop. Subtle, content-derived.

Blur + Tint example — `blur+tint`
Blur + Tint
Blurred screenshot with a saturated color wash + white scrim for caption legibility. Punchier.

Background presets

Built-in textured / structural backgrounds (bg.kind = preset).

Paper example — `paper`
Paper
Soft paper grain. Warm, editorial.

Gallery frame example — `frame`
Gallery frame
Double-border gallery mat around the device.

Card example — `card`
Card
Inner white panel floating behind the device.

Mesh gradient example — `mesh`
Mesh gradient
Smooth multi-stop mesh gradient from your color.

Device frames

The device bezel around the screenshot (screenshot.frameId).

iPhone example — `iphone`
iPhone
Realistic iPhone 16 Pro Max bezel. Use for App Store.

Generic — minimal example — `generic-minimal`
Generic — minimal
Frameless rounded screenshot, no bezel.

Generic — outline example — `generic-outline`
Generic — outline
Thin colored outline around a rounded screenshot.

Generic — glow example — `generic-glow`
Generic — glow
Neon glow border around a rounded screenshot.

Also available: solid color and custom image backgrounds, four sizes (ios-6.9 / 6.7 / 6.5, play), and six output layouts. See /v1/catalog for the machine-readable list.