How to Import AI-Generated CSV Into Excel Without Breaking Accented Characters

Summary

• Accented characters break in Excel when the CSV’s encoding (UTF-8 vs ANSI/Windows-1252) is misread during import.
• The most reliable fix is importing via Excel’s data import (not double-clicking the CSV) and explicitly choosing “65001: Unicode (UTF-8)” when available.
• If Excel still mangles accents, convert the file to “UTF-8 with BOM” before importing, or use a delimiter/encoding-aware workflow.
• Always run a quick “result check” on a few known accented strings (e.g., “José”, “München”, “Łódź”) before sharing the workbook.
• AI-generated CSVs can also fail due to delimiter/quote issues; validate commas, quotes, and line breaks alongside encoding.

If you generated a CSV with an AI tool and Excel turns “José” into “José” (or “München” into “München”), the problem is almost never the accents themselves. It’s Excel importing the file using the wrong text encoding. The fix is to import the CSV through the right Excel workflow and explicitly set UTF-8 (or convert the file to UTF-8 with BOM) so Excel reads the bytes correctly.

This guide shows a reproducible example, step-by-step import instructions for Excel desktop and Excel for the web, plus a quick result check so you can confirm the accents are preserved before you continue working.

Why accented characters “break” in Excel CSV imports

A CSV file is plain text. Plain text only becomes readable characters after an app chooses an encoding (a mapping from bytes to characters). Many AI tools output CSV in UTF-8. Excel sometimes opens CSVs as if they were ANSI/Windows-1252 (or another legacy encoding), which causes the classic mojibake effect:

• Expected: José
• Broken: José

That “é” is a strong hint the file is UTF-8 but was interpreted as a single-byte encoding.

A reproducible example you can test

Create a small CSV that includes a range of accented characters and a non-ASCII punctuation mark. Copy the text below into a plain-text editor (Notepad, VS Code, TextEdit in plain text mode) and save it as ai-sample.csv using UTF-8 encoding.

name,city,notes
José,São Paulo,Café com leite
München,München,Fußgängerzone
François,Québec,Crème brûlée
Łódź,Łódź,Zażółć gęślą jaźń
Zoë,Zürich,naïve coöperate

Important: If your editor offers an encoding choice, pick UTF-8. If it offers UTF-8 with BOM, that can be helpful for Excel (more on that below).

Best method (Excel desktop): Import the CSV and set UTF-8 explicitly

The most reliable approach is to import the CSV through Excel’s data import flow rather than opening it by double-clicking. The exact labels can vary by Excel version, but the key is: use the import wizard and choose UTF-8.

Option A: Use “From Text/CSV” (recommended when available)

1. Open Excel (desktop) and create a new workbook.
2. Go to the Data tab.
3. Choose Get Data (or Get & Transform Data), then select From Text/CSV.
4. Select your CSV file.
5. In the import preview dialog, look for a setting like File Origin or Encoding.
6. Select 65001: Unicode (UTF-8) (or an option explicitly labeled UTF-8).
7. Confirm the delimiter (comma) and verify the preview shows accents correctly.
8. Click Load (or Transform Data if you need to fix columns first).

Option B: Use the legacy text import wizard (if your Excel shows it)

Some Excel installations provide a “Text Import Wizard” path (or a way to import text with encoding selection). If you see an import wizard that asks for file type and encoding:

1. Choose Delimited.
2. Set File origin to Unicode (UTF-8) if available.
3. Select Comma as the delimiter.
4. Finish the import and check the results.

If you do not see UTF-8 as an option in the wizard, jump to the “Convert to UTF-8 with BOM” section below.

What not to do (common ways accents get corrupted)

• Don’t double-click the CSV and assume Excel will detect UTF-8 correctly.
• Don’t copy/paste the raw CSV text into Excel unless you are certain the clipboard text is being interpreted as UTF-8 and the delimiter/quotes are intact.
• Don’t “Save As CSV” after corruption and then send that file onward; you may be saving the broken characters permanently.

If Excel still breaks accents: convert the CSV to “UTF-8 with BOM”

Some Excel setups recognize UTF-8 more reliably when the file includes a BOM (byte order mark). This does not change your visible text; it adds a small signature at the start of the file that helps some programs detect UTF-8.

Windows: Convert using Notepad

1. Right-click the CSV and open it with Notepad.
2. Go to File > Save As.
3. Set Encoding to UTF-8 (in some Notepad versions this may effectively write a BOM; the label varies).
4. Save as a new file name (e.g., ai-sample-utf8.csv) to avoid overwriting the original.
5. Import the new file into Excel using Data > From Text/CSV and re-check the preview.

Cross-platform: Convert using VS Code

1. Open the CSV in VS Code.
2. Click the encoding indicator in the status bar (often shows “UTF-8”).
3. Choose Save with Encoding.
4. Select UTF-8 with BOM.
5. Re-import into Excel.

If you cannot find “UTF-8 with BOM,” you can still try plain UTF-8 plus the explicit UTF-8 selection during import. The goal is: Excel must read the file as UTF-8.

Excel for the web (browser): what to expect and a safer workflow

Excel for the web can open CSVs, but encoding handling and import controls can be more limited than desktop Excel. If your accents break in the browser:

• First, convert the CSV to UTF-8 with BOM and try uploading/opening again.
• If it still breaks, import the CSV in Excel desktop with UTF-8 selected, then save as .xlsx and open that workbook in the browser.

This “import on desktop, then use .xlsx in the browser” approach avoids repeated CSV encoding detection steps.

Result check: confirm accents are preserved (before you continue)

After import, do a quick verification pass:

• Search within the sheet for José, München, São, Łódź, and Zoë.
• Look for telltale corruption patterns like Ã, Â, or replacement characters (often shown as a diamond with a question mark).
• If you see corruption, stop and re-import using the UTF-8 steps above. Fixing after the fact is harder than importing correctly.

AI-generated CSV gotchas beyond encoding (that can look like “character issues”)

Sometimes the accents are fine, but the CSV structure is broken, which can make the sheet look garbled.

1) Wrong delimiter (comma vs semicolon)

In some locales, Excel expects semicolons as separators. If your entire row lands in one column, it may be a delimiter mismatch. During import, set the delimiter explicitly (comma or semicolon) and confirm the preview splits into columns correctly.

2) Unescaped quotes

If AI output includes quotes inside fields (e.g., He said "hello") without proper escaping, Excel may shift columns or merge lines. In CSV, embedded quotes should be doubled (e.g., He said ""hello"") when the field is quoted.

3) Line breaks inside fields

If a field contains a newline (common in AI-generated “notes” columns), it must be wrapped in quotes. Otherwise, Excel may treat it as a new row.

4) Mixed encodings in one pipeline

If you copy the CSV through multiple tools (chat window, email, editor, download), you can end up with a file saved in a different encoding than you think. When in doubt, re-save as UTF-8 (or UTF-8 with BOM) from a code editor and re-import.

Practical “do this every time” workflow for AI-generated CSVs

1. Generate the CSV from your AI tool.
2. Save it as a file in UTF-8 (preferably UTF-8 with BOM if Excel has misread it before).
3. Import via Excel desktop Data > From Text/CSV and set encoding to UTF-8.
4. Check a few known accented strings immediately.
5. Convert to .xlsx once it looks correct, especially if you will share or open it in Excel for the web.

Frequently Asked Questions

Back to FAQ Table of Contents

Back to FAQ Table of Contents

Back to FAQ Table of Contents

Back to FAQ Table of Contents

Back to FAQ Table of Contents

Back to FAQ Table of Contents

Back to FAQ Table of Contents

Back to FAQ Table of Contents

Related Guides

• What Is an AI Context Pack?
• How to Prepare Better Context for ChatGPT
• How to Organize Copied Text for AI Work
• Source-Labeled Context for AI: Why It Matters
• ChatGPT Context Pack for Consultants