Chapter 11·Scripts and Layout·~7 min·
CJK Font Fallback and Character Coverage
Unicode unifies CJK ideographs into shared code points across Simplified Chinese, Traditional Chinese, Japanese, and Korean. Browsers resolve font fallback per character and rely on the HTML lang attribute and regional font stacks to select the correct regional glyph.
Overview
Unicode unifies CJK ideographs that share an etymological origin into single code points across Chinese, Japanese, and Korean. A font stack without an explicit `lang` attribute and regional font list falls back to the operating system default, mixing glyph styles within a single line.
Core rule
Declare the HTML lang attribute and assign a regional CJK font stack to each language so the browser selects the correct regional glyph forms.
Specification note: Simplified Chinese, Traditional Chinese, and Japanese share the code point U+76F4 (直), but each writing system draws the internal strokes differently.
Failure mode
Han unification assigns a single Unicode code point to ideographs that share an etymological origin across Chinese, Japanese, and Korean, even when regional stroke conventions differ. A Latin webfont contains no CJK glyphs. When a page omits both a regional CJK font stack and an HTML lang attribute, the operating system selects a fallback font per character, mixing Simplified Chinese, Traditional Chinese, and Japanese glyph shapes inside the same heading.
Chinese, Japanese, and Korean share historical Han characters that share Unicode codes but differ in visual glyph design. Missing fonts display wrong stroke shapes.
Business stakes & user risk
Japanese users presented with Chinese-style font glyphs immediately recognize the text as foreign and non-native, eroding trust in financial and e-commerce applications.
Rule of thumb
Always set the HTML lang attribute and declare locale-specific font stacks for zh-CN, zh-TW, ja, and ko.
The Novice Trap vs. Production Standard
Contrast the intuitive assumption with the architecture required for global releases.
“A single universal CJK font or generic sans-serif renders Asian characters identically for all users.”
Naive approach: Generic font stack without lang tag
<body style={{ fontFamily: "sans-serif" }}>骨格品質</body>Defect:Without a lang tag, the browser guesses which system font to use. Japanese users often see Chinese stroke variants for characters like 骨 and 刃.
Unicode unified Han characters (Han unification). The exact same Unicode code point requires distinct brush strokes and radical shapes in Tokyo vs. Beijing.
Production standard: Explicit lang attribute and regional font stack
<html lang="ja" className="font-ja">...</html>Benefit:Instructs the browser and operating system font engine to render authentic Japanese typographic glyph variants.
Cross-Functional Review Questions
Questions for product managers, designers, engineers, and testers to ask during sprint reviews.
“Does our design system specify distinct font families for Simplified Chinese, Traditional Chinese, Japanese, and Korean?”
“Does the application root update the lang attribute dynamically on locale changes?”
“Are webfonts budgeted for Asian markets, or do we rely on system font fallbacks?”
“Are Japanese characters inspected on both macOS and Windows devices to verify glyph forms?”
Mechanism
Per-character font fallback and Han unification
The CSS font-family property evaluates fallback per character rather than per element. For each code point, the browser uses the first font in the list that contains a glyph for that character. Because Latin display fonts rarely contain CJK glyphs, the browser falls past the end of a Latin-only font stack to an operating-system default font. A single heading can therefore mix two or three fonts with mismatched baselines and weights across platforms.
Under Han unification, Unicode assigns a single code point to ideographs that Simplified Chinese, Traditional Chinese, and Japanese draw with different stroke shapes, such as 直 (U+76F4). The browser uses the HTML lang attribute to select the regional fallback font and the OpenType locl glyph table for unified code points. Set lang on the document root and on every inline element that switches language.
Interactive demo
Guided exercises
- 1On the default mixed sample, compare the “Naive (Helvetica/Arial)” row against the Noto row. The naive stack renders CJK text only because the operating system substitutes a system fallback font. The availability line under each row shows which fonts in the stack exist on this device.
- 2Switch the sample to “Traditional Han characters”. Traditional `說` (U+8AAA) and Simplified `说` (U+8BF4) use separate code points, whereas unified characters share one code point and rely on the font stack for regional stroke shapes.
- 3Compare the measured pixel widths listed for each stack. Identical text produces different pixel widths across font stacks. Font fallback alters line length and truncation points across operating systems.
- 4Compare the “N of M fonts available on this device” line across the five stacks. Font availability depends on the client operating system. A stack that resolves cleanly on macOS can fall back to a different system substitute on Windows or Linux.
The two Chinese samples share 使用, 直接, and 客服 but differ in 請/请 and 說/说, so a reviewer who does not read Chinese can miss Simplified strings in a Traditional build.
font-family: 'Helvetica Neue', Arial, sans-serif
No CJK font in the stack, so the browser uses the operating system's fallback font for Han, kana, and Hangul, which differs on macOS, Windows, and Android.
Per-font availability check
- Helvetica Neue
- Arial
font-family: 'Inter', 'Noto Sans', 'Noto Sans SC', 'Noto Sans JP', 'Noto Sans KR', 'Noto Sans TC', sans-serif
Noto aims to cover every script in Unicode. A Han character renders in the first regional font listed that has it (SC here), whatever the text's language.
Per-font availability check
- Inter
- Noto Sans
- Noto Sans SC
- Noto Sans JP
- Noto Sans KR
- Noto Sans TC
font-family: 'Inter', 'PingFang SC', 'Hiragino Sans GB', 'Microsoft YaHei', 'Source Han Sans SC', sans-serif
Uses the Chinese system font on each OS: PingFang SC on macOS, Microsoft YaHei on Windows.
Per-font availability check
- Inter
- PingFang SC
- Hiragino Sans GB
- Microsoft YaHei
- Source Han Sans SC
font-family: 'Inter', 'Hiragino Kaku Gothic ProN', 'Hiragino Sans', 'Yu Gothic UI', 'Meiryo', sans-serif
Chinese text in this stack renders in Japanese glyph shapes wherever the Japanese font has the character.
Per-font availability check
- Inter
- Hiragino Kaku Gothic ProN
- Hiragino Sans
- Yu Gothic UI
- Meiryo
font-family: 'Source Serif 4', 'Noto Serif', 'Noto Serif SC', 'Noto Serif JP', 'Noto Serif KR', serif
A serif stack for long-form text in mixed scripts.
Per-font availability check
- Source Serif 4
- Noto Serif
- Noto Serif SC
- Noto Serif JP
- Noto Serif KR
Where the CJK font goes in the stack
List the CJK font after the Latin face. Most CJK fonts include their own Latin glyphs, so one listed first also sets the Latin text.
Implementation rules
- Specify regional CJK webfonts per locale. Load
Noto Sans SCfor Simplified Chinese,Noto Sans TCfor Traditional Chinese,Noto Sans JPfor Japanese, andNoto Sans KRfor Korean. - Set the HTML
langattribute on all CJK containers. Thelangtag activates OpenTypeloclglyph substitution tables in pan-CJK fonts and directs browser system fallback to the matching regional font. - Define locale-scoped CSS font stacks with
:lang(). Prioritize native system fonts in each rule, such asPingFang SCandMicrosoft YaHeifor:lang(zh-Hans), andHiragino SansandMeiryofor:lang(ja). - Verify CJK rendering across target operating systems. Inspect glyph shapes on macOS, Windows, iOS, and Android, because default system fallback fonts differ on each platform.
Operational context
Roles
Workflow stages
- ·Preparing typography for CJK market launches
- ·Auditing design system font stacks
- ·Evaluating webfont subsetting and licensing
See it in a market: Japan · needs a CJK webfont →
Production incident
Han unification assigns shared code points to thousands of Chinese, Japanese, and Korean ideographs that use distinct regional stroke conventions. The active font and the HTML lang attribute determine which regional glyph shape appears on screen. Text that renders without missing-glyph boxes can still display the wrong regional character forms for the target market.