Transform

Transform legacy Windows-1252, ISO-8859-1, and Shift-JIS files into universal UTF-8

Fix mangled accented characters (mojibake) by decoding legacy encodings into clean UTF-8.

🛡️ Your rows never leave your browser.
Why Onfyt: Uses native Web TextDecoder to stream-convert legacy byte buffers to UTF-8 without data loss or server uploads.

Interactive Sample Data

idemployeecity
1Renée DuPontMontréal
2Björn ÅkessonMalmö
3José GarcíaSão Paulo

How this tool works

Files saved on older Windows systems are often encoded in Windows-1252 (also called ANSI), not UTF-8. When a modern application reads a Windows-1252 file as UTF-8, every accented character beyond ASCII 127 turns to mojibake: the name Renée arrives as Renée, the currency symbol £ becomes £, and the em-dash — renders as â€". The corruption is silent—no error is thrown; the bytes are just reinterpreted under the wrong code page. This occurs because legacy encodings represent international characters using single byte values between 128 and 255. In UTF-8, however, code points above 127 require carefully formatted multi-byte sequences (two to four bytes starting with specific leading bit patterns). Reading a single-byte legacy character through a UTF-8 decoder results in invalid byte sequence errors or substitution with the black diamond question mark (). DataFix utilizes the browser's native TextDecoder API to accurately interpret incoming raw byte buffers using the source encoding of your choice (Windows-1252, ISO-8859-1, Mac-Roman, Shift-JIS, GB18030, EUC-KR). Remapping legacy byte sequences to Unicode codepoints resolves mojibake before text enters database ingestion tables.

Things that usually go wrong

  • Encoding detection is probabilistic — for very short files, confidence may be low. Check the detected encoding before converting.
  • Double-converting (UTF-8 → UTF-8) is a no-op and safe.

Edge cases we tested

🧪 Windows-1252 smart quotes and curly apostrophes

Converted from byte codes 0x91-0x94 into standard Unicode quotation marks.

🧪 Euro currency symbol (€ at byte 0x80 in Windows-1252)

Mapped to Unicode U+20AC (UTF-8 bytes 0xE2 0x82 0xAC) instead of failing.

🧪 Double-encoded UTF-8 strings ('Renée')

Decoded back to original clean representation ('Renée').

Frequently Asked Questions

How can I tell if my file has encoding problems?

Garbled characters (é, ’) in place of accented letters or smart quotes are the telltale signs of a Windows-1252 file read as UTF-8.

What is the most common mis-encoding?

Windows-1252 (also called CP-1252) is by far the most common. It is the default encoding for many Windows applications.

Related tools

Transform

Column to Comma-Separated List

Extract a CSV column and convert it to a comma-separated list for SQL IN clauses or code arrays.

Open Tool →
Transform

Comma-Separated List to Column

Convert a comma-separated, line-separated, or SQL IN list into a single-column CSV.

Open Tool →
Transform

Lines to CSV

Convert plain-text newline-delimited records into structured CSV tables.

Open Tool →