JSON Crack: Interactive Graph Visualization for JSON, YAML, XML, and CSV
GitHub describes it as ✨ Innovative and open-source visualization application that transforms various data formats, such as JSON, YAML, XML and CSV into interactive graphs.. The repository metadata lists TypeScript as its primary language. The metadata lists the Apache-2.0 license. This article stays within the project description and details documented in the GitHub repository README.
At a glance
- What is it?
- JSON Crack turns structured data into interactive graphs and trees, with conversion, validation, and code generation. It is a TypeScript monorepo with web, VS Code, and Chrome extensions, but its node limit and local-only processing shape its real-world fit.
- Who is it for?
- Adopt JSON Crack if you need a free, local-first way to explore nested JSON or YAML as an interactive graph, and you can stay within the configurable node limit. Avoid it if you require very large data sets, server-side processing, or a non-Node toolchain.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 62 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- AykutSarac/jsoncrack.com44,599 ★ · +311
| Repository | 2026-08-13 | 2026-11-15 |
|---|---|---|
| AykutSarac/jsoncrack.com | 44.3k | 44.6k |
311 Stars in the last 94 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What JSON Crack solves and who it targets
JSON Crack addresses a narrow but common pain: reading deeply nested JSON, YAML, XML, or CSV by eye. The README frames it as an open-source JSON editor that visualizes data into interactive graphs. The target user is a developer or data analyst who needs to explore a structure, spot relationships, or debug a payload without switching between a text editor and a separate visualization service. The tool also covers conversion between formats, validation, JSON Schema generation, and code generation for TypeScript interfaces, Golang structs, Kotlin data classes, and Rust serde types. That breadth suggests JSON Crack is not just a viewer but a small data workbench. The mention of jq and JSON path queries in the advanced tools points to a user who already knows query syntax and wants it applied to the graph.
How the visualization mechanism works
The repository is a pnpm monorepo with workspaces for the web app, a VS Code extension, and a Chrome extension. The core is a web application built with Next.js, given the NEXT_PUBLIC_ env prefix and the pnpm dev:www script that runs on localhost:3000. The README states that all data processing is local and nothing is stored on servers, which means the graph rendering and format conversion happen in the browser. The interactive graph is the central artifact, with dark and light modes. The tool accepts JSON, YAML, CSV, and XML as input and renders them as graphs or trees.
Getting it running: commands and configuration
The README gives explicit setup steps. You need Node.js version 24.x or newer and pnpm version 10 or newer. Clone the repository, run pnpm install, then pnpm dev:www to start the web app on localhost:3000. For production builds, pnpm build:www is available. The monorepo also exposes pnpm dev:vscode and pnpm dev:chrome for the extensions, plus a pnpm dev command that runs all workspaces. Docker is supported from apps/www: cd apps/www, then docker compose build and docker compose up, which serves on localhost:8888. The single documented configuration key is NEXT_PUBLIC_NODE_LIMIT in apps/www/.env, which changes the supported node limit. That is a sparse configuration surface, which is either simplicity or a limitation depending on your needs.
The node limit is the first real constraint
The README mentions NEXT_PUBLIC_NODE_LIMIT as the way to change the supported node limit, but it does not state the default value or the maximum. That omission is a problem for evaluation. If you plan to visualize a large JSON file, you cannot know from the documentation whether it will render or fail. The node limit exists because interactive graph rendering in the browser has performance ceilings, but the project does not publish benchmarks or guidance. This is a genuine limitation: for payloads with thousands of nodes, you may need to trim the data or use a different tool. The README also does not describe what happens when the limit is exceeded, whether it errors, truncates, or warns. That ambiguity is a real gap for adoption decisions.
Privacy and processing model: local by design
The README claims that all data processing is local and nothing is stored on servers. That is a strong privacy statement, and it aligns with the browser-based architecture. For developers handling sensitive or proprietary JSON, this is a major advantage over cloud-based visualization tools that upload data to a backend. However, the claim is not backed by a detailed data flow description in the README. There is no mention of whether the web app at jsoncrack.com also processes locally, or whether the local-only guarantee applies only to the self-hosted version. The Docker setup for apps/www suggests you can run your own instance, which would give you full control. But the README does not clarify if the hosted site has telemetry or analytics. That distinction matters for a privacy-sensitive user.
Integrations and distribution channels
JSON Crack is distributed beyond the web app. The README lists a VS Code extension, a Chrome extension, and an npm package called jsoncrack-react. The VS Code extension is notable because it lets you visualize a .json file directly in the editor, with a command named JSON Crack: Enable JSON Crack visualization. The Chrome extension is for viewing JSON in the browser. The jsoncrack-react package suggests you can embed the visualization in your own React applications, which is a different integration path than using the standalone site. The README does not document the npm package's API or usage, so you would need to inspect its own README or source. The monorepo structure with apps for each extension means the codebase is not a single web app but a multi-target project, which increases maintenance surface but also reach.
Maintenance and upgrade considerations
The repository shows active development: v4.0.0 in April 2025, v5.0.0-beta.1 in July 2025, and v5.0.0 in March 2026. That cadence indicates the project is not abandoned, but it also means upgrades come frequently. The README suggests watching releases for updates. The license is Apache-2.0, which permits commercial use and modification, but the README includes a link to the LICENSE file for additional details when distributing code. The sponsor link to ToDiagram is a commercial tie, but it does not affect the open-source license. The Docker setup is straightforward, but the monorepo with web, VS Code and Chrome targets means a full build involves more than a single command.
Alternatives and where JSON Crack falls short
A common alternative is a text-based JSON viewer with tree collapsing, such as the built-in JSON viewer in VS Code or a jq-based workflow. Those tools do not produce interactive graphs, but they handle arbitrarily large files without a node limit. Another alternative is a dedicated diagramming tool like draw.io, which can import JSON but requires manual mapping. The key difference is that JSON Crack auto-generates the graph from the data structure, which is faster for exploration but less flexible for custom layouts. A more direct alternative is a browser extension like JSON Viewer, which renders JSON as a collapsible tree but does not offer graph edges or conversion features. JSON Crack's graph view is its differentiator, but that comes with the node limit and the browser performance ceiling. For data that fits within the limit, it is a strong choice; for data that does not, you are better off with a plain text editor and jq.
Editorial conclusion
Adopt JSON Crack if you need a free, local-first way to explore nested JSON or YAML as an interactive graph, and you can stay within the configurable node limit. Avoid it if you require very large data sets, server-side processing, or a non-Node toolchain. Before committing, verify the node limit for your typical payloads, test the CSV and XML parsers on your own files, and check the Apache-2.0 license details in the repository's LICENSE file.
Frequently asked questions
How do I run JSON Crack locally for development?
Install Node.js 24 or newer and pnpm 10 or newer, clone the repository, then run pnpm install followed by pnpm dev:www, which serves the web app on http://localhost:3000/. Turbo scripts are filtered per workspace, with pnpm dev:vscode and pnpm dev:chrome for the extensions.
Can I self-host JSON Crack with Docker?
Yes. The Docker assets live in apps/www, and from that directory you run docker compose build and then docker compose up, after which the app is on http://localhost:8888. The image covers the web app; the VS Code and Chrome extensions are separate build outputs.
Does JSON Crack send my data to a server?
The project states that all data processing is local and that nothing is stored on their servers. The Docker option lets you run the app on your own machine at localhost:8888.
How do I raise the node limit in JSON Crack?
Edit NEXT_PUBLIC_NODE_LIMIT in apps/www/.env. Because the variable carries the NEXT_PUBLIC_ prefix, the value is compiled into the client bundle, so changing the limit means rebuilding the web app rather than restarting it.
What are the JSON Crack VS Code and Chrome extensions?
They are separate products built from the same monorepo, each with its own turbo filter, build and lint script. The VS Code extension is debugged by pressing F5 in VS Code, choosing Run VSCode Extension (apps/vscode) and running the command JSON Crack: Enable JSON Crack visualization on a .json file.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/aykutsarac-jsoncrack-com)Star history chart for your README
[](https://hysenlabs.com/projects/aykutsarac-jsoncrack-com)Was this useful?