CSV Escape & Formatter Tool
Prepare CSV fields with RFC 4180-compatible quotes, commas, newlines, and escaped internal quotes.
- Sin límites de longitud
- Sin registro
- Gratis para siempre
- Tu texto nunca sale de tu navegador
The CSV Comma and Quote Problem
CSV is a plain-text table: rows are records, columns are separated by a delimiter — usually a comma — and quoting exists so that delimiter can appear inside a cell. The trouble begins when real content contains commas, double quotes, or line breaks, which user-generated text does all the time. A naive splitter that cuts on every comma pushes a name like Smith, John into two columns, and a field containing a newline breaks the record apart entirely.
A global find-and-replace cannot fix this, because the correct treatment depends on context: a comma inside a quoted cell must stay, while a comma between cells must split. The working rule is to quote every field that contains a delimiter, a double quote, or a line break, and to escape quotes inside quoted fields by doubling them. That is exactly the behavior this page implements for you in both directions.
The RFC 4180 Standard
RFC 4180 is the de facto definition of CSV. Fields are separated by commas, records are separated by CRLF line endings, and any field containing a comma, a double quote, or a line break must be wrapped in double quotes. A double quote inside such a field is written twice: the cell He said "Hi" becomes "He said ""Hi""".
When every field follows those rules, any standards-aware reader — Excel, Google Sheets, and the CSV libraries of every mainstream language — parses the file identically. The tool applies the quoting automatically and offers the inverse direction too: given a quoted CSV line, it unescapes each field so you can see exactly what every cell contains. Keep the file in UTF-8 (with a BOM for Excel) and confirm the separator your spreadsheet expects, since some locales default to semicolons rather than commas.
Preguntas frecuentes
Why does Excel put my CSV data into a single column?
The parser is not seeing the delimiters you expect, and the cause is usually one of three things: a separator mismatch (your regional list separator is “;” but the file uses commas, or the reverse), a file whose fields lack the quoting needed to protect embedded commas and newlines, or an encoding problem that garbles accents and quotes. Open the file with the import wizard, choose the delimiter and encoding explicitly — UTF-8 with BOM for Excel — and confirm the quoting; the data will then split into the columns you intended.
Tu texto nunca sale de tu navegador
Cada herramienta se ejecuta localmente en tu dispositivo. Nada de lo que pegues se sube, se almacena ni se rastrea.