Explorer
Tree explorer will appear here once JSON is loaded
Inspector
Select a node to inspect it
Tree explorer will appear here once JSON is loaded
Select a node to inspect it
Most online JSON viewers start to lag somewhere between 1 and 5 MB, because they parse into a full JavaScript object tree on the main thread and then render every node as a real DOM element. Jsontify is built specifically to avoid both of those costs: parsing runs in a background worker over typed arrays instead of building a full object graph up front, and the tree only renders the rows currently in view (virtual scrolling), so opening a large file doesn't mean rendering hundreds of thousands of DOM nodes at once.
The size difference is concrete, not aspirational: a 1 MB document parses in well under 100 ms, a 10 MB document in under a second with the main thread never blocked for more than about 50 ms at a time, and files up to 100 MB stay scrollable with a progress indicator instead of crashing the tab. These are the same thresholds tracked in the project's own performance test suite, re-run on every change that touches parsing or rendering.
Depth is handled separately from size. A document nested thousands of levels deep can overflow a browser's call stack if a parser or renderer uses ordinary recursion - Jsontify's parser and tree builder are iterative, walking the document with an explicit stack instead of function calls, so a deeply nested file parses and renders without that failure mode, independent of how large it is in bytes.
None of this changes what happens to your data: a large file is processed exactly the same way as a small one - entirely in your browser, in a Web Worker on your device. Nothing is uploaded to our servers, which matters more, not less, when the file is a multi-megabyte production log or database export you would rather not paste into a random web form.