260 free tools, one URL, no signup — building Toolenza

Most "free online tools" sites lie about three things: how free they are, how online they are, and how many tools they actually have. Toolenza tries to be honest on all three. This is the why.

The three lies

Lie one: "free." You merge a PDF on Smallpdf, get 2 documents in, and hit a paywall. Calling it free is technically correct; it's also annoying.

Lie two: "online." You compress an image on most "online image compressor" sites and your file gets uploaded to a server, compressed there, and downloaded back. That's not really "online" in the way a developer would mean — it's "upload-and-process." For sensitive files (medical records, contracts, anything with a face in it) that should worry you.

Lie three: "all the tools." Multi-tool sites usually have 20–40 tools and pad the directory with affiliate-flavoured ad space. Tools you'll actually open are maybe a third of that.

We built Toolenza to be honestly free, honestly browser-based, and honestly comprehensive. 260 tools, one URL pattern, one keyboard shortcut.

The shape

Every tool lives at /tools/{slug}. Press ⌘K (or Ctrl-K on Linux/Windows) anywhere on the site, type three letters of what you want, hit enter. Recently used tools float to the top. That's the whole UX.

About 90% of the tools run entirely in your browser. JSON formatter, regex tester, JWT decoder, base64 encoder, hash generator, all the calculators, sticky notes, todo lists, color picker, image resizer, PDF merger / splitter / rotator / cropper — every one runs without uploading. The exceptions are clearly labelled and only used when there's no way to do the work client-side: PDF compress (needs Ghostscript), PDF protect/unlock (needs qpdf), AI text (calls OpenAI), live currency rates (calls an FX API), geocoding (calls Google/Mapbox).

The unsexy infrastructure

The interesting product decisions weren't on the tool list — they were the infrastructure choices that made the tool list possible:

• One config file, every tool. Adding a new tool to Toolenza means adding a slug to config/toolenza.php and writing a Blade view. No DB migration, no admin UI, no deploy ceremony. A slug becomes a fully-indexed, OG-cardable, FAQ-rich-result-eligible page with one PR.
• SEO is a first-class output, not a retrofit. Every tool generates a dynamic OG image (/og/{slug}.png), a comparison page against the biggest competitor (/tools/{slug}/vs/{competitor}), an FAQ JSON-LD block, a HowTo schema block, and a row in sitemap.xml. Programmatic SEO at 260 pages is only worth doing if it costs zero extra effort per new tool, and that means baking it into the catalog format.
• Personas, not just tools. A free-tools site indexed only by tool name is a directory. Indexed by user role (/for/developer, /for/teacher, /for/lawyer, etc.) it becomes a story. Eighteen personas, each with a hand-written intro and a curated tool list, do more for new-user retention than another 50 tools would.
• Embed early. Every tool also lives at /embed/{slug}, a minimal layout designed to be iframed on third-party sites. Each embed is one backlink. The embed builder shipped on day one because retroactively adding embeds to a 260-tool site is roughly five hundred times harder than building it in from day zero.

The honest cost model

Running 260 free tools that don't upload is cheap. Most tools never touch our infrastructure — they execute as JavaScript in your browser. The actual cost centres are:

• The few tools that need a server (PDF compress / protect / unlock) — bounded by file size and per-IP throttling.
• The AI tools that hit OpenAI — gated by a daily quota per IP on the free tier.
• The currency / geocoder endpoints — externally rate-limited, cached aggressively.
• Static hosting + CDN — fractions of a cent per visitor at our current scale.

This is why Toolenza can stay genuinely free. The unit economics don't require a paywall on tool use. There will be a Pro tier eventually, but it'll buy you sync, sharing, retention, an @handle profile page — not "more uses." The math just works.

What's next

The catalog is feature-complete for v1. The next year is about:

1. Distribution. Embeds on third-party blogs. Aggressive comparison-page SEO. Persona-targeted Reddit + Indie Hackers + Hacker News posts.
2. A handful of higher-effort tools. Word↔PDF and Excel↔PDF conversions, which need a third-party rendering service. Audio waveform editing. Live collaboration on sticky-notes / todos.
3. An API tier. The browser-only tools that have a natural server-side equivalent (currency, geo, JSON-validate, QR generation) are already wired up at /api/v1/*. Developers page here if you want to plug them into your own apps.

If you've got a tool you want and we don't have, the feedback widget in the bottom-right is the fastest way to tell us. Read every message; reply to most.

Thanks for being here on day one.