Screenshot Text Counter

Screenshot text is just pixels in an image — App Store Connect and Play Console never parse or count it, so there is no field to overflow. What enforces brevity is physics: a 6.9″ screenshot displayed as a search-result thumbnail is a few hundred pixels tall on the viewer’s screen. At that scale, a headline needs to occupy a large fraction of the image width to be readable, and a large font plus 40 characters is roughly what fits on one to two lines without crowding the UI you are trying to show.

The 70-character supporting line follows the same logic one level down: it is small enough that it only becomes readable once someone opens your product page, so it should carry secondary detail, not the core message. If your value proposition only makes sense with the supporting line, the headline is not doing its job.

Lead with benefits, not features: “Fall asleep faster” outperforms “Sleep sound library” because it names the outcome the user wants. Each screenshot should make exactly one claim — sets that cram three bullet points per image test worse than sets with one bold line each, because at browsing speed users read at most one line per image before swiping or scrolling on.

Remember that captions are also your cheapest localization lever. The same screenshot art with translated headlines routinely lifts conversion in non-English storefronts by double digits, because a headline in the viewer’s language signals the app itself is localized. Keep source copy short and idiom-free so translations don’t balloon past the guideline — German and Finnish translations often run 30–40% longer than the English original.