JSON tools
Paste an array of objects. Select fields, reorder columns and check the table before exporting.
Processed in this browser. Your input is not uploaded or stored.
Convert to preview rows.
Convert to discover fields. Input or nested-strategy changes reset selection. Arrows change column order only.
Changes detected. Updating the result…
An API response is useful in documentation only when its important fields fit the page. JSON to Markdown table turns the selected records into a readable reference without asking you to maintain separator rows by hand.
A field that appears only in the last record still deserves a column. This JSON to Markdown converter scans the whole array, retains the original numeric spelling and lets you decide which fields your reader needs.
JSON to Markdown table discovers fields across all records before selecting them. Move an identifier beside its description, hide internal flags and keep later optional fields visible. The original array remains unchanged throughout this process.
An address can remain compact JSON when readers need the whole object. Switch to flattened object paths when city and postcode deserve separate columns. Arrays stay in one cell, so an item with several tags still occupies one row.
The first conversion collects every field. Selection and arrow controls then set your exported columns. Editing input or switching nested strategy resets the field list; changing alignment or format keeps the current selection.
Automatic conversion waits 400 ms after your last edit. Turn it off to use Convert or Ctrl/Cmd + Enter. Every input, option and column-order change disables export until the next successful conversion finishes.
The preview shows 50 records at a time; Show more adds another 50. Source view exposes pipes, separator colons and generated line breaks. Copy and download include all records, including those beyond the preview.
Column order follows first appearance, including fields from later objects. Missing fields become empty cells; explicit null prints null, while false, zero and empty strings keep their distinct source representation where a text table can express it.
Pipes and backslashes are escaped in every cell, including header names. Markdown emphasis and link syntax are treated as text. Literal HTML is entity encoded before source line breaks become generated <br> elements.
Choose left, center or right alignment for every column. Markdown includes the required header and delimiter rows. HTML exports a table fragment with header scopes and aligned cells. Downloads use table.md or table.html accordingly.
Long identifiers, exponent notation, trailing decimal zeros and negative zero survive the parser as original tokens. Nested JSON remains compact text; objects can be flattened without splitting arrays or multiplying parent rows.
Use an array containing only objects, such as [{"name":"Ada"}]. Each object contributes one row. Fields discovered across the entire array provide the headers. A top-level object is not automatically reinterpreted as key/value rows.
Yes, the table uses GitHub Flavored Markdown syntax, including a header separator and alignment markers. Check the actual destination when using another wiki. A renderer that disables inline HTML may handle <br> differently.
Choose left, center or right in the alignment selector. This applies to all selected columns and updates both the table preview and exported format. It does not sort values, change numeric types or add spaces to pad columns.
Keep the default to display objects and arrays as compact JSON in one cell. Flatten exposes object leaves through JSON Pointer headers. Arrays always remain compact JSON, and empty objects stay visible as {}.
If a pasted table breaks into extra columns, inspect its pipes and newlines. This tool escapes pipes in headers and values and replaces source line breaks with <br>. It generates the required separator row and exports the full selected table.
Found an edge case this converter gets wrong?
Use JSON to Markdown table when a README needs a focused view of real records. Check optional fields, choose the appropriate nested representation and paste the current result into your document.