Skip to main content
CSV First Aid

CSV quote repair — fix broken and unmatched quotes

One missing closing quote turns a single field into a multi-row monster and shifts every column after it. We find the unmatched ones, close them, and re-escape the inner ones — per RFC 4180.

Quotes repaired

Before

"John,"Smith",25

After

"John","Smith","25"

Drop your CSV file here

or click to browse

The "quoting" fix will be auto-detected.

What is this and why does it matter?

When a CSV value contains commas or line breaks, it needs to be wrapped in quotation marks. But many export tools get this wrong — they forget a closing quote, or don't handle quotes inside the data properly.

The result: columns shift to the wrong positions, data from multiple rows gets merged into one giant cell, or your import tool gives a cryptic error. The file looks broken and it's hard to tell where the problem actually is.

CSV First Aid reads your file carefully, finds all the quoting problems, and rewrites the file with proper quotation marks. The fix report tells you exactly how many fields had issues.

How it works

  1. 1Drop your CSV. We parse the file and look for mismatched or broken quotation marks.
  2. 2The diagnosis card shows how many fields have quoting problems.
  3. 3Apply → fields are properly quoted. Download.

FAQ

What about fields with smart quotes (curly quotes)?

Smart quotes are treated as regular characters (not field delimiters). The parser only recognizes straight double quotes (") as CSV quote characters, which matches the RFC 4180 standard.

My CSV has single-quoted fields. Does this work?

Single quotes are not standard CSV field delimiters. The parser treats them as regular characters. If your data uses single quotes as delimiters, the fields will be preserved as-is (without stripping quotes).

Can unmatched quotes cause data loss?

In a naive parser, yes — an unmatched opening quote swallows everything until the next quote in the file. CSV First Aid's tolerant parser limits the damage by recovering at line boundaries, but always review the output to confirm.

Related tools