Language guide

Translate App Store Screenshots to Korean

Korean screenshot localization means translating both the app UI and the captions into Hangul, keeping the spaces between words, wrapping lines at word boundaries and choosing one consistent speech level. StoreLocale produces a single Korean set (ko) that you upload to ko in App Store Connect and ko-KR in Google Play Console.

Last updated:

Which store locale codes should you use?

App Store Connect
CodeLanguageNotes
koKoreanA bare language code, with no region suffix.
Google Play Console
CodeLanguageNotes
ko-KRKoreanRegion-qualified, unlike the App Store code.

Why does Korean keep spaces when Japanese and Chinese do not?

Unlike Japanese and Chinese, Korean separates words with spaces. The W3C Requirements for Hangul Text Layout (opens in a new tab) state in section 5.2 that "in principle, Korean words are separated by spaces." The spacing unit is the eojeol, a word plus any particles or endings attached to it.

This catches teams that reuse a CJK pipeline or copy settings from a Japanese layout. Stripping the spaces from a three-word Korean caption meaning "organize photos easily" leaves one unbroken string that Korean readers struggle to parse.

The opposite mistake happens too. Particles, such as the object markers and the particle meaning "at" or "from", attach directly to the preceding noun, so a space before them is wrong. Watch for it whenever someone edits a caption by hand.

Where should a Korean caption wrap?

KLREQ section 7.1.1 allows two approaches when a line ends in Hangul: break at any syllable, or break only between words. Documents can pick either, but short marketing headlines read far better with word-based breaks.

Syllable-based wrapping can cut the five-syllable Korean verb for "share" after its third syllable, leaving the polite ending alone on the next line. Each Hangul syllable block is a valid break point for a renderer, so check every narrow caption and add a manual break between words where needed.

Which punctuation belongs in Korean captions?

Horizontal Korean text uses the same half-width comma and period as English, per KLREQ section 6.1.2. The full-width ideographic marks 、 and 。 belong to vertical writing, so they look foreign in a horizontal screenshot headline.

Punctuation in horizontal Korean screenshot text
ElementUseAvoid
Full stop. (half-width)。 copied from a Japanese or Chinese layout
Comma, (half-width)、
Headline endingNo period on noun-style headlinesA period added only on some slides

How long does Korean copy run compared with English?

Individual words can be shorter. In the W3C article Text size in translation (opens in a new tab), the English word "views" becomes a two-syllable Korean word, a ratio of 0.8. That ratio already counts each Korean character as two English characters wide, because Hangul glyphs are much wider than Latin letters, so the Korean word is shorter even in width.

Full sentences behave differently from single words. Polite verb endings and particles add syllables, so a three-word English call to action can turn into a longer Korean phrase. Hangul syllable blocks are also dense and need enough size and line height to stay readable in a store thumbnail.

Measure the rendered caption rather than trusting a character count. The text expansion guide compares Korean with other languages.

Which speech level should Korean screenshots use?

Korean grammar encodes politeness in verb endings, and a screenshot set that switches level between slides reads as sloppy. Decide on one approach before translating and write it into the brief for your translator or reviewer.

  • Formal polite endings: sound official, suit finance, health and enterprise apps.
  • Informal polite endings: warmer and conversational, common for consumer products (for example, a polite "Get started").
  • Noun-ending headlines (for example, a Korean phrase meaning "easy photo editing"): short, neutral, and avoid the politeness question altogether.
  • Plain speech: very casual; use only if your in-app UI speaks this way.

Whatever you pick, match the tone of the Korean app UI shown inside the device frame. A formal caption above a casual interface is an obvious mismatch to Korean users.

What does StoreLocale generate for Korean?

StoreLocale offers one Korean target, code ko, listed in the language picker as 한국어. The ZIP places the PNGs in a ko folder under each platform, and you upload the same set to both consoles yourself.

  • Detecting and translating on-screen strings costs 0 credits. Edit spacing or speech level in each string before you generate.
  • Repainting the in-app UI with Korean text costs 1, 2 or 4 credits per screenshot for Standard (1K), Pro (2K) or Ultra (up to 4K) output.
  • Brand names and acronyms such as 4K or PRO stay in Latin letters during translation.

What should a native Korean reviewer check?

  1. Every word boundary has a space, and no particle is separated from its noun.
  2. No caption breaks inside a word; wraps fall between eojeol.
  3. Punctuation is half-width, and headline endings follow one rule across the set.
  4. The speech level is identical on every slide and matches the app UI.
  5. Repainted Hangul has no broken or invented syllable blocks, especially in small UI labels.
  6. Fallback fonts render Hangul evenly next to Latin brand text, with no empty boxes.
  7. Feature names match the terms in the shipped Korean build, whether they are native Korean words or transliterated loanwords.

Frequently asked questions

What is the Korean locale code on each store?

App Store Connect uses ko, and Google Play Console uses ko-KR, as listed in Apple's localization reference (opens in a new tab) and Play Console Help (opens in a new tab). There is one Korean localization on each store.

Should Korean captions have spaces between words?

Yes. Unlike Japanese and Chinese, Korean separates words with spaces. Removing them makes captions hard to read, while adding a space before a particle is also an error.

Is Korean shorter than English on a screenshot?

It depends on the string. W3C's "views" example comes out at 0.8 of the English width, even after counting each Hangul syllable as two Latin characters wide, but polite endings and particles can make full phrases longer. Measure the rendered text.

Which politeness level works best for app screenshots?

There is no single right answer. Formal polite endings suit serious categories, informal polite endings feel friendlier, and noun-style headlines stay neutral. Match the speech level of your in-app UI.

Does StoreLocale upload Korean screenshots to the stores?

No. StoreLocale exports a ZIP of PNGs with a ko folder per platform. You upload those files to App Store Connect and Google Play Console yourself.

Sources

  1. App Store localizations (App Store Connect Help)
  2. Translate and localize your app (Play Console Help)
  3. W3C Requirements for Hangul Text Layout (KLREQ)
  4. W3C Text size in translation

Related pages

Translate your next screenshot set with StoreLocale

Upload your screenshots, pick target languages, and review every localized version before you export.