Most bookmarked dev-tool sites get slower and more ad-heavy over time, or start gating basic features behind a signup. Quietbench is a small suite of the utilities I reach for most often - JSON formatter, regex tester, cron builder, WCAG contrast checker, and API request tester - built to stay fast, free, and signup-free. Everything runs entirely client-side in your browser. No accounts, no data sent to a server, no ads. Built with React, Vite, and TypeScript, deployed on Cloudflare Pages.
No reviews yetBe the first to leave a review for Quietbench
Maker
📌
Hey everyone 👋
I built Quietbench because I had a handful of bookmarked utility sites - JSON formatter, regex tester, that kind of thing - that kept getting slower, more ad-heavy, or started gating basic features behind a signup over time.
So I built my own small suite: JSON formatter with a tree view, a regex tester with live highlighting and plain-English explanations, a cron builder that shows your next 5 run times, a WCAG contrast checker, and a lightweight API request tester.
Everything runs entirely in the browser - no accounts, no data sent anywhere, no ads. Built with React, Vite, and TypeScript, deployed on Cloudflare Pages.
This is very much a solo side project, and I'd genuinely love feedback - especially anything that feels broken, confusing, or missing. What utility would you want added next?
Report
💡 Bright idea
With everything running client-side, are there any size limits I should expect on the API request tester, or does it fall back gracefully when a response gets too large to render smoothly in the browser?
Report
Maker
@buse1342588 Good question! Right now there's no hard-coded size limit - it renders whatever the browser can handle in a /JSON view. For very large responses (multi-MB), you'll start to feel some lag since it's all client-side with no virtualization yet. That's actually a good callout for a "next utility" improvement — I could add response size warnings or a "download instead of render" fallback for huge payloads. Appreciate you flagging it 🙏
Report
the all-client-side approach is genuinely nice—no waiting on a server roundtrip just to format some JSON, and nothing leaks anywhere. love that the regex tester shows matches in real time as you type.
Report
Maker
@sebahatyen41239 Thank you! That was the whole point of building it this way - wanted something I could paste real API keys/tokens into for testing without worrying about where the data goes. Glad it's landing well 🙌
Report
the all-client-side approach is a really thoughtful choice, especially for tools like these where you don't want your test data leaving the machine. love seeing utility sites that respect that.
Report
Maker
@makbulemest Exactly the reasoning - most online JSON/regex tools send your data through a server, which felt wrong for anything with real credentials or PII in it. Thanks for noticing!
With everything running client-side, are there any size limits I should expect on the API request tester, or does it fall back gracefully when a response gets too large to render smoothly in the browser?
@buse1342588 Good question! Right now there's no hard-coded size limit - it renders whatever the browser can handle in a /JSON view. For very large responses (multi-MB), you'll start to feel some lag since it's all client-side with no virtualization yet. That's actually a good callout for a "next utility" improvement — I could add response size warnings or a "download instead of render" fallback for huge payloads. Appreciate you flagging it 🙏
the all-client-side approach is genuinely nice—no waiting on a server roundtrip just to format some JSON, and nothing leaks anywhere. love that the regex tester shows matches in real time as you type.
@sebahatyen41239 Thank you! That was the whole point of building it this way - wanted something I could paste real API keys/tokens into for testing without worrying about where the data goes. Glad it's landing well 🙌
the all-client-side approach is a really thoughtful choice, especially for tools like these where you don't want your test data leaving the machine. love seeing utility sites that respect that.
@makbulemest Exactly the reasoning - most online JSON/regex tools send your data through a server, which felt wrong for anything with real credentials or PII in it. Thanks for noticing!