Search DevTools

Jump to any tool or page

Table Manager

Import, edit, and manage your data effortlessly — supports JSON and CSV with reorderable, renameable columns. Large files paginate at 25 rows per page.

Table

Import a JSON or CSV file to see your data here.

Visual Creation

About Table Manager

Paste CSV, TSV or Markdown table text and edit it as a grid, then export back to any of those formats or to JSON. The awkward part of tabular interchange is not the rows but the quoting: RFC 4180 says a field containing a comma, a double quote or a line break must be quoted, and embedded quotes doubled — rules that hand-built exporters routinely get wrong.

Related Visual Creation tools

Resume BuilderChart GeneratorSVG AnimatorIndian MapColor Palette

Frequently asked questions

How are embedded commas, quotes and newlines handled on export?
Following RFC 4180, any field containing a delimiter, a double quote or a CR/LF is wrapped in double quotes, and each literal double quote inside is escaped by doubling it. So the value He said "hi", loudly becomes "He said ""hi"", loudly". A field with an embedded newline stays quoted and spans physical lines, which means a CSV file's line count is not its row count — naive line-splitting parsers break on exactly this case.
Why do my leading zeros and long numbers change when I round-trip through a spreadsheet?
CSV carries no types, so the consumer guesses. Excel and Google Sheets coerce 007 to 7, treat 1-2 as a date, and push identifiers longer than 15 digits into floating point, losing the tail. Nothing in the file signals otherwise. If the data must survive, export to JSON where strings stay strings, or prefix values with an apostrophe for spreadsheet import. Round-tripping through a spreadsheet is lossy in a way round-tripping through JSON is not.
What does the tool do with ragged rows and duplicate headers?
Rows shorter than the header are padded with empty cells and longer rows keep their extra values in unnamed trailing columns, so nothing is discarded silently. Duplicate header names are a genuine ambiguity in the CSV-to-JSON direction because object keys must be unique — later duplicates are suffixed rather than overwriting the earlier column. Renaming the header before exporting to JSON is usually clearer than relying on the suffix.
Why does my exported CSV show mojibake in Excel?
Excel on Windows still assumes the system ANSI code page when opening a .csv by double-click, so UTF-8 text renders as é and similar. The conventional fix is a UTF-8 byte order mark at the start of the file, which Excel detects and honours. The BOM is invisible in most editors but is real bytes — parsers that do not strip it will read the first header as \ufeffid rather than id, a classic source of a mysteriously missing first column.
Are Markdown tables a lossless target?
No, and it is worth knowing why before choosing that export. Markdown pipe tables cannot contain a literal newline in a cell, so multi-line values must be flattened or turned into a break tag. Pipe characters need escaping as \| . Alignment colons in the separator row carry presentation, not data. And there is no notion of typed or empty-versus-null cells. Use Markdown for documentation output and CSV or JSON when the data will be parsed again.