Rows inspected
--
CSV Tools
CSV Import Error Checker and Repair Tool
Find structural CSV import problems, preview safe local repairs, and download a separate cleaned copy with diagnostic evidence.
Free local diagnostic tool
Diagnostic workspace
Awaiting local file intake
Upload a CSV to inspect its structure, identify import problems and preview safe repairs.
Columns detected
--
Issues found
--
Affected rows
--
Repairs available
--
File structure map
Issue profile
Structure--
Quoting--
Headers--
Encoding--
Hidden characters--
Spreadsheet risk--
Why CSV files fail to import
CSV is a family of dialects, not one universal file format. A file can fail because rows use inconsistent column counts, a comma is mistaken for a semicolon or tab, quotation marks are unbalanced, or a UTF-8 BOM changes the first header. Mixed line endings, blank or duplicate headers, hidden Unicode characters, embedded line breaks, and spreadsheet formula interpretation can also affect an import.
A structurally clean file may still need field mapping, data types, date formats, or other platform-specific expectations for Excel, Power BI, Shopify, or a database import.
What CSV Import Doctor checks
- Delimiter evidence, quote handling, line endings, BOM, encoding clues, and modal column count.
- Malformed rows, column mismatches, blank or duplicate headers, trailing delimiters, and empty terminal records.
- Invisible characters, control characters, unusually long cells, and spreadsheet formula interpretation risk.
Safe repairs you can preview
Previewable repairs include removing a UTF-8 BOM, normalising line endings, removing empty terminal rows, trimming trailing whitespace, replacing selected invisible characters, generating or de-duplicating headers, padding missing trailing columns, and neutralising formula-like values. Every change is shown before a separate download is created.
CSV problems that require manual review
The tool will not truncate extra columns, guess quote positions, move values between fields, convert decimal or date formats, or delete duplicate records. Those changes can alter meaning or discard data and need a human decision.
How local CSV inspection protects your data
Your file is read, inspected, repaired, and reported inside this browser. MicroIntent does not upload it to a server, store it, or share it. Refreshing or clearing the tool removes its in-memory state.
Related MicroIntent tools
Frequently asked questions
Why is my CSV not importing correctly?
CSV imports commonly fail when a row has a different number of columns, the delimiter is unexpected, a quoted field is unbalanced, headers are duplicated, or the encoding is not what the destination expects. CSV Import Doctor shows evidence for the supported structural checks.
Can this tool repair a broken CSV?
It can preview selected deterministic repairs such as removing a UTF-8 BOM, normalising line endings, naming blank headers, padding missing trailing fields, and neutralising formula-like cells. It does not guess malformed quotes, move values between columns, or alter formats automatically.
Does MicroIntent upload or store my CSV?
No. Inspection, repair preview, report generation, and downloads run locally in your browser. The tool does not upload, store, or share the selected CSV.
What causes a CSV column mismatch?
A record can have too few or too many delimiter-separated fields compared with the modal column count. Missing trailing fields can be padded in the repair preview; extra fields require review because truncating them could lose data.
What is a CSV delimiter?
A delimiter separates fields in a row. Comma is common, but semicolon, tab, and pipe-delimited files are also used. The tool infers a likely delimiter from consistent record widths and reports that interpretation.
What is a UTF-8 BOM?
A byte-order mark is an optional marker at the start of some UTF-8 files. Some importers expect it while others treat it as part of the first header. The tool reports it and can preview removal without changing the original.
Why do quoted fields cause import errors?
Quoted fields can safely contain delimiters and line breaks, but an unclosed quote or unexpected text after a closing quote can make a parser interpret the rest of the file incorrectly. These quote errors require manual review.
Can the tool check CSV files for Excel or Power BI?
Choose the Excel or Power BI profile to frame the review, but the checks remain structural. A structurally clean CSV can still need platform-specific field mapping, data types, and destination settings.
Will the repaired CSV overwrite my original file?
No. Repairs are previewed in memory and downloading creates a separate file named with the microintent-repaired suffix.
What CSV problems require manual review?
Extra columns, malformed quote closures, moving values between columns, date or decimal format changes, and duplicate-row deletion are deliberately not automatic because they need a human decision.