Free · No signup · Runs in your browser
Fix CSVEncoding & Mojibake
Turn garbled cells like "é" and "’" back into clean é and ' — no upload, no server, no data ever leaving your browser.
Turn garbled cells like "é" and "’" back into clean é and ' — no upload, no server, no data ever leaving your browser.
Mojibake happens when a UTF-8 file is read as Windows-1252 or Latin-1, so "café" becomes "café" and a curly apostrophe becomes "’". This tool applies a fixed map of the most common corruption sequences across every header and cell, and optionally strips a leading byte-order mark. Everything runs client-side.
Drop in the CSV showing mojibake — sequences like é, ñ, ’, “, or a stray at the start of the first header. The file is parsed locally; nothing is uploaded.
Leave "Strip byte-order mark" on (the default) to remove an invisible BOM that can break the first column name. Turn it off only if a downstream tool expects the BOM to remain.
The tool rewrites each cell with corrected characters, reports how many cells it fixed, and gives you clean RFC-4180 CSV ready for Excel, a database import, or any other CSV tool.
Garbled text is a data-quality problem hiding in plain sight — it breaks joins, search, and display. Repairing it locally keeps potentially sensitive rows on your machine.
The repair runs entirely in your browser with JavaScript. Customer names, emails, and addresses in your CSV never touch a server, so there is nothing to leak or log.
Handles the classic UTF-8-as-Latin-1 patterns: accented letters (é, ñ, ü), smart quotes and dashes (’, “, —), currency and symbols (€, £, ©), and stray from misread non-breaking spaces.
Mojibake in column names is just as damaging as in values — it breaks lookups by header. This tool repairs the header row alongside the data so column matching works again.
You get a "cells fixed" count so you can see exactly how much was repaired. Output is strict RFC-4180 CSV, properly quoted, ready for the next step in your pipeline.