CSV Encoding Inspector
About CSV Encoding Inspector
CSV Encoding Inspector examines uploaded files at the byte level to explain garbled characters, failed imports, unexpected separators and cross-platform newline problems.
How it works
Raw-byte inspection
File uploads are read as bytes rather than decoded immediately. The report checks UTF byte-order marks, strict UTF-8 validity and byte patterns that suggest UTF-16 or a legacy single-byte encoding.
CSV transport clues
The inspector reports the dominant newline style, mixed line endings and a best delimiter guess based on consistent unquoted separators across the first rows.
Readable diagnostics
A decoded preview and issue list call out replacement characters, NUL bytes and common mojibake patterns without modifying the source file.
Frequently asked questions
Can encoding always be identified with certainty?
No. A BOM or valid UTF structure is strong evidence, but many single-byte encodings are inherently ambiguous. The report labels heuristic results accordingly.
Why should I upload rather than paste?
Pasting happens after another application has decoded the bytes. Uploading preserves the original byte stream, BOM and invalid sequences for inspection.
Does the file leave my browser?
No. Byte analysis and preview decoding are local.
Sources & last verified
The behaviour of this tool and the claims on this page were checked against the specifications below on . Everything runs in your browser, so the output you see is exactly what the engine produced.
Found a wrong result or an outdated claim? Report an error and it will be re-verified.