How to Fix Encoding
- 1Choose a supported file or use sample data when available.
- 2Set the options shown for this workflow.
- 3Process the file locally, inspect the result, and download a new copy.
Optimize & Repair · browser workspace
Fix weird symbols (e.g., é -> é). Process locally in your browser with HappyCSV.
Quick start
Everything runs in your browser, so you can test the workflow with sample data when available before using production files.
Output: A new file or report produced locally in your browser.
A new file or report produced locally in your browser.
Up to 100 MB per CSV, 20 MB per complex document; 250,000 rows, 1,000 columns, 2 million cells, and 128 MB output. Jobs stop after two minutes. Large files may need splitting.
No. File processing stays in your browser. Files are not automatically saved for the next visit.
This tool processes one file at a time.
Use the symptom-specific walkthrough before changing a production file.
Repair mojibake, black diamonds, and broken accented characters by converting the CSV to a known text encoding.
Convert a Shopify product or customer CSV to UTF-8, distinguish encoding damage from malformed quotes, and validate the file before importing it.
Prepare a UTF-8 CSV for Salesforce Data Loader and remove a UTF-8 byte-order mark when it causes an invalid-format error.
Convert a HubSpot import file to UTF-8 and verify its headers, identifiers and character data before uploading it.