Tablizer

Convert JSON to TXT Online

Paste a JSON table below, edit it if you need to, and get TXT back. The conversion runs in your browser, so nothing is uploaded, there is no size limit and there is no signup.

From

The only part of this site that uses a server. The address is sent to it so the page can be fetched, because a browser is not allowed to fetch someone else's page itself. Your own files are never involved.

Nothing here is uploaded. The parsing happens on this page.
Edit
Paste or upload something above and it will appear here.
ToDataMarkupDocumentsCodeSchemasImages

The output will appear here once there is a table to convert.

What JSON is

JSON is a text format for nested data: objects with named keys, arrays, strings, numbers, booleans and null. It has no date type and no comments.

Every web API, most configuration files and anything that talks to JavaScript.

What TXT is

Plain text here means columns lined up with spaces, the way a command line tool prints a table.

Terminal output, log files, fixed-width exports from older systems.

What changes when you convert JSON to TXT

Four shapes all read correctly: an array of objects, an array of arrays with a header row, an object of column arrays, and an object keyed by row id. A single wrapper key holding the array, which is how most APIs reply, is unwrapped automatically. Nested objects are flattened one level into dotted keys; anything deeper is kept as JSON text in the cell, because a table cannot hold a tree.

Columns are padded to the widest value. Width is counted in display columns rather than characters, so a table containing Chinese, Japanese or Korean text still lines up: those glyphs occupy two columns in a monospace font.

What carries over from JSON to TXT

JSON records 4 things about a table that plain text has no way to hold.

JSON distinguishes a number from the text of a number; plain text does not, so every value arrives as text and has to be re-parsed by whatever reads it next.

An empty cell and a missing one are the same thing in plain text, so a null and an empty string in the JSON both come out blank and can no longer be told apart.

JSON can hold a value that is itself a list or an object. plain text has only flat cells, so nested values are flattened into one cell rather than being spread across columns.

A line break inside a cell ends the row in plain text, so line breaks are replaced rather than carried through.

The keys stop being repeated: plain text writes the column names once at the top, so the same table takes noticeably less space.

The identifier 007 comes out of the TXT as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.

The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a TXT file goes wrong.

The quotes around Jonah "Jo" Pryce are left as a plain quote character in the TXT.

A worked example

Three rows of staff data, with an identifier that has a leading zero, a value containing a comma, a value containing quotes and one blank cell. Those are the four places formats disagree, so they are the four places to look.

JSON in
[
  { "id": "007", "name": "Halima Yusuf", "role": "Analyst, data", "started": "2024-03-15", "hours": "38.5" },
  { "id": "012", "name": "Jonah \"Jo\" Pryce", "role": "Engineer", "started": "2025-11-02", "hours": "" },
  { "id": "104", "name": "Wei Chen", "role": "Manager", "started": "2023-06-30", "hours": "40" }
]
TXT out
id   name              role           started     hours
007  Halima Yusuf      Analyst, data  2024-03-15  38.5
012  Jonah "Jo" Pryce  Engineer       2025-11-02
104  Wei Chen          Manager        2023-06-30  40

Questions

How do I convert JSON to TXT?

Paste your JSON into the box above or drop the file onto it. Check the table in the grid, then copy or download the TXT from the output panel. It takes one step and the data never leaves your browser.

Why did my zip code lose its leading zero?

Type inference turned the text 07030 into the number 7030. Tablizer leaves inference off by default for exactly this reason, and refuses to convert any value starting with a zero followed by a digit even when it is on.

Will my numbers still be numbers?

They will read the same, but plain text stores them as text. Anything that sorts or sums the result will need to parse them first, and a leading zero or a currency symbol is the usual place that goes wrong.

What happens to nested values?

plain text has no nested cell, so a list or object inside a JSON value is flattened into a single cell rather than expanded into extra columns. Split it before converting if the parts need to be separate.

One of my cells has a line break in it - what happens?

A line break would end the row in plain text, so it is replaced instead of carried through. The rest of the cell stays where it belongs.

Is there a limit on file size?

No. The work happens on your own machine, so the limit is your machine's memory rather than an upload cap. A file with tens of thousands of rows converts in a second or two.

Is my data uploaded anywhere?

No. The parsing and generating are done by JavaScript running on this page. You can watch the network tab while you convert and see that nothing is sent.

Related conversions