How to convert decimal separators without retyping
A German supplier sends an invoice in European format — 1.234,56 € — and your spreadsheet expects US format. The naive fix is find-and-replace, which breaks immediately: swapping every comma for a dot turns 1.234,56 into 1.234.56, which a US spreadsheet reads as one point two three four, not one thousand two hundred thirty-four and fifty-six cents. The thousands separator has to go first, then the decimal comma becomes a dot — and the same trap runs in reverse.
This tool does exactly that, where the text already is: on your own device. When you paste text here, your browser:
- Finds the numbers and reads each one in the source format — grouping is validated, not guessed: western groups must be exactly three digits, Indian groups follow the lakh pattern (12,34,567.89), French groups are separated by a space. A number that does not fit the source format is left alone, not forced.
- Detects the source format when you leave it on Auto-detect — a number that only reads one way proves the format: 1.234,56 can only be European, 1,234.56 can only be US/UK. If no number proves it, the tool says so and asks you to pick the format instead of guessing.
- Rewrites each number in the target format and lists every change — original next to converted, plus the ambiguous numbers it refused to guess and the bare integers it left alone, so you can check the result before pasting it back. A downloadable text report carries the same detail.
What makes this converter different
The pages that top the results for this search mostly format one number at a time — type a value, get its formats — or normalise a list of numbers line by line, one value per row, with currency and accounting handling. Decimal conversion inside a CSV tool is a side option, not the job. None of them converts the numbers inside a pasted paragraph, invoice or price list in place, with the words untouched. This page is the only free, fully client-side dedicated decimal separator converter we found that does that — converting numbers in running text between six formats in any direction, auto-detecting the source when the text proves it, flagging ambiguous numbers instead of guessing them, and reporting every change — with no daily limits, no account and no watermark — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.
When is converting the right choice — and when is it the wrong one?
Converting is right whenever numbers cross a locale boundary: a European invoice into a US spreadsheet, a US price list into a German report, an Indian ledger into plain machine format for an import. It is the wrong choice for a document whose numbers are meant to stay as written — a legal text quoting a foreign invoice, or a dataset where the separators carry meaning beyond the value. If the destination accepts the source format, leave the numbers alone instead of converting them.
Honest limitations
Bare integers stay bare
A number with no separator at all — 2024, 1234567 — is left unchanged, because it is usually a year, a code or an ID. Grouping it would corrupt the text.
Versions look like decimals
A version number such as 1.1 looks exactly like a decimal number, so it converts like one. Check the change list after converting.
Dates are left alone
12.03.2024 and 192.168.1.1 have more than one decimal separator, so they are not numbers in any supported format — they are left unchanged.
Western digits only
Only 0-9 are handled. Arabic-Indic (٠-٩) and Persian (۰-۹) digits are a different conversion and are left unchanged.
French spaces can mislead
French grouping uses spaces, so a phone fragment such as 555 123 can look like a French number. In auto mode it is flagged, not converted.
It never changes a value
This tool only moves separators. It never rounds, never re-values, and never touches the words around a number — if a number looks wrong, the source text was wrong, not the conversion.