Why isn't the reverse 100% accurate?

Because Simplified Chinese collapsed several distinct Traditional characters into one. The most-cited case is 后: in Traditional it means either "queen" (后) or "after" (後), but Simplified writes both as 后. When you go S→T we pick the more common reading; when you go T→S the mapping is deterministic. Always read the output if context matters — no character-level engine, including OpenCC, solves this without sentence-level context.

Does this handle 1-to-many ambiguities like 后 → 後 / 后?

We use OpenCC's first candidate (most common in modern usage) — so for example 头发 → 頭髮 (hair) rather than 頭發 (head + send). For most modern prose the result matches a native speaker's expectation. Niche literary or legal texts may need manual review of a handful of such characters.

Is Taiwan, Hong Kong, and Singapore Chinese all the same as "Traditional"?

They share the same character set but differ in vocabulary. 软件 (mainland) is 軟體 in Taiwan but also commonly 軟件 in Hong Kong; 鼠标 is 滑鼠 in TW/HK. Character conversion alone doesn't translate these — turn on the "Region phrasebook" option to substitute common terms. For full localization (TW vs HK Cantonese) you still want a human pass.

Why are some characters not converted?

Three reasons. (1) Many characters are identical in both scripts (e.g. 中, 人, 我) — there's nothing to convert. (2) Rare CJK Extension B characters are excluded to keep the bundle small; if your text is historical or scholarly use a server-side OpenCC build. (3) The character may have been written as a variant form not in the dictionary — paste it into a search engine to find its standard equivalent.

Does this preserve formatting like line breaks and spaces?

Yes. Conversion is per-codepoint, so newlines, spaces, punctuation, numbers, English words, emoji, and code symbols are passed through unchanged. Paste a whole song lyric, a JSON blob with Chinese values, or a Markdown article — only the Han characters change.

Localizing a mainland app's UI strings for a Taiwan release

You shipped a React app with 800 zh-CN strings and now need a zh-TW build. Paste the JSON values, run S→T, and turn on the region phrasebook so 软件 becomes 軟體 and 鼠标 becomes 滑鼠, not just the glyphs. The line breaks and the JSON keys stay byte-for-byte intact, so you can diff the two files and only the Han values light up.

Reading a Hong Kong PDF that was pasted as Traditional text

A colleague sends a 3-page contract in Traditional characters and you read Simplified faster. Paste it, run T→S, and the deterministic mapping gives you clean Simplified in one pass. Punctuation, the numbered clauses, and the English defined terms come through untouched, so the structure is identical and only the script flips.

Spot-checking a 后/後 ambiguity in a song lyric

You converted a 40-line lyric S→T and one line about a "queen" looks wrong. Click swap to run it back T→S, see the character resolve, and confirm whether the engine picked 后 or 後. Because the page is fully in-browser, you can re-run the swap dozens of times on the same paste with zero latency and no upload of the unreleased lyrics.

Cleaning Traditional code comments before merging upstream

A contributor's pull request has 30 Chinese code comments in Traditional, but the repo standard is Simplified. Paste the diff, run T→S, and the per-codepoint conversion leaves every bracket, semicolon, variable name, and indent exactly where it was. Only the comment text changes, so the patch stays mergeable with no manual fix-ups to the surrounding code.

Traditional ⇄ Simplified Chinese Converter — Free, Instant, In-Browser

Traditional ⇄ Simplified Chinese — fast, character-level, no API.

Runs locally
Category Text
Best for Removing repetitive cleanup work from everyday writing and operations.

Region phrasebook (TW/HK)

简体 / Simplified

0 chars

繁體 / Traditional

0 chars

繁體輸出顯示於此。

What this tool does

Free online Traditional ⇄ Simplified Chinese converter. Paste any text and get the other script instantly, both directions supported in one click. Character-level mapping (~6,400 pairs) is derived from the OpenCC project (Apache-2.0) and bundled inside the page — no server call, no rate limit, no upload. Common 1-simplified-to-many-traditional ambiguities like 后 → 後 / 后 are resolved using the most-common candidate (you can swap directions with one click to spot-check). Optional region phrasebook converts common mainland↔TW/HK terms (软件 ⇄ 軟體, 鼠标 ⇄ 滑鼠) when enabled. Works on Mandarin, Cantonese, Classical Chinese, song lyrics, and code comments — formatting, line breaks, and punctuation are preserved exactly.

Tool details

Input: Text; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy + Download; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: No account required; Open the page and use it; whether results survive refresh depends on the tool.
Performance budget: Initial JS <= 50 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Text · Content Creator; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How Traditional ⇄ Simplified Chinese Converter fits into your work

Use it to clean, compare, reshape, or extract plain text before it goes into a document, CMS, spreadsheet, or prompt.

Text jobs

Removing repetitive cleanup work from everyday writing and operations.
Making text easier to compare, paste, publish, or feed into another tool.
Working with content locally when the text is private or unfinished.

Text checks

Scan for unintended whitespace, duplicate lines, and lost punctuation.
For long text, test the first few lines before applying the whole change.
Copy the final output only after checking the preview.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Localizing a mainland app's UI strings for a Taiwan release
You shipped a React app with 800 zh-CN strings and now need a zh-TW build. Paste the JSON values, run S→T, and turn on the region phrasebook so 软件 becomes 軟體 and 鼠标 becomes 滑鼠, not just the glyphs. The line breaks and the JSON keys stay byte-for-byte intact, so you can diff the two files and only the Han values light up.
Reading a Hong Kong PDF that was pasted as Traditional text
A colleague sends a 3-page contract in Traditional characters and you read Simplified faster. Paste it, run T→S, and the deterministic mapping gives you clean Simplified in one pass. Punctuation, the numbered clauses, and the English defined terms come through untouched, so the structure is identical and only the script flips.
Spot-checking a 后/後 ambiguity in a song lyric
You converted a 40-line lyric S→T and one line about a "queen" looks wrong. Click swap to run it back T→S, see the character resolve, and confirm whether the engine picked 后 or 後. Because the page is fully in-browser, you can re-run the swap dozens of times on the same paste with zero latency and no upload of the unreleased lyrics.
Cleaning Traditional code comments before merging upstream
A contributor's pull request has 30 Chinese code comments in Traditional, but the repo standard is Simplified. Paste the diff, run T→S, and the per-codepoint conversion leaves every bracket, semicolon, variable name, and indent exactly where it was. Only the comment text changes, so the patch stays mergeable with no manual fix-ups to the surrounding code.

Common pitfalls

Trusting S→T blindly on 后 is risky because the engine picks 後 by frequency, so "皇后" (queen) can come out as "皇後". Click swap to verify.
Expecting vocabulary translation without the phrasebook fails, because plain T→S keeps 軟體 as 软体, not 软件. Turn on the region phrasebook for 软件/鼠标-style swaps.
Pasting scanned text with variant glyphs (e.g. a non-standard 為 form) and assuming it failed; copy the unconverted character into a search engine to find its standard equivalent first.

Privacy

Everything runs in your browser. The ~6,400-pair OpenCC dictionary is bundled in the page, so your pasted text never leaves the device and hits no server or API. Your input is not written to the URL, so sharing a link won't leak a contract, an unreleased lyric, or private code comments. Close the tab and the text is gone.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Browse all tools for this role

Traditional ⇄ Simplified Chinese Converter — Free, Instant, In-Browser

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How Traditional ⇄ Simplified Chinese Converter fits into your work

Text jobs

Text checks

Good next steps

Real-world use cases

Localizing a mainland app's UI strings for a Taiwan release

Reading a Hong Kong PDF that was pasted as Traditional text

Spot-checking a 后/後 ambiguity in a song lyric

Cleaning Traditional code comments before merging upstream

Common pitfalls

Privacy

FAQ

Lunar Calendar Converter (Chinese Nongli)

Chinese Pinyin Converter

Multicultural Name Generator

Case Converter

Word Counter

Chinese Numeric Converter

Chinese Stroke Counter

Chengyu Chain Game

A1Z26 Cipher (Letter ⇄ Number)

Chinese Acupoint Locator

Ad Copy Checklist

Add Line Numbers