Overview
Paste CSV on the left and edit it as a real spreadsheet grid: the first row becomes editable column headers, every cell is an input, and buttons add or remove rows and columns. Parsing is done by PapaParse, a browser CSV library that follows RFC 4180, so quoted fields, embedded commas, and escaped quotes in your input are read correctly. Export downloads the edited table as a .csv file.
How It Works
Paste CSV text into the small textarea and press Parse; the grid appears with the first row as headers and the rest as rows. Edit any header or cell in place. Use the + Row button to append an empty row and + Column to append a column named ColN; the small x button on each header removes that column, and the x in the row-number gutter removes that row. When the table looks right, press Export CSV to download the result as table.csv.
Step-by-Step Usage Guide
- Paste your CSV into the textarea and press Parse to load the grid.
- Edit headers and cells directly; changes are local to the page.
- Add or delete rows and columns with the buttons and the x controls.
- Press Export CSV to download the edited table as a file.
Technical Specifications & Standards
Reading and writing CSV are treated as different problems here, and the gap shows in edge cases. Reading is delegated to PapaParse with header parsing off and empty lines skipped, which means quoting per RFC 4180 is handled for you: a cell containing a comma, a newline, or a doubled quote round-trips into the grid intact. Writing is the tool's own serializer: each row is joined with commas, and a value is wrapped in double quotes only if it contains a comma. That is a weaker rule than the RFC requires. A cell that contains a double quote but no comma is written raw, producing output that strict parsers will misread, and a cell containing only a newline without a comma is likewise unquoted. Practically: if your data contains quotes or newlines, clean them in the grid or post-process the file; the parse path is stricter than the export path, so data can survive ingestion and then be written back incorrectly. Columns added later get a ColN header rather than a blank, which keeps the export unambiguous, and row and column removal happen independently so you can reshape rectangular data without touching a formula grid.
Targeted Use Cases
- Cleaning a small dataset before importing it into a database or spreadsheet tool.
- Fixing header names in an exported report without opening Excel.
- Deleting rows and columns from a large CSV pasted from a log or a ticket.
- Preparing test fixtures with specific cell values for an application you are testing.
Notes & Gotchas
- Re-check exported cells that contain double quotes or line breaks; the export quotes only values containing commas.
- Press Parse after every paste rather than editing the raw textarea, since the grid is the source of truth for the export.
- Use Parse to re-import your own exported file if you want to verify the round trip.
- Keep numeric data free of thousands separators in the grid if the downstream system expects raw numbers.
Frequently Asked Questions
Does it handle quoted fields with commas inside?
Yes. Parsing is done by PapaParse, which implements RFC 4180 quoting, so commas, doubled quotes and embedded newlines inside quoted fields are parsed into single cells correctly.
Are there limits on file size?
There is no fixed limit, but the whole table renders as live inputs, so very large files (tens of thousands of rows) will feel slow. For big data, crop it in a text editor first or use a dedicated tool.
Can I rename column headers?
Yes. Each header cell is an editable input in the grid's header row, and the names you type are written as the first row of the exported file.
Why did my exported file misbehave in another program?
The exporter wraps a value in quotes only when it contains a comma. A value with a double quote but no comma is written unquoted, which some strict parsers treat as invalid. Clean such cells before exporting or fix the file afterward.