How it works
The first row is treated as the header. Quoted fields may contain commas and escaped double quotes.
Each data row maps header[i] to row[i].
Debugging scenario
Take a redacted export with quoted commas, escaped quotes, blank cells and embedded line breaks. Convert a small slice, then compare header names and each output property against the source row. Confirm the file actually uses commas rather than tabs or a locale-specific delimiter.
How to interpret the result
The first record defines property names and all output values remain strings. Blank and missing fields can carry different business meanings even if they look similar. Duplicate headers can overwrite properties, and this lightweight parser is not a replacement for a dialect-aware ingestion pipeline.
Input reference
- CSV input
- Example default: Sample input included
Common mistakes
- Pasting secrets, credentials, customer records or other production data into a browser tool or shareable URL.
- Assuming semicolon, tab, encoding, duplicate-header and malformed-row behavior matches the production importer.
- Treating a convenient preview as validation by the target runtime, parser, database or security control.
Before using the result
- Reduce the input to a synthetic example that still reproduces the behavior.
- Compare row and column counts and validate the output with the production schema before type coercion.
- Add the accepted input and expected output to the project regression tests before release.
Questions to check before production use
Does the first row need headers?
Yes. The first row becomes the property names in each object.
What delimiter is supported?
This lightweight tool expects commas. Use a spreadsheet export with comma-separated values.
Independent developer utility. Review output before using it in production.