Change CSV text encoding
Decode CSV with a chosen source encoding and export UTF-8, UTF-8 with BOM or UTF-16 LE.
- 1Add files
- 2Options
- 3Convert
- 4Save
Preparing the converter…
Supported formats and settings
- Input formats
- CSV, TXT
- Output formats
- CSV
- Per-file limit
- Current device memory
- Total selected-file limit
- Estimated by file count and format
- Number of selectable files
- 1–1
Recommended input total: 8 MiB on mobile / 32 MiB on desktop. Low memory can reduce the effective limit.
Your files are not uploaded to a conversion server. A new result is created in your browser.
How to use this tool
- Choose files in CSV, TXT format. Maximum files per batch: 1.
- Review Source encoding, Output encoding, then start processing.
- Download the CSV result and check its content and quality.
What this tool does
- Decode CSV with a chosen source encoding and export UTF-8, UTF-8 with BOM or UTF-16 LE.
- Read CSV, TXT input and save the CSV result as a new file.
- Available settings: Source encoding, Output encoding.
Limitations
- The source encoding must be correct. This does not repair text that was already corrupted before upload.
Frequently asked questions
Change CSV text encoding — What should I check before using this tool?
The source encoding must be correct. This does not repair text that was already corrupted before upload.
Which files can I choose?
Choose files in CSV, TXT format. Maximum files per batch: 1.
How can I adjust the result?
Source encoding, Output encoding.
Understand the formats
CSV
CSV stores rows of delimited text. Quoted fields can contain commas and line breaks; encoding and header conventions vary between applications.
Use CSV for exchanging a simple table. Select the correct character encoding and inspect the column names before converting to JSON.
Leading zeros, dates and long identifiers can be changed by spreadsheet software when opened. Coverton neutralizes formula-like cells in supported table exports; encoding-only conversion preserves the original text.
When is this useful?
Change output encoding when the source CSV encoding is known. This cannot restore already-corrupted characters.
Input and result example
known source encoding → UTF-8/BOM/UTF-16 LE CSVExamples illustrate the workflow; actual size, support and recognition depend on the source and settings.