CSV Viewer and Editor

About CSV Viewer and Editor

How to Use the Viewer

Action	How
Load data	Upload a .csv, .tsv, or .txt file, or paste raw CSV text into the input area
Edit a cell	Click any cell to type a new value directly
Edit headers	Click a column header to rename it
Sort by column	Click the column header arrow - numbers sort numerically, text alphabetically
Search / filter	Type in the search box to show only rows containing the term in any column
Add row	Click the Add Row button to insert a blank row at the bottom
Add column	Click Add Column to append a new column with a default header
Delete row/column	Click the X button on any row or column to remove it
Download	Click Download Edited CSV to save all your changes as a new CSV file

What Makes This Better Than a Text Editor?

Feature	Text Editor	This CSV Viewer	Full Spreadsheet App
Visual table layout	No - raw commas and quotes	Yes - clean aligned columns	Yes
Sorting	No	Yes - click to sort any column	Yes
Search / filter	Find text only	Yes - filters visible rows	Yes
Inline editing	Yes but error-prone	Yes - click to edit cells	Yes
Add/remove rows/columns	Manual text editing	One-click buttons	Yes
Startup time	Instant	Instant (browser tab)	Several seconds to launch
Install required	Usually pre-installed	No - runs in browser	Yes (or cloud account)
Handles quoted fields	Shows raw quotes	Parses correctly	Usually

This tool fills the gap between raw text editing (too error-prone for structured data) and a full spreadsheet application (too heavy for a quick look at a CSV export).

How Column Sorting Works

Clicking a column header toggles between ascending and descending order. The sorter detects whether a column contains numeric data or text and sorts accordingly. Pure numeric columns sort by value (so 2 comes before 10), while mixed or text columns sort alphabetically. The sort applies to all rows, not just the visible filtered subset.

Common CSV Viewer Workflows

Workflow	Steps
Quick inspection of a database export	Upload the CSV, scan the table, check row count and column names
Fix a few values before importing elsewhere	Upload, click cells to edit, download the corrected CSV
Filter for specific records	Upload, type a name or ID in the search box, review matching rows
Remove unwanted columns	Upload, click X on columns you do not need, download the trimmed file
Add a missing column	Upload, click Add Column, rename the header, fill in values, download
Sort to find outliers	Upload, sort a numeric column descending to see the largest values at the top

Supported File Formats

Format	Extension	Delimiter	Supported
Comma-Separated Values	.csv	Comma (,)	Yes
Tab-Separated Values	.tsv	Tab	Yes
Plain text delimited	.txt	Comma or tab	Yes
Semicolon-separated (European)	.csv	Semicolon (;)	Yes - auto-detected
Excel (.xlsx)	.xlsx	N/A	No - use the Excel to CSV converter first

The parser handles quoted fields, embedded commas, escaped quotes, multi-line cell values, and mixed line endings (CRLF, LF, CR) automatically.

Tips for Working with CSV Data

Tip	Why
Always check the header row	Some exports include metadata rows above the actual headers - delete them before processing
Watch for encoding issues	If you see garbled characters (é, £), the file may use a different encoding than UTF-8
Be careful with leading zeros	Values like 00123 (zip codes, product codes) may lose zeros when opened in Excel - keep them as CSV for safety
Use search to audit data	Search for empty strings, "null", or "N/A" to find missing values quickly
Sort before sharing	Sorting by a key column (date, name, ID) makes the data easier for recipients to navigate

Need to convert your CSV to a proper Excel spreadsheet with formatting? Use the CSV to Excel converter. Going the other direction, the Excel to CSV tool extracts sheet data into plain CSV format. All processing runs client-side - your data stays in your browser and is never uploaded.

What Does RFC 4180 Actually Say?

RFC 4180 is the IETF informational specification that defines the CSV format, published in October 2005 by Y. Shafranovich. The spec is short but strict: fields are separated by commas, records by CRLF line breaks, and any field containing a comma, double-quote, or line break must be enclosed in double-quotes. Inner double-quotes are escaped by doubling them (a literal " becomes ""). A header row is optional but recommended. In practice most real-world CSV files deviate from the spec: LF-only line endings are common (Unix exports), UTF-8 with a BOM appears in Windows exports, and semicolons are used as delimiters across much of Europe because the comma is their decimal separator. The parser behind this viewer handles all of these variants.

Why Do European CSVs Use Semicolons?

In locales where the comma is the decimal separator (most of continental Europe, including Germany, France, Spain, Italy, and the Nordics), using the comma as a field separator would be ambiguous - a value like 1,50 could be one number or two fields. Microsoft Excel's List Separator setting defaults to the semicolon in those locales, so CSV files exported from Excel in German or French Windows use ; between fields. The viewer auto-detects the delimiter by scanning the first line and picking whichever character appears most consistently. If you see everything crammed into a single column, the detection failed - try opening the file in a text editor and re-pasting with the correct delimiter.

How Big Can CSVs Get Before They Break?

Row count	Typical source	Browser behaviour
Up to 10,000	Analytics exports, contact lists	Instant - table renders in under a second
10,000 to 100,000	Ecommerce order history, CRM extracts	Fast - parsing takes 1-3 seconds, scrolling is smooth
100,000 to 1,000,000	Server logs, large transaction exports	Works but slower - initial render takes 5-15 seconds
Over 1,000,000	Full database dumps	Better handled by a database tool or streaming parser; the browser will struggle

The file upload hard cap here is 100 MB, which in practice covers millions of rows for most text-heavy exports. Files larger than that are usually better split or loaded into a proper database (DuckDB, SQLite, Postgres).

Common CSV Parsing Pitfalls

Pitfall	What happens	Fix
Embedded newlines in a cell	Without quoting, the row splits unexpectedly	Wrap the whole field in double-quotes - RFC 4180 permits multi-line quoted fields
Unescaped quotes inside a field	Parser thinks the field has ended, shifts subsequent columns	Double every internal quote: He said "hi" becomes "He said ""hi"""
Byte-order mark (BOM) at the start	First header becomes Name instead of Name	Save the file as plain UTF-8 without BOM, or rename the first header after import
Mixed line endings	Some tools produce a single mega-row	PapaParse handles this automatically - most basic split-by-comma parsers do not
Trailing empty lines	Blank rows appear at the bottom	Delete them after import using the row X button - skipEmptyLines is on by default here
Numbers with thousand separators	Sorting treats 1,000 as text	Strip separators before export, or sort using a clean numeric column

When Is CSV the Right Format, and When Is It Not?

CSV is the best choice when you need a format that every database, spreadsheet, language, and analytics tool can read without a library - it is the lowest common denominator for tabular data interchange. The W3C's Tabular Data and Metadata Working Group published a formal model for CSV on the Web in 2015, reinforcing its role as the default data publishing format for open government datasets (see data.gov.uk and data.gov).

CSV breaks down when you need typed columns (dates, booleans, nested objects), multiple tables in one file, or large binary-friendly columns. In those cases Parquet or JSON are better. For everyday exports, database dumps, config files, and quick hand-edits though, plain CSV is hard to beat. If you need to move data between CSV and structured formats, the JSON to CSV tool flattens JSON arrays into CSV rows.

Browser vs Desktop CSV Tools

Opening a CSV in Excel or LibreOffice Calc is powerful but has downsides: Excel famously mangles leading zeros on product codes, auto-converts strings that look like dates (the classic SEPT1 gene name issue), and requires a round-trip through the Save As dialog to get back to clean CSV. A browser-based viewer avoids all of this - values are treated as text by default, nothing auto-converts, and downloading gives you back a clean RFC-style CSV. For spotting a malformed row, renaming a few columns, or filtering to a subset before sharing, a browser tool is usually faster than launching a spreadsheet app.

Sources

• IETF RFC 4180 - Common Format and MIME Type for CSV Files
• W3C - Model for Tabular Data and Metadata on the Web
• W3C - CSV on the Web: A Primer
• MDN - FileReader API
• PapaParse - CSV Parser Documentation
• data.gov.uk - Publishing Your Data (CSV recommended)
• ISO/IEC 29500 (Office Open XML) - Related File Formats