DEV Community

Cover image for Why I finally stopped using random JSON formatters and built my own (client-side only)
User. Me
User. Me

Posted on

Why I finally stopped using random JSON formatters and built my own (client-side only)

Be honest—how many times a week do you just Google "JSON formatter" or "MD5 hash"? For me, it's practically a daily habit. We usually just click the first link, paste our stuff, get what we need, and move on.

But recently, I had a wake-up call. I was debugging a messy API integration and copied a massive JSON payload straight from our production environment into a random online formatter. About two seconds after I hit paste, I froze.

Wait... did that payload have user emails in it? Did I really just send live production data to a random third-party server?

It suddenly hit me how sketchy most of these top-ranking utility sites actually are. They’re complete black boxes. For dummy text, who cares. But when we’re working with real API responses, database dumps, or proprietary strings, uploading that data to an unknown server is a massive security risk.

Plus, it's getting harder to even use them. You have to dodge five different auto-playing ads just to find the "format" button, and half of them are now hiding basic features behind sign-up walls.

I was over it. So, I decided to build my own.

The Rule: Zero Server Uploads
I wanted a set of tools where privacy wasn't just a privacy policy, but an architectural guarantee. I built a JSON Formatter & Validator and an MD5 Hash Generator with one strict rule: everything had to run completely client-side.

The JSON Formatter:
I set it up so the JavaScript processes the data directly inside your browser tab. Because it makes zero API calls to format or validate your code, you can paste API keys, private tokens, or PII without stressing about it getting saved to someone's server logs. As a bonus, having no network latency means the syntax validation is actually instant—if you miss a trailing comma, it tells you immediately.

The MD5 Generator:
Generating a hash shouldn't require a network request. Whether you need a quick hash for caching logic or verifying file integrity, my tool calculates the checksum locally as you type. It just works, instantly.

Falling down the rabbit hole...
Once I had the local-processing architecture figured out, I kind of couldn't stop. I realized there were dozens of other tools I was tired of hunting down every week.

What started as a simple JSON tool quickly snowballed into a "Swiss Army Knife" for developers. I expanded the site to include over 30 different utilities, including:

Base64 Encoding/Decoding (that actually handles UTF-8 emojis properly)

URL Encoders and Parsers

HTML, CSS, and JS Minifiers

Client-side PDF tools (like Image to PDF and a PDF Merger that processes your files locally)

Even some everyday calculators (ROI, Compound Interest, BMI)

Try it out (Seriously: no ads, no sign-ups)
I originally built these tools to fix my own daily workflow, but I've opened the whole suite up for the community. There are no paywalls, no annoying ads, and absolutely no accounts required.

If you are also a little paranoid about where your data goes when you hit "format," you can bookmark the full suite of client-side tools here: https://www.cricblink.com/.

I’d love to hear what you guys think. What is the one small developer utility you find yourself Googling constantly? Let me know in the comments and I'll try to build it next!

Top comments (0)