Feature
Localized screenshot sets from per-locale copy you supply.
Pass locale tags and your own localized strings to generate a complete store screenshot set for each market in the same render.
Per-locale captions you provide
Each locale can carry its own headline and subtitle strings, keyed by BCP-47 tag, while sharing the same captures, canvases, theme tokens, and preset. You supply the translated copy; text fitting keeps long strings inside the type scale locked across the set.
A render combines canvases and locales in one request through output: a 6-slide set across appstore.iphone_6_9, appstore.ipad_13, and play.phone for en-US, es-ES, fr-FR, and ja-JP. Results come back as CDN image URLs tagged with locale, store, and canvas metadata, or as a Fastlane-compatible ZIP via output.format.
{
"canvas": { "preset": "appstore.iphone_6_9" },
"slides": [
{
"headline": { "lines": ["Track every habit"] },
"screenshot": { "url": "https://acme.app/shots/home.png" }
}
],
"output": {
"locales": ["en-US", "es-ES", "fr-FR", "ja-JP"],
"stores": ["appstore", "play"]
}
}Localization control
Use your own translated strings for deterministic output, or route copy drafting through the optional brief assist before rendering. The final render request still carries explicit per-locale text so release assets stay reviewable.
For right-to-left markets, supply RTL-ready strings and layout intent in the request. Keep a manual copy review step for Arabic and Hebrew sets before upload, the same way you would review store metadata.
API details
Locales output.locales: BCP-47 tags you pass per render (live)
Inputs your localized captions, captures, canvases, theme tokens, preset
Outputs one designed, linted screenshot set per locale and canvas
Review manual copy and layout QA for RTL markets before upload
Use it in a release pipeline
Render the set from CI with POST /v1/renders, check the compliance lint report, then download the finished images for review before App Store Connect or Google Play upload.