What this tool does
Inspect a CSV structure before an import fails
The CSV Header Inspector reads the first record, identifies every column, and immediately checks its name for common structural problems. Findings distinguish errors that should be fixed from warnings that deserve review.
It does not modify your file or pretend to know every destination's private rules. Instead, it gives you a clear, portable baseline before you import into Excel, Shopify, a CRM, a database, or another business system.
Why headers matter
Column names are the contract for your data
Importers use headers to map values into fields. A blank name can make a column disappear, a repeated name can route data to the wrong field, and invisible whitespace can make a familiar header fail an exact match. These problems are easy to miss in a spreadsheet because two names can look identical on screen.
Common import failures
Small header defects cause confusing errors
- Two columns share the same exact name
- A trailing comma creates an unnamed final column
- Spaces appear before or after a field name
- Names collide after case or separator normalization
- Tabs, line breaks, or invisible characters are present
- A very wide file exceeds spreadsheet column limits
Best practices
Use headers that travel well between systems
- Give every column a name. Avoid empty cells and generated placeholders such as Unnamed: 0.
- Keep every name distinct. Do not rely on capitalization, spaces, hyphens, or underscores as the only difference.
- Prefer concise visible text. Letters, numbers, spaces, underscores, hyphens, and periods work reliably across many importers.
- Check the destination template. A structurally sound CSV can still require exact platform field names.
Examples
How the inspector classifies header problems
| Header example | Finding | Severity |
|---|---|---|
| email, email | Exact duplicate names | Error |
| sku, | Blank second header | Error |
| Customer ID, customer_id | Repeated after normalization | Warning |
| " product_title " | Leading and trailing whitespace | Warning |
CSV Toolkit
Continue checking your file locally
FAQ
Questions about CSV header validation
Does UtilityDock upload or store my CSV?
No. Your CSV never leaves your computer. The file is decoded, parsed, validated, and reported entirely inside your browser.
What does the inspector consider a duplicate header?
It reports exact repeated names as errors. It also warns when different-looking names become identical after common normalization, such as Customer ID and customer_id.
Can the inspector repair my headers?
No. Version 1 is intentionally an inspector. It explains structural risks without changing your source file, so you stay in control of every correction.
Does a Ready status guarantee that every import will succeed?
No. Ready means no generic structural header issues were found. Shopify, Excel, databases, CRMs, and other destinations can still apply their own required field names and rules.
What is included in the downloaded report?
The JSON report includes the source filename, detected header names, summary counts, severity, issues, and recommendations. It does not include your CSV data rows.