Free App Store Character Counter (iOS & Android Metadata Limits, Checked Instantly)

Every App Store and Google Play metadata field has a hard character limit, and neither store tells you how close you are while you type in most editors. Go over, and your save gets rejected or your text gets truncated mid-word in search results. This is a free, no-signup character counter that checks every field against the real 2026 limits for both stores as you type.

Try it directly: WhixFrame Character Counter.

What This Tool Does

Paste your app name, subtitle, keyword field, promotional text, or description into the counter and it shows a live count against the correct limit for that specific field and platform, with a progress bar that turns amber near the limit and red once you are over. It is built for indie developers and ASO managers who are finalizing a listing and want to stop guessing or counting in a text editor.

Why Exact Character Limits Matter

Going over a limit is not a review rejection risk the way a broken privacy policy URL is. It is a display and submission problem: App Store Connect and Google Play Console will either refuse to save the field or silently truncate it, sometimes mid-word, in a way you will not notice until you check the live listing. The subtitle field is worth extra care since it is indexed for search on iOS, so wasting characters on filler words costs you keyword coverage, not just cosmetics.

iOS vs. Android Character Limits (2026)

Apple has no dedicated keyword field equivalent on Google Play; Google ranks primarily on the visible title and description text instead, which is why the same ASO copy strategy does not transfer directly between the two stores.

A Worked Example: Fitting a Real App Name and Subtitle

Say you are launching a habit-tracking app called "Streakly" and want to work a category keyword into your metadata. On iOS, "Streakly" is 9 characters, leaving 21 characters of your 30-character app name budget. "Streakly: Habit Tracker" uses all 24 characters and reads naturally, still leaving 6 characters of headroom. Your 30-character subtitle is separate and indexed for search, so it should not repeat "habit tracker" again. Something like "Daily Goals & Streaks" (22 characters) covers different keyword territory instead of wasting the field on a repeat.

On Google Play, the same app name has 30 characters to work with but no separate subtitle field, only an 80-character short description. "Streakly" leaves 71 characters for a benefit-led line, for example "Build daily habits and streaks that actually stick" (52 characters), which both fits comfortably and reads as a pitch rather than a keyword list, since Google Play's algorithm evaluates natural language quality more than exact keyword matches.

How to Spend the 100-Character Keyword Field

Apple's hidden 100-character keyword field is comma-separated and invisible to users, so every character should carry search weight, not readability. A few rules that make a real difference:

• Do not repeat words already in your app name or subtitle. Apple already indexes those fields; repeating a keyword there in the keyword field wastes characters that could cover a new term entirely.
• Skip spaces after commas. "habit,tracker,goals" indexes the same as "habit, tracker, goals" but saves 2 characters per comma, which adds up across a full field.
• Use singular forms only when Apple\'s matching is known to stem plurals for that term, and when unsure, test both in separate updates rather than guessing.
• Prioritize terms with real search volume over exact brand-adjacent terms nobody actually searches for.

Emoji, Accents, and Non-Latin Characters

Character limits count Unicode characters, not bytes, so an accented letter like "é" or an emoji each count as 1 character toward your limit in most cases, the same as a plain letter. That said, some emoji are technically multiple Unicode code points combined (for example, flag emoji or emoji with skin-tone modifiers), and how a given tool counts them can vary. If you are localizing into a language with non-Latin script, such as Japanese or Korean, a 30-character limit still means 30 characters in that script, not 30 Latin-equivalent words, so translated metadata often communicates more per character than the English original and needs separate review rather than a direct translation pasted in unchanged.

How to Use It

1. Open the free character counter, no account needed.
2. Paste your draft app name, subtitle, keyword field, and description into the matching fields.
3. Watch the live count and progress bar for each field against its real limit.
4. Trim or rewrite anything flagged red before you paste it into App Store Connect or Google Play Console.

Common Mistakes

Frequently Asked Questions