Data & Text 100% Client-Side Engine Operational

CSV Separator & Encoding Fixer

Fix CSV delimiters, handle text encodings and convert spreadsheet files into compatible formats.

Privacy Certified: Zero server transmission. Files & text execute entirely in local browser memory.
CSV / TSV / Delimited Raw Text Input 0 lines • 0 chars

Pasted text is already decoded into Unicode by your browser. Source encoding selection is applied when uploading raw files.

Delimiter Configuration

Input: Auto Detect

Source Text Encoding

Auto: UTF-8

Exports are standardized to clean UTF-8. ISO-8859-1 is decoded according to WHATWG standard Windows-1252 mapping.

Parsing & Export Options

Workflow Guide

How to Operate CSV Separator & Encoding Fixer

Solve common spreadsheet import errors caused by regional delimiter differences (such as European semicolons) or incompatible character encodings (such as ANSI Windows-1252 vs. UTF-8).

  1. 1 Drop your CSV, TSV, or TXT file or paste raw delimited content.
  2. 2 UtilityHub inspects raw file bytes to detect Byte Order Marks (BOM), UTF-8 validity, and delimiter structure.
  3. 3 Select or verify your desired input delimiter, output delimiter, and source encoding.
  4. 4 Click "Convert Delimiter & Fix Encoding" to preview your records and export clean UTF-8 CSV with optional BOM.

Example Input & Output

Sample Input: 
name;city;age
Arpit;Ahmedabad;22
Rahul;Surat;23
Expected Output: 
name,city,age
Arpit,Ahmedabad,22
Rahul,Surat,23

Supported Inputs

  • Comma (,), Semicolon (;), Tab (\t), and Pipe (|) delimited files
  • Files encoded in UTF-8 (with or without BOM), UTF-16 LE, UTF-16 BE, Windows-1252, and ISO-8859-1
  • Complex fields with quotes, multiline values, and embedded delimiters

Browser Technical Limits

  • Pasted text is already decoded by your browser/OS clipboard into Unicode; upload the raw file if you need byte-level encoding reinterpretation.
  • TextEncoder standardizes exported CSV files to clean UTF-8 (with optional BOM for Excel compatibility).
Q&A

Frequently Asked Questions

Everything you need to know about CSV Separator & Encoding Fixer, formats, and privacy guarantees.

Why do European CSV files frequently use semicolons instead of commas?

In many European countries, the comma is used as the decimal separator (e.g., 12,50 instead of 12.50). Spreadsheet software like Microsoft Excel defaults to using semicolons as list separators in these regions to prevent ambiguity between cell boundaries and decimal numbers.

What is a UTF-8 BOM and when should I enable it?

A Byte Order Mark (BOM) consists of the byte sequence EF BB BF at the very start of a file. While UTF-8 does not require a BOM, desktop Microsoft Excel on Windows relies on it to identify UTF-8 encoding automatically. Enabling the UTF-8 BOM checkbox ensures non-English characters like Gujarati, Japanese, and accented letters display properly in Excel.

Why can’t I re-decode character encodings on pasted text?

When you copy and paste text into a browser textarea, the operating system and browser have already decoded the raw bytes into JavaScript Unicode strings. To re-interpret a file using a different source encoding (such as Windows-1252), you must upload the original raw file so UtilityHub can access the underlying byte buffer.

How does the parser handle commas and newlines inside quoted fields?

UtilityHub implements a Finite State Machine (FSM) conforming to RFC 4180. Delimiters, escaped quotes (""), and newlines located inside double quotes are treated as literal cell values rather than structural field or record separators.

Is my data secure and private?

Yes, 100%. All parsing, delimiter conversion, and encoding detection happen locally inside your browser using JavaScript and Web Workers. No file data or text is ever sent to any remote server or external API.