How to Open a UTF-16 CSV File Correctly

Not every CSV is UTF-8. Many Windows tools, older systems, and spreadsheet exports can produce UTF-16 delimited files. The rows and columns may be perfectly valid, but the file looks broken when opened with a tool that assumes the wrong encoding.

Encoding and delimiter are separate

A delimiter tells the parser where columns split: comma, tab, semicolon, pipe, or another separator. Encoding tells the app how to turn bytes into characters.

You need both to be right. A UTF-16 tab-delimited export still needs UTF-16 decoding before tabs, line breaks, and text make sense.

What broken UTF-16 looks like

When a UTF-16 file is read as UTF-8 or Windows-1252, you may see:

• strange boxes between letters
• null-looking characters
• only the first character of a value
• garbled non-Latin text
• a file that seems empty or unreadable

That does not always mean the data is damaged. It often means the viewer guessed the wrong encoding.

Open it with encoding detection

CEESVEE detects common encodings, including UTF-8, UTF-16 little-endian, UTF-16 big-endian, and Windows-1252. It also handles byte-order marks correctly.

The workflow:

1. Open the CSV in CEESVEE.
2. Confirm the text displays correctly.
3. Confirm the delimiter produced the expected columns.
4. If needed, Save As with a different encoding such as UTF-8.

For the broader topic, see fixing CSV encoding problems.

When to convert to UTF-8

UTF-8 is usually the safest modern default for sharing and importing. If your downstream system accepts UTF-8, converting a UTF-16 CSV to UTF-8 can reduce surprises.

Do the conversion deliberately through Save As, and keep the original file until the import or handoff is confirmed.

The bottom line

A UTF-16 CSV is not broken just because it looks strange in a text editor. Decode it with the right encoding, verify the delimiter, and export intentionally.

Download CEESVEE for free and open UTF-16 CSV files without guessing.