UtilityPilot.Find a tool

Data & Tables

CSV Viewer and Validator

Inspect a CSV or TSV before importing it elsewhere. See columns, record counts and clear syntax errors without spreadsheet type conversion.

Processed in your browserPrivacy details ↗

5 MiB per input · 50,000 records · 200 columns

Adjust your options

Spreadsheet-safe export can change formula-like cells by adding an apostrophe. Turning it off preserves raw values; use raw exports only in a trusted importer.

No sign-up. No upload.

How to use this tool

  1. Choose a local file or paste the table text.
  2. Select the correct delimiter, header mode and file encoding.
  3. Inspect the first 50 records and the full record count; download if needed.

How the operation works

Records are parsed independently of physical line breaks. A newline inside quotes belongs to its field. Every record must have the same number of fields; malformed quoting and inconsistent widths stop processing. The screen preview is limited to 50 data records to remain responsive, while the output includes all accepted records.

What you see before importing

Choose a local file or paste table text. Select delimiter, header mode and encoding. The screen preview shows the first 50 data records; the full record count is reported separately. Exports contain all accepted records within the stated limits—not only the preview.

Records are parsed independently of physical line breaks: a newline inside quotes belongs to its field. Every record must have the same number of fields. Malformed quoting and inconsistent widths stop processing with a clear error instead of producing a silent partial file.

Diagnosing common load failures

One column — wrong delimiter; try semicolon or tab. Garbled text — wrong encoding; choose UTF-8, UTF-16 or Windows-1252 to match the source. Extra columns mid-file — an unquoted delimiter inside a value, or a record width mismatch. Missing first header — a UTF-8 BOM was present; it is stripped from parsing, not part of the first header.

This is a structural check, not verification that a postal code, email or business value is correct. Guide: Fix CSV import problems without damaging values.

Example inspection

name,note
Ada,"Hello, world"
Sam,Plain

Two data records, two columns. The comma inside the quoted note stays in the field. If this file were loaded as semicolon-delimited, both rows would appear as a single column—select the correct delimiter before judging the data.

After inspection

Common next steps: change the delimiter, adjust columns, remove duplicate rows, convert to JSON, or merge aligned files. Keep the original export throughout.

Limits: 5 MiB per input, 50,000 records, 200 columns. Preview truncation does not truncate downloads.

A worked example

name,note
Ada,"Hello, world"

One data record with two fields: name = Ada; note = Hello, world.

If a semicolon export appears as one column, select Semicolon. This is a structural check, not verification that a postal code, email or business value is correct.

What the preview shows

The table preview shows the first 50 data records so the page stays responsive; the record count and the download include every accepted row. All rows must have the same number of fields. A quoted delimiter or newline is part of the field, not a new record. Malformed quoting or inconsistent widths stop the parse and report an error instead of guessing a repair.

The viewer reports structure, not meaning. It does not decide whether a postal code, date or email address is valid, and it does not convert numeric strings into spreadsheet numbers. That is deliberate: identifiers with leading zeros stay intact.

When a CSV appears as one column

Check the delimiter first. A semicolon export opened with comma mode gives one wide column. Next check quoting: an unescaped quote can swallow the rest of the file. A UTF-8 BOM is an encoding marker and may appear as part of the first header in some tools. CRLF line endings are supported, but mixing line-ending styles can produce blank-looking records.

If the structure is wrong, fix the source or choose the matching delimiter and header setting. The viewer does not edit cells; use CSV Column Editor for schema changes or a spreadsheet for value edits.

Processing and privacy

CSV Viewer reads the file locally to report structure; the rows are not sent to a server. Input stays in browser memory until you reset or leave the page. Copy and download run only when you choose them. No tool input is sent to a processing service. Website pages and scripts still make ordinary hosting requests; the privacy policy separates those from tool processing.

Frequently asked questions

Does the preview truncate my download?

No. Only the table preview is limited to 50 records. Exports contain all accepted records within the limits.

Can the tool fix broken quoting?

No. It reports the error. Repair the source file or correct the delimiter/encoding choice.

Which encodings are supported?

UTF-8 (default), UTF-16 and Windows-1252. Choose the encoding the source system actually uses.

Is this a spreadsheet?

No. It is an inspector with optional download. It does not edit cell values or recalculate formulas.

Will opening here change my file?

No. The file is read locally; nothing is rewritten unless you download an explicit export.

Does the 50-record preview limit my download?

No. Only the on-screen preview is limited; exports contain all accepted records within the stated limits.

Can I fix a bad cell in the viewer?

No. The viewer reports structure and values but does not edit them. Use a column editor or spreadsheet.

How this tool was checked

CSV Viewer was checked with quoted separators, multiline fields, BOM-prefixed files, inconsistent record widths, delimiter choices and previews that must not truncate an export. See the testing method or report a failure.