DEV Community

Ahmed Elsaka
Ahmed Elsaka

Posted on

I built 562 free browser-only tools — here's what I learned

A few weeks ago I set out to build a comprehensive collection of free browser-based tools. The result: alltools.app — 562 tools
across 22 categories.

The core rule: Everything runs client-side.
No uploads. No accounts. No limits. Ever.

The stack

  • Astro 6 — static site generation
  • Cloudflare Pages — free hosting, edge CDN
  • Tailwind CSS v4 — styling
  • pdf-lib + PDF.js — PDF processing
  • Canvas API — image processing
  • Web Crypto API — security tools
  • MediaRecorder API — video/audio tools

What surprised me

562 tools is achievable client-side.
I expected to hit walls — video compression, PDF manipulation, image processing. But browser APIs have matured enormously.
ffmpeg.wasm, pdf-lib, and the Canvas API handle more than I expected.

Static + Edge = zero infrastructure cost.
685 static pages deployed on Cloudflare Pages.
Zero server costs. Zero maintenance.

SEO at scale is a different problem.
562 tool pages means 562 opportunities for long-tail keywords. But it also means 562 pages that need quality content.

The philosophy

Most "free" online tools upload your files to remote servers. Your resume, invoices, photos, passwords — they all pass through infrastructure you don't control.

We built an architecture where that's impossible. Files never leave your browser.

What's next

  • Chrome Extension (built, submitting to Store)
  • Arabic translation (MENA)
  • 8 new high-value tools.

Happy to answer questions about the architecture, the Astro setup, or client-side processing at this scale.

alltools.app

Top comments (0)