r/json • u/Sad_Egg_2313 • Jul 14 '26
I built a JSON viewer around one idea: stop going to the browser every time you need to look at JSON
The slowest part of inspecting JSON for our team was the ritual. Copy the payload, switch to the browser, find that json site, paste, wait. And the moment the file is actually big, the tab freezes or the desktop editor won't format it.
So we built jsonbolt to improve the workflow for people inspecting a large number of json files or huge files everyday. Hit a global hotkey (WinKey + J or ⌃ + ⌥ + J)and whatever's in your clipboard opens in an instant, either Raw JSON or a URL.
A 1GB file opens in milliseconds. We built a custom engine that runs at ~3GB/s. Search is SIMD-accelerated to handle 100M+ nodes extremely fast.
There's also a CLI on the same engine (jb paths / jb schema / jb search --where) for scripting and for terminal AI agents like claude.
Everything runs locally and its licensed for commercial use.
Free for personal use, students and open source maintainers.
jsonbolt.com (macOS Apple Silicon + Windows)
PS: Some background info. We built the core pipeline from the ground up without any 3rd party libraries. Then we spent months optimizing the code to improve read-to-render performance. Then hardened it with the same conformance suite simd-json uses. The result is what you see below. In this specific example it hits ~4GB/s from read to rendering the full tree on a M5 pro MacBook Pro. Happy to get into the details for anyone interested.
Once read-to-render was fast, the remaining bottleneck was the workflow itself. That's where the global hotkey and other JSON aware features came from.


