6 fields, every cap checked
Listing Kit
One sheet instead of six tabs
App Store Connect asks for six pieces of text, each with a different limit: app name and subtitle at 30 characters, the keyword field at 100, promotional text at 170, and the description and What’s New at 4,000 each. Overrunning any of them is a rejected field at the worst possible moment.
Pick an app and the name, description and What’s New arrive from the live listing. The subtitle, keyword field and promotional text cannot — Apple does not publish them for any app — so those start empty and stay empty until you paste them.
About this tool
Every App Store Connect metadata field on one sheet
Submitting a listing means filling a dozen fields across several screens, each with its own cap, and discovering an overflow after you have written the copy. This puts every field on one page with live character validation and a CSV export.
Load a live app to prefill what Apple publishes, then fill the rest and check it before you paste anything into App Store Connect.
How it works
- 1Pick an app, or start blank. One request prefills the fields Apple exposes.
- 2Each field shows characters used against its cap, validated by the same rules the metadata checker and release notes writer use, so no two pages here can disagree about a limit.
- 3Fields Apple does not publish start blank behind a badge saying so.
- 4Export to CSV when it is ready.
What it cannot tell you
- Subtitle, keyword field and promotional text are genuinely absent from Apple’s public API — verified across three apps and both endpoints, where the keys do not exist rather than being empty. They start blank and are never guessed.
- It validates caps and mechanics, not quality. Whether the copy is any good is not a character count question.
- It cannot submit anything. This produces a sheet you paste from.
Questions
What are the App Store metadata character limits?
Name 30, subtitle 30, keyword field 100, promotional text 170, description 4,000 and What’s New 4,000. Every field here validates against those live.
Why can I not prefill the keyword field from a live app?
Because Apple never exposes it. Subtitle and promotional text are absent from the public API too — those three fields are flagged rather than filled with a guess.
Can I use this for a localized listing?
Yes — fill it per language. The localized metadata writer drafts a first version for any of the 38 App Store languages, and this is where you check what it produced.
Written up on the blog
- App Store screenshot sizes — you need two sets, not eightApple lists dozens of accepted screenshot dimensions, but only two display sizes are required. Everything else scales from what you upload. Here is the chain, from Apple's own reference.
- The App Store hides a keyword field. Google Play reads your description.Apple names four text inputs for search, not the description. Google names the description and has no keyword field. Both halves, sourced at each vendor.
- Most of your App Store description is never read, and the cut point is not a numberApple documents the 4,000-character limit and says nothing about where the text is cut. Here is why no fixed character count can be right, and what one real listing lost above the fold.
Listing & metadata
Or browse every free App Store optimization tool.