Home / Fix Thai CSV Encoding (TIS-620 / Windows-874 to UTF-8 BOM)
Fix Thai CSV Encoding (TIS-620 / Windows-874 to UTF-8 BOM)
Repair garbled Thai text in CSV files and export UTF-8 with BOM for reliable opening in Excel.
Drop files here or choose files from your device
Processing happens directly on your device. No file bytes are uploaded, and this tool uses no Cloudflare Container compute.
How to use Fix Thai CSV Encoding (TIS-620 / Windows-874 to UTF-8 BOM) in 3 steps
- Choose your file: Supports .csv, .tsv; Maximum 15 MiB
- Review the preview or confirm processing: Processing happens directly on your device. No file bytes are uploaded, and this tool uses no Cloudflare Container compute.
- Get the result immediately: Download the processed file and open it in Microsoft Excel or Google Sheets
Why does this problem happen, and how does this tool fix it?
CSV reports from Thai banking, accounting, ERP, and ecommerce systems may look correct in a text editor but become unreadable in Excel. This usually happens when Excel interprets TIS-620, Windows-874, or UTF-8 without a byte-order mark using the wrong encoding.
How it works and protects your data: The tool detects UTF-8 and Thai Windows-874/TIS-620 inside your browser, then exports UTF-8 with the BOM bytes Excel expects. Your file stays on your device throughout the conversion.
Frequently asked questions
Why is the CSV readable in a text editor but garbled in Microsoft Excel?
Many text editors detect UTF-8 without a BOM automatically. Excel may instead fall back to the computer’s legacy ANSI encoding unless it finds the UTF-8 BOM at the beginning of the file.
Is a CSV containing customer or sales data uploaded to a server?
No. This tool reads, converts, and creates the download entirely through browser APIs on your device.