Quick answer
The short description is capped at 80 characters and exists to sell the app in one line. The full description is capped at 4,000 characters and exists to answer questions. Write the full one first, then compress your best sentence into the short one.
The short answer
> Quick answer: The short description is 80 characters and sells the app. The full description is 4,000 characters and explains it. Write the short one last.
Most developers fill these two boxes in the order Play Console shows them. That's backwards. The short description is the hardest 80 characters in the whole listing, and it's far easier to write once you know what the long one says. I read Google's current metadata pages before writing this. The limits haven't moved. What has changed is how strictly the wording rules get applied.
Most developers fill these two boxes in the order Play Console shows them. That's backwards. The short description is the hardest 80 characters in the whole listing, and it's far easier to write once you know what the long one says. I read Google's current metadata pages before writing this. The limits haven't moved. What has changed is how strictly the wording rules get applied.
The three limits, in one place
App name: 30 characters. Short description: 80 characters. Full description: 4,000 characters. Those are hard caps inside Play Console, not suggestions. The box stops accepting text when you hit the ceiling.
One detail catches people out. The limit counts full width and half width characters the same way. A Japanese or Chinese listing still gets 80 characters. So a localized short description has far more room to say something than the English one does.
One detail catches people out. The limit counts full width and half width characters the same way. A Japanese or Chinese listing still gets 80 characters. So a localized short description has far more room to say something than the English one does.
Where each one actually shows up
The short description is the first text a user sees on your store listing page in the Play Store app. It sits under the app name and the install button. A small arrow expands it into the full description.
So the short description competes with your icon and your first screenshot for the same half second. The full description only reaches somebody who already tapped for more. That person is much closer to installing. The App Store version of this field behaves differently, so don't copy one into the other.
So the short description competes with your icon and your first screenshot for the same half second. The full description only reaches somebody who already tapped for more. That person is much closer to installing. The App Store version of this field behaves differently, so don't copy one into the other.
What the short description is for
Google's own guidance calls it a quick synopsis meant to spark interest by outlining your app's key value. That's a fair description of the job.
One sentence. One reason to care. No feature list.
Google also warns that the short description can appear in places outside your listing, so it has to stand on its own. If somebody reads only those 80 characters, they should still know what the app does. Write it so it survives out of context.
One sentence. One reason to care. No feature list.
Google also warns that the short description can appear in places outside your listing, so it has to stand on its own. If somebody reads only those 80 characters, they should still know what the app does. Write it so it survives out of context.
The 80 characters go faster than you think
Count a real one. "Turn your app screenshots into store ready mockups in under a minute" is 68 characters. Adding a brand name would push it past the cap.
Spaces count. Punctuation counts. That's why generic openers hurt so much. "The best way to" spends 16 characters saying nothing at all.
I counted the wasted words across ten short descriptions I pulled off Play. Six of them opened with the app's own name, which already sits on screen directly above.
Spaces count. Punctuation counts. That's why generic openers hurt so much. "The best way to" spends 16 characters saying nothing at all.
I counted the wasted words across ten short descriptions I pulled off Play. Six of them opened with the app's own name, which already sits on screen directly above.
Words Google rejects in a short description
The preview asset rules name the banned categories directly. No language about Play performance, ranking, awards or user testimonials. No price or promotion language either. The examples Google gives are "Best", "#1", "Top", "New", "Discount", "Sale" and "Million Downloads".
Calls to action are out too. "Download now", "install now", "play now" and "try now" are all named in the same list. The install button is right there anyway.
Calls to action are out too. "Download now", "install now", "play now" and "try now" are all named in the same list. The install button is right there anyway.
Formatting rules most people never read
There's a formatting list buried in the same page. Use periods only if your short description runs to more than one sentence. Line breaks are out. No emoji or emoticons. Repeated punctuation such as two exclamation marks is banned. Decorative symbols like stars are banned too.
Copyright, registered trademark and trademark marks are allowed where they genuinely apply.
Capitalization has its own rule. Don't capitalize for emphasis, and only capitalize your app name if the listing name is capitalized.
Copyright, registered trademark and trademark marks are allowed where they genuinely apply.
Capitalization has its own rule. Don't capitalize for emphasis, and only capitalize your app name if the listing name is capitalized.
What the full description is for
The full description answers the questions the short one raised. Who is this for. What does it actually do. What happens after I install it.
It's also where you handle objections. Does it work offline. Does it need an account. Is there a free tier.
Treat it as the page somebody reads while deciding, not the page that made them look in the first place. The rest of your listing assets already did the attracting.
It's also where you handle objections. Does it work offline. Does it need an account. Is there a free tier.
Treat it as the page somebody reads while deciding, not the page that made them look in the first place. The rest of your listing assets already did the attracting.
4,000 characters is a ceiling, not a target
Google's metadata policy says shorter descriptions tend to give a better user experience, especially on small displays. It then says excessive length, detail, improper formatting or repetition can be a policy violation.
Read that twice. Length on its own can put you out of policy.
I'd treat 1,200 to 1,800 characters as a healthy range for most apps. Games with a lot of modes need more. A single purpose utility needs far less.
Read that twice. Length on its own can put you out of policy.
I'd treat 1,200 to 1,800 characters as a healthy range for most apps. Games with a lot of modes need more. A single purpose utility needs far less.
The first two lines do all the work
Play hides the full description behind a tap, and then the reader still has to scroll. So the first two lines carry the weight a first paragraph carries anywhere else.
Put the concrete promise there. Put the feature list underneath it.
Short paragraphs help more than headers do. Long unbroken blocks read badly on a phone, and Google specifically calls out word blocks and vertical word lists as a common violation of the metadata policy.
Put the concrete promise there. Put the feature list underneath it.
Short paragraphs help more than headers do. Long unbroken blocks read badly on a phone, and Google specifically calls out word blocks and vertical word lists as a common violation of the metadata policy.
Keyword stuffing does nothing here
This one deserves to be blunt. Google states that unnecessary keywords added in an attempt to improve search results will not impact ranking, and that they give users a bad experience.
That is the platform owner saying the tactic doesn't work.
Use the words a real person would type. Use each of them once, inside a sentence that reads normally. A phrase repeated eight times in a full description is a policy risk with no upside attached.
That is the platform owner saying the tactic doesn't work.
Use the words a real person would type. Use each of them once, inside a sentence that reads normally. A phrase repeated eight times in a full description is a policy risk with no upside attached.
Testimonials and comparison claims
Two things get listings pulled more often than people expect. Unattributed or anonymous user testimonials are not allowed in a description. "Users love it" with no source behind it is exactly that pattern.
Data comparisons against other apps or brands sit on the same list of common violations.
If you want social proof, the star rating and the review count already sit above your description. Those are attributed to real accounts. Yours are not.
Data comparisons against other apps or brands sit on the same list of common violations.
If you want social proof, the star rating and the review count already sit above your description. Those are attributed to real accounts. Yours are not.
Capitals, emoji and punctuation
Avoid ALL CAPS unless it's part of your brand name. Acronyms in capitals are fine. Emoji, emoticons and repeated special characters are banned outright in the title, icon and developer name, and the same tone is expected across the rest of the listing.
I've seen plenty of live listings breaking every one of these. That isn't permission. Enforcement is uneven, and it tends to catch up during the review of an update you needed shipped yesterday.
I've seen plenty of live listings breaking every one of these. That isn't permission. Enforcement is uneven, and it tends to catch up during the review of an update you needed shipped yesterday.
Localization is where the limits bite
You get one short description per language, and each one carries the same 80 character budget. German runs long. Japanese packs far more meaning into the same count.
So a straight translation of your English line usually overflows or wastes half the box.
Write each one to the limit in its own language. Our localization guide walks through the workflow. Google asks you to localize as appropriate for each market rather than shipping one language everywhere.
So a straight translation of your English line usually overflows or wastes half the box.
Write each one to the limit in its own language. Our localization guide walks through the workflow. Google asks you to localize as appropriate for each market rather than shipping one language everywhere.
The order that works better
Draft the full description first, in plain sentences, with no keyword thinking at all. Then cut it down to the parts a stranger would still read.
Only then lift the single best sentence out of it and squeeze that into 80 characters.
The short description ends up as a compression of something true instead of a slogan invented on the spot. It also stops the same claim appearing twice, which Google asks you to avoid across your assets.
Only then lift the single best sentence out of it and squeeze that into 80 characters.
The short description ends up as a compression of something true instead of a slogan invented on the spot. It also stops the same claim appearing twice, which Google asks you to avoid across your assets.
The check before you save
Run this list before you publish. App name under 30 characters. Short description under 80, one idea, no call to action, no ranking or price words. Full description under 4,000 and closer to 1,500.
No emoji. Nothing in ALL CAPS. No anonymous testimonials. Every keyword appears once.
Then build the visuals so they match what you just promised. You can frame your screenshots in the browser without opening a design tool at all.
No emoji. Nothing in ALL CAPS. No anonymous testimonials. Every keyword appears once.
Then build the visuals so they match what you just promised. You can frame your screenshots in the browser without opening a design tool at all.
Frequently asked questions
How long should a Play Store short description be?
The hard limit is 80 characters and you should use most of them. One clear sentence about what the app does beats half a feature list. Google counts full width characters the same as half width ones, so a Japanese or Chinese listing gets the same 80. Count it in a plain text editor before you paste, because Play Console trims silently at the cap.
Does the full description affect Play Store search ranking?
Google states that keywords added purely to improve search results will not impact ranking. Write for a reader instead. Cover what the app does in normal sentences and the useful words show up on their own. The app title carries far more weight than either description does, and it only holds 30 characters, so spend those on the words people actually search for.
Can I use emoji in my Play Store description?
No. Emoji, emoticons and repeated special characters are called out in Google's metadata policy. Stars, arrows and decorative symbols fall in the same bucket. Standard punctuation for your language is all you get.
Should the short description repeat the app name?
Usually not. Your app name already sits directly above the short description on the listing page. Repeating it spends characters you can't spare. Say what the app does instead, and let your [screenshots](/blog/play-store-screenshot-sizes-2026) carry the look.
How often should I rewrite these two fields?
Change them when the app changes, not on a schedule. Google asks you to reflect the current state of your app and avoid time sensitive copy that goes stale fast. A description built around a seasonal promotion needs constant maintenance. I check mine whenever a release changes what the first screen of the app looks like.
Build the mockup in your browser.
Drop a screenshot into a real device frame and export at the exact store size — free, no signup.