Fix unescaped quotation marks inside CSV cells per RFC 4180
Escape internal quotation marks to prevent broken rows in standard parsers.
🛡️ Your rows never leave your browser.
Why Onfyt: Repairs unescaped quote corruption that crashes database ingest scripts without manual regex wrangling.
Interactive Sample Data
| id | comment |
|---|---|
| 1 | Customer said "urgent" today |
| 2 | Part is 12" length |
How this tool works
Under the international RFC 4180 standard, quotation marks ("") serve as cell text delimiters. If a text cell itself contains quote marks (e.g., product dimensions like 15" or quoted speech like 'He said "Yes"'), an unescaped quote tells the parser that the cell has terminated prematurely. This causes mismatched column counts, broken line breaks, and import crashes.
To safely represent quotes inside a CSV cell, the cell must be wrapped in quotes and every internal quotation mark must be escaped as two consecutive double quotes (`""`).
DataFix scans cell values, identifies unescaped quotation marks, and formats them in compliance with strict RFC 4180 standards.
RFC 4180 mandates that literal double quotes occurring inside a quoted CSV field must be escaped by prefixing them with another double quote (i.e., replacing " with ""). Unescaped quotes inside string fields confuse CSV parsers, causing them to treat the quote as a field terminator and resulting in broken column counts, jagged rows, and corrupted records downstream. DataFix analyzes the token structure of every field, identifying unescaped interior quotes, escaped quotes, and boundary markers. It normalizes all quotes according to RFC specifications so your data loads without parser exceptions into Python, R, Postgres, and Excel.
RFC 4180 specifies that literal quotation marks appearing inside quoted text fields must be escaped using paired double quotes. Unescaped quotes prematurely terminate field boundaries, causing jagged column counts and corrupted row offsets in Python, Pandas, and database engines. Normalizing quote escapes restores full parser compatibility.
Things that usually go wrong
- Already-correctly-escaped quotes are not double-escaped — the tool detects and skips them.
- Single quotes are not modified by this tool.
Edge cases we tested
🧪 Cells with inch marks (14" screen)
Properly doubled to 14"" within outer quotes.
🧪 Already escaped quotes
Detected to avoid triple-escaping.
Frequently Asked Questions
Why are double quotes escaped by doubling them?
RFC 4180 specifies that a double-quote inside a quoted field is escaped by preceding it with another double-quote.
When does this matter?
When your data contains addresses like 6" ruler or abbreviations like 'said he'. Unescaped quotes break CSV parsers.
Related tools
Format
JSON Formatter
Beautify and indent unformatted JSON strings into clean, human-readable structured trees.
Open Tool →
Format
JSON Minifier
Compress structured JSON files into single-line minified strings to reduce payload size.
Open Tool →
Format
Change CSV Delimiter
Switch spreadsheet delimiters between commas, semicolons, tabs, and pipes seamlessly.
Open Tool →