Excel Import CSV with Decimal Point: Fix Number Parsing

Errors & fixes · Updated November 19, 2026

To import a CSV with decimal points correctly in Excel for Microsoft 365 on Windows, use Data > From Text/CSV instead of double-clicking the file. Choose Transform Data, select the affected column, then use Transform > Data Type > Using Locale and choose Decimal Number with a locale that uses a point as its decimal mark, such as English (United States). This tells Excel how to interpret the values before loading them.

Why Excel changes decimal points

A CSV file stores text separated by a delimiter; it does not reliably carry spreadsheet formatting or tell every program what a decimal mark means. When Excel opens a CSV directly, it tries to interpret the text using settings on your computer. Those settings can differ from the conventions used to create the file. For example, one region may write a decimal as 12.50, while another writes it as 12,50.

As a result, a value such as 12.50 may be imported as text, treated as a different number, or—in some cases—read as 1250 if punctuation is interpreted as a thousands separator. A value such as 1.234 is particularly ambiguous: depending on the source convention, it could mean one and 234 thousandths or one thousand two hundred thirty-four. Excel cannot infer the intended meaning from the characters alone.

It is useful to distinguish three things that often get mixed up:

  • Decimal separator: the mark between whole and fractional parts, such as the point in 12.50.
  • Thousands separator: an optional grouping mark, as in 1,234.50.
  • CSV delimiter: the character between fields, commonly a comma, semicolon, or tab.

A comma-delimited CSV can contain decimal points without conflict: for instance, a row might contain 12.50,North. But a comma used inside a number can be confused with the field delimiter unless the field is quoted or another delimiter is used. The delimiter and decimal convention are separate choices.

Use Power Query for a controlled import

Power Query is the most reliable option when you want to choose the file delimiter and decimal interpretation explicitly. It also makes it easier to repeat the same import if the source file is updated. These steps are for Excel for Microsoft 365 on Windows:

  1. Open the workbook where the imported data should go and select Data > From Text/CSV.
  2. Browse to the CSV and select Import. Check the preview, especially the delimiter and whether the columns line up as expected.
  3. Select Transform Data to open the Power Query Editor. If a numeric column has already been assigned an unsuitable type, select it and change its type using a locale.
  4. On the Transform tab, open Data Type and choose Using Locale. In the dialog, choose Decimal Number as the data type and select a locale that recognizes the source’s decimal point, such as English (United States).
  5. Check the preview for correct values and error indicators, then select Home > Close & Load to place the result in Excel.

The locale setting is a parsing instruction, not merely a display preference. For example, if a source column contains 12.50 and the selected locale recognizes the point as the decimal mark, Power Query can convert the text into a number with a value of twelve and a half. If the source uses a different convention, choose the locale that matches the source data, not simply the language you prefer to use in Excel.

Choose the right locale and inspect the source

Before converting a column, look at several original values and, if possible, confirm the format with the person or system that produced the CSV. A column containing 12.50 and 103.75 strongly suggests a point decimal, but values without fractional digits do not reveal the convention. Thousands grouping creates another complication: 1,234.56 commonly means one thousand two hundred thirty-four and 56 hundredths in a point-decimal convention, while 1.234,56 commonly expresses the same number in a comma-decimal convention.

Do not select a locale just because it makes the preview look plausible for one row. Check small and large values, negative values, and values with more than two decimal places. If a source contains both a decimal point and a comma grouping mark, confirm that the locale recognizes both. If the source has inconsistent punctuation, fix or clarify the source rather than trusting an automatic conversion to guess correctly.

Locale can matter for more than numbers. It can also affect how dates are interpreted: 03/04/2026 may represent March 4 or April 3, depending on the convention. When importing several columns, check date and number columns separately. In Power Query, you can assign a suitable type and locale to each column rather than relying on one assumption for every field.

Set Excel’s decimal separator for direct entry

If you regularly work with files that use a point decimal and want Excel itself to use that convention, you can change Excel’s separator settings. On Windows, go to File > Options > Advanced. Under Editing options, clear Use system separators, then enter a period for Decimal separator and, if appropriate for your data, a comma for Thousands separator.

This setting changes how Excel interprets and displays numbers in the application; it is not a targeted repair for one CSV. It can affect other workbooks and data you enter, so consider whether changing it will disrupt your usual work. To return to the computer’s regional settings, select Use system separators again. If the goal is to import one unusual file, Power Query’s locale conversion is generally more controlled.

On Mac, Excel’s settings and labels differ from the Windows path. Current Microsoft 365 builds may offer text/CSV import through the Data tab, but the available Power Query features and dialogs can vary by build. If the locale option is not available, use the Mac version’s regional or separator settings carefully, or import the file in a Windows desktop version that provides the needed conversion controls. Excel for the web also has a different set of import and query controls from desktop Excel.

Fix a CSV that is already open or imported

If the values are still text, you may be able to convert them without starting over. First determine whether Excel has stored them as text or as numbers with the wrong magnitude. Text values often align to the left by default, but alignment is only a clue: formatting can override it. Select a cell and inspect the formula bar, or use a harmless test in a blank cell to check whether Excel recognizes a value numerically.

For a small, clearly consistent dataset, you can use Data > Text to Columns to re-interpret a column. Select the column, start the wizard, choose the appropriate delimiter settings, and proceed to the final step. The Advanced button there lets you specify the decimal and thousands separators used for conversion. Set the decimal separator to a period when the source uses a point decimal, and set the thousands separator only if the data actually uses one. Review the preview before completing the operation; this tool can split data if the wrong delimiter is selected.

Another option is to return to the import query and change the column’s type using the correct locale, then refresh or reload the result. This is preferable for recurring imports because the conversion is recorded in the query steps. Avoid broad find-and-replace operations on punctuation unless you know the data structure: replacing every period with a comma, for example, could alter dates, identifiers, or text as well as numbers.

Common import problems and how to diagnose them

  • The column is text, not a number. Excel may leave values unchanged when their punctuation does not match its parsing rules. Convert the column using the source locale, then confirm that totals and calculations recognize the values.
  • Values are 100 or 1,000 times too large or small. The decimal mark may have been treated as grouping punctuation, or the source may include a scaling convention. Compare the imported result with the original text before making a bulk correction.
  • Columns are shifted. Check the delimiter and whether fields containing that delimiter are correctly quoted. A decimal point normally does not split a comma-delimited row, but an unquoted comma inside a value can.
  • Some rows show errors while others convert. Look for mixed formats, blank markers such as N/A, currency symbols, spaces, or inconsistent separators. Decide whether those entries should remain text, be cleaned, or be handled as missing values.
  • Leading zeros disappear. Codes such as 00127 are often identifiers, not quantities. Set that column to text during import rather than converting it to a number.

A CSV is plain text, so the displayed number format from the program that created it is not necessarily preserved. After import, apply an Excel number format if you want a particular number of displayed decimal places. Formatting changes how a value appears; it does not correct a value that was parsed incorrectly. Verify the underlying value first.

Direct opening versus importing

Double-clicking a CSV is quick, but it gives Excel less opportunity for you to specify how the file should be interpreted. Depending on Windows regional settings and file associations, Excel may use the system’s decimal and list separators. This can be adequate for a one-off file already prepared for the same locale, but it is a poor choice when the source convention is different or the data needs to be repeatable.

Using Data > From Text/CSV lets you inspect the delimiter and use Power Query to set types and locale. The extra step is worthwhile for financial exports, scientific measurements, or operational reports where a silent change in magnitude could matter. For a file that has already been imported incorrectly, re-importing with explicit settings is often safer than trying to repair many cells individually.

Frequently Asked Questions

Why does Excel change 12.50 to 1250?
Excel may be interpreting the period according to a different regional convention, such as treating it as a grouping mark. Re-import the column with Using Locale and a locale that uses a point decimal, then verify the resulting value.

Can I import a comma-delimited CSV that has decimal points?
Yes. A comma can separate fields while a period marks the decimal fraction. Choose comma as the delimiter in the import preview and set the number column’s locale to match the decimal-point source.

Should I change Windows regional settings or Excel settings?
For one file, prefer a Power Query locale conversion because it is specific to that import. Changing Excel’s separator settings may suit a consistent workflow, but it can affect other workbooks and data entry.

Why are imported decimal values left-aligned?
They may have been imported as text, although alignment alone is not proof. Check whether Excel can use the cell in a calculation, then convert the column with the correct locale if necessary.

Will number formatting fix a decimal point imported incorrectly?
No. Number formatting changes the appearance of a numeric value, not the value’s interpretation. Correct the conversion first, check the underlying number, and then apply the display format you want.

What if the CSV mixes decimal conventions?
Do not apply one locale blindly to the entire column. Confirm the source rules and clean or separate inconsistent values before conversion. If the intended value is uncertain, ask the source owner rather than guessing.

Related

Try it: the Formula Explainer: paste any formula and see each function and reference in plain English.

More in Errors & fixes

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.