How to Write a Google Play Full Description
Play gives you 4,000 characters. Google’s own example of what fails is a comma list of synonyms. Here is the structure that stays inside that rule.
Quick answer
How long is a Google Play full description, and what should it say?
The Google Play full description allows 4,000 characters. The short description is a separate 80-character field, and Google says not to repeat it in the full description. Write the job, the audience, and the mechanism in the first few sentences, because users may only read those. Do not paste a keyword list. Google’s own bad example is a block of synonyms like “car racing, car driving, race cars.”
- Full description: up to 4,000 characters
- Short description: 80 characters, and it must not be copied into the full description
- Users may only read the first few sentences
- Repetitive word blocks violate Play’s metadata guidance
- No ranking claims, prices, or anonymous testimonials
On this page
- Key takeaways
- Two description fields, two jobs
- The sentence Google uses as the bad example
- Put the job in the first few sentences
- A full description that would survive the policy page
- Policy traps that show up in real listings
- The first screenshot has to match sentence one
- Write and ship a Play full description
- Play full-description questions
The Google Play full description is the long box under the screenshots. It holds 4,000 characters. Most indie listings either leave it as a feature dump or fill it with the same noun twelve times because someone said Android indexes every word. Google does not publish a keyword-count formula. What it does publish is a ban on repetitive word blocks, and an instruction to put the useful part first.
The rules live in Best practices for your store listing and the metadata policy . The 80-character line above this field is a different job — see the Google Play short description guide. Count both in the ASO Character Counter before you paste into Play Console.
Two description fields, two jobs
Play’s help article uses two names for the short field. In the description section it is the short description: 80 characters, a summary of the biggest benefits. In the next section it is the promotional description: the short text that can appear in search results. Same 80-character box. The full description is the other box, up to 4,000 characters, and Google says not to repeat the short description inside it.
| Field | Limit | What Google says it is for |
|---|---|---|
| App title | 30 | Name the app. Unique, no “Free,” no ranking claims, no emoji stacks. |
| Short / promotional description | 80 | Biggest benefits, in a line people can read on a search card. |
| Full description | 4,000 | Accurate functionality. Succinct. First sentences do the work. |
The 80-character line can show up in search. The 4,000-character full description is the listing body. Do not paste one into the other.
The sentence Google uses as the bad example
Play’s listing guidance says to avoid excessive length, detail, improper formatting, and repetition of words. The example they print is not a long essay. It is this: “Car racing, car driving, race cars, car races, race track, driving, drive, race, cars, vehicles, automobiles, trucks.” A block of words in a list is not a description. Everyday language is.
That example is why an App Store keyword export is the wrong input. Apple’s 100-character field is supposed to look like habit,streak,journal. On Play, that shape is the pattern the help article tells you not to ship. Write sentences a person would say out loud. Put extra terms in those sentences only when they name a real feature.
The store-by-store split is in App Store vs Google Play ASO. On iOS, the long description is conversion copy. On Play, the full description is still listing metadata, which means the metadata policy applies to every sentence — including translations.
Put the job in the first few sentences
Google’s line is blunt: keep the description succinct, because users may only read the first few sentences. You do not need to hit 4,000. A 900-character description that says what the app does will beat a 3,800-character synonym pile. Use the length for structure, not for adjectives.
- Sentence one: the job and who it is for. “Send invoices from your phone if you already have the client and the rate.”
- Sentence two: the mechanism, in product language. “Turn a photo of a receipt into a PDF and a payment link.”
- Then a short “how it works” in three or four sentences, in the order a new user actually taps.
- Then the features that are easy to misunderstand, each as its own short paragraph.
- Then who it is not for. A boundary (“not accounting software, not payroll”) prevents the one-star review you would otherwise earn.
- Stop. Do not add a keyword footer.
A full description that would survive the policy page
This is a fictional invoicing app, written to the structure above. It is not a template to paste. It is a shape: specific, short, and free of the car-racing pattern.
| Block | Copy |
|---|---|
| First sentences | Send an invoice from your phone after the job is done. Built for freelancers who already know the client and the rate, and who do not want a desktop accounting suite. |
| How it works | Add a line item, attach a photo of the receipt, and share a PDF or a payment link. Clients can pay without creating an account. You see which invoices are still open. |
| Boundary | This is not bookkeeping, tax filing, or payroll. If you need a general ledger, use accounting software. This app sends the bill. |
The first sentences name the job and the audience. Later paragraphs explain the mechanism and the boundary. None of them is a comma list.
Policy traps that show up in real listings
| Line | Why it fails |
|---|---|
| The #1 invoicing app on Google Play | Store-performance claim. “#1,” “Best,” and “Popular” are called out by name. |
| “Changed my business!!” — a happy user | Unattributed testimonial. Quotes need a clear source. |
| 50% off Pro this week only | Price and promotional offers do not belong in listing text. |
| Like QuickBooks but simpler and free | Comparison and another product’s name. Stay on your own functionality. |
| invoice invoicing invoices billing bill bills payments | The car-racing pattern. A word block is not a description. |
Ranking boasts, anonymous quotes, prices, competitor names, and synonym lists are the failures Google prints. Functionality is the copy that is allowed.
The first screenshot has to match sentence one
If the opening sentence is “attach a photo of the receipt,” frame one cannot be a logo on a gradient. Play’s screenshot guidance says to highlight in-app experiences and to keep text on screenshots minimal. Write the description, then cut the frames to the same three moments. Size and order are in the Google Play screenshot recommendations. When you have traffic, test one variable at a time with a store listing experiment — the description or screenshot one, not both in the same run.
Write and ship a Play full description
Do this after the 30-character title and the 80-character short description are locked, so you do not spend the opening repeating them.
Write the two opening sentences out loud
Job, audience, mechanism. If a stranger cannot tell what the app does from those two sentences, the rest of the 4,000 characters will not save the listing.
Add how-it-works and a boundary
Three or four sentences in tap order, then one paragraph on what the app does not do. Delete any sentence that could sit on a competitor unchanged.
Hunt the car-racing pattern
Search the draft for a comma list, a word repeated in a row, or a footer of synonyms. Replace it with a sentence or delete it.
Strip policy problems
No #1, no prices, no “free for a limited time,” no anonymous quotes, no other apps’ names. The metadata policy applies to graphics too, so check screenshot captions in the same pass.
Count, then match frame one
Stay under 4,000. You do not get a prize for using all of them. Then make sure the first Play screenshot shows the action in sentence one.
Play full-description questions
What is the Google Play full description character limit?
4,000 characters. The short description is a separate field at 80 characters or less. Play Console shows a counter on each field. You do not need to use all 4,000.
Should I repeat keywords in the full description?
Name a feature when you are describing that feature. Do not stack synonyms. Google’s published bad example is a list like “car racing, car driving, race cars.” The metadata policy also bans repetitive or unrelated keywords. Google does not publish a required mention count.
Does the full description show in Play search?
Play’s help article says the short promotional description appears in places like search results. The full description is the long listing text users read to decide whether to try the app, and Google warns that users may only read the first few sentences. Write those sentences for a person, not for a scraper.
Can I paste my App Store description into Play?
Only if you rewrite it. Apple tells you not to stuff the iOS description for search. Play tells you not to use word blocks and not to repeat the short description. The same prose can be the starting point. The comma list from the iOS keyword field cannot.
Sources, verified 2026-09-22:
Need store-sized exports? Use the App Store screenshot generator or the Google Play screenshot generator.
Keep reading
Google Play Short Description: 80 Characters That Rank
Play indexes the 80-character short description and shows it on search cards. How to write one that ranks and still reads like a human.
App Store vs Google Play ASO: What Indies Should Do Differently
The stores look similar. Indexed fields, screenshots, descriptions, and ranking signals are not. One checklist per store.
How to Write an App Store Description That Converts
Apple’s description is 4,000 characters of conversion copy, not a keyword essay. Structure, first-sentence rules, and why a “description generator” still needs you.
Play Wants Four Screenshots. Two Just Publishes.
Google Play will ship a listing with two screenshots. The large recommendation surfaces that actually use screenshots ask for four frames at 1080px or larger. That gap is how indie Android apps stay live and stay invisible.
App Store & Google Play Character Limits (2026)
Exact character limits for every App Store Connect and Google Play metadata field - name, subtitle, keywords, promo text, descriptions - plus how to use each one.
Google Play Store Listing Experiments: A Practical Guide
How to test a Play Store icon, screenshots, feature graphic, or video without fooling yourself with a tiny sample or a muddy hypothesis.
Free tools that help here
Top App Store Apps
Track Apple App Store top charts across 30 countries. View top free and paid rankings for ASO research - updated from Apple's public RSS feed.
ASO Character Counter
Count characters for every App Store and Google Play metadata field against exact store limits. Live counts and over-limit warnings - nothing gets truncated at submission.
Screenshot Beautifier
Add polished backgrounds, padding, shadows, and rounded corners to any screenshot in seconds. Perfect for social posts, docs, and portfolios.
The description explains the job. Screenshots prove it.
Once the first sentences are honest, the first Play frames have to show the same feature. AppGrowthKit turns real app screens into editable, store-ready screenshots for Google Play and the App Store.
Try AppGrowthKit for Free