I built a free browser-based JSON toolkit for everyday developer tasks
I often need quick JSON utilities while debugging APIs, cleaning payloads, or converting data for spreadsheets, so I put together a simple browser-based toolkit:
It currently includes:
- JSON Formatter
- JSON Validator
- JSON Viewer
- JSON Minifier
- JSON Editor
- JSON to CSV Converter
- CSV to JSON Converter
The tools are designed for quick use without creating an account. They are especially useful when you want to format, inspect, or validate JSON snippets during development.
I am still improving the examples, edge cases, and documentation. Feedback from developers who work with JSON regularly would be useful.
The CSV to JSON converter is the one that always gets me, every time I think I will just do it manually and every time I immediately regret that decision.
Quick question, how are you handling nested JSON structures in the CSV converter? That edge case tends to be where these tools either shine or fall apart.
Great question. I originally kept the converter conservative: CSV rows are converted into an array of flat objects using the header row, because that is what most spreadsheet exports expect.
Your point is exactly the edge case worth supporting, so I added an optional “Nested JSON from headers” mode. so the same CSV can produce nested objects and arrays when needed. Flat output remains the default.
Thanks for calling this out. I also added it to the FAQ/docs so the behavior is explicit.
The probe confirmation approach is actually the more interesting part here.
Most uptime tools treat “down” as a single signal, but in practice the failure mode is often distributional (region + path + timing), not binary.
Curious how you’re handling cases where all probes disagree but degradation is still real (slow partial failure vs full outage).
I think this may have landed on the wrong product thread. JSON Utility Kit is a browser-based JSON/CSV utility, not an uptime or probe monitoring tool.
That said, I agree with your point. If I build a monitoring product later, I would separate full outage, regional disagreement, and slow partial degradation instead of collapsing everything into a single up/down signal.