FracturedJson
Shares rank 2 of 7 code formatters by recommenders
Formats JSON in a middle ground between sparse pretty printing and compact output, keeping it readable and short. Critics say some layouts look worse and it requires .NET.
Formats JSON in a middle ground between sparse pretty printing and compact output, keeping it readable and short. Critics say some layouts look worse and it requires .NET.
20 people gave an opinion
- recommend it
- 18
- criticize it
- 2
- approval share
- 90%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 18 people recommend itNeeds 10 or more, met.
- 9 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Readable middle ground between sparse and compact
“the middle ground between too-sparse pretty printing, and too-compact non-pretty printing”
Comment from 2 Jan 2026 in “FracturedJson” “This is great! The more human-readable, the better!”
Comment from 2 Jan 2026 in “FracturedJson” Reduces file height for easier viewing
“if something can reduce the height of the file thats welcome”
Comment from 2 Jan 2026 in “FracturedJson” “need a quick and concise visualization without the ability (or time) to add substantial code”
Comment from 2 Jan 2026 in “FracturedJson” Could suit editors and extensions
“I could see FracturedJson being great for a browser extension or preview extension in IDE”
Comment from 2 Jan 2026 in “FracturedJson” “Let's implement this formatting in all code editors and replace YAML with it”
Comment from 2 Jan 2026 in “FracturedJson”
What people warn about
Each mark is one comment
Requires a .NET runtime to install
“I don't think I want this enough to install .NET to get it, so that's that.”
Comment from 2 Jan 2026 in “FracturedJson” “You must install a valid .NET runtime”
Comment from 2 Jan 2026 in “FracturedJson”
Other code formatters people recommend
The four most recommended other code formatters, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 7 code formatters, rankedWhat people said
17 of the 22 comments that mention it, newest first. Each links to the original comment.
“I much prefer fracjson[0] pretty printing to jq”
“The NUL thing can be configured away if needed, but requires a conscious decision to do so.”
“this tool also looks super useful, I spend so much time at work looking at json logs that this will surely come in handy”
“I could see FracturedJson being great for a browser extension or preview extension in IDE”
“I don't think I want this enough to install .NET to get it, so that's that.”
“need a quick and concise visualization without the ability (or time) to add substantial code”
“Let's implement this formatting in all code editors and replace YAML with it”
“if something can reduce the height of the file thats welcome”
“the attack-plans example IMO looks worse with this formatting”
“the middle ground between too-sparse pretty printing, and too-compact non-pretty printing”
“this would be a nice formatting option when doing local dev to prettify it without full decomposition”
“This is great! The more human-readable, the better!”
“You must install a valid .NET runtime”
“Now integrate this into every JSON library and tool so I get to see it's output more often”
“The one example I didn't like is the expanded one where it expanded all but 1 of the elements.”
“This is pretty cool, but I hope it isn't used for human-readable config files.”
“thanks for supporting comments”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.