
When users look at your screenshots, where are their eyes actually going?
The answer may not be what you think. Eye-tracking research shows that users scan app screenshots in an F-shaped path: first a horizontal sweep across the top, then a shorter horizontal sweep across the middle, and finally a vertical scan down the left side.
What this means for screenshot design: where you put content decides whether users see it.
Nielsen Norman Group's eye-tracking research found that when users browse web content, their gaze follows an F shape:
The same pattern holds for app screenshots.
Picture your screenshot as an F-shaped heat map:
[■■■■■■■■■■■■■■■■■] ← First gaze zone (hottest)
[■■■■■■■■■■ ] ← Second gaze zone (warm)
[■ ]
[■■■■■■ ] ← Third gaze zone (fairly warm)
[■ ]
[■ ] ← Left vertical scan zone
Conclusion: the top and left side get the most attention; the bottom-right corner is the easiest to ignore.
If your screenshot uses a split layout (text on the left, visual on the right), the core copy should sit at the top left: the first place the gaze lands in the F-pattern.
| Position | Gaze heat | Recommended content |
|---|---|---|
| Top left | ★★★★★ | Core value proposition (your single most important line) |
| Top right | ★★★★ | App UI / result showcase |
| Middle left | ★★★ | Features / data |
| Middle right | ★★ | Supporting visuals |
| Bottom | ★ | Least important / optional content |
The two horizontal bars of the F are the only places users actually "read". The headline must have:
Put subheadlines and feature tags in smaller sizes along the left vertical scan line: users don't need to read them in full, just catch the keywords.
The F-pattern shows users pay significantly less attention to the right side than the left. So the right side should hold:
Not:
[ Core value proposition (large, bold) ] ← F top bar
[ ]
[ App UI / result showcase ] ← F middle bar zone
[ ]
[ Feature tag 1 Feature tag 2 ] ← F stem, left side
Key points: the headline spans the full width; feature tags are left-aligned.
[ Core | ] ← F top bar
[ value | App UI ]
[ prop. | screenshot ]
[ Feat 1 | ] ← F stem
[ Feat 2 | ]
Key points: the left side is the text zone, ordered top to bottom following the F; the right side is the visual zone.
[ ]
[ Oversized visual ]
[ + short bottom headline ] ← Departs from the F; relies on visual impact
[ ]
Note: this layout doesn't follow the F-pattern; it relies on the visual's appeal. It only suits apps whose visuals are the core selling point (photography, drawing, wallpapers, etc.). For other apps, prefer an F-pattern layout.
Besides the F-pattern, there's also a Z-shaped scanning pattern:
[1━━━━━━━━━━━━━━━━━━━━━━2]
↕ ↕
[4━━━━━━━━━━━━━━━━━━━━━━3]
The gaze moves from the top left (1) to the top right (2), diagonally down to the bottom left (3), then across to the bottom right (4).
The Z-pattern suits: landscape screenshots, Feature Graphics, and quick scans of the first screenshot.
Choosing F vs Z:
Don't want to research layouts and font sizes by hand? AppShot Maker (appshotmaker.com) templates are already optimized for F-pattern visual hierarchy: the positions of the headline, feature tags and visuals are eye-tracking-validated, so you just fill in your content to get a high-converting screenshot layout.
Users "scan" your screenshots, they don't "read" them. F-pattern visual hierarchy means:
Don't put content where users won't see it. Design along users' line of sight, not against it.