App Store Screenshot Localization for South Korea: A Practical 2026 Guide
How to localize App Store screenshots for South Korea in 2026: Hangul glyph density, KakaoTalk-aware sample content, formal vs casual register, and the workflow that ships a Korean screenshot set across iPhone and Galaxy.
By Screenhance Team
Why South Korea ranks Tier 1
South Korea consistently ranks among the top 5 single locales to localize App Store screenshots for, alongside Japan, Germany, France, and Simplified Chinese:
Mobile-first market. Korea has one of the highest smartphone penetration rates globally and consistently high in-app spend across productivity, social, gaming, and lifestyle categories. The absolute revenue per converted Korean user is high. Native-language preference. Korean users explicitly seek out Korean-language apps. The conversion gap between English-only and Korean listings in Korea is consistently 2-3x — at the higher end of Apple's published 2-3x range. iPhone + Samsung Galaxy parity. Unlike Japan (iPhone-dominant) or India (Android-dominant), Korea has roughly balanced iPhone and Galaxy market share, so both App Store and Google Play localizations earn ROI. Galaxy is slightly ahead among younger demographics; iPhone is slightly ahead in premium segments. Mature App Store culture. Korean users read reviews carefully, share App Store listings on KakaoTalk (the dominant messaging app), and respond to localization quality in their reviews. Bad Korean shows up in 1-star reviews quickly; good Korean compounds into recommendations.What to translate (and what to leave alone)
Korean localization is more than vocabulary substitution. The register and tone matter as much as the words:
Translate with native-speaker review: Caption headlines, app description, keywords, what's-new release notes, in-app onboarding. Korean has multiple registers and the wrong register is immediately visible. Use a native Korean translator (Crowdin, Lokalise, or a freelance translator who has done App Store work specifically). Translate carefully, watch for register: Feature lists, benefit statements, call-to-action buttons. Korean's formality registers shift the entire tone of a sentence — using formal-polite (합니다체) on a casual consumer app reads as stiff; using casual-polite (해요체) on a B2B app reads as unprofessional. The same English caption needs different Korean register choices depending on the app category. Leave alone or transliterate, don't translate: Product and brand names (your app name in English usually works; some apps adopt Hangul versions like 인스타그램 for Instagram). Device names ("iPhone 17 Pro" stays in English — Apple's Korean Apple Store uses the English product names with Korean prepositions around them). Technical terms with no clean Korean equivalent.The register decision: 합니다체 vs 해요체 vs 반말
Korean has three primary registers relevant to App Store captions:
합니다체 (formal-polite, "ha-mni-da" style). The most formal common register. Reads as professional, slightly distant, respectful. Use for: B2B apps, finance apps, productivity tools targeting older or professional demographics, government-adjacent apps. Example caption: "예산을 쉽게 관리합니다" ("Easily manage your budget"). 해요체 (informal-polite, "hae-yo" style). Polite but warmer. The default for most consumer apps in 2026. Reads as approachable and friendly without being too casual. Use for: most B2C apps, lifestyle apps, social apps, health apps, anything targeting general audiences. Example caption: "예산을 쉽게 관리해요" (same meaning, warmer tone). 반말 (casual, "ban-mal" style). Drops the polite ending entirely. Reads as casual, friendly, sometimes too informal. Use for: youth-oriented social apps, casual games targeting under-25, lifestyle apps with deliberately casual branding. Example caption: "예산을 쉽게 관리해" (same meaning, friend-to-friend tone). The cost of getting register wrong: A 반말 caption on a banking app reads as unprofessional and reduces conversion meaningfully. A 합니다체 caption on a casual social app reads as cold and corporate. When in doubt, default to 해요체 — it's the safest middle ground and the one that fits the broadest range of apps.Brief the translator explicitly on the register the app uses. Don't accept "translator default" — there is no default that fits every app.
Hangul glyph density and font sizing
Hangul characters are visually denser than Latin script (a single Hangul block represents 1-3 phonemes packed into one square), so the same caption character count occupies different visual space.
Rule of thumb: Korean translations are typically 70-90% the character count of the English source (Korean compresses meaning into fewer characters than English), but each character is visually denser. Net visual length is usually similar to English, sometimes shorter. This makes Korean one of the easier languages to fit into existing layouts — the opposite of German, which expands 30-40%. Fonts: Use a Korean-native sans-serif. Apple SD Gothic Neo is the iOS system font and the safe default for screenshots captured from Simulator. Noto Sans KR is the cross-platform alternative. Pretendard (a popular open-source Korean font) is increasingly common in modern Korean app design. Avoid using a Latin font that happens to render Hangul — the quality difference is significant. Mixed Hangul and Latin strings: Captions that mix Hangul and Latin characters ("AI로 분석하기" = "Analyze with AI") need careful font pairing. Some Korean fonts pair badly with their Latin fallback and create visible weight mismatches. Test mixed strings before shipping.Sample content that signals "made for Korea"
Beyond translated captions, the sample content shown in screenshots influences conversion:
Names: Use Korean names (김민준, 이지유, 박서준, 최지우). Avoid English names with Korean captions — the inconsistency reads as careless. Currency: ₩ symbol with thousands separators (₩15,000 not $15). Korea uses commas as thousands separators and periods as decimals (₩1,500,000.00), matching English convention rather than European. Dates: YYYY.MM.DD format is most common (2026.12.31), though YYYY-MM-DD is also acceptable. Avoid US MM/DD/YYYY format. Time: 24-hour format is default in Korean apps (14:30 not 2:30 PM), though 12-hour with 오전/오후 (AM/PM) is also acceptable. KakaoTalk references. KakaoTalk is the dominant messaging app in Korea (roughly equivalent to WhatsApp's dominance in Latin America). If your app has share-to-messaging features and your screenshots show messaging integration, include KakaoTalk in the visible apps — its yellow K logo is a strong cultural-fit signal for Korean users. Locations: Korean cities (서울, 부산, 인천, 대구) in any location-aware screenshots. International-sounding addresses ("123 Main St, Anytown") in a Korean-localized screenshot break trust.In-app content: switch the locale, capture fresh
Same principle as Japan and Germany localizations: switch Simulator or device to Korean locale before capturing app screenshots, so the underlying UI renders in Korean rather than English-with-translated-overlays.
Specifically watch for:- App navigation labels in Korean (홈/탐색/프로필/설정 instead of Home/Explore/Profile/Settings)
- Date and currency formatting in Korean conventions
- Sample data using Korean names and locations
- Push notification examples shown in Korean
If your app isn't yet localized for Korean, the marketing-only localization approach (translate overlays but leave English UI underneath) converts roughly 50-60% as well as a fully localized listing. It's worth running as a validation experiment before investing in full in-app Korean localization, but it leaks trust on first open.
When to localize Korean before or after Japanese
Both are Tier 1, but they target different demographics and serve different ROI profiles:
Japan first if: Your app targets older demographics (30+), the category is productivity or finance, or you have iPhone-heavy install patterns globally. Japan's market is larger by absolute revenue but skews older and more conservative. Korea first if: Your app targets younger demographics (under 30), the category is social or gaming, or your existing user base already over-indexes on K-pop or K-drama-adjacent audiences. Korea's market is more concentrated but spends more per user in the categories where it's strong. Both at the same time if: The translation budget allows. CJK localization batches well — a single translator brief can cover Japanese and Korean (different translators, same workflow), and the production tooling handles both with the same per-locale caption swap pattern. Adding Korean on top of Japanese costs roughly 30-50% more time than Japan alone.The workflow that ships in under an hour
Assuming Korean translations are prepared (native-speaker review done, register confirmed for app category):
1. Build a Korean master from the English master. Duplicate the English screenshot set. Layout stays identical; captions swap.
2. Swap captions per screenshot. Paste reviewed Korean strings into each caption field. Korean's compact character count usually fits the existing layout without font adjustments.
3. Switch font to Apple SD Gothic Neo or Noto Sans KR. Latin fonts that happen to render Hangul produce visibly poor results.
4. Re-shoot in-app screenshots in Korean locale. Simulator: Settings → General → Language & Region → Korean.
5. Export every required Apple App Store and Google Play size per locale. Use a tool that exports all required dimensions in one pass — Screenhance's App Store screenshot translator handles 80+ languages including Korean with proper Hangul typography.
6. Upload to App Store Connect and Google Play Console. Korean (ko) in App Store Connect, Korean (ko-KR) in Play Console. Both stores accept per-locale screenshot uploads.
Total time for steps 1-5 with the right tooling: 40-60 minutes per locale. Upload step adds 10-15 minutes per store.
Measuring the impact
Track in App Store Connect Analytics filtered to South Korea:
- Conversion rate lift: Expected 2-3x in Korea versus English-only — at the high end of Apple's published range because Korean users are especially responsive to localization quality.
- Reviews and ratings: Watch for register complaints. Korean reviewers frequently flag bad localization with phrases like "번역이 이상해요" (translation is weird) or "딱딱해요" (it's stiff/cold).
- Search rank: Korean keyword rank typically improves within 2-3 weeks of localized listing going live.
- Retention: Korean users who install based on properly-localized listings retain meaningfully better than those who install based on English listings — the trust signal compounds.
If conversion lift is below 1.5x after 30 days, the issue is usually register mismatch. Audit which register the captions use and whether it fits the app category, then re-translate with explicit register guidance.
Frequently Asked Questions
Is Korean App Store localization worth it for a small indie app?
Yes for most app categories. Korea is one of the highest-converting locales for properly localized listings, with conversion lifts often at the top of Apple's published 2-3x range. Translation cost for 5-8 screenshot captions is $30-100 with a freelance Korean translator. The compounding ROI is meaningful for any app that targets consumer audiences or has existing Korea install signal.
How is Korean App Store localization different from Japanese?
Korean is CJK like Japanese (similar font requirements, similar visual density), but the workflow differs in two key ways: Korean translations are usually shorter than English (Japanese is usually similar or slightly longer), and Korean register choices are more impactful on conversion than Japanese keigo choices. The production tooling handles both similarly, but the translator brief needs to be more explicit about register for Korean.
Should I use Apple SD Gothic Neo or Noto Sans KR for screenshots?
Apple SD Gothic Neo is the iOS system font and the safest default if you're capturing screenshots from Simulator — the screenshots match what users see in the app. Noto Sans KR is the safe cross-platform alternative for marketing overlays where iOS system font isn't accessible. Pretendard is increasingly common in modern Korean app design and reads as more contemporary; consider it for younger-demographic apps.
Can I use AI translation for Korean?
For first-draft work, yes — modern AI translation produces grammatically correct Korean roughly 70-75% of the time. But register choices are where AI consistently struggles. The cost difference between AI-only and AI-plus-Korean-native-review is small relative to the conversion impact of getting register right. Use AI as a starting point; never ship AI-only Korean.
Do I need different Korean for North Korea vs South Korea?
No — the App Store and Google Play only support South Korean (ko-KR) for store listings. North Korea is not an App Store market. There are minor vocabulary differences in the two dialects, but Korean App Store work universally targets South Korean conventions.
Should I localize Hangul and use Korean keywords in App Store Connect?
Yes. Korean keywords in App Store Connect produce much better Korean search rank than relying on English keywords with translated screenshots only. Translate your keyword list separately from the screenshot captions — keywords are a different optimization (search match, not conversion polish).
How quickly will I see results from Korean localization?
App Store Connect Analytics shows install lift within 7-14 days of the localized listing going live. Full conversion impact compounds over 30-60 days as Korean keyword rankings improve. The 2-3x conversion lift Apple cites is a 90-day metric — short-term measurements often underestimate the long-term impact, especially in Korea where word-of-mouth via KakaoTalk drives compounding install growth.
What if my app isn't localized for Korean yet?
Decide whether marketing-only Korean is worth the trust cost. The case for shipping: validate Korean demand before investing in full in-app localization. The case against: users who install based on Korean screenshots, find English UI, and leave a 1-star review create durable negative signal. Compromise: ship marketing-only Korean with a clear "한국어 지원 곧 제공 예정" (Korean support coming soon) disclaimer.
Related Reading
- App Store Screenshot Translator - The tool that ships this workflow across 80+ languages
- App Store Screenshot Localization for Japan - The Japan-specific guide for the other major CJK market
- App Store Screenshot Localization for Germany - European text expansion playbook
- App Store Screenshot Localization Guide - The general playbook this Korea-specific guide builds on
- App Store Screenshot Dimensions 2026 - Pixel-exact sizes for every required device