Map Extract

If a CSV shows é instead of é, £ instead of £ or ’ instead of an apostrophe, the file is UTF-8 and Excel has read it as an older Windows encoding. The data is usually fine. Import it with Data, From Text/CSV and set File Origin to 65001: Unicode (UTF-8), or give the file a byte order mark (BOM) so Excel recognises UTF-8 on a double-click. When you save, choose CSV UTF-8 (Comma delimited).

This is one of the export problems in the B2B lead list cleaning checklist. Lead lists hit it constantly, because business names, addresses and descriptions contain accents, currency symbols and curly apostrophes.

Why it happens

A CSV is just text. RFC 4180 defines commas, quotes and line breaks but does not fix a character set; it allows an optional charset parameter that a file on disk never carries. So the program opening the file has to guess.

Most modern tools write UTF-8, where characters outside basic English take two to four bytes. When you double-click a CSV, Excel for Windows assumes your system's legacy code page (Windows-1252 in the UK and US) unless the file starts with a BOM. Each multi-byte character is then shown as two or three separate characters. That pattern has a name: mojibake.

The mojibake table

Find the garbled text you see, and the right-hand column tells you what it should be.

You seeShould beUTF-8 bytesTypical in lead data
ééC3 A9Café, Chloé, Société
üüC3 BCMüller, Zürich
ööC3 B6Björk, Köln
ççC3 A7Façade, Françoise
££C2 A3"From £49" in descriptions
 before a spacenon-breaking spaceC2 A0Copied website text
€€E2 82 ACPrices for Irish and EU businesses
’’ (curly apostrophe)E2 80 99Joe’s Café, Smith’s Garage
““ (opening curly quote)E2 80 9CQuoted taglines
ŵŵC5 B5Welsh place names
Å‚łC5 82Polish names (Łódź, Michał)
ÅŸşC5 9FTurkish names
ααCE B1Greek business names
ддD0 B4Cyrillic names
ã‚«カE3 82 ABJapanese names
 at the start of the first header(BOM)EF BB BFA UTF-8 file with a BOM opened by a tool that does not expect one
ééMojibake that was saved and read again (double encoding)
� or ?Any non-ASCII characterThe opposite problem: a non-UTF-8 file read as UTF-8, or characters lost on saving

If almost every accented character turns into a pair starting with à or Â, you are looking at UTF-8 read as Windows-1252. That is the common case and the easy one to fix.

Fix 1: import the file as UTF-8

Microsoft's own guide, opening CSV UTF-8 files correctly in Excel, recommends importing rather than double-clicking:

  1. Open a blank workbook.
  2. Go to Data, Get Data, From File, From Text/CSV and choose the file.
  3. In the preview, set File Origin to 65001: Unicode (UTF-8). The garbled characters in the preview should correct themselves immediately.
  4. Check Delimiter is Comma.
  5. Select Transform Data if any column needs to stay as text (phone numbers, postcodes, IDs), set those columns' type to Text, then Close & Load. Otherwise select Load.

While you are in the import, protect phone numbers too: the same double-click that garbles accents strips leading zeros. See Excel removes the leading zero from phone numbers.

Microsoft also documents the legacy route, Get Data From Text, which opens the Text Import Wizard; choose 65001: Unicode (UTF-8) in its File origin box.

Fix 2: add a byte order mark

Microsoft's page notes that "You can open a CSV file encoded with UTF-8 normally if it was saved with BOM (Byte Order Mark)". The BOM is three bytes, EF BB BF, at the very start of the file. Excel takes them as a signal to read the file as UTF-8.

Ways to add one:

  • Re-export with a BOM. Many tools offer "UTF-8 with BOM" or "Excel-compatible UTF-8" as an export option.
  • Windows Notepad. Open the CSV, choose File, Save As, set Encoding to UTF-8 with BOM, and save.
  • Excel itself. Saving as CSV UTF-8 (Comma delimited) in current Windows versions of Excel typically writes a BOM; check the first bytes in a text editor if a downstream tool complains (see below).

When not to use a BOM

Some importers, scripts and older CRMs do not expect a BOM. They treat the three bytes as part of the first column name, so name becomes name and the import fails with "column not found". If you see that, export without a BOM for that tool. A sensible habit: BOM for files a person will open in Excel, no BOM for machine imports, and check the target tool's documentation.

Fix 3: save it back without losing characters

Saving is where accents are lost for good.

Save as typeEncoding writtenWhat happens to non-Latin characters
CSV UTF-8 (Comma delimited)UTF-8 with BOMKept
CSV (Comma delimited)Your computer's legacy code pageCharacters outside it become ?
Excel Workbook (.xlsx)Unicode internallyKept

So "Michał" survives CSV UTF-8 but becomes "Micha?" in plain CSV on a UK computer. Once saved, the original letter is gone from that file. Keep the working copy as XLSX and export CSV UTF-8 only when another tool needs a CSV.

Repair a file that already contains mojibake

First check which case you have. Open the CSV in a plain text editor that shows encoding (Notepad shows it in the status bar).

  • The text editor shows é correctly: the file is fine; only Excel's import was wrong. Use Fix 1 or Fix 2.
  • The text editor also shows é: someone opened the file wrongly and saved it, so the garbled characters are now real. Re-importing will not help.

For the second case, the best fix is to re-export from the original source. If that is not possible, the damage can usually be reversed, because it was caused by one specific mistake. In Python, for example:

fixed = garbled.encode("cp1252").decode("utf-8")

turns é back into é. Test it on a copy, and check characters such as curly quotes, which can fail where the Windows-1252 table has gaps. Double-encoded text (é) needs the step applied twice.

Prevent it next time

  • Export lead data as UTF-8. Add a BOM if the file is for Excel users.
  • Open CSVs with Data, From Text/CSV, never by double-clicking, unless the file has a BOM.
  • Keep the master copy in XLSX or the source system, not in a CSV someone edits.
  • Save with CSV UTF-8 (Comma delimited), never plain CSV, when names contain anything beyond A to Z.
  • Spot-check a few names with accents, a pound sign and an apostrophe after every export.

Once the characters are right, cleaning a B2B lead list covers tidying names and other fields, and deduplicating business leads covers match keys.

How Map Extract helps

  • CSV exports from Map Extract can be written as Excel-compatible UTF-8 with a byte order mark, so accented business names and the pound sign open correctly in Excel on a double-click. Leave the option off for tools that reject a BOM.
  • Exports are also available as XLSX, which avoids CSV encoding guesses altogether, and as JSONL for scripts and databases.
  • The website data extractor keeps the original text it captured from each site, and can add English display versions of eligible descriptive fields alongside the source-language text, without replacing the original.
  • The workflow builder saves your sources and their order as a repeatable recipe, so each run produces the same columns for a saved import to refresh.

What it does not do: it cannot change how Excel opens a file on your computer, and it cannot repair a CSV that was garbled and saved after export.

Key takeaways

  • é, £ and ’ mean UTF-8 read as Windows-1252; the data is usually fine.
  • Import with Data, From Text/CSV and File Origin 65001: Unicode (UTF-8).
  • A BOM makes Excel recognise UTF-8 on a double-click, but some importers reject it.
  • Save as CSV UTF-8 (Comma delimited), never plain CSV, to keep non-Latin characters.
  • If the garbled text was saved, re-export from source or reverse it with a cp1252 to UTF-8 conversion.

Frequently asked questions

Why does my CSV show £ instead of £ in Excel?

The file is saved as UTF-8, where the pound sign is stored as two bytes, but Excel opened it with a Windows code page such as Windows-1252, which reads those two bytes as two separate characters, Â and £. Nothing is wrong with the data. Import the file with Data, From Text/CSV and set File Origin to 65001: Unicode (UTF-8), or add a byte order mark.

What is a BOM in a CSV file?

A byte order mark is three invisible bytes, EF BB BF, at the very start of a UTF-8 file. Excel uses them as a signal that the file is UTF-8, so a CSV with a BOM opens correctly when double-clicked. Some other tools do not expect it and show  before the first column name. Use a BOM for files people open in Excel, and no BOM for imports that reject it.

How do I save a CSV from Excel without losing accents?

Use File, Save As and choose CSV UTF-8 (Comma delimited) rather than CSV (Comma delimited). The plain CSV option saves in your computer's legacy code page, so characters outside it, such as Polish, Greek, Arabic or Chinese letters, are replaced with question marks. The UTF-8 option keeps every character and, in current Windows versions, typically adds a byte order mark, so Excel reads it back correctly.

Can I repair a CSV that already shows é everywhere?

If the file itself is fine and only Excel's display is wrong, re-import it as UTF-8 and the characters reappear. If someone has already saved the garbled text, the bytes now really contain é, and re-importing will not help. That damage can usually be reversed by encoding the text back as Windows-1252 and decoding it as UTF-8, but re-exporting from the original source is safer.

Sources

  1. Opening CSV UTF-8 files correctly in Excel, Microsoft Support
  2. RFC 4180: Common Format and MIME Type for CSV Files
  3. Microsoft Support: Set automatic data conversions

Written by the Map Extract editorial team. Found an error? Email [email protected] and we will check and correct it. How we research guides: editorial policy.

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top