Convert Chinese text between Simplified, Traditional (general/Taiwan/Hong Kong) and vocabulary variants. 简繁转换。Runs entirely in your browser.
Chinese Converter Tool
How to Use the Chinese Converter
Pick a conversion mode
Use the dropdown above the input pane to choose direction. The default is Simplified → Taiwan with vocabulary (软件 → 軟體) — the most useful mode for ASEAN readers publishing across the Strait. Modes are grouped by region: General, Taiwan, and Hong Kong.
Paste or type your text
Type or paste up to 10,000 Chinese characters into the left pane. Conversion runs live as you type, debounced at 200 ms so it stays snappy. The output pane on the right updates automatically.
Copy or download the result
Click Copy to send the converted text to your clipboard, or Download to save it as a plain-text file. The diff highlighter shows which characters changed — toggle it off for clean copy-paste.
Swap direction with one click
Use the ⇄ Swap button to flip input ↔ output. The mode reverses automatically (e.g. cn|twp becomes twp|cn). Handy for proofreading both directions of a translation.
The glyph-only modes (cn|t, cn|tw, cn|hk) round-trip exactly. The vocabulary pair cn|twp ⇄ twp|cn does not — vocabulary mapping is many-to-one, so 程序设计 → 程式設計 → 编程.
Why Chinese Has Multiple Written Forms — And Why It Matters in ASEAN
Chinese isn't one written language but several closely related ones. In 1956, mainland China launched the Simplified Chinese Character Scheme — a reform that reduced the stroke count of about 2,238 commonly-used characters. Taiwan, Hong Kong, Macau, and most overseas Chinese communities outside Singapore and Malaysia kept the traditional forms. Seventy years on, the two systems coexist: roughly 1.4 billion readers use Simplified, around 35 million use Traditional. The split feels regional, but for many ASEAN families and businesses, it's a daily switching cost.
The common framing — Simplified versus Traditional — is one axis only. The real picture has at least four. Characters differ (龍 ↔ 龙). Vocabulary differs across regions even within Traditional (Taiwan's 軟體 versus Hong Kong's 軟件). Punctuation conventions differ. And cultural register — what reads as formal, breezy, or technical — varies enough that a clean character-by-character conversion can still read as "off" to native readers. Naive tools handle axis 1 and miss the rest.
"Singapore is home to roughly 2.9 million ethnic Chinese — about 76% of its citizen population — yet daily media consumption blends Mainland Simplified, Taiwan Traditional, and Hong Kong Cantonese sources." — Singapore Department of Statistics, Population Trends 2023
The vocabulary problem that character conversion cannot solve
Take the word for "software". A character-only converter sees 软件 (Simplified) and outputs 軟件 — the literal Traditional form. That's correct for Hong Kong, where 軟件 is the accepted term. It's wrong for Taiwan, where readers expect 軟體. Three more examples: 信息 (Mainland) ↔ 資訊 (Taiwan, "information"); 程序 ↔ 程式 ("program"); 鼠标 ↔ 滑鼠 ("mouse"). Phrase-level dictionaries — what OpenCC calls its "p" modes — catch these by recognising the source word and substituting the regional target, not the literal character mapping.
Then there's ambiguity. The character 后 means "queen" in 皇后 (empress) but "behind / after" in 后来 (later). A blind one-to-one map can't choose; a phrase-aware dictionary disambiguates by reading at least one neighbouring character. Same problem with 干 (do / dry), 乾 (dry, only), 幹 (to do, only) — three Traditional characters that all map back to the single Simplified 干 depending on context. Round-trip conversion (Simplified → Traditional → Simplified) only stays lossless when the dictionary recognises the original phrase.
What this means for ASEAN businesses and readers
For Singapore firms publishing for Taiwan or Hong Kong clients, the difference between 軟體 and 軟件 is the difference between sounding local and sounding translated. For Malaysian Chinese-language press — Sin Chew, Nanyang, China Press — daily decisions about which regional variant to use ripple through tone and credibility with different reader segments. Subtitle and dubbing teams, e-commerce listings sold across the Strait, tourism content marketing to Hong Kong visitors arriving in Bali or Phuket — all of them benefit from the vocabulary modes, not just the character ones.
The privacy angle matters too. For legal drafts, internal memos, financial disclosures, or anything covered by PDPA / GDPR data-residency rules, "runs in your browser" isn't a feature — it's a compliance baseline. This tool loads the OpenCC engine as a self-hosted JavaScript bundle on first input; your text is never transmitted, logged, or processed on our servers. Verify it yourself: open DevTools, watch the Network tab while you type, and you'll see one bundle load and no further requests.
10 Things to Know About Chinese Script Conversion
3,000 years apart. Oracle bone script (商朝) and modern Simplified Chinese share only ~30% of glyphs unchanged.
1956 reform. Mainland China's Simplified Chinese Character Scheme officially launched 28 January 1956 — affecting 2,238 characters.
Taiwan + HK held the line. Neither region adopted Simplified — Traditional Chinese has been preserved continuously for over 70 years.
Singapore picked Simplified. Singapore officially adopted Simplified Chinese in 1976 — the only major overseas Chinese community to do so.
Same character, different meaning. 后 means "queen" in 皇后 but "behind" in 后来 — context disambiguates, which is why naive conversion fails.
Vocabulary divergence. 软件 (Mainland), 軟件 (HK), 軟體 (Taiwan) — three different words for "software" depending on region.
OpenCC since 2010. The open-source converter has had 15+ years of dictionary refinement, contributed by translators worldwide.
76% Chinese in Singapore. Per Department of Statistics 2023 Population Trends — making proper Chinese tooling a daily need.
22% Chinese in Malaysia. ~6.7 million ethnic Chinese, predominantly using Simplified for school and Traditional for cultural media.
In-browser is possible. Modern JavaScript runs OpenCC's dictionary engine (~1.1 MB) entirely client-side — your text never leaves your device.
Frequently Asked Questions
-
Simplified Chinese reduces the stroke count of common characters (e.g. 龍 → 龙, 後 → 后), introduced in Mainland China in 1956. Traditional Chinese preserves the older forms still used in Taiwan, Hong Kong, Macau, and most overseas Chinese communities outside Singapore and Malaysia. Beyond stroke reduction, the systems also differ in word choice (vocabulary), punctuation conventions, and occasionally word order. About 2,200 characters were officially simplified, but Traditional has remained largely unchanged for centuries.
-
Both regions use Traditional characters, but they diverged on which traditional forms are "standard" plus vocabulary. Taiwan follows the Ministry of Education standard form (often called 國字標準字體). Hong Kong follows the Hong Kong Supplementary Character Set, which includes Cantonese-specific characters and slightly different glyph standards. The differences are subtle for most everyday text but matter for publishing, subtitles, and legal documents — which is why OpenCC ships separate dictionaries for each.
-
The "+ vocabulary" modes (twp/cnp) do phrase-level substitution, not just character-by-character. Without it, "软件" becomes "軟件" (character conversion only). With it, "软件" becomes "軟體" — the actual word Taiwanese readers use. Same for 程序 → 程式 (program), 信息 → 資訊 (information), 鼠标 → 滑鼠 (mouse). For marketing copy, technical docs, or anything where natural-sounding regional Chinese matters, you almost always want vocabulary mode.
-
No. All conversion runs client-side in your browser using the OpenCC engine (loaded as a 1.1 MB JavaScript bundle on first input). Your input text, output text, and the conversion process never touch our servers. This matters for legal drafts, financial materials, internal memos, or anything covered by PDPA / GDPR data-residency requirements. You can verify by opening DevTools → Network and watching what happens when you type — only the bundle loads, no upload of your text.
-
OpenCC is a dictionary-based converter, not a translator, and that is both its strength and its limit: it never invents a character the way a language model can, but it also cannot read context the dictionary does not already cover. For running prose in modern standard Chinese it is reliable — the dictionary holds multi-character entries, so 头发 → 頭髮 and 干杯 → 乾杯 are right and convert back to the original. Names are where it fails, and it fails silently. Simplification merged several distinct Traditional characters into one, and going back the dictionary picks whichever is commonest rather than asking whether the string is a name: 我姓余 becomes 我姓餘 and 干先生 becomes 幹先生, both wrong. Yet 范冰冰 and 钟先生 come out right, because those names are in the dictionary. Nothing on the page tells you which case you are in, so proofread names by hand. For classical Chinese (文言文), ancient names, or specialised technical terms not in the dictionary, OpenCC leaves the original characters unchanged rather than guessing.
-
Singapore officially uses Simplified Chinese, so most input will be Simplified. If you're writing for a Singapore audience: no conversion needed. If you're publishing for Taiwan readers, pick "Simplified → Taiwan + vocabulary" (the default mode on this tool — cn|twp). If you're publishing for Hong Kong, pick "Simplified → Hong Kong" (cn|hk) — note HK doesn't have a separate vocabulary mode in OpenCC because Cantonese-specific terms are best handled manually.
-
Yes, but with caveats. The character forms convert correctly — 學而時習之 (Traditional) ↔ 学而时习之 (Simplified) works fine. However, classical Chinese uses different vocabulary and grammar than modern Chinese, so the vocabulary modes (twp/cnp) won't add value. For classical text, use the plain modes (cn|t or t|cn). Classical idioms (成語) typically have stable forms across regions and convert cleanly.
-
Three reasons. First, some characters are identical in both systems — 人, 中, 文, 大 don't need converting. Second, names of people, places, and brands often retain their original form by convention even when written in the other system. Third, a few rare or specialised characters may not appear in OpenCC's dictionary. If you spot an obvious miss, it's likely a dictionary gap — OpenCC is open-source on GitHub and accepts contributions.
-
Yes — 10,000 characters per conversion. This is a safety limit, not a technical one (OpenCC could handle millions). Conversion is debounced at 200 ms, and very long texts can briefly stall the browser tab while the dictionary engine walks the input. The 10K cap covers most use cases (a typical news article is 500-1500 characters; a long-form essay is 3000-5000). For larger batches, split your text into sections.
-
Yes. OpenCC is MIT-licensed and the converted text is your own work product — there's no licensing restriction from using this tool. We don't claim any rights to your input or output. The tool itself is free with no signup; we monetise through display advertising on the page, not through fees or paid tiers. For professional publishing, we still recommend a human review pass for register, tone, and any regional idioms the dictionary may have missed.
Related News
You may be interested in these recent stories from our newsroom.
-
Saudi Arabia's humain-m3 Is MiniMax's M3, Under MiniMax's Licence
Same 428 billion parameters, same 23 billion active, same mixture-of-experts design as the model Shanghai open-weighted in June. The Arabic...
-
OpenAI's GPT-6 Astra Costs 2.5 Times More and Matches GPT-5.6 on the Independent Index
OpenAI called the launch the start of the AGI era. Artificial Analysis, which OpenAI neither ran nor selected, scores Astra 61 — exactly wha...
-
Six AI Releases in Three Days, and Two Were New Models
The 72-hour launch count folds together two new models, a safeguard variant, two point releases, a pricing tier and a feature that is not a...
Method & sources
How it computes
Conversion is a dictionary lookup, not a translation. The OpenCC engine walks the input against a trie of single- and multi-character entries, longest match first, rewrites what it finds and passes through what it does not. Eight directed modes cover general Simplified/Traditional plus Taiwan and Hong Kong standard forms; the two Taiwan phrase modes additionally substitute regional vocabulary, so 软件 becomes 軟體 rather than only 軟件. Everything runs in the browser from a self-hosted bundle.
What this tool implements
- Longest-match-first over multi-character entries, not character-by-character substitution. This is why 头发 → 頭髮 and 干杯 → 乾杯 are correct and survive a round trip back to the input, where a per-character table would produce 头髮 and 干杯 from the wrong 干.
- Character form and regional vocabulary are separate choices, kept separate. cn|tw rewrites the glyphs only; cn|twp also swaps the terms. Picking the wrong one yields text that is orthographically Traditional and lexically mainland — 臺灣資訊軟體 comes back as 台湾资讯软体 under tw|cn but 台湾信息软件 under twp|cn.
- Taiwan and Hong Kong are not one "Traditional" and the tool does not treat them as one. Verified against the served bundle: 里面 → 裡面 in Taiwan mode but 裏面 in Hong Kong mode; 着急 → 著急 in Taiwan mode but 着急 in Hong Kong mode.
- ⚠️ NAMES ARE WHERE THIS BREAKS, AND IT BREAKS SILENTLY. Simplification merged distinct Traditional characters; converting back, the dictionary resolves each merge by frequency rather than by whether the string is a name. Verified 2026-08-31: 余华 → 餘華 and 我姓余 → 我姓餘 are both wrong (the surname is 余; 餘 means "surplus"), and 干先生 → 幹先生 is wrong. Yet 范冰冰 and 钟先生 come out right because those names are in the dictionary. Nothing on the page tells you which case you are in, so proofread every name by hand in either direction.
- It is a converter, not a translator, and it never invents. A character with no dictionary entry is passed through unchanged rather than guessed at — which is the right behaviour for 文言文, ancient names and specialist terms, and is the one respect in which it is genuinely safer than a language model.
- The text never leaves the browser. The engine is a self-hosted bundle loaded on first input, and no input, output or intermediate state is transmitted or logged.
Sources
- opencc-js v1.3.1 (MIT), the conversion engine: https://github.com/nk2028/opencc-js — the JavaScript port of Open Chinese Convert. The bundle served at /tools/chinese-converter/opencc-bundle.js was confirmed byte-identical to that package's dist/umd/full.js on 2026-08-31 (SHA-256 01c0921d3685f410…, 1,124,229 bytes), so the audited package and the shipped copy are the same file.
- Open Chinese Convert (OpenCC), Apache-2.0: https://github.com/BYVoid/OpenCC — the upstream project the conversion tables originate from.
- Dictionary licensing: per opencc-js's own THIRD_PARTY_LICENSES.md the bundled tables are generated at build time from opencc-data (https://github.com/nk2028/opencc-data) and redistributed under the Apache License 2.0 — a different licence from the MIT-licensed engine code, and one this tool previously did not name.
- Taiwan standard character forms: 常用國字標準字體表 (4,808 characters, 1982) and 次常用國字標準字體表 (6,341 characters, 1982), Ministry of Education, Republic of China: https://language.moe.gov.tw/ — the orthography the tool's Taiwan modes target.
- Hong Kong standard character forms: 常用字字形表 (List of Graphemes of Commonly-used Chinese Characters), Education Bureau, first issued 1986 and reissued in typeset form in 2007 with 4,762 characters: https://www.edbchinese.hk/lexlist/ — the orthography the tool's Hong Kong modes target, and the reason 裡/裏 and 著/着 differ from Taiwan.
What can make this go out of date
- The dictionaries are compiled into the vendored bundle and nothing refetches at runtime. Updating them means bumping opencc-js and re-copying the bundle; a bump that is not re-copied would leave the audited version and the served bytes disagreeing, which is why the byte comparison above is recorded rather than a version banner.
- ⚠️ Regional vocabulary dates faster than character forms do. The phrase tables encode what a term was called when they were compiled — new technical vocabulary diverges between markets before any dictionary records it, so a recent coinage will convert its characters and keep its mainland wording.
- Hong Kong has no vocabulary mode, only character forms. Cantonese-specific lexis is not substituted by any mode and has to be handled by a human.
Pick up where you left off
Stored only in this browser — never sent to our servers.