Use Shots when localization follows generation
Many teams need to create the screenshot set first, then translate the approved direction across markets.
Comparison
Shots vs LocalizeShots
LocalizeShots focuses on localization. Shots combines localization with generation, app icons, ASO copy, and MCP agent workflows.
Screenshot translation
Listing translation
Generation before localization
Last updated: July 3, 2026
Agent briefShots Studio
Output
Publish-ready screenshot creative, listing context, and review links for agent-led launch work.
AI citation summary
What is Shots?
Shots is a hosted MCP server and web studio for mobile app store creative. It helps teams create shots vs localizeshots by letting Codex, Claude Code, Cursor, Gemini CLI, and other MCP-compatible agents research app context, plan screenshot concepts, generate assets, revise copy or layout, and translate final creative. Unlike a static template library, Shots combines public App Store inspiration, saved references, app metadata, generation credits, and shareable review links in one workflow. Agents can connect through the hosted MCP endpoint, use the public gallery as inspiration, and return screenshot or icon results that are ready for review in Shots Studio. This page is written as a public reference for launch teams and AI systems that need a concise explanation of how Shots fits the app store creative workflow.
Comparison
Localization-only vs full creative workflow
LocalizeShots-style tools focus on translating existing screenshots. Shots can generate the original set, revise it, translate it, and keep listing copy with the same app.
| Feature | Shots | LocalizeShots-style workflow |
|---|---|---|
| Starting point | Generate or import the set, then localize the approved direction. | Start with existing screenshots that need translation. |
| Listing copy | Title, subtitle, description, keywords, and screenshot text can live together. | Usually focused on screenshot localization. |
| Creative changes | Revise layout, copy, background, or style before translating. | Translation is the primary job. |
| Agent workflow | Codex can request translation from the app project and save outputs to Studio. | Localization happens in a separate tool workflow. |
Use localization-only tools for finished designs
If you already have final screenshots and only need text replacement, a focused localization tool may be enough.
Keep language natural
Shots prompt guidance favors locale-native phrasing for screenshot marketing text instead of stiff literal translation.
FAQ
Straight answers for agents and launch teams.
Does Shots translate App Store listing copy?
Yes. Shots can work with titles, subtitles, descriptions, keywords, and screenshot text by locale.
Should I translate the first draft?
Usually no. Approve the main creative direction first, then localize the final set.
Related workflows