IT Market
Tools/Code/Documents/CSV to Excel Table Preview Online — Free Viewer
CSV → EXCEL

Просмотр CSV в Excel-стиле

Tool guide

CSV to Excel Table Preview Online — Free Viewer

Ad-platform exports, bank statements and CRM dumps arrive as one long comma-separated blob that is almost unreadable by eye. Paste the CSV here and it is drawn as a tidy grid with a header row, the way a spreadsheet would show it. It is a preview and nothing more — the page does not build or download an XLSX file. Parsing happens in the browser, so the export never leaves your machine. See also: fix the delimiters in the source CSV, build a sheet out of a JSON export, send the same rows to an API as JSON.

How to use it

  1. Copy the contents of your CSV file and paste them into the input box; the placeholder shows the name,age,city shape with data on the next line.
  2. Keep the first line as the header — it becomes the top row of the preview grid.
  3. Leave «Delimiter:» on «Detect automatically», or pick the comma, the semicolon or the tab yourself — there is no need to rewrite the export in a text editor first.
  4. Press the Preview button and the table appears below the input.
  5. Scan the grid for trouble: a column that slips out of place almost always means a stray comma inside a value.

FAQ

Do I get an XLSX file after the preview?

No, and it is worth knowing up front. The page only draws your data as a table in the browser; there is no save-as-XLSX button. For a real Excel file, import the original CSV in the spreadsheet application itself, or use a converter that returns a file. The preview is for checking the shape of an export quickly, not for producing a document.

My CSV is semicolon-separated. Will it work?

Nothing: a semicolon is detected on its own, and if the guess misses you can choose it in «Delimiter:» alongside the comma and the tab. European Excel locales and many bank portals export exactly that, and the file no longer has to be rewritten in a text editor first. The delimiter the file was parsed with is shown in the status line under the table.

Why are my columns shifted into the wrong places?

Almost always a comma inside a value: an address like New York, NY or a thousands separator splits the row into an extra field. The standard fix is wrapping such values in double quotes. Find the row whose field count differs from the header and repair it before previewing again.

How large a CSV can I paste?

A few thousand rows is the sensible limit. The grid is rendered straight into the browser DOM, so an export with tens of thousands of rows will slow the tab down noticeably or hang it on a weak device. For a structure check, the first two hundred rows are usually enough to expose formatting errors.

Does non-Latin text display correctly?

Yes, provided you copy from a UTF-8 file. Trouble starts with Windows-1251 exports: opened without declaring the encoding, the labels are already mangled before you paste them. Re-save the source as UTF-8 and copy the data again.

Is the export uploaded anywhere?

No. A script on the page parses the string and builds the table, and none of your data is sent over the network. What you pasted does stay in the field until you reload, though, so on a shared computer it is worth clearing the box after previewing a statement or a customer list.

Examples

Staff list exported from a CRM
Before: name,age,city John,30,NYC Anna,27,Berlin
After: A three-column grid: header name / age / city with two data rows below it
A row knocked out of shape by a comma inside a value
Before: name,city John,New York, NY
After: The row parses into three fields instead of two — the value needs quoting