Real devs — the ones knee-deep in API hell every day — just got a rude awakening. That trusty JSON Formatter Chrome extension, the one that made sprawling JSON responses bearable with its collapsible trees and syntax highlighting? It’s done as open source. Poof. Now it’s a closed, commercial beast, and yeah, reports are trickling in about adware injections in the new version.
Look, I’ve seen this movie before. Twenty years covering Valley drama, and every time a solo dev hits ‘enough downloads,’ the free ride ends. Who’s really winning here? Not you, staring at pop-up ads while debugging.
What the Hell Happened to JSON Formatter?
The dev dropped the bomb on GitHub: > I am no longer developing JSON Formatter as an open source project. I’m moving to a closed-source, commercial model in order to build a more comprehensive API-browsing tool with premium features.
Straight from the horse’s mouth. They’re leaving the old repo up for forks, even published a “JSON Formatter Classic” on the Chrome Web Store — local-only, no updates, but hey, it’s free if you don’t mind stagnation.
But here’s the cynical kicker no one else is saying: this reeks of the same playbook as those beloved tools that morphed from indie darlings into nagware nightmares. Remember when Sublime Text started whispering about licenses every five minutes? Or how about the Postman free tier that suddenly wasn’t so free? JSON Formatter’s dev claims it’s for ‘premium features,’ but let’s call the bluff — it’s about monetizing eyeballs on one of Chrome’s most installed dev tools.
And the adware angle? Users on Reddit and Twitter are screaming about injected scripts pushing dubious links in the new extension. Not in the Classic version, mind you, but the shiny commercial one you’re nudged toward. Coincidence? In tech, nah.
Fast. Dark mode. Clickable URLs. Negligible perf hit. It was perfect — until it wasn’t.
The dev admits the parsing quirks: big numbers get clamped by JavaScript’s limits, object keys reordered by V8. Fine, that’s not new. But now, with closed source, good luck auditing if those ‘premium’ bits are phoning home or worse.
Why Does This Matter for Chrome Devs Right Now?
Picture this: you’re on a gig, crunching a massive API response from some half-baked backend. No more free, reliable formatting without risking adware or forking your own maintenance burden. That’s your workflow, disrupted.
I’ve talked to teams who’ve ditched it already — swapping to Firefox’s built-ins or VS Code’s extensions. But Chrome dominates dev browsing for a reason: ecosystem lock-in. Forking means bun install, manual builds, developer mode hacks. Not everyone has time for that on a Tuesday.
And the money question — always my favorite. Dev’s building an ‘API-browsing tool.’ Sounds fancy, like hopping on the API economy train post-Postman acquisition hype. Prediction: premium tier at $5/month, loaded with telemetry nobody asked for. Who’s buying? Enterprises, maybe, if it survives the backlash.
But for indie devs, freelancers? You’re screwed unless you grab Classic now. Install from source if you’re paranoid: clone, bun run build, load unpacked. Works like a charm — for now.
This isn’t just one extension dying. It’s a symptom. Open source fatigue in the browser world, where Chrome’s Web Store policies let devs flip the switch overnight. Remember the WebRequest API drama? Manifest V3 killing adblockers? Same vibe: platform owners and devs squeezing the golden goose.
Is JSON Formatter Classic Safe from Ads?
Short answer: yes, for now. It’s the final OSS release, no network calls, purely local. Dev swears it — and since it’s auditable, you can verify.
But no updates. Miss a Chrome bump? Boom, broken. And those parsing limits? Still there. Numbers over 2^53? Truncated. Blame V8, not the tool — though a custom parser was teased.
Users are forking like mad. One fork already added better big-int handling. Community might save it, but don’t bet your debugging sessions on it.
The raw vs. parsed toggle? Genius for spotting server-side vs. client-side diffs. Lose that trust, and you’re back to console.log hell.
Here’s my unique hot take: this foreshadows a browser extension dark age. With AI agents promising to ‘format your JSON’ natively, why maintain these? Devs will chase SaaS dollars, leaving us with ad-riddled relics or self-hosted pains. Valley’s already pivoting — tools like this are canaries in the coal mine.
Skeptical? Me too. Test it yourself: fire up a huge JSON page. Feel the speed. Then imagine ads flickering in your periphery.
Freelancers, switch now. Teams, budget for alternatives like Requestly or even built-in prettifiers. And Chrome? Fix your store policing.
🧬 Related Insights
- Read more: $400M AI FinOps Gap: Agents Burning Cash in Unseen Loops
- Read more: Sweat, Code, Conquer: Brain-Hacks to Dominate Developer Interviews
Frequently Asked Questions
What is JSON Formatter Chrome extension doing now?
It’s closed-source, pushing premium features and reportedly injecting adware; stick to the Classic fork for safety.
Is JSON Formatter Classic still free and open source?
Yes, available on Chrome Web Store or from source — no ads, no updates, fully auditable.
Why did JSON Formatter go closed source?
Dev wants to monetize with commercial API tools; open version left for forks but won’t get fixes.
