DroidKit Nothing is uploaded

Writing a Play Store listing that survives being cut off

17 November 2026

Play gives you 30 characters of title, 80 of short description and 4000 of full description. Almost nobody reads the 4000. The listing is won or lost in the first two screenshots and the first line of text, and most of what you write is cut off before it is ever shown.

The limits, and where they actually bite

FieldLimitWhere it gets cut
App title30Search results cut well before 30 on narrow screens
Short description80Shown in full under the title on the listing page
Full description4000Collapsed after a few lines behind "Read more"

The title limit is the one that misleads people. You get 30 characters in Play Console, so 30 feels like the target. In a search results list on a small phone, with a font the user may have scaled up, a title is often cut around the high teens.

Put the word that identifies your app at the front. A title in the shape of "AppName: Thing It Does" survives truncation, because the half that disappears is the half the user can infer.

The short description does the selling

Those 80 characters sit directly under your title and are the most-read text in the whole listing. They should say what the app does for the person reading, in plain words, without repeating the title.

Keyword stuffing here reads as spam to a human and does not help as much as people hope. One clear sentence outperforms a comma-separated list of search terms.

The full description, and the "Read more" line

Play collapses the full description after a few lines. Everything below that fold is read only by people who already want the app and are looking for a reason to be sure.

So the first two lines carry the weight. Write them as if they were the whole description, then use the remaining space for the detail that answers a hesitation: what it costs, whether it works offline, what it does not do.

Being explicit about limitations in the description is worth more than it costs. An install from someone who understood the app is worth several from people who are about to leave a one-star review because it did not do a thing you never claimed.

The assets, and the rules that reject them

Icon

512 × 512 PNG, 32-bit. Play rounds the corners itself, so send a full square. The two recurring rejections are an alpha channel and corners that were already rounded in the source file.

Feature graphic

1024 × 500, and no transparency. This one catches people constantly, because a PNG exported from a design tool keeps its alpha channel even when nothing in the image is transparent. The upload fails with a message about the format and the file looks completely fine when you open it. Flatten it onto a solid background and re-export.

Screenshots

Between 320 and 3840 px on each side, no wider than 2:1, and you need at least two to publish. Eight is the maximum.

Only the first two screenshots exist

On most devices, two screenshots are visible without scrolling. Treat the rest as material for people who are already interested.

Which means the first two should show the single thing that makes someone install, not your onboarding screen and your settings page. A raw screenshot asks the viewer to work out what they are looking at; a short caption above it tells them. Keep captions to a few words about what they get rather than what the screen is called. "Everything in one place" does more than "Home screen".

Things worth checking before you upload

The Play Store Listing Preview shows where your title gets cut at real search-result widths and inspects your uploaded assets for the transparency and dimension problems that cause rejections. For the screenshots themselves, the Screenshot Framer adds a device frame, background and caption and exports at sizes Play accepts. Both run in your browser, so unannounced listing copy stays on your machine.