When does a CSV field need quoting?

Per RFC 4180, a field must be wrapped in double quotes if it contains the delimiter, a double quote, or a line break. Fields without any of those characters are left bare. This tool quotes only when required, keeping output minimal and readable.

How are embedded double quotes handled?

Inside a quoted field, each literal double quote is escaped by doubling it. So the value 6" pipe becomes "6"" pipe". Unescaping reverses this by collapsing each doubled quote back to a single one and stripping the surrounding quotes.

Why does my field need quoting just for a newline?

A bare newline would end the CSV record early and split one value across two rows. Wrapping the field in quotes tells parsers the newline is part of the data, so multi-line addresses or notes stay in a single field.

Can I use a semicolon or tab delimiter?

Yes. Many European locales use semicolons because the comma is a decimal separator, and tab-separated values are common in data exports. Selecting the delimiter changes which character triggers quoting; the quote-doubling rule is unchanged.

Does this escape against CSV injection?

RFC 4180 escaping makes fields parse correctly but does not stop formula injection in spreadsheets, where a value starting with = or + can execute. For untrusted data destined for Excel, also prefix risky values with a single quote or space.

CSV Field Escaper/Unescaper

CSV looks simple until a value contains a comma, a quote, or a line break. This tool applies the RFC 4180 rules to escape a single field so it round-trips correctly, and unescapes a quoted field back to its raw value.

How it works

A field is quoted only when it must be, and embedded quotes are doubled:

needs quoting if field contains: delimiter, double quote, or newline
escape: wrap in " ... " and replace every " with ""
"plain"            -> plain            (no special chars, left bare)
a,b                -> "a,b"            (comma forces quoting)
6" pipe            -> "6"" pipe"       (quote doubled)
line1\nline2       -> "line1\nline2"   (newline forces quoting)

Unescaping detects a field wrapped in double quotes, strips the outer pair, and collapses every "" back to a single ".

Tips and notes

Quote only when necessary — over-quoting every field is legal but bloats the file and hurts readability. If your data uses semicolons (common where the comma is a decimal point) or tabs, set the delimiter so quoting triggers on the right character. Finally, remember that RFC 4180 escaping is about parsing correctness, not spreadsheet formula safety: values beginning with =, +, -, or @ can still execute in Excel and should be neutralised separately.