Форматируйте и просматривайте CSV таблицы
Tool guide
Exports from a CRM or an ad dashboard arrive as one long wall of text where nothing lines up and a single stray delimiter is invisible. This page parses the pasted CSV into rows and cells, shows the same data as a plain table and hands the text back in a tidy shape. It is the quickest way to sanity-check a file before importing it somewhere expensive. Everything is parsed by the page script in your own tab. See also: open the same CSV as an Excel table, turn the rows into an array of objects, pull an HTML table off a page into CSV.
The delimiter is worked out for you now: the page reads the first lines, chooses between a comma, a semicolon and a tab, and names its pick in the status line. Override it in «Delimiter:» when the guess is wrong. A value holding a comma or a line break only needs double quotes around it — such a field is parsed whole. A bare comma in an unquoted value will still split the row into an extra column.
Everything lives in the tab's memory, so a few thousand rows format instantly while a file of several hundred thousand rows will stall the browser — the text sits in a single field and redrawing it is expensive. For huge exports paste the first couple of thousand rows, confirm the structure here, and load the full file into a database or a spreadsheet.
That is exactly what this page is for. It runs in any browser, including a phone, and needs no install. Paste the text into «CSV Input», press Format, and the rows and columns appear. You cannot edit cells, run formulas or build pivots here — it is a viewer and a tidier, not a spreadsheet editor.
The text is handled as UTF-8, so accented and Cyrillic characters survive. Trouble usually appears later: Excel on some locales opens a double-clicked CSV as Windows-1251 and shows gibberish. Import through Data → From Text/CSV and pick Unicode UTF-8, or open the file in Google Sheets, which detects the encoding itself.
A multi-line value is legal when it is wrapped in double quotes, but such a file is hard to read by eye because one record spans several visual lines. If the formatted output shows a record sprawling, replace the in-field newlines with spaces in the source export — most import targets prefer it that way.
Here the format is the same going in and coming out: CSV stays CSV and only its readability changes. If your code needs an array of objects, use the separate CSV to JSON page, and the JSON to CSV page covers the trip back from an array to a table.
No. The page script does the parsing and the table rendering, no network request carries your rows, and the Download button assembles the file inside the browser. An export holding customer phone numbers or deal amounts can be pasted here safely; closing the tab clears it.
Before: date,campaign,cost 2026-05-30,search,1200 2026-05-31,retarget,780
After: date | campaign | cost 2026-05-30 | search | 1200 2026-05-31 | retarget | 780
Before: id,name,city 7,Ivanov, Perm,RU
After: The second row has four cells instead of three — an extra comma inside the city value
Your rating and feedback help decide what to improve next.