What is CSV Studio?

CSV Studio is a browser-based workspace for working with CSV data the way you actually need to — not just converting it to another format, but seeing it as an editable table, understanding what's really in each column, and fixing the messy parts (duplicate rows, inconsistent casing, missing values) before you use it somewhere else. It's deliberately not just "CSV to JSON" — conversion is one export option among several, not the whole point of the tool.

What can you do with it?

Import, paste, or start from scratch — bring in a CSV/TSV file, paste delimited data directly, or build a new sheet from nothing.
Edit like a spreadsheet — click any cell to edit it, rename columns, add/remove rows and columns, reorder columns.
Search, filter, and sort — find rows instantly and sort any column ascending or descending.
Clean the data — trim whitespace, remove empty rows, remove duplicate rows, normalize case, find-and-replace, fill empty cells, convert a column's type.
Export correctly — CSV, TSV, or JSON, with quoting and Unicode preserved exactly.

Column intelligence

Every column is automatically analyzed and shown in the sidebar with its detected type (integer, decimal, date, boolean, or text) and, for numeric columns, min/max/average and a missing-value count — so you can spot data quality problems (a "revenue" column with unexpected text in it, a date column with inconsistent formats) at a glance rather than by scrolling through every row.

When should you use it?

Use CSV Studio whenever a CSV export needs a cleanup pass before it's actually usable — deduplicating a contact list, standardizing casing in a category column, filling in blanks, or just understanding what a file someone sent you actually contains. If you need to write real queries against the data (filtering by multiple conditions, joining against a second table, aggregating), use SQL Studio instead — CSV Studio's "Open in SQL Studio" button hands your table straight over.

Limitations

Very large files (hundreds of thousands of rows) may be slow, since the whole table is held in browser memory and paginated for display.
Type detection is a best-effort sample of each column's actual values — always spot-check a column before relying on its detected type for downstream processing.
Column reordering, renaming, and deletion apply to the current in-browser table only — the original imported file is never modified.

Privacy

Everything happens in your browser — importing, editing, and exporting never send your file to a server.

Frequently asked questions

How is this different from just opening a CSV in a spreadsheet app?

CSV Studio is built for a narrower, more deliberate job: understanding and cleaning the actual data — automatic column-type detection, per-column statistics, find-and-replace, deduplication — without any spreadsheet-app formulas, formatting, or file-format complexity to work around. It's the step between "raw export" and "the file I actually want to use," not a full spreadsheet application.

Will editing and re-exporting corrupt my data?

No — CSV Studio uses a strict RFC4180-compliant parser and writer, meaning quoted fields, commas inside quoted values, embedded line breaks, escaped quotes, and Unicode all survive a full import → edit → export round trip correctly. This was specifically tested, not assumed.

What delimiters does it support?

Comma, semicolon, tab, and pipe — auto-detected from your file by checking which delimiter produces a consistent column count across the first several lines.

What data types does it detect?

Integer, decimal, date, boolean, text, and empty/null — detected per column by sampling every value in that column, so a column is only marked as a type if most of its actual values fit that pattern.

Can I undo a cleaning operation?

Yes — every edit, cleaning operation, and structural change (add/remove column or row) is tracked, and Undo/Redo step through the full history of changes to the current table.

Can I move data from CSV Studio into other Convertam tools?

Yes — "Open in SQL Studio" hands your current table straight to SQL Studio so you can write real SQL against it without a manual export/re-import step.