Blog

Engineering notes, comparisons, and design decisions from building Big JSON Viewer.

• Embed a JSON Snippet in Your Page with an iframe

  Jun 16, 2026 · 5 min read · implementation, integration

  Render 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 Parsing

  May 21, 2026 · 8 min read · implementation, rendering

  Most 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 Data

  May 21, 2026 · 6 min read · architecture, privacy

  The 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 DevTools

  May 21, 2026 · 7 min read · comparison

  A 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 Streaming

  May 21, 2026 · 8 min read · implementation, networking

  How 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 Needle

  May 21, 2026 · 7 min read · meta, seo

  We 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.