Text Encoding and Delimiter Inspector

Inspect CSV encoding and delimiter evidence, then download the complete decoded file as UTF-8.

On-device No sign-up Free to use

Inspect text file controls

  1. 1 Add files
  2. 2 Arrange/Options
  3. 3 Download

Drop your CSV file here

or choose one from your device

One file up to 1 MiB. Nothing is uploaded; the bytes are read in your browser.

    Result

    Showing an example.

    Inspect a small UTF-8 CSV.

    The report shows valid UTF-8 byte evidence and LF line endings, with comma as a consistent two-column delimiter candidate.

    Loading the tool. Your result will appear here.

    https://usefreetools.net/text-encoding-delimiter-inspector · 20 November 2026

    Was this helpful?

    How to use Text Encoding and Delimiter Inspector

    1. Choose one text or CSV file up to 1 MiB.
    2. Use automatic mode to check supported byte-order marks or valid UTF-8. If evidence is insufficient, choose a supported encoding deliberately.
    3. Run the inspector and compare encoding evidence, line endings, delimiter candidates and the preview. A chosen encoding is not proof of the file's original encoding.
    4. Download the complete decoded file as UTF-8. Its original separators and rows remain; the tool does not clean a malformed table.

    Example: Text Encoding and Delimiter Inspector

    Inspect a small UTF-8 CSV.

    You add
    UTF-8 file without BOM: name,score Ada,10 Grace,20 , using LF line endings. Encoding: Auto; delimiter: Auto.
    You get
    The report shows valid UTF-8 byte evidence and LF line endings, with comma as a consistent two-column delimiter candidate.

    Supported inputs and limits

    File countOne text file
    Input sizeUp to 1 MiB
    EvidenceUncertainty is reported
    • One local file up to 1 MiB.
    • Automatic mode recognizes supported BOMs and valid UTF-8; legacy encodings need an explicit choice when evidence is insufficient.
    • Delimiter candidates may tie.
    • The UTF-8 download contains the complete decoded file, preserving delimiters and rows; it does not repair a malformed table or guess unsupported encodings.

    Where your input is processed

    This tool does not upload your inputs. See the limits for anything saved on your device.

    Byte evidence and an encoding guess differ

    A byte-order mark provides useful evidence. Without one, bytes may fit more than one character set. The report does not establish the language or original application, and it does not silently substitute replacement characters for an invalid UTF-8 stream.

    A consistent separator is only a candidate

    Quoted separators, uneven rows and a small sample can make delimiter detection uncertain. Inspect the preview and row widths before selecting the delimiter for another tool. This page reports file evidence; it does not clean or rewrite the dataset.

    Questions about Text Encoding and Delimiter Inspector

    Can a file’s encoding always be identified?

    No. Several encodings can produce valid text from the same bytes. The report separates evidence from an explicit decoding choice.

    Why can two delimiters tie?

    A file may be a single column, contain too few rows or use more than one punctuation character consistently. Inspect the preview and choose deliberately.

    Does a comma inside quotes count as a column break?

    The delimiter analysis uses quote-aware CSV parsing, so a properly quoted comma remains inside its field.

    Page updated · Project managed by Tony Hines · Report a problem with Text Encoding and Delimiter Inspector

    Related reading

    All guides