Short answer: Korea second, done deep

Korea should be your second non-English App Store locale after Japan: top-tier revenue per user, gaming and productivity spend, and thin indie competition. Ship the ko locale with Hangul keywords plus the English terms Korean shoppers use, packed comma separated with no repeats, plus translated screenshots to match. Wait two weeks, then judge downloads after two months.

Why Korea earns your second App Store locale slot

Korea pairs some of the highest revenue per user in mobile with shoppers who discover apps through search, and that mix makes it the best second bet after Japan. AppScreenshotStudio ranks Korean fifth of its seven priority markets for 2026, after the US baseline, Japan, China, and Germany, and notes high engagement and spending in gaming, productivity, and fintech, with Korean revenue per user near the top of the world through in-app purchases and subscriptions. LocalizeRank puts South Korea fourth in its indie order, after Japan, Germany, and France. The mechanism is simple. Your Japan win proved one deep market pass beats five shallow ones, and Korea is where that same pass buys the most next. Korean shoppers search in a mix of Hangul and English terms, most indie rivals serve Korea in English, and one focused Korea pass turns that gap into downloads. Fund Korea from the Japan result, read the numbers, then roll the playbook onward with money the first two wins paid for.

One honest question comes up at this point: why not Germany, since the alphabet matches? Familiar letters don't pay your rent. Revenue per user does, and Korea beats every European market on that number while matching Germany on iPhone spending power. Our localization strategy guide orders later waves the same way: fund what pays, then expand. Germany is a fine third market. It's a worse second one.

Korean keywords run on Hangul plus the English shoppers use

Korean shoppers don't search in one script the way a translation tool assumes. They type category terms in Hangul and mix in English brand and tech terms they already know, sometimes in the same search session. Translate your English keyword field word for word into Hangul and you'll miss every shopper who searches the English term, while a pure-English field misses everyone else. The Korean voiceover guide that covers this market best states the rule plainly: keep Korean and English variants visible during research, and decide from observed usage instead of a rule that every English word must go.

Build the field from evidence, not instinct. Open the Korean storefront and search the way a shopper would: category terms in Hangul, your feature terms in both scripts, and the English terms rivals keep in their titles. Collect each candidate with its meaning and intent, then pack the 100-character keyword field the same disciplined way our keywords-field guide teaches for every locale. Four rules keep the Korea field tight:

  • Gather Hangul terms from Korean search suggestions and rival titles; keep English terms only where top Korean charts show shoppers using them.
  • Write commas with no spaces and drop duplicates across title, subtitle, and keywords, since Apple reads the fields together.
  • Favor terms rival Korean titles repeat; those repeats are validated demand.
  • Cut brand names you do not own, vague promises, and filler words; each of the 100 characters must earn its slot.

One honest limit shapes this work. Free heuristics can surface candidate terms from your listing and rival titles, but they can't show search volume per term the way paid ASO tools do. Our cost guide prices the research step so you know what each added hour buys. Collect thirty candidates, keep the best mix that fits one hundred characters, and ship. You can refine after indexing tells you which terms moved. If a later editor swaps a chosen term for a smoother synonym, make them show search evidence first, because synonyms with different search behavior are how Korea fields quietly break.

Screenshots that sell in Korea

Screenshots decide the Korea pass more than keywords do, because shoppers see art before they read anything. A Korean title above English screenshots reads as unfinished, and a fully translated set in the wrong tone reads as foreign. Korean runs on Hangul, a phonetic script that compresses well, so captions typically land shorter than their English equivalents. That compression is a gift: shorter captions leave room for denser proof panels without crowding the frame. Our screenshot translation guide walks through the re-render session frame by frame.

Three Korea specifics go beyond translation. First, get the register right. Korean has distinct formal and informal registers, and the wrong one for your category (formal for a casual game, informal for fintech) signals a non-native team before shoppers read a second frame. Match the tone rival Korean listings in your category use. Second, respect the density norm. Korean shoppers tolerate high information density, between US and Japanese norms, so proof panels (ratings, streaks, before and after) can carry more content than your US set. Third, tune the visuals per category: anime and character art convert in gaming and entertainment, while soft gradients, glossy product shots, and local color cues work in lifestyle, beauty, and shopping. Off-pattern creative reads as a non-local app. Three checks, one export pass:

  • Every visible string in Korean at the right register, set in a font with full Korean coverage such as Apple SD Gothic Neo.
  • Proof frames (results, streaks, ratings) ahead of promise frames, using won pricing, YYYY/MM/DD dates, and period decimals where numbers appear.
  • At least one frame with local-feeling faces or category-typical art, not imported stock.

Ship both required sizes per frame (iPhone 14 Plus 1284x2778 and iPad Pro 12.9-inch 2048x2732) so the set looks finished on every device. Then run one visual QA pass with a native speaker if you can find one: our QA pass guide orders the check as text, then keywords, then visuals, so a single sitting catches caption errors and art errors together. A Korea set with one English frame left inside will draw the one-star review that mentions exactly that frame.

Adding the Korean locale in App Store Connect

The mechanics take minutes once the words and art are ready. Korean ships as its own locale, and every field below must be filled before the set feels complete to shoppers or reviewers.

  1. Open App Store Connect, pick your app, and add Korean (ko) under the localization list for the version.
  2. Fill the title (30 characters), subtitle (30 characters), and keyword field (100 characters) from your packed Hangul-plus-English set.
  3. Paste the Korean description and promotional text, then upload the Korean screenshot set for each device size you support.
  4. Sweep every locale before submitting: titles inside caps, screenshots matching their language, no English frame hiding in the Korean set.
  5. Submit and expect 24 to 48 hours for metadata review; one flagged locale holds the whole version, so the sweep in step four is the schedule.

One stacking note saves future work. The Korea storefront pairs Korean with English (U.K.) as its secondary locale, so the no-repeat rule from our cross-localization guide applies: don't burn characters repeating a keyword across both locales when each slot could rank for a new term. Set that split once and it keeps paying every wave after.

How App Store Localizer handles the Korea pass

Paste your public App Store URL and the tool pulls your title, description, icon, and screenshots through Apple's public lookup API, so the Korea pass starts from your real listing instead of a blank form. It translates the title, subtitle, description, and the 100-character keyword field into Korean, re-renders your screenshots with translated captions, and covers around twenty target locales with Korean among them. You get both device sizes out of the same session (iPhone 14 Plus plus iPad Pro 12.9-inch), plus ASO keyword heuristics built from free signals over your listing. One afternoon takes you from an English-only listing to a review-ready Korean set.

The price is one-time, not a subscription: the Starter package covers three languages for one listing at $19.99, and the Global package covers every supported language at $99.99. That pricing fits the fund-each-wave model in this guide: Japan first, Korea from the result, Germany next. Two limits to respect: the output is machine-generated, so a native-speaker review pass still earns its fee before submission, and the tool handles store listing copy only, not in-app strings or Google Play. Download the assets or publish straight to App Store Connect, then start your two quiet weeks.

Frequently asked questions

  • Why should Korea come second instead of Germany? Korea beats every European market on revenue per user while matching Germany on spending power, and most indie rivals still serve Korea in English. Germany is a fine third market. It's a worse second one, because familiar letters do not convert the way top-tier spending does.
  • Should my Korean keywords be all Hangul, or do I keep English terms? Keep both, chosen from observed usage. Korean shoppers search category terms in Hangul and mix in English brand and tech terms they know. Research on the Korean storefront, keep each variant whose rivals repeat it, and cut English terms the charts do not show.
  • Do Korean screenshots need more than translated captions? Yes. Match the formal or informal register your category uses, use the density tolerance for proof panels, tune art per category, and set type in a font with full Korean coverage. Translation alone without those four steps still reads as foreign to shoppers.
  • How long before my Korea localization shows results? Plan one afternoon of active work, one to three days for App Review, two quiet weeks before reading ranks, and six to ten weeks before judging downloads. Change nothing in the first two weeks after launch. Early edits restart the indexing you just paid waiting time for.

Paste your App Store URL at https://asolocalization.com today and draft the whole Korea pass (Korean metadata plus Korean screenshots) in one afternoon. Then give Korea its due: a native-speaker review before submission, two quiet weeks for indexing, and eight honest weeks before the verdict. The market that spends most per user rewards the teams that treat it second, not someday.

If Japan is already live, this is the next afternoon. If it isn't, read our Japan first-market guide, ship that locale, and come back with money the first win paid for.