About
This tool allows you to insert commas or periods into numbers within a text. It functions by identifying numbers and then applying commas or periods where appropriate. Typically, when representing numerical values, any numbers with more than three digits have a comma added after every third digit, counting from right to left.
The tool operates on the assumption that the numbers in the text lack proper formatting, but it can identify decimal separators and the fractional part of numbers (e.g., 1000.00). Once you've applied commas, you cannot subsequently apply periods (for European languages). To undo these changes, use the undo function accessible under the edit button.
Use Comma
In US/UK English, a comma is used to separate every third digit, while a period serves as the decimal separator. This is the default setting.
Before
1000
1000.00
10000
After
1,000
1,000.00
10,000
Use Period
In many European countries, the roles are reversed. A period serves as the thousands separator, while a comma is used as the decimal point. Choose this option for other languages.
Before
1000
1000,00
10000
After
1.000
1.000,00
10.000
Format long numbers with grouping separators. Review totals in reports while keeping identifiers separate from quantities.
How to use
Choose comma or period grouping, paste unformatted numbers, and apply. Keep an untouched copy when converting data that already contains separators.
Example
1000000 becomes 1,000,000 with comma grouping. Check decimal values separately before reusing financial figures.
FAQ
Should I format phone numbers or codes?
No. Grouping changes their text. Select only numeric quantities and check decimals, existing punctuation, and account identifiers.
A practical task
Separate quantities from codes before applying grouping. In a stock report, 12000 units is a quantity, but product code 0012000 is an identifier. Keep those columns apart so formatting does not silently change the code.
Another useful question
Should I apply grouping twice?
Work from the unformatted source. Reprocessing already grouped values can produce unexpected punctuation, especially when the source mixes decimal conventions.
Details for interpreting the result
| Detail | Explanation |
|---|---|
| Units and quantities | Arithmetic needs compatible quantities. A count, a currency amount, a rate, and a label can share the same digits but mean different things. Keep units next to the inputs when checking a numerical result. |
| Strings and values | The JSON string "12" differs from the number 12, and "false" differs from false. Type changes affect comparisons and imports. Keep identifiers as strings when their leading zeros or exact digits matter. |
