All-in-One Metadata Length Checker
PopularValidate every App Store and Google Play text field against its limit in one screen.
Preparing a store submission means juggling eight different character limits across two platforms: 30 for the iOS name and subtitle, 100 for the keyword field, 170 for promotional text, 4,000 for both long descriptions, 30 for the Play title, and 80 for the Play short description. This checker lays all of them out on one screen so you can paste an entire metadata set and see every violation at once.
It is built for the moment before you hit submit — final QA on a new release, a localization batch, or a metadata handoff from a copywriter. One field over its limit is enough to block a submission in App Store Connect or Play Console; here you catch it in seconds instead of at upload time.
How to run a full metadata length check
- 1
Paste each field of your metadata set into its matching input — iOS fields on top, Google Play below.
- 2
Scan the counters: any field over its limit is flagged immediately, before the store consoles reject it.
- 3
Check for near-empty fields too — an 11-character subtitle or a 40-character keyword field passes validation but wastes indexed space.
- 4
Repeat per localization; every language version has its own set of limits and its own overflow risks after translation.
Every App Store and Google Play character limit in one place
On iOS: app name 30 characters, subtitle 30, the hidden keyword field 100, promotional text 170, and the description 4,000. On Google Play: title 30, short description 80, and full description 4,000. The numbers hide asymmetries that trip up cross-platform teams — Play has no subtitle and no keyword field, iOS does not index its descriptions, and only promotional text (iOS) and Play listing text can change without an app release.
The consoles enforce these limits differently, too. App Store Connect hard-blocks over-limit input at save time, which sounds safe until an over-long localized subtitle blocks a release train at 6 p.m. on submission day. Play Console truncates some pasted input silently instead — your 84-character short description becomes an 80-character one that ends mid-word, and nobody notices until it is live.
Why localization is where length checks really pay off
English drafts are usually written against the limits; translations are not. German routinely runs 20–35% longer than English, and a 28-character English subtitle can come back from translation at 41 characters. Multiply that by five iOS text fields, three Play fields, and a dozen locales, and manual checking stops scaling — which is exactly the failure mode this multi-field view exists for: paste a locale’s full set, scan for red, move to the next.
The reverse problem is quieter but costs rankings: translations that come back far under the limit. A keyword field using 60 of 100 characters in Japanese is leaving indexed terms unclaimed in one of the highest-value App Store markets. Treat the recommended-usage guidance as a per-locale target, not an English-only one.
Frequently asked questions
What are all the App Store character limits?
App name: 30 characters. Subtitle: 30. Keyword field: 100. Promotional text: 170. Description: 4,000. Additionally, release notes (“What’s New”) allow 4,000 characters. All limits apply per localization.
What are the Google Play character limits?
App title: 30 characters. Short description: 80. Full description: 4,000. Like Apple’s, all Play limits apply per locale, so each language’s store listing is checked independently.
What happens if a field exceeds its limit at submission?
App Store Connect refuses to save over-limit text, blocking the submission until you trim it. Play Console rejects or silently truncates depending on the field and entry method — the truncation case is more dangerous because the broken text can go live unnoticed.
Are the limits the same in every language?
The character counts are identical across localizations, but they are counted in user-perceived characters — so a Japanese or Korean subtitle can carry far more meaning in 30 characters than an English one, while German translations frequently overflow limits the English draft fit comfortably.
Which of these fields can I edit without an app release?
On iOS, only promotional text updates without a new version and review. On Google Play, all store listing text — title, short description, and full description — can be edited independently of releases. Everything else on iOS waits for your next submitted build.
Which fields actually matter for search rankings?
On iOS: name, subtitle, and the keyword field — descriptions and promotional text are not indexed. On Google Play: title, short description, and full description are all indexed, with title weighted highest. Length compliance is just the entry ticket; ranking comes from what you put in the indexed fields.
Manage every field and locale from one editor
Appalize’s ASO Editor holds your full metadata set for both stores, validates limits as you type in every localization, and pushes approved changes straight to App Store Connect.
Related free tools
App Name Character Counter
Check your App Store app name against the 30-character limit as you type.
Keywords Field Counter (100 chars)
Fit the maximum keywords into Apple’s hidden 100-character field.
Google Play Title Counter
Check your Android app title against Google Play’s 30-character limit and naming policy.
Metadata Diff Tool
Compare two versions of any metadata text with a word-level diff.