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 HTML is
An HTML table is a table element containing thead and tbody, with th cells for headers and td cells for data.
Web pages, email templates and anything pasted into a CMS.
What changes when you convert JSON to HTML
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.
Semantic markup: a real thead, a real tbody, th for the header row. Angle brackets and ampersands in your data are escaped, so a value like <script> is written safely and shows as text on the page.
What carries over from JSON to HTML
JSON records 2 things about a table that HTML has no way to hold.
JSON distinguishes a number from the text of a number; HTML 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 HTML, so a null and an empty string in the JSON both come out blank and can no longer be told apart.
HTML marks header cells differently from data cells, so the keys are lifted out and written once as a marked header row rather than repeated on every row.
The identifier 007 comes out of the HTML 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 HTML file goes wrong.
The quotes around Jonah "Jo" Pryce are written as the HTML entity " in the HTML.