App Store screenshots, designedand published from one studio
Most screenshot generators stop at a PNG you still have to upload by hand, locale by locale. MetaRun's studio designs the set (3D device frames, captions, backgrounds), translates it into every language you ship, renders at exact App Store sizes, and publishes to App Store Connect in slide order.
Six slides on the bench from the live set: 3D frame, captions drafted. Say the word and I publish.
- 01
Compose slides, not files
Each screenshot is a slide: your app screenshot inside a 2D or true-3D device frame, a caption, a background (solid, gradient, image, or noise), plus text, icons, badges, and award laurels. Project defaults seed every new slide so a set stays coherent.
- 02
Caption with AI, translate to 40 locales
AI vision reads your screenshots and drafts benefit-led captions. Per-slide text is localized per store language, and AI translation fills all 40 locales in one pass while you keep per-language editing control.
- 03
One renderer, preview equals export
The canvas you see is the pipeline that exports: same math, same fonts, same 3D compositing. What you approve on screen is byte-for-byte what renders at Apple's required pixel sizes.
- 04
Publish to App Store Connect directly
The publish flow renders each slide, uploads it, and stages the screenshot set on your listing in order, with optional replace-existing. No export folder, no manual drag-and-drop into App Store Connect.
Nutrio: AI Calorie Tracker
4.6· v1.15.3 · app.nutr.io
Live specimen: Nutrio's real App Store slides
3D device mockups, in the browser
Flat device frames all look the same because everyone uses the same PNG templates. MetaRun renders real 3D device models (including current iPhone and iPad Pro hardware) with adjustable angle and perspective, composited into the slide at full export resolution. The result reads as a product shot, not a template.
It runs entirely in the browser on a shared WebGL renderer, so there is no design tool to install and no per-slide re-export: rotate the device, watch the composition update live, and the export pipeline reproduces it exactly.
Screenshots are a localization surface too
Screenshot captions are marketing copy, and shipping English captions to 40 storefronts wastes them. The studio keys both captions and the underlying app screenshots per store locale: a German user can see a German UI screenshot with a German caption, while your project stays one document.
AI translation drafts every locale from your source language in a single pass, and a caption audit can check your slides against the keywords you target per market, so the screenshot set pulls in the same direction as your metadata.
The last mile: publishing without leaving the studio
Uploading screenshots is the worst part of every release: ten slides, several device sizes, dozens of locales. MetaRun's publish drawer does it through the App Store Connect API: it renders from the studio, uploads each asset, and stages the set in slide order per display type, with a preview step before anything replaces what is live.
Because the studio's documents live server-side, MILO can operate it too: ask for a re-render with a new caption, an export, or a publish from chat or from your IDE via MCP, and the same renderer produces the same pixels with no studio tab open.
- True device models, not flat PNGs
- 3D
- Caption locales via AI translate
- 40
- Renderer: preview equals export
- 1
- Publish to App Store Connect
- Direct
Frequently asked questions
What size do App Store screenshots need to be in 2026?
The required set is the 6.9-inch iPhone size (1320x2868) or 6.7-inch (1290x2796); Apple scales those down for smaller devices, with separate sizes for iPad. MetaRun's presets render at the exact required pixel dimensions so uploads never bounce.
How many screenshots can I upload to the App Store?
Up to 10 per device size per locale. Most converting listings use 4 to 8, and the first 2 or 3 do most of the work since they show in search results before anyone taps through.
Can I put my screenshots inside an iPhone frame?
Yes, framed marketing-style screenshots are standard practice and accepted by App Review as long as the images represent the app. MetaRun offers both classic 2D frames and posable 3D device models.
How do I translate my screenshot captions into other languages?
Slide text is stored per store locale, and AI translation drafts all 40 languages from your source captions in one pass. You can hand-edit any locale afterward; the design layout stays identical across languages.
Can I upload screenshots to App Store Connect automatically?
Yes. The publish flow renders your slides and stages them on your listing through the official API, in order, per display type and locale, with an optional clean-replace of the existing set. You confirm before anything changes on the store.
Do App Store screenshots allow transparency?
No, the App Store requires opaque images (no alpha channel). The studio always renders a full background layer, so exports are valid by construction.
Do better screenshots actually increase downloads?
Screenshots are the largest visual element on your product page and appear directly in search results, so they carry a large share of conversion. Treating them as a localized, regularly refreshed asset (rather than a launch-day artifact) is one of the highest-leverage ASO habits.
Related capabilities
Capability file 04
Listing translation
AI-translate your name, subtitle, description, and keywords into 40 locales.
Open fileCapability file 06
Metadata editor
Bulk-edit every locale of your listing with preview, apply, and one-tap revert.
Open fileCapability file 07
MCP server
Drive your entire App Store from Claude Code or any MCP-capable IDE.
Open fileMILO standing by
14-day free trial. No credit card. Your keys stay encrypted.