Alternatives
Products that do what JSON Dive – A better online JSON viewer does
We've all been there: you have some JSON data you need to make sense of, so you Google "json formatter" and end up at a site ridden with ads. I used to look at at lot of JSON (mostly log data) for $oldjob, so I set out to build something better. I know there are a lot of tools in this space, but I've put a lot of love into JSON Dive: things like Vim keyboard shortcuts to navigate, dark mode, timestamp/image previews, and multi-file-format-support (XML-in-JSON was a format I dealt with in the context of LLMs/tool calls). I've also made an effort to ensure it can handle large files,…
- 1JA
Hey, Hacker News! Today I'm proud to release jless, a command-line JSON viewer. jless provides a JSON viewing experience similar to what you see in a browser's network tab in the developer console, but from the comfort of your terminal, with a whole suite of vim-inspired key bindings to easily manipulate your view of the data and full-text regex search. I'm sure many of you have some piped together some combination of cat, jq and less before; hopefully jless can replace that usage (hence the name). It supports newline delimited JSON too, so it can handle any output from jq. I built jless to…
2022 · pauljuliusmartinez.github.io
- 2
- 3
- 4JA
2020 · github.com
- 5AS
2013 · jsonblob.com
- 6
- 7
- 8SS
Hi HN, I’m building SEE (Semantic Entropy Encoding): a searchable compression format for JSON/NDJSON. Goal: reduce the “data tax” (storage/egress) and “CPU tax” (decompress/parse) by keeping JSON searchable while compressed, with page-level random access. I just published a proof-first evaluation release: Offline DEMO ZIP (~10 min): prints compression ratios + skip rates + lookup latency (p50/p95/p99) DD pack: audit/repro evidence (decode mismatch=0, extended mismatch=0, audit PASS) Latest release:…
Feb 2026 · gitlab.com
- 9
- 10JM
2012 · github.com
- 11
- 12IM
Hey NN, I've create a tool that allows you to easily manipulate and transform json data. After looking round for something to allow me to perform json to json transformations I couldn't find any easy to use tools or libraries that offered this sort of functionality without requiring learning obscure syntax adding unnecessary complexity to my work or the alternative being manual changes often resulting in lots of errors or bugs. This is why I built JSON Transformer in the hope it will make these sort of tasks as simple as they should be. Would love to get your thoughts and feedback you have…
2024 · jsontransformer.com
- 13JD
2015 · json-diff.com
- 14MO
2020 · jsonformatter.live
- 15QI
2017 · quicktype.io
- 16CL
2018 · github.com
- 17TA
TYON (typed object notation) is my attempt to address the main frustrations I have with JSON. 1. Key repetition - you can specify the key names once at the start of a list or map, instead of on each object separately. 2. Escaping strings - everything in a string is literal except for " which is escaped as "". This makes writing regexes and multiline text easier without introducing a bunch of different string styles or excess escaping, which I am not a fan of. 3. While not nearly as important as the first two to me, I did reduce symbol clutter when possible. Files are implicitly maps, keys…
2023 · github.com
- 18AE
2019 · github.com
- 19BJ
Just a simple tool I hacked together last night. I wanted to paste a bunch of JSON for reference in an IRC channel, but the JSON that I wanted to paste was not formatted. I didn't quickly find a pastebin that formatted JSON for me so I just made one. It's probably so simple that it's borderline useless, but here it is! http://jsonifier.com/ example output: http://jsonifier.com/paste/4e3f84b46f3b792dde000000
2011
- 20JT
2019 · github.com
- 21JA
2019 · github.com
- 22JN
Hi HN! Happy to share that jist can now search JSON 17x faster than jq for a provided input (string or a file). The major change is using the bleeding edge simdjson parser as the preferred way of parsing and querying the input. Since simdjson can only work on files up to 4.2GB, jist falls back to its earlier implementation of scanning through input in chunks of 1MB which means it can still query files of virtually infinite size 3x faster than jq ever could while using ~10MB of memory. The next major feature will be summarizing input JSON into a schema - and it will do this by scanning the…
2025 · github.com
- 23JA
2016 · github.com
- 24JJ
Mar 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →