Start With a Triage Question
Ask: is the file unreadable, readable but wrong shape, or right shape but wrong values? That split decides whether you fix mechanics (delimiter/encoding), structure (headers/columns), or types (dates/IDs).
Diagnostic Checklist (Top to Bottom)
Work in order—later steps assume earlier ones pass.
- Open in a text editor or Online CSV Editor: do you see distinct columns?
- Confirm delimiter (, ; tab) and quoting.
- Confirm encoding (UTF-8 vs legacy) on non-ASCII samples.
- Confirm one header row and stable column count.
- Compare row counts before/after conversion.
- Spot-check IDs, dates, amounts, and accented text.
- Only then debug the target system (Excel, JSON schema, database).
Symptom → Likely Cause → Fix
A quick map for the tickets you see weekly.
| Symptom | Likely cause | Fix |
|---|---|---|
| All data in one column | Wrong delimiter | Set ; or tab explicitly |
| Shifted columns mid-file | Unescaped comma/newline | Fix quoting; re-export |
| é / � characters | Encoding mismatch | Re-encode to UTF-8 |
| Zeros missing on IDs | Numeric coercion | Force text types |
| Dates wrong by months | Locale / Excel serial | Use ISO dates |
| JSON numbers broke IDs | Parsed as number | Emit strings |
| DB column count error | Header/BOM/delimiter | Stage as text; inspect |
| Fewer rows than source | Broken newlines or filter | Compare counts; check quotes |
Excel Conversion Problems
Most "CSV to Excel" pain is Excel auto-detect.
- Do not double-click to open critical CSV files.
- Use Data → From Text/CSV or CSV to Excel conversion with review.
- If Excel already mutated values, go back to the raw CSV—do not convert the damaged sheet forward.
JSON and SQL Conversion Problems
Different targets, similar root causes.
CSV → JSON
Watch type coercion, duplicate headers, and empty rows becoming null objects. Validate with a JSON Schema when downstream APIs are strict.
CSV → SQL
Escape quotes in strings, batch inserts, and load via staging. Native COPY/LOAD DATA errors deserve the database troubleshooting path after the file itself is clean.
Step-by-Step: Isolate With a Minimal Repro
Shrink the problem until it is obvious.
- Copy the header + 5 failing rows into a tiny CSV.
- Convert only that sample.
- If the sample works, the issue is later in the file (quotes/newlines).
- If the sample fails, the issue is global (delimiter, encoding, header).
- Apply the fix to the full file and re-verify counts.
Real-World Examples
Playbook in action.
Partner file "randomly" breaks at row 12,481
An address field contained a raw newline without quotes. Fixing the exporter’s quoting resolved every later row.
JSON API rejects order_id
IDs over 2^53 lost precision as JSON numbers. Switching to strings fixed mobile clients.
Semicolon CSV in the US
European export used ; while the pipeline assumed ,. Preview showed one column; setting delimiter fixed the load.
Common Mistakes While Troubleshooting
Do not make it worse.
- Editing in Excel mid-debug and introducing new type changes.
- Fixing only the first error when the root cause is global encoding.
- Changing three settings at once so you never learn what worked.
- Discarding the original file.
- Blaming the converter when the source CSV is invalid.
Best Practices
Prevent the next fire drill.
- Keep raw files immutable.
- Document delimiter + encoding in every hand-off.
- Always verify row counts after conversion.
- Use samples to debug, then scale the fix.
- Automate lint checks (column count, encoding, required headers).
Why Use Convert CSV Online?
Convert CSV Online is free, browser-based, and requires no account for everyday conversions. The Online CSV Editor is the fastest place to see delimiter and encoding issues; converters then prove the fix toward Excel, JSON, or SQL. Client-side workflows work on Windows, macOS, and Linux browsers.
Visual proof
If columns look right in preview, you are ready to convert; if not, stop and fix the source.
Conclusion
Troubleshooting CSV conversion is systematic: mechanics, structure, then values. Reproduce on a tiny sample, fix the root cause, verify counts, and only then trust the full output.
FAQ
Why did my CSV conversion fail?
Most failures come from wrong delimiter, encoding mismatch, broken quoting, or type coercion in Excel/JSON. Triage in that order.
How do I fix CSV that opens in one column?
The delimiter is probably semicolon or tab while the tool expects comma. Set the correct separator and re-import.
Why are characters garbled after conversion?
Encoding mismatch—often Windows-1252 read as UTF-8 or the reverse. Re-encode to UTF-8 and convert again.
How do I find which row breaks a CSV parser?
Binary search with smaller slices, or validate with a strict parser that reports line numbers. Unescaped quotes and newlines are usual suspects.
Should I debug in Excel?
Use Excel carefully—it can mutate data. Prefer a text/CSV editor for diagnosis, then Excel only as a target format.
What is the fastest first step?
Open the file in the Online CSV Editor and check whether columns, headers, and special characters look correct before converting again.
References
Convert your CSV in the browser
Preview, clean, and convert CSV files free with Convert CSV Online—no installation and no account required for everyday conversions.