Map Extract
Free tool

Fix a CSV so Excel opens it properly

Drop in a lead list or any CSV and get back a copy that Excel opens in clean columns, with accents and £ signs intact, phone numbers that keep their first 0 and long IDs that stay whole.

Runs in your browser. Nothing you enter is uploaded.

Repairing a file

  1. Load the CSV

    Choose or drop the file, or paste the rows. A file is decoded from its raw bytes: UTF-8 with or without a byte order mark, UTF-16, or Windows-1252 when the bytes are not valid UTF-8. Pasted text counts as UTF-8.

  2. Read the four counters

    The tool reports the encoding it read, the delimiter it found (comma, semicolon, tab or pipe, counted outside quotes), the number of data rows and how many garbled sequences such as é are already in the text.

  3. Pick the separator for the person opening it

    Choose Comma for Excel with UK, Irish or US regional settings, Semicolon for a colleague whose Windows uses a decimal comma, or Tab. Keep the byte order mark ticked unless the file goes to a system that rejects one.

  4. Choose the columns to protect

    Columns holding values Excel would alter are listed and ticked, each with the reason and an example. Columns named like phones, postcodes or IDs appear too, unticked when nothing in them is at risk.

  5. Compare and download

    Check the change report and the before and after lines, then select Download fixed CSV. The copy keeps your file name with -excel added.

Example: a semicolon export that was opened and saved once too often

This fictional four-row list had already been through the wrong program: the accents had turned into é and É, the pound sign into £ and an apostrophe into ’. It also used semicolons, and its gm_cid column held 20-digit place identifiers that Excel would round.

The tool found the semicolon, counted four garbled runs and flagged two columns at risk: gm_phone (leading zeros and a +44 number) and gm_cid (long numbers). With Comma, the byte order mark, the repair option and both protections on, the report read: four runs repaired, delimiter changed from semicolon to comma, line endings changed from LF to CRLF, the BOM added and eight cells written as ="...". The postcode column was listed for its name but left unticked, because M1 1AA contains a space.

Input
gm_business_name;gm_phone;gm_postcode;gm_cid;gm_city;notes
Café Lumen;01614960000;M1 1AA;12345678901234567890;Manchester;Owner Émilie
Quay Joinery;+447700900000;LS1 4AP;98765432109876543210;Leeds;£50 call-out
Result
gm_business_name,gm_phone,gm_postcode,gm_cid,gm_city,notes
Café Lumen,"=""01614960000""",M1 1AA,"=""12345678901234567890""",Manchester,Owner Émilie
Quay Joinery,"=""+447700900000""",LS1 4AP,"=""98765432109876543210""",Leeds,£50 call-out

What Excel does to each kind of value

These are the patterns the tool looks for. A value is only wrapped when it matches one of them, so ordinary text and plain numbers such as ratings are written unchanged.

Value in the CSVWhat a double-click in Excel showsWhy
016149600001614960000Numbers have no leading zeros
+4477009000004.47701E+11The plus is read as a sign, then scientific notation
123456789012345678901.23457E+19Over 15 significant digits are rounded and lost on save
12-14a date such as Dec-14Looks like a month and year
2E5200000Read as a power of ten
0161 496 00000161 496 0000The spaces make it text, so it survives
CaféCaféAlready damaged: needs the repair, not just a BOM

Why the byte order mark matters

A CSV file carries no label saying which character set it uses. When Excel for Windows opens one without a hint, it falls back to the computer's legacy code page, which on a UK machine is usually Windows-1252. UTF-8 stores é as two bytes, and read as Windows-1252 those two bytes display as é. The file is fine; the reading is wrong.

The byte order mark is three bytes (EF BB BF) at the very start of the file that tell Excel the text is UTF-8. Many web apps and scripts write UTF-8 without it, which is why their exports look broken in Excel but fine in a text editor.

The harder case is a file that was opened with the wrong encoding and then saved: the é is now real text, and a byte order mark preserves it faithfully. The repair option turns each garbled run back into its original bytes and decodes them as UTF-8, replacing a run only when the result is valid, so correct accented text is never touched.

Columns, delimiters and the formula trade-off

Excel splits a double-clicked CSV on the Windows list separator. With UK settings that is a comma. In many European regions the decimal mark is a comma, so the list separator becomes a semicolon, and a comma file lands in column A as one long string. Switching the delimiter here, rather than asking the recipient to change Windows settings, is usually the kinder fix. Values that contain the new delimiter are quoted automatically.

Protection works by writing a cell as ="07700900000", a tiny formula whose result is the text. Excel shows the digits exactly, sorts them as text and, if you later save as CSV from Excel, writes the plain value back out. The catch is that any other program reads the raw characters, equals sign and quotes included. Keep the protected copy for people who will open it in Excel, and send the original, or a copy with protection switched off, to a CRM import or a database. Cells that begin with =, +, - or @ without being numbers are counted in the report too, since Excel may run them as formulas.

Questions people ask

How do I stop Excel removing leading zeros from a CSV?

Either import the file through Data, From Text/CSV and set the column type to Text, or prepare the file so a double-click works: write each zero-led value as ="0123", which Excel displays exactly as typed. This page does the second for the columns you tick, and only changes values Excel would otherwise convert, such as 01614960000 or a 20-digit ID.

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

The file is UTF-8 but Excel read it with the Windows code page because nothing told it otherwise. Adding a UTF-8 byte order mark at the start fixes that for future opens. If the é is now stored in the file because someone saved it after opening it wrongly, the text itself needs repairing, which the repair option here does for one round of that damage.

Why does Excel put all my CSV data in one column?

Excel splits CSV columns using the list separator from your Windows regional settings. A comma file opens in one column on a computer set up for semicolons, which is common across Europe, and the reverse happens too. Convert the file to the separator the person opening it uses; quoted values containing that character stay in one cell.

What is a UTF-8 BOM and is it safe to add?

It is a three-byte marker, EF BB BF, at the start of a text file that declares the encoding as UTF-8. Excel, Google Sheets and most spreadsheet tools handle it without trouble, and Excel needs it to show accents reliably. A few strict parsers or command line tools treat it as part of the first column name, so untick the option for files headed to those.

Does this tool upload my CSV?

No. The file is read by JavaScript in your browser tab, decoded, analysed and rewritten there, and the download is created on your device. Nothing is sent to Map Extract or anyone else, which makes it suitable for client lists. Closing the tab discards everything you loaded.

Where your data goes

Your CSV never leaves this browser tab. Decoding, the repair and the rewrite happen locally, and the fixed copy is generated on your device when you press download. Nothing is kept afterwards.

Checked against the tool on

Top