Big JSON Viewer

为大 JSON 文件而生的浏览器查看器——500MB 的 JSON 经实测可流畅打开，上限取决于浏览器内存，应用本身不设限。搜索、折叠、复制都很流畅，数据始终留在本地。

功能

• 为大 JSON 文件而生canvas 虚拟化树形渲染只画可见的行，文件一旦解析完成，滚动、折叠、搜索都是常数时间——无论嵌套多深、文件多大。
• 完全本地处理所有逻辑都在浏览器中运行。你的 JSON 不会上传、不会被记录、不会发送到任何服务器。
• 实用工具齐全多标签页工作区、key 路径复制、格式化/原始切换、便利的搜索、深色模式，以及 9 种语言。

常见问题

关于 Big JSON Viewer 的常见问题。

博客

• Embed a JSON Snippet in Your Page with an iframeRender any JSON snippet as a collapsible tree inside an iframe on your own site. The data rides in the URL hash — gzipped and base64url-encoded — so nothing is uploaded. Here is the exact payload spec.
• Why JSON Viewers Stall on Rendering, Not ParsingMost JSON viewers freeze at 50 MB because they render millions of DOM nodes. Parse capacity is a browser-imposed ceiling we can’t fix, but the rendering bottleneck is fixable — and that’s where Big JSON Viewer wins.
• Local-Only by Design: Why a JSON Viewer Should Never See Your DataThe privacy story behind Big JSON Viewer is also the architecture: no server, no upload, no logs, no telemetry on your file contents. Here is what that looks like in practice.
• Big JSON Viewer vs jq, JSON Crack, and Chrome DevToolsA practical comparison of four very different JSON tools, with use cases where each one is actually the right choice — and the cases where each one breaks down.
• Sharing 500 MB of JSON in the Browser: Resumable Uploads and Gzip StreamingHow we share 500 MB JSON files via the user’s own Google Drive, with chunked resumable uploads, client-side gzip, abortable progress, and transparent decompression on the recipient side.
• Migrating from Vite to Next.js for SEO: What Actually Moved the NeedleWe moved Big JSON Viewer from a Vite SPA to Next.js to fix indexability. Here is what helped, what we expected to help but didn’t, and what was the framework just doing the work for us.