Chinese number converter
1234 becomes 一千二百三十四 in everyday Chinese numerals: convert whole numbers into common or anti-fraud financial characters for receipts, invoices and lessons, or turn a Chinese numeral back into digits. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value to convert
- 1234
- Conversion direction: to_chinese
- To chinese
- Character set: everyday
- Everyday
- Result
- 一千二百三十四
- Value
- 1,234
- Chinese
- 一千二百三十四
- Integer
- 1,234
Chinese numerals appear on receipts, bank drafts, invoices, legal amounts, classroom worksheets, and localization pipelines that must show 一二三 or the anti-fraud capital forms 壹贰叁 instead of Arabic digits. Values outside the published digit range fail with a clear invalid input error and are not charged.
Directions, styles, and how Chinese place values work
Send a required value and a required direction. Style everyday uses the common characters taught in schools: zero through nine as 零一二三四五六七八九, plus 十百千万亿 for ten, hundred, thousand, ten-thousand, and hundred-million. Style financial uses the capital forms preferred on checks and formal amounts: 零壹贰叁肆伍陆柒捌玖 with 拾佰仟 for the small units, still grouping with 万 and 亿.
Chinese numbers group by four digits, not three: after the ones section come 万, then 亿, then 万亿, so one hundred thousand is 十万 and one million is 一百万, not a Western-style million word. Everyday teens may open with bare 十 for ten through nineteen when that phrase leads the numeral; financial form always writes an explicit 壹 before 拾. Negative integers use a leading 负.
Absolute values may have at most sixteen decimal digits; anything larger is out of range and rejected. Identical inputs always produce identical outputs because the path is pure arithmetic with fixed tables, no random seed, and no wall clock.
Where Chinese numerals are used, and their limits
Call the free in-browser Chinese number converter for homework checks, receipt previews, and quick localization demos without installing a Chinese NLP stack. Pair encode with financial style when the next step is a formal amount line that auditors expect in capital characters; pair everyday style with UI labels, flashcards, and reading practice. From_chinese is useful for OCR clean-up pipelines that already extracted a numeral string and need a numeric field for sorting or arithmetic.
Source inputs follow the same retention rules as other KIT parse items. Authors shipping SDKs can map chinese and integer directly into bilingual tables that show Arabic digits beside Chinese forms—the same comparison students and clerks make on paper when they verify an amount by hand.
What you can do with it
Invoices and financial capital amounts
Billing systems convert line totals into financial 大写 numerals for Chinese-style invoices and drafts, and reject out-of-range figures before they hit a PDF template.
Localization and data pipelines
ETL jobs and CMS exporters turn product counts or IDs into Chinese numerals for zh locales, or parse Chinese numeral strings from documents into integers for analytics.
FAQ
How do I convert an integer to Chinese numerals?
Optional style everyday or financial selects common or capital characters. The chinese and result fields hold the numeral string.
How do I decode Chinese numerals back to a number?
Use the same style as the characters. The integer and result fields hold the number.
What is the difference between everyday and financial styles?
Everyday uses 一二三…十百千 (小写). Financial uses capital anti-fraud forms 壹贰叁…拾佰仟 (大写) common on checks and formal amounts. Do not mix the two sets in one string.
What values are out of range?
Fractions, empty strings, and unparseable text also fail and are not charged.
Is the Chinese number converter free?
The browser tool runs free on your device.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/fmt/chinese-numerals \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":"1234","direction":"to_chinese"}'const res = await fetch("https://api.kit.forhosting.com/fmt/chinese-numerals", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": "1234",
"direction": "to_chinese"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/fmt/chinese-numerals",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": "1234",
"direction": "to_chinese"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/fmt/chinese-numerals", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":"1234","direction":"to_chinese"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":"1234","direction":"to_chinese"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/fmt/chinese-numerals", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": "1234",
"direction": "to_chinese"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "fmt.chinese_numerals",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
This capability converts whole integers in either direction: from a plain integer into a Chinese numeral string, or from a Chinese numeral string back into an integer, with an explicit choice between everyday characters and financial capital characters.
Directions, styles, and how Chinese place values work
Direction to_chinese accepts a whole integer as a JSON number or a digit string with an optional sign and returns the Chinese numeral in the chosen style. Direction from_chinese accepts a Chinese numeral string built from the matching character set and returns the integer.
Reading the response and avoiding invalid input
Typical failures include missing value or direction, non-integer decimals or scientific notation on encode, mixed everyday and financial characters in one string, characters that do not match the declared style, empty or incomplete numeral phrases such as a bare section unit without a coefficient, and out-of-range magnitudes beyond sixteen digits. Strip spaces from Chinese text before sending, or rely on the engine which collapses whitespace. Do not send currency unit words such as 元 or 圆 when you only need the numeric body; this product converts the integer core, not a full spoken money phrase. On success the response echoes direction and style, exposes chinese for the numeral string, integer for the numeric value, and result as the primary field for the direction you chose so UIs can bind a single key. Method is everyday or financial_capital so downstream code can branch without sniffing glyph shapes. Integers that fit safe JSON numbers are returned as numbers; larger exact values are decimal strings so no precision is lost. Round-trip is supported when you keep the same style: encode with to_chinese, decode with from_chinese, and the integer matches. Failures raise invalid_input and are not charged after the engine rejects the request. Prefer digit strings for integers near the top of the range so JSON number rounding never corrupts the input.
API usage, pricing, localization workflows, and practical limits
Use the prepaid API when an invoicing service, banking back-office tool, ERP export, education app, or content pipeline needs a stable contract under KIT balance at $0.002 per successful item.
Integration use cases
Education and reading practice
Teachers and apps show everyday 小写 forms for integers, quiz students on decoding 一万零一 back to 10001, and keep answers identical across browser and API.