Table of contents
- Quick nav
Game vs Utility App Store Screenshots: Different Jobs, Different Layouts
One playbook doesn't fit both
Most screenshot advice is written as if every app were the same: big caption, device frame, one benefit per frame. That advice works well for a habit tracker. It works much less well for a puzzle game, a racing game, or an RPG.
The reason is simple: people browse games and utilities with different questions in mind.
| Utility / productivity apps | Games | |
|---|---|---|
| User's question | "Will this solve my problem?" | "Will this be fun for me?" |
| What sells | A clear outcome | A feeling, a fantasy, a hook |
| Main visual | App UI | Gameplay, characters, worlds |
| Text role | Explains the benefit | Sets the mood, names the genre |
| Device frames | Often helpful | Often unnecessary |
| Orientation | Usually portrait | Matches how the game is played |
Below is a practical breakdown of how to design each, plus the mistakes that come from mixing the two.
Utility apps: sell the outcome, show the proof
People who search for "PDF scanner," "budget tracker," or "screen recorder" already know their problem. Your screenshots need to confirm, quickly, that your app solves it, and that it's pleasant to use.
What works
- Lead with the outcome, not the feature list. "Scan receipts into expense reports" beats "OCR, PDF export, cloud sync."
- Show real UI. Utility users want to see what they'll be using. Hiding the interface behind illustrations raises doubts.
- One task per frame. Each screenshot answers one question: How do I capture? How do I organize? How do I share?
- Readable captions. Short phrases of a few words, large enough to read in search results.
- Trust signals, carefully. Privacy notes ("Works offline"), platform support, or awards you've actually received.
A five-frame template for utility apps
| Frame | Purpose | Example caption |
|---|---|---|
| 1 | The core outcome | "Turn any photo into a clean PDF" |
| 2 | How easy it is | "One tap to scan, auto-crop included" |
| 3 | The differentiator | "Search text inside every document" |
| 4 | Workflow fit | "Share to email, Drive, or Files" |
| 5 | Reassurance | "No account needed, works offline" |
Utility mistakes to avoid
- Five frames that all show the same screen with different captions.
- Long sentences that only make sense at full size.
- Generic stock photos of smiling people instead of the actual product.
- Settings screens. Nobody downloads an app because of its settings.
Games: sell the experience, keep it honest
Game shoppers browse more and search less precisely. They're scanning for genre, art style, and whether it looks like something they'd enjoy. Your screenshots need to communicate what kind of game this is within the first frame.
What works
- Gameplay-first visuals. Show the screen the player actually sees during play, ideally at an exciting moment.
- Clear genre signals. Match-3 boards, cards, maps, or cockpits tell players instantly what they're getting.
- Art style as the hook. For many games, the art is the main differentiator. Give it room; don't shrink it inside a phone frame.
- Short, punchy captions. Mood and verbs work better than explanations: "Build your kingdom," "Race through neon cities."
- Native orientation. If the game is played in landscape, landscape screenshots usually represent it better.
A five-frame template for games
| Frame | Purpose | What to show |
|---|---|---|
| 1 | Hook | The most striking gameplay moment, genre obvious |
| 2 | Core loop | What players do over and over |
| 3 | Progression | Upgrades, new worlds, unlocked characters |
| 4 | Variety or social | Different modes, events, multiplayer |
| 5 | Depth or polish | Bosses, collections, customization |
Game mistakes to avoid
- Cinematic art that isn't in the game. Using pre-rendered key art or CGI that looks nothing like actual gameplay can mislead players and may conflict with store rules about accurately representing the app. If you include key art, make sure the rest of the set shows real gameplay.
- Cluttered HUDs. Hide debug elements, odd currency counts, and tutorial pop-ups.
- Phone frames around landscape gameplay. They shrink the art and add little.
- Paywall or purchase screens as selling points. Focus on play, not the store.
Where the two overlap
Some apps live in between: fitness apps with game mechanics, language learning with streaks, kids' learning games. Here, borrow from both:
| Hybrid type | Borrow from utility | Borrow from games |
|---|---|---|
| Gamified fitness | Clear outcome ("Run your first 5K") | Badges, streaks, energy |
| Language learning | Lesson UI clarity | Progress, rewards, characters |
| Brain training | Science-based framing, carefully worded | Puzzles, levels, score screens |
| Kids' learning | Parent-facing reassurance | Bright, character-driven art |
For kids' categories, remember that both stores have additional rules for content and marketing aimed at children.
Captions: length, tone, and placement
| Element | Utility apps | Games |
|---|---|---|
| Length | Short, but can be a full benefit | Very short, often 2–4 words |
| Tone | Clear, practical | Evocative, energetic |
| Placement | Above or below the UI | Over the art, in a safe zone |
| Typography | Clean sans-serif | Can match the game's style, but stay readable |
| Numbers | Specific, verifiable ("Export in 3 formats") | Avoid fake stats ("10M players") unless true |
Device frames: when to use them
- Utility apps: Frames can help signal "this is a phone app" and make the UI feel premium, especially on the first frame. They're optional, not required.
- Games: Usually skip frames. Full-bleed gameplay is bigger, more immersive, and closer to what players will see.
- Exceptions: A game that relies on a special interaction (tilt, AR, a companion watch) can use a frame or hand-held context to explain it.
If you do frame utility screenshots, a free mockup tool like appshotmaker.com can apply consistent device frames and export store sizes in one pass.
Testing what works for your category
Category norms are a starting point, not a rule. Use the tools each store provides:
- App Store: Product Page Optimization lets you test alternative screenshot sets against your original.
- Google Play: Store listing experiments let you test graphics and text on your main or custom listings.
Good first tests:
- Utility: outcome-led caption vs feature-led caption on frame 1.
- Games: gameplay-first vs key-art-first on frame 1.
- Both: portrait vs landscape, if your app supports both.
Summary
Utility screenshots sell a clear outcome with real UI and readable captions. Game screenshots sell an experience with honest gameplay, strong genre signals, and minimal text. Pick the playbook that matches what your users are asking when they land on your page, then test the first frame, where the decision is usually made.