What encoding means
Encoding tells software how to interpret every byte
A CSV is plain text, but plain text still needs a character encoding. UTF-8 represents international text efficiently and is the safest default for most modern imports. When software assumes a different encoding, accented letters, symbols, and non-Latin text can become replacement characters or unreadable sequences.
Common delimiter problems
The file extension does not reveal the separator
A file ending in .csv may use commas, semicolons, tabs, or pipes. Regional spreadsheet settings commonly produce semicolon-separated files, while data exports may prefer tabs or pipes. If an importer assumes the wrong separator, an entire record can collapse into one column.
UtilityDock compares separators across logical records and ignores characters inside quoted fields, so a comma in a product description does not automatically become the detected delimiter.
UTF-8 vs UTF-8 BOM
Both are UTF-8, but one begins with a signature
A UTF-8 byte-order mark is a three-byte signature at the start of a file. Some spreadsheet applications use it to recognize UTF-8 reliably; some strict pipelines prefer UTF-8 without it. This detector reports the distinction so you can compare it with the destination's documented requirements.
Why imports fail
Structure assumptions often disagree
- The importer expects commas but receives semicolons
- UTF-16 is supplied to a UTF-8-only workflow
- Windows and Unix line endings are mixed
- Records contain inconsistent field counts
- The first record contains data instead of headers
- Quoted delimiters are handled as real separators
Examples
Common structural signatures
| File characteristic | What it usually means |
|---|---|
| name,email | Comma-delimited CSV |
| name;email | Semicolon-delimited CSV |
| EF BB BF | UTF-8 BOM byte signature |
| CRLF | Windows-style record endings |
CSV Toolkit
Continue inspecting and cleaning your file locally
FAQ
Questions about CSV structure detection
Does UtilityDock upload or store my CSV?
No. Your CSV never leaves your computer. Byte inspection, decoding, delimiter scoring, record counting, and warnings all run locally inside your browser.
Which delimiters can the detector identify?
Version 1 checks comma, semicolon, tab, and pipe delimiters. It compares multiple logical records and ignores delimiter characters inside properly quoted fields.
How is encoding detected?
UTF-8 BOM and UTF-16 BOM files are confirmed from their leading bytes. UTF-8 without a BOM is validated across the file. UTF-16 without a BOM is only estimated from practical null-byte patterns and is labeled accordingly.
Is header detection guaranteed?
No. Generic header detection is inherently heuristic. UtilityDock compares the first record with later value types and labels the result Likely, Unclear, or Not detected.
Does this tool repair encoding or delimiters?
No. Version 1 is read-only. It explains the detected structure and potential risks without rewriting or downloading a modified file.