Why CSV Files Don't Display Correctly in Excel: Troubleshooting Guide
Urgent, practical guide to diagnosing why CSV files don't display correctly in Excel. Learn encoding, delimiter, and import settings with MyDataTables guidance.
Most display issues in Excel come from encoding or delimiter mismatches. Quick steps: 1) Reopen the CSV with Data > Get & Transform, select UTF-8 encoding or ANSI as needed. 2) Confirm the delimiter (comma vs semicolon) aligns with your regional settings. 3) Import with the proper Text/CSV wizard and adjust column breaks. If problems persist, re-save as UTF-8.
Why CSV display issues happen in Excel
CSV is a plain-text interchange format that Excel tries to parse into a grid of cells. When columns are not parsed correctly, you’ll see data spilling into adjacent cells or appearing in a single column. The question you’re solving—why csv file is not displaying correctly in excel—often reduces to two root causes: encoding and delimiter handling. Locale differences, export tools, and even how Excel opens the file (double-click vs. using the Import wizard) can all influence the result. According to MyDataTables, encoding and delimiter mismatches are common culprits in 2026, and addressing them early prevents cascading formatting problems. As you troubleshoot, remember that a CSV is not Excel-native formatting; you’re enforcing Excel’s parsing rules to interpret a plain text stream. This means the more you tailor the import step to your data, the better your initial view will be. The goal is to get reliable column breaks on first load, so you can inspect data types, dates, and numbers without guesswork.
Encoding, BOM, and character sets
Encoding determines how bytes map to characters. UTF-8 is the most common and versatile, but some CSVs arrive with a Byte Order Mark (BOM) at the start. Depending on Excel version and locale, BOM can confuse parsing, causing header names to shift or characters to appear garbled. If you see strange characters like or misrepresented accents, you’re likely facing an encoding or BOM mismatch. Test by re-saving the file as UTF-8 without BOM, or as ANSI if the data contains only standard ASCII. When you re-import, specify the correct encoding explicitly, rather than relying on Excel’s automatic guess. Always verify headers after import to ensure the first row represents column names rather than data entries.
Delimiters and regional settings: comma vs semicolon vs tabs
Delimiters are the characters Excel uses to split fields. In the US, comma-delimited files are common, but many European and other locales use semicolons because of decimal separators. If your CSV uses a semicolon or a tab and Excel expects a comma (or vice versa), fields end up merging into single cells. Check your regional settings and the source CSV’s delimiter, then import via Data > From Text/CSV where you can explicitly choose the delimiter. If you’re sharing files across regions, consider exporting a version with a consistent delimiter like comma and document the encoding used.
Excel’s import workflow vs. direct opening
Opening a CSV directly by double-clicking often bypasses the precise parsing controls that Excel’s Import Wizard provides. The safer path is to use Data > From Text/CSV (or Get Data) and walk through the import steps: specify the file origin, encoding, delimiter, and how to interpret data types. This reduces surprises such as dates being read as text, or numbers mis-formatted as text. If you must open directly, ensure your default program configuration aligns with the data’s encoding and delimiter. Consistency is key when you’re distributing files to teammates who might have different Excel settings.
The import wizard steps for the most common fix
To fix the most frequent issue, perform these steps: 1) Open Excel and select Data > From Text/CSV. 2) Browse to the CSV and choose the correct file origin (encoding) and delimiter. 3) Preview the data and adjust column types (dates, numbers, text). 4) Load the data into a new worksheet. If the preview still shows mismatches, go back and try UTF-8 with BOM or UTF-8 without BOM, depending on what the preview indicates. This workflow minimizes guesswork and reduces the need for post-import repairs.
Handling edge cases: dates, numbers, and quoted fields
Dates can be interpreted as text or shifted into the wrong format if the day-month order doesn’t match regional defaults. Numbers with thousand separators or currency symbols may also misparse if the delimiter and decimal settings are off. Quoted fields containing delimiters should be preserved; ensure quotes are correctly recognized during import. If your dataset includes mixed data types, consider performing a post-import data-type correction with Excel’s Power Query or a simple data-cleaning pass in MyDataTables guidance.
Prevention: best practices to avoid future issues
Proactively align your export and import workflows. Use UTF-8 encoding for broad compatibility, avoid BOM when the target system doesn’t require it, and export with a consistent delimiter (prefer comma for cross-region files, or semicolon for European locales with comma decimals). Encourage teammates to open via the import path rather than double-clicking, and provide a short guide for opening common CSVs. Keeping a small reference sheet with your organization’s CSV standards helps reduce recurring issues.
Quick checks before sharing CSV with teammates
Before distributing a CSV, validate a few quick checks: ensure the first row has headers, confirm the delimiter matches the recipient’s expectations, and verify that non-ASCII characters render correctly. Share a small sample and include notes about encoding and delimiter. If possible, provide both a UTF-8 CSV and a backup in a regional format (e.g., semicolon-delimited for EU users). These steps help ensure teammates see consistent data on arrival.
Steps
Estimated time: 30-45 minutes
- 1
Open Data > From Text/CSV
Launch Excel and navigate to the Data tab, then choose From Text/CSV to start a controlled import. This ensures you can specify encoding and delimiter before the data populates the sheet.
Tip: If you don’t see the option, update Excel or enable Power Query as needed. - 2
Choose the CSV file
Select the problematic CSV file from your filesystem. The preview pane will show how Excel plans to parse the data before loading it into the workbook.
Tip: If the preview looks wrong, don’t click Load yet. - 3
Set file origin (encoding) and delimiter
Choose the correct encoding (UTF-8 or ANSI) and the right delimiter (comma, semicolon, or tab). This is the critical step to ensure fields split correctly.
Tip: When in doubt, start with UTF-8 and comma, then adjust if needed. - 4
Preview and adjust data types
Review how Excel interprets headers and columns. Adjust data types (date, number, text) to prevent misformatted values after loading.
Tip: If a date is wrong, try a different date format in the import option. - 5
Load to worksheet
Click Load to place the parsed data into a new worksheet. Consider loading to a new sheet to keep a clean workspace.
Tip: Always load to a new sheet during troubleshooting to preserve the original data. - 6
Validate once loaded
Scan a few rows to confirm columns align, headers are correct, and there are no stray characters.
Tip: If anything looks off, repeat with a different encoding or delimiter. - 7
Document export/import settings
Record the selected encoding and delimiter so future CSVs follow the same reliable path.
Tip: Include notes on regional settings for teammates. - 8
If problems persist, consider alternatives
If you consistently see issues, export as UTF-8 without BOM or share via XLSX when formatting is needed; otherwise use a script to sanitize the CSV first.
Tip: For ongoing workflows, standardize on a single encoding and delimiter in your data pipelines.
Diagnosis: CSV data appears garbled or columns merge into a single column when opened in Excel
Possible Causes
- highIncorrect encoding (e.g., UTF-8 with BOM not detected, or ANSI)
- highDelimiter mismatch (CSV uses semicolons or tabs, but Excel expects commas)
- mediumRegional settings causing delimiter/regional date interpretation
Fixes
- easyOpen with Data > From Text/CSV and specify encoding (UTF-8 with BOM or ANSI) and correct delimiter
- easyTemporarily change Excel's regional settings or specify delimiter during import
- easyResave CSV using UTF-8 without BOM if BOM creates issues; or use a delimited version
People Also Ask
Why does my CSV show all data in one column in Excel?
This usually happens when Excel doesn’t parse the delimiter correctly or when the encoding is misread. Use the Import Wizard to specify the right delimiter and encoding, then reload the data.
If all data appears in one column, that’s a parsing issue—fix by importing with the correct delimiter and encoding, then reload.
How do I fix encoding problems in CSV for Excel?
Save the file as UTF-8 (with or without BOM depending on your Excel version) and re-import using the From Text/CSV wizard. This often resolves garbled characters.
Encoding problems usually show up as garbled characters; re-save as UTF-8 and import with the wizard.
What delimiter should I use if my regional settings use semicolons?
If your region uses semicolons, import with a semicolon delimiter, or export the CSV using semicolons and verify in the import dialog.
If your region uses semicolons, set the delimiter to semicolon during import.
Is there a safe way to share CSV with Excel that avoids parsing errors?
Yes. Use UTF-8 encoding, quote fields containing commas, and provide a brief guide on how to import. Consider sharing an XLSX version for formatting needs.
Share UTF-8 CSVs with quoted fields and provide import instructions for reliability.
When should I export as Excel instead of CSV?
Export to Excel when you need formatting, formulas, or multiple sheets; use CSV for raw data interchange and cross-platform compatibility.
Choose Excel when you need features; CSV for data-only interchange.
Watch Video
Main Points
- Check encoding and delimiter first
- Use Data > From Text/CSV for reliable parsing
- Standardize on UTF-8 and a consistent delimiter
- Test and document import settings for future CSVs
