Start with a small, recognizable sample.
Choose your file or paste its text, check the encoding and separator, then inspect it. Compare the preview with a known row. If two separators look equally plausible, select the intended one explicitly. Broken quotes and extra columns need manual correction in the text or source application.
Example: decimal commas are values.
product_id;price 00124;4,50
With semicolon selected, this is two columns. Converting to comma produces 00124,"4,50". The decimal comma is kept inside quotes; it is not changed into a decimal point. A spreadsheet may still infer types during import.
Questions before exporting
Can I automatically fix a row with missing values?
No. A short record may be missing a middle field. End-padding is available only after you confirm the missing fields belong at the end. Extra fields or malformed quotes block export until you edit the source.
Why might a structurally valid file still fail to import?
Your destination may require particular headers, types or unique identifiers. Those rules are outside a general CSV structure check. Review the text-import guide before importing identifiers into Excel.
Are my files uploaded?
No. Selecting or dropping a file reads it in your browser. No file contents, names or tool inputs are sent to a server, stored in browser storage, or included in analytics. See the privacy notice.
What does the corrected download change?
It uses the output delimiter and line endings you chose, writes required CSV quotes, and encodes the copy as UTF-8. It preserves decoded field strings. Any confirmed padding is described in the report. Serialization may change quote style; it does not promise a byte-identical copy.