Big JSON Viewer

대용량 JSON 파일을 위한 브라우저 내 뷰어 — 500 MB JSON으로 검증했고, 상한은 앱이 아니라 브라우저 메모리가 정합니다. 검색·접기·복사가 모두 가볍고, 데이터는 컴퓨터를 떠나지 않습니다.

기능

• 대용량 JSON 파일을 위한 설계canvas 기반 가상 트리는 보이는 줄만 그리므로, 파싱이 끝나면 깊이나 파일 크기와 무관하게 스크롤·접기·검색이 모두 일정 시간에 동작합니다.
• 전부 로컬 처리모든 연산이 브라우저에서 끝납니다. JSON은 서버로 전송되지 않고 어디에도 기록되지 않습니다.
• 실용적인 기능탭 워크스페이스, 키 경로 복사, 정리 / 원본 전환, 검색, 다크 모드, 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.