DEV Community

mengstone
mengstone

Posted on

37 free browser tools, no login - what I learned building them

37 free browser tools, no login 鈥?what I learned building them

I have been building small browser tools instead of another SaaS. The rule is simple: no login, no upload, no server-side processing. Open the page, do the task, close it.

The collection is here: https://www.mengstone.com/tools/

What is in it

  • Images: compress (batch + ZIP + target KB), convert, favicon, QR, images to PDF, PDF merge, PDF split
  • Documents: invoice / quote / receipt, service agreement, contract save
  • Text/dev: word count, case, markdown, JSON, CSV, base64-ish encoders, URL, hash, color, percentage
  • Finance: mortgage, auto loan, refinance, credit card payoff, savings goal, compound interest
  • Game launch: press kit, Steam capsule, privacy, copyright checks

Why no-login tools

  1. Search intent is explicit. People search the task, not the brand.
  2. Zero marginal cost. Canvas, PDF-lib, JSZip and Web Crypto run in the browser.
  3. No account friction. The tool is usable in one click.

What I got wrong

  • Page count is not distribution. I have 37 tools and still almost no traffic.
  • A tool without an ad layer earns nothing, even if it is useful.
  • Long-tail pages matter more than another generic utility. "Mortgage with PMI" is a better page than "mortgage calculator #38".

What I would do next

  • Add the ad layer (AdSense/Ezoic) before adding more tools.
  • Build long-tail pages around high-intent finance queries.
  • Keep everything static and fast.

Honest status

No orders, no meaningful traffic, no ad revenue yet. The tools are real and the contracts pass; the business is not proven.

If you want to try them: https://www.mengstone.com/tools/

Top comments (1)

Collapse
 
onelifevibe profile image
OneLifeVibe •

The honest status section is the most useful part — 37 working tools and almost no traffic is a clear reminder that page count is not distribution. Your long-tail point lands well too; a specific page like mortgage with PMI answers a search people actually type, where a generic calculator does not. If you add the ad layer first, will you keep the tools fully client-side, or does that change how you think about the next batch?