Thai numeral converter
2026 in Thai numerals is ๒๐๒๖: each digit is swapped for its Thai shape and the value stays the same. Convert either way, negatives included, for Thai-market PDFs, posters, shop pages and reading practice. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Whole integer to convert
- 2026
- Conversion direction
- To thai
- Result
- ๒๐๒๖
- Western
- 2026
- Thai
- ๒๐๒๖
- Sign
- 1
Thai numeral digits are the ten Unicode characters from zero through nine used across Thai-language print, signage, government forms, school materials, and many local software locales. They look different from Western Arabic digits but encode the exact same place-value integers: each Thai digit maps one-to-one onto 0 through 9. This converter takes a whole integer and a direction—Western to Thai or Thai to Western—and returns both spellings plus a primary result string so you can paste the form you need into a document, CMS field, or automated pipeline. Only integers are accepted: fractions, decimals, mixed scripts for the chosen direction, and empty values fail with a clear validation error instead of a silent wrong answer.
How Western and Thai digit conversion works
Western Arabic digits are the familiar ASCII characters zero through nine. Thai numerals occupy the contiguous Unicode block from U+0E50 through U+0E59 and are conventionally written ๐ ๑ ๒ ๓ ๔ ๕ ๖ ๗ ๘ ๙ for the same values zero through nine. Conversion is a pure glyph substitution on each digit of a whole integer: the place value never changes, only the script of each digit character.
To go from Western to Thai, walk the absolute digit string left to right and replace every ASCII digit with its Thai counterpart from a fixed ten-entry table. To go from Thai to Western, reverse the map and rebuild the ASCII digit string. An optional leading ASCII minus is preserved so negative whole numbers stay signed on both sides; zero is always returned unsigned.
Leading zeros in the absolute body are normalized so that multiple zeros collapse to a single zero while non-zero magnitudes keep their significant digits. Digit length is capped so results stay practical for forms and safe for exact integer handling in common runtimes. This is not a full Thai language number-to-words engine and does not translate words such as year names; it only rewrites the ten numeral glyphs of an integer.
Where Thai numeral converters show up in real work
Localization and desktop-publishing teams prepare Thai-market PDFs, invoices, and posters where house style requires Thai digits for years, page numbers, and quantities while internal data stores still use Western digits. E-commerce and booking systems display stock counts or order totals in Thai script for local storefronts and need a deterministic map that never invents fractions. Education platforms and language-learning apps quiz learners on reading Thai prices and calendar years, so teachers need a trusted oracle that converts whole integers both ways without model drift.
Treat full Thai number-to-words prose, currency formatting with baht subunits, date localization, and general multi-base radix conversion as separate search intents with their own landings rather than stretching this integer digit-script converter past its honest scope.
What you can do with it
Thai DTP and invoice digits
Rewrite Western years, quantities, and page numbers as Thai numerals for print-ready Thai-market layouts while keeping internal data in ASCII digits.
Storefront and CMS localization
Convert whole integer stock counts and order totals between Western storage and Thai display scripts for local storefronts and templates.
FAQ
Which Thai digits does this converter use?
The standard ten Thai numerals ๐ ๑ ๒ ๓ ๔ ๕ ๖ ๗ ๘ ๙ (Unicode U+0E50 through U+0E59), mapped one-to-one onto Western digits 0 through 9.
What directions are supported?
Direction is required so the expected script is explicit.
Are negative integers allowed?
Yes. An optional ASCII leading minus is preserved on both the western and thai fields. Zero is always returned without a sign.
What does it cost?
The browser tool is free and runs locally.
Does it also write numbers as Thai words?
No. It only swaps the ten digit shapes of a whole number, so 2026 becomes ๒๐๒๖. Writing numbers out as Thai words, currency formats and dates are outside what it does.
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/thai-numerals \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":"2026","direction":"to_thai"}'const res = await fetch("https://api.kit.forhosting.com/fmt/thai-numerals", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": "2026",
"direction": "to_thai"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/fmt/thai-numerals",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": "2026",
"direction": "to_thai"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/fmt/thai-numerals", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":"2026","direction":"to_thai"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":"2026","direction":"to_thai"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/fmt/thai-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": "2026",
"direction": "to_thai"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "fmt.thai_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.
Limits
max_digits | 15 |
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
Successful API calls use the published base of $0.002 per item; invalid input is not charged.
How Western and Thai digit conversion works
The algorithm uses only string tables and character walks: no floating-point rounding, no random seeds, no wall-clock timestamps, and no network calls, so identical inputs always produce identical JSON. Values that are not whole integers—decimal points, commas as separators, scientific notation, letters, spaces inside the body, or Thai digits when Western was required—are rejected with invalid_input.
What you send and what you get back
Send two required fields: value and direction. Classic checks include two thousand twenty-six encoding to ๒๐๒๖, zero staying zero in both scripts, and decoding ๑๒๓ back to one hundred twenty-three. Direction must be to_thai when value is a Western whole integer, or to_western when value is written with Thai numeral digits. Aliases are accepted so forms and scripts can use the names that fit their UI: value also accepts n, number, input, text, and digits; direction also accepts dir, mode, and op, plus short synonyms such as to, thai, from, and western. For to_thai, value may be a JSON integer or a digit string with an optional leading plus or minus; fractions, scientific notation, bare words, NaN, Infinity, and Thai glyphs in the body fail with invalid_input and are not charged. For to_western, every body character must be one of the ten Thai numeral digits; Western digits in that direction fail with a message that names the wrong character. On success the response echoes the cleaned value token, the normalized direction, western and thai spellings of the same integer (including sign when negative), result as the primary converted form for the chosen direction, sign as one or negative one, digit_count for the absolute magnitude, and script as thai or western to label which form is the conversion target. Pricing for successful API calls is the published base of $0.002 per item; validation failures do not consume prepaid balance.
Where Thai numeral converters show up in real work
Government and civic tech projects normalize scanned forms that mix scripts: a field may arrive with Thai digits while the backend schema expects ASCII, or the reverse for print templates. Because this capability is a pure parse engine, API pricing is the published base of $0.002 per successful item and failed validation does not consume balance.
Integration use cases
Teaching and round-trip fixtures
Generate homework keys and golden Western ↔ Thai digit pairs for language apps, unit tests, and form-normalization pipelines.
Technical questions
Does it accept decimals or fractions?
No. Only whole integers are accepted. Decimal points, commas, scientific notation, and other non-integer tokens fail with invalid_input.