CSV Unescape Online — Unquote CSV Fields

Strip RFC 4180 quoting from CSV rows and decode doubled quotes back to a single character. Browser-only — paste quoted rows, copy clean cell values.

Quoted CSV Input

Unescaped Cells (pipe-separated)

What is CSV Unescaping?

CSV unescaping reverses RFC 4180 quoting: it strips the surrounding double quotes from a quoted field and converts every doubled internal quote ("") back to a single double quote ("). The result is the original cell value the producer intended to store.

CSV looks simple but parsing it correctly requires respecting the quoting rules — a comma inside a quoted field is data, not a delimiter. The OpenFormatter CSV unescape tool runs a state-machine parser entirely in your browser. Paste a row with embedded commas, doubled quotes, or even multi-line cells and it returns each unescaped cell value.

How to unescape CSV online — 4 steps

Paste quoted CSV rows. Drop RFC 4180 escaped content into the Input panel. Quoted fields, doubled quotes, and embedded commas are all handled.
Click Unescape. The state-machine parser walks each line one character at a time, splitting on commas only when outside a quoted region.
Inspect cell boundaries. Each row is rendered with cells separated by " | " so you can verify the parser identified field boundaries correctly.
Copy clean values. The unescaped cells are now plain text — paste them into your code, database, or downstream pipeline.

Sample input and output

Quoted CSV input

name,note,city
Alice,"She said ""hi"" today",New York
Bob,"Lives at 123 Main St, Apt 5",Boston
Carol,"Multi-line
note value",Chicago

Unescaped cells

name | note | city
Alice | She said "hi" today | New York
Bob | Lives at 123 Main St, Apt 5 | Boston
Carol | Multi-line
note value | Chicago

State-Machine Parser

Walks each line character-by-character, tracking whether the cursor is inside a quoted region. Commas inside quotes stay as data.

Doubled-Quote Aware

Detects "" sequences inside quoted fields and collapses them to a single quote — the canonical RFC 4180 unescape.

Browser-Only

Parsing happens in your browser. CSV files with PII, financial records, or proprietary data never leave the device.

Common use cases

check_circleInspecting CSV exports from CRM, ERP, or BI tools to see actual cell values
check_circleDebugging row-shift issues caused by unbalanced quotes in CSV
check_circlePreparing values from a CSV column for inclusion in code constants
check_circleVerifying that an upstream producer escaped fields correctly per RFC 4180
check_circleReading individual quoted cells from a database dump in CSV format
check_circleDecoding survey-export CSV with quoted free-text comments
check_circleSpot-checking CSV produced by COPY TO from Postgres before consuming it
check_circleManually inspecting log-line CSV where the message column contains commas

CSV unescape vs JSON parse vs SQL unquote

Each format has different rules for getting back to the raw value. CSV unescape strips outer double quotes and collapses doubled quotes — there are no backslash sequences. JSON parse evaluates backslash escapes (\", \n, \u00xx) inside double-quoted strings. SQL unquote usually strips outer single quotes and collapses doubled single quotes (dialect-dependent). Running a JSON-style parser on CSV will trip on backslashes that should be literal data.

Need to escape, or convert to JSON?

Apply RFC 4180 quoting with CSV Escape, or transform CSV into structured JSON for further processing.

CSV Escape CSV to JSON All Escape Tools

Frequently Asked Questions

How does CSV unescaping work?

A field that begins and ends with a double-quote is dequoted: the outer quotes are removed and every doubled-quote ("") inside is converted back to a single double quote ("). Fields without surrounding quotes are returned unchanged. Commas inside quoted fields are treated as literal data, not as column separators.

How are doubled double quotes ("") handled?

The doubled-quote convention from RFC 4180 means two consecutive double quotes inside a quoted field represent a single literal quote. The unescape parser walks the field one character at a time and collapses each "" into a single " in the output, restoring the original cell contents.

What about embedded newlines inside a field?

A newline inside a quoted CSV field is part of the field value, not a row terminator. This unescape tool processes input line-by-line, so multi-line fields are most useful when fed as a single logical row. For full multi-line CSV parsing, use a streaming parser like Papa Parse or Python's csv module.

What if my field is not quoted?

Plain unquoted fields require no unescaping. The tool detects them and passes them through unchanged. Only fields wrapped in matching outer double quotes are dequoted, so the operation is safe to run on mixed input.

Does it handle leading or trailing whitespace inside fields?

Whitespace inside a quoted field is preserved exactly. RFC 4180 says any whitespace inside the quotes is part of the value. Whitespace outside the quotes (between the comma and the opening quote) is implementation-defined; this tool keeps it as-is.

Will it work with semicolon or tab separated values?

The tool is configured for comma-separated input — the canonical RFC 4180 delimiter. Semicolon (common in European locales) and tab (TSV) follow the same quoting rules but use a different separator; you would adjust the split character to match your file.

Why are my fields shown joined by a pipe ( | )?

The output uses " | " between fields purely as a visual separator so you can see where each cell starts and ends after unescaping. The actual data inside each cell is the unescaped value — no pipe characters were introduced.

Is the data sent to your servers?

No. CSV unescape runs entirely in JavaScript inside your browser. The tool is safe for files containing customer data, financial records, or other PII — nothing leaves your machine. Verify with DevTools Network tab.