App Store Screenshot Text Gets Cut Off: How to Fix It

Identify what is going wrong

Open the exported image before editing it. If a word is already missing letters there, the artwork itself needs repair. If the export is intact but the store presentation appears to trim an edge, move the focal content away from that edge and inspect the store preview. Apple advises keeping key elements readable across App Store appearances, placing focal artwork toward the center to avoid unwanted clipping, and using the App Store Connect preview tool to see how assets appear before they go live.

Do not treat every unreadable line as cropping. Google Play warns that small text and backgrounds competing with it may not be visible on many phone screens. Its guidance for Chromebook and tablet screenshots also warns that extra text outside the core app experience can be cut off on Play homepages at certain screen sizes. Check the device type and placement you are designing for rather than assuming one image will look identical everywhere.

Repair the composition, not just the caption

Consider a fictional budgeting-app screenshot. The headline “See all your upcoming bills in one place” sits close to the top edge, while its second line overlaps the bill dates. In the export, check whether the top of the headline is actually missing; in a smaller view, check whether the words and dates can still be distinguished. Even if the headline is intact, enlarging it alone would cover more of the screen.

Revise the headline to “See upcoming bills.” Place it farther from the edge in a clear area beside or above the app capture, and adjust the app capture so the bill names and dates remain visible. If the layout cannot give both elements room, try removing the headline rather than shrinking the dates. The revised image should still let someone recognize the feature from the pictured app, not just from the promise above it.

Apple recommends a short overlay phrase that enhances the visual rather than merely describing it. Google Play advises adding screenshot taglines only when needed to convey key characteristics and limiting them to no more than 20% of the image. Those are reasons to make the message earn its space, not to force a headline onto every screenshot.

If you are preparing the artwork in Minimalist Screens, use any layout, font, or text adjustments available in your workflow to make that revision. The decision belongs to the rendered image: do not assume a shorter line or a different template has fixed the problem until you inspect the result.

Inspect the finished image at two viewing sizes

First, open the final export at full size. Scan every edge for missing letters or artwork, then check that the headline does not cover the dates, controls, or result that make the app screen meaningful. If a line is cut off in the file itself, return to the composition; a store preview cannot restore missing pixels.

Next, reduce the image to a small, listing-like size and read it without zooming in. Ask two separate questions: can you understand the headline at a glance, and can you still identify the important app detail beneath it? For the budgeting example, “See upcoming bills” is useful only if the upcoming dates remain recognizable. If they vanish at the smaller size, give the app capture more area or choose a clearer app state instead of adding more explanatory copy.

Finally, inspect the asset in the destination’s available presentation preview where possible. Apple says the product page preview tool can show how screenshots and other page elements will appear before publication. A local small-size check helps you edit quickly; the store preview checks the surrounding presentation. Revisit the file if either view makes the message or the app evidence hard to see.

This is a composition check, not a substitute for checking export specifications. If only a translated caption fails to fit, review that language’s finished artwork separately rather than shrinking every language’s text to accommodate one version.