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.