DEV Community

ToolVerse USA
ToolVerse USA

Posted on

I built 100+ free tools that run entirely in your browser — no sign-up, no uploads

#webdev #javascript #showdev #tools

Hey DEV 👋

I've been building ToolVerse USA — a free tools site with 100+ pages, and I wanted to share it here because half of it is built for developers, and the other half taught me a lot about building for the web.

What's on the site

Money calculators (US-focused) — rent affordability (the 30% rule), salary needed for rent, roommate rent split, mortgage & down payment, debt payoff, car insurance cost, cost of living by state, medical coder salary, and more.

Browser tools — the part DEV will care about:

  • JSON Formatter & Validator (with clear error messages)
  • CSV → JSON converter
  • Base64 encoder/decoder
  • Unit converter
  • Image compressor (JPG/PNG, adjustable quality)
  • Strong password generator (up to 128 chars)
  • Word counter, case converter, date duration calculator
  • SERP preview tool (see your Google title/description before publishing)

The rule I built everything around

Every browser tool runs 100% client-side. Paste your JSON, your CSV, your password inputs, your images — nothing is ever sent to a server. There is no server for these tools at all; the analytics on tool pages never sends input values. Privacy wasn't a feature I added later — it's the architecture.

How it's built

  • Static site hosted on GitHub Pages (plus a small Vercel backend for the main site features)
  • Vanilla JavaScript — no framework for the tools
  • The tool pages are generated: each tool is defined by a small JSON definition + an HTML/JS fragment, and a Node build script renders the final pages, the search index, and the sitemap from a shared shell template. Add a definition, rebuild, and the tool appears in the hub and sitemap automatically
  • PWA with offline support

Repo (public): https://github.com/ToolVerseUSA/ToolVerse
Live site: https://toolverseusa.github.io/ToolVerse/
Tools hub: https://toolverseusa.github.io/ToolVerse/tools/

What I'd love from you

Try breaking the tools 😄 — edge cases in the JSON formatter or the CSV converter, weird units in the converter, huge files in the image compressor. And tell me: which tool should I build next?

Thanks for reading!

Top comments (3)

Collapse
 
toolverse_usa profile image
ToolVerse USA •

Quick index of the most-used tools, if you want to jump straight in 👇

All free, no sign-up — and for the browser tools, your data never leaves your device.

Question for you: which tool should I build next? I'm collecting ideas for the roadmap 👇

Collapse
 
wolf2016 profile image
wolf Valencia •

Shipping 100+ tools as static pages on GitHub Pages, with nothing uploaded anywhere, is a neat way to keep the privacy promise honest. A couple of small things I noticed clicking around (I do QA for a living, so it's habit):

  1. Most page titles get clipped in search results. 32 of the first 40 pages in your sitemap have titles over 60 characters, e.g. the homepage's "Can I Afford This? | Free US Affordability Calculator | ToolVerse" (65). Since the pages share a template, dropping the " | ToolVerse" suffix (or the part after the first pipe) when a title is already long fixes them all at once.
  2. The homepage sets og:title, og:description and a twitter:card, but there's no og:image, so shared links unfurl as a text-only card. One 1200×630 image referenced from the shared head template (og:image + twitter:image, with the card switched to summary_large_image) covers every tool.

If it's handy, I can paste the list of the longest titles in a reply.

Collapse
 
sujalkhatri profile image
Sujal Khatri •

The JSON-definition-driven page generation is the part I'd steal from this — most tools sites end up with 100 hand-copied pages that quietly drift apart, and a Node build script keeping them consistent is the kind of boring engineering that pays off silently. Clear error messages in the JSON formatter is also a genuinely good differentiator; half the formatters out there just say 'invalid JSON' and leave you hunting through line numbers. Since you asked what to build next: a text-diff tool is the most-requested thing on my own similar tool set, and it fits your client-side rule perfectly. Curious — how does the PWA offline support interact with the tool pages being generated at build time?