Skip to content

Tools / CSV import diagnostic

Inspect the source

CSV import diagnostic

Spot leading zeros, long identifiers, uneven records, blanks, and formula-like text before importing.

LOCAL PROCESSING · UP TO 5 MB / 10,000 DATA RECORDS PER FILE

Your file contents stay in this page. No account, upload endpoint, analytics, or advertising script is used on this tool page. Choose files only on a device you trust.

How to use this tool

Paste CSV text or choose a UTF-8 file, check the delimiter, and run the inspection. Data stays in the page. A quoted comma or newline remains part of its field. Findings point to import decisions; they do not determine whether a transaction is valid.

Leading-zero IDs and long references should be imported as Text. Date-like values need an agreed convention. Blank fields need a business rule. Formula-like text should be inspected before a spreadsheet opens it.

Check the built-in sample

The sample contains 14 data records and 11 columns. Its quoted multiline note is one field. Findings can overlap on the same cell.

Limits and the downloaded report

The parser supports comma, semicolon, and tab delimiters, quoted separators, escaped quotes, and multiline fields. It reads UTF-8 text, with an optional byte-order mark. An unclosed quote or an invalid field boundary stops processing. Large files should be handled in an appropriate local spreadsheet or data application.

Data remains in memory until you clear or leave the page. The tool does not save it to browser storage. Reports retain unresolved findings. Formula-like text is prefixed with an apostrophe in downloaded review reports; this is a deliberate report-only change. CSV does not define text column types, so import identifiers as Text.

Follow the complete example

Import an order CSV without damaging IDs or dates ↗

Read the calculation and tool verification method.