Typography is the most underrated part of a screenshot
Store screenshots are viewed small: in search results, in a scrolling gallery, often at arm's length on a phone. The caption is usually the first thing a visitor reads, and if it's hard to read, the message fails no matter how good the UI underneath is.
This guide covers practical typography for screenshot captions: which fonts to consider, how big to set them, and how to keep them readable across devices and languages. There's no single "best font," but there are clear rules for choosing a good one.
What makes a font work for screenshots
A screenshot caption font needs to:
- Stay legible at small sizes. Open letter shapes, generous x-height, and clear distinction between similar characters (I, l, 1; O, 0).
- Have strong bold weights. Captions are usually set bold or semibold to stand out against busy UI.
- Cover your languages. If you localize, the font needs the scripts you ship—Latin with diacritics, Cyrillic, Greek, CJK, Arabic, and so on.
- Be licensed for your use. Marketing images are a commercial use.
- Fit your brand without fighting the UI. The caption shouldn't clash with the typography inside your app.
Font options to consider
Platform system fonts
Using the same typeface your app UI uses creates visual harmony between caption and screenshot. On Apple platforms, that's San Francisco (SF Pro); on Android, Roboto or your app's chosen font.
Licensing caution: Apple's fonts are distributed under a license with specific usage terms. Read the license that ships with the fonts on Apple's fonts page before using them in marketing images—don't assume that "it's the system font" means any use is allowed. If you're unsure, choose an openly licensed alternative.
Open-source sans serifs
Fonts released under the SIL Open Font License (for example, many on Google Fonts) are generally usable in commercial images. Popular choices for UI-adjacent marketing include:
- Inter — designed for screens, very legible at small sizes, wide language coverage.
- Roboto — familiar to Android users, many weights.
- Noto Sans — enormous script coverage, ideal when you localize widely.
- Manrope, DM Sans, Plus Jakarta Sans — slightly more personality while staying readable.
Always check the specific license file for the font version you download.
Brand fonts
If your brand has a custom or licensed typeface, use it—but confirm your license covers digital marketing images and that it supports every language you localize into. A brand font missing Cyrillic or CJK glyphs will fall back to something random in those locales.
Display and script fonts
Thin, condensed, decorative, or handwritten fonts look great in a design tool at 100% zoom and fall apart in a search result thumbnail. Use them sparingly—perhaps for a single word—if at all.
Size: design for the thumbnail, not the canvas
The most common mistake is judging caption size on a full-resolution canvas. A 1320 × 2868 iPhone screenshot is displayed at a fraction of that size on a phone, and smaller still in search results.
Practical rules:
- Preview at thumbnail scale. Zoom your canvas out until it's roughly the size it appears in App Store search results on a phone. If you can't read the caption comfortably, it's too small.
- Make captions big. For portrait phone screenshots, headline captions commonly take a large share of the canvas width. Many effective listings use type sizes that look almost too big at full resolution.
- Limit to one headline and, optionally, one short subline. Body-copy-sized text is invisible on a store page.
- Keep line count low. Two lines is comfortable; three is the practical limit.
Weight, case, and spacing
- Bold or semibold for headlines. Regular weights often disappear against UI.
- Sentence case reads fastest. ALL CAPS slows reading and feels shouty, especially in longer captions.
- Tighten letter spacing slightly for large bold type, loosen it for small text. Default tracking is designed for body sizes.
- Comfortable line height. For two-line headlines, a line height around 1.1–1.25× the font size usually works.
- Short lines. Break captions at natural phrase boundaries: "Track every habit / in one place," not "Track every / habit in one place."
Contrast and backgrounds
Readability depends as much on contrast as on size:
- Put captions on calm areas—a solid or gradient band above the device, not over detailed UI.
- Check contrast ratios. WCAG's 4.5:1 for normal text and 3:1 for large text are useful targets even for marketing images. Our contrast checker tests text and background colors in seconds.
- Avoid thin white text on light photos. If you must place text on imagery, add a darker overlay behind it.
- Pull colors from your app. The color extractor helps build a caption palette that matches your UI.
For a deeper look at readable creatives, see Accessibility & Dynamic Type in Store Screenshots.
Hierarchy across the set
Typography should also be consistent across all frames:
- Same font, same size, same position for headlines on every frame. Inconsistency reads as low quality.
- One accent technique. Highlight a key word with your brand color or weight—not color, underline, and italics at once.
- Consistent alignment. Centered captions are common for portrait screenshots; left-aligned can work for landscape or iPad. Pick one per set.
Localization-safe typography
Captions often grow 20–40% when translated from English into languages like German or French, and scripts like Thai or Arabic have different vertical metrics. To avoid redesigns:
- Leave headroom. Design English captions that fill no more than about two-thirds of the available text area.
- Pick a font family with broad coverage, or define per-script fallbacks deliberately (for example, Noto Sans CJK for Japanese, Chinese, and Korean).
- Support right-to-left layouts if you localize for Arabic or Hebrew—alignment and device placement may need to mirror.
- Rewrite, don't shrink. If a translation doesn't fit, shorten the message rather than dropping the font size on one locale.
See the cultural adaptation guide for more localization practices.
A quick typography spec you can copy
| Element | Recommendation |
|---|
| Font | Legible sans serif with bold weight and needed scripts |
| Headline | Bold/semibold, sentence case, 1–2 lines |
| Subline | Optional, regular/medium, clearly smaller, 1 line |
| Line height | ~1.1–1.25× for headlines |
| Contrast | Aim for ≥ 4.5:1 (or ≥ 3:1 for very large text) |
| Position | Consistent on every frame, on a calm background |
| Test | Preview at search-result thumbnail size |
Putting it into practice
You can set captions, choose positions, and preview store layouts directly in the AppShotMaker screenshot editor, then export store-sized files. Before uploading, run sizes through the screenshot checker. For writing the words themselves, pair this guide with How to Make App Store Screenshots That Convert.
Bottom line
The best screenshot font is a legible, properly licensed sans serif with strong bold weights and the scripts you need. Set captions large, keep them short, ensure contrast, stay consistent across frames, and always judge your typography at the size shoppers actually see.