All posts

Google Play store listing for a first app: pre-submit check

· 6 min read

Your first Google Play listing is more than a name and a few pictures. Play Console asks for text, an icon, a feature graphic and screenshots. Google's Metadata policy then sets rules on what you may write and show. This post goes through the required fields, the graphic assets, what the policy forbids, and a check to run before you submit. I checked Google's pages in November 2026. They change, so check them again before you rely on them.

The text fields

Google's Store listings page gives these limits:

  • App name: 30 characters.
  • Short description: 80 characters. Users can expand it to see the full description.
  • Full description: 4,000 characters.

The page says the limits apply to both full-width and half-width characters. It also says a contact email address is required. Other details, such as the package name and whether the app is free or paid, are set when you create the app. Check that page for the full list.

The graphic assets

Google's page Add preview assets to showcase your app lists the specs:

  • App icon: 32-bit PNG (with alpha), 512px by 512px, maximum file size 1024KB.
  • Feature graphic: JPEG or 24-bit PNG (no alpha), 1024px by 500px.
  • Screenshots: JPEG or 24-bit PNG (no alpha). Each side must be at least 320px and at most 3840px. You can add up to 8 screenshots for each supported device type. You must provide a minimum of two screenshots across different device types to publish your store listing.
  • Preview video: one video, added as a YouTube URL. Its privacy setting must be public or unlisted, not private.

For Chromebooks and tablets, the page says you can add a minimum of 4 screenshots, with a 16:9 aspect ratio for landscape and 9:16 for portrait. It also recommends at least four screenshots at 1080px or more for your app to be eligible for recommendation formats. Those are recommendations, not rules for a first listing.

What the Metadata policy does not allow

This is where first listings get flagged. Google's Metadata policy says it doesn't allow apps with "misleading, improperly formatted, non-descriptive, irrelevant, excessive, or inappropriate metadata". The policy covers "the app's description, developer name, title, icon, screenshots, and promotional images". In plain words:

  • Titles, icons and developer names: no emojis, emoticons or repeated special characters. Avoid ALL CAPS unless it is part of your brand name. The title must be 30 characters or less.
  • Ranking claims: no text or images that indicate store performance or ranking. Google's examples are "App of the year" and "#1".
  • Price and promotions: no text or images that indicate price and promotional information. Examples: "10% off" and "$50 cash back".
  • Google Play programs: no text or images that suggest a Google Play program, such as "Editor's choice" or "New".
  • Keywords: avoid repetitive or unrelated keywords or references. Don't use special characters or all caps to manipulate search ranking.
  • Deceptive claims: Google gives "best game ever" as an example of what not to write.
  • Testimonials: no unattributed or anonymous user testimonials in the description.
  • Names and logos: don't use a celebrity's name or a brand's logo without permission.
  • Length and formatting: "Excessive length, detail, improper formatting, or repetition" can be a violation.

The same page lists inappropriate content too, such as profane language and graphic violence in icons or promotional images. Under its "Do" list it also says to provide screenshots and videos that reflect your app's actual experience. That line is the one I would keep in mind for every picture you upload.

A check to run before you submit

  1. Compare screenshots with the app. Install the build you are releasing. Does every screenshot match what a user sees today? Old screens from an early design are a common mistake.
  2. Read the short description as a stranger. In 80 characters, can someone tell what the app does and who it is for?
  3. Remove claims you can't back up. No "best", no "#1", no badges, no prices or discounts in images.
  4. Check the title. At most 30 characters, no emoji, no stray caps, no keyword list.
  5. Check the testimonials. If you quote users, say who they are or remove the quote.
  6. Check asset specs. Icon 512px PNG, feature graphic 1024 by 500, at least two screenshots, no alpha on the feature graphic and screenshots.
  7. Open the privacy policy link. It must load for anyone, without a login. I covered the rules in the Data safety form post.
  8. Match the Data safety answers to the listing. If the description says "no account needed" but the app asks for a sign-in, one of them is wrong.
  9. Test on a phone. Look at the listing preview on a small screen. Is the first line of the description the one you want shown?

Why the first line matters

Users can expand the short description to read the full one. So the short description does most of the work. Write it first, in plain words, and say what the app does. Then write the full description to back it up. If a sentence in the full description would not survive a stranger asking "is that true?", cut it. A short, honest description is easier to keep correct when the app changes, and you will change the app after launch. Each time you ship an update that changes a screen, check that the screenshots still match.

Do this early

Don't leave the listing for the night before production. It is part of what you set up while the closed test runs. If you are still planning that part, see applying for production access and the pre-launch report and Android vitals. I can't tell you what Google will accept. This post only repeats what its pages say today. Shipping on iPhone too? The Apple side is in the App Store product page check.

Where TestSwap fits

TestSwap is a free site where app makers review each other's apps. It is not affiliated with Google. A tester can't approve your listing, but a stranger can tell you whether the listing matches what they found in the app. That is the same check you just read, done by someone who hasn't seen your screenshots before.

  • Makers post web, iOS and Android apps with a link testers can open or install, like a Google Play testing link.
  • You can add a test login that only signed-in testers see.
  • Everyone starts with 3 credits. Writing a review earns 1, and each review your app receives costs 1.
  • The maker can rate each review 👍 or 👎, and a 👎 takes back the reviewer's credit.

Give testers one clear job, for example "read the store listing, then use the app for 10 minutes and list anything the listing promised that you did not find". I wrote about that in how to write a test task.

Try it

Post your app on TestSwap with a task that sends testers to your listing text and screenshots first. Reviewing someone else's app first is the quickest way to see how it works. Tell me what's missing or broken (@dizid on X).