This post is based on Korean-language app names; Korean example names are kept as written, with their meaning in parentheses.
AI-generated image
The App Store allows up to 30 characters for an app name, while Google Play’s Korean help page lists “15 Hangul characters (30 English characters)”. To use the same name in both stores, keeping a Korean name within 15 characters is the safest choice. The limits below were checked directly on both companies’ official help pages on 2026-11-07, and the example counts were measured with Geuljasu’s counting function.
How many characters does each store input field allow?
Apple’s App Store Connect help states the app name as “at least 2 and no more than 30 characters”, the subtitle as “can’t be longer than 30 characters”, promotional text as 170 characters, the description as 4000 characters, and keywords as 100 bytes. Google Play Console help shows the limits for app name, short description and full description in a table.
| Field | App Store | Google Play |
|---|---|---|
| App name | 2 to 30 characters | Korean page “15 Hangul (30 English)”, English page 30 |
| Subtitle | up to 30 characters | no such field |
| Short description | no such field | 80 characters |
| Promotional text | 170 characters | no such field |
| Full description | 4000 characters | 4,000 characters |
| Keywords | 100 bytes | no such field |
“No such field” means the item does not appear on the two help pages above.
Why treat the Hangul 15 limit separately?
Google Play’s help page words the app name cell differently in its Korean and English versions. The Korean table says “15 Hangul characters (30 English characters)”, while the English table shows only 30. Both versions have a footnote saying the limits apply to both full-width and half-width characters, and the Korean footnote adds that the listed numbers are maximums regardless of character type.
Because the two versions differ, the help page alone cannot tell which one applies on the actual input screen. This post therefore takes the conservative side: keep Hangul names within 15 characters and confirm the final value with the counter on the Play Console input screen.
Counting real app names
| Example name | Characters (with spaces) | 15-Hangul baseline | 30-character baseline |
|---|---|---|---|
| 하루 지출 기록 가계부 (daily expense log ledger) | 12 | pass | pass |
| 하루 지출 기록 가계부 앱 (daily expense log ledger app) | 14 | pass | pass |
| 하루 지출 기록 한눈에 보기 (see daily expenses at a glance) | 15 | exactly at limit | pass |
| 하루 지출 기록 가계부 - 소비 관리 (daily expense log ledger - spending management) | 20 | 5 over | pass |
| Daily Expense Tracker | 21 | not applicable (English) | pass |
| Daily Expense Tracker - Budget Note | 35 | not applicable (English) | 5 over |
A space counts as one character. “하루 지출 기록 가계부” is 9 Hangul characters plus 3 spaces, 12 in total. Cutting spaces, as in the 15-character example, buys extra room.
A sequence for settling the name
Keep the core name short and move the feature description to the App Store subtitle (30) or the Google Play short description (80); that touches the limits least. Chaining long search terms into the name field hits the limit easily, so a short name is better.
FAQ
Can I use the same name in the App Store and Google Play? By limits alone, a Korean name of 15 characters or fewer passes both stores. Whether the name is already used by another app must be checked separately in each store.
Do spaces count? In Geuljasu’s counting, a space is one character. The official help pages do not explain space handling, so confirm the final value with the counter on each console input screen.
How is the 100-byte keyword limit different from characters? Apple’s help gives keywords in bytes, not characters. A Hangul character is 3 bytes in UTF-8, so the example “하루 지출 기록 가계부” is 12 characters but 30 bytes. You can see bytes together with characters in the character counter.
To check whether a draft exceeds a limit and trim the excess, use Fit text to a limit. Platform policies can change, so recheck the official help pages and input screens before submitting.