DEV Community

Ammar Ahmed Kiani
Ammar Ahmed Kiani

Posted on

What I Learned Building 1,700+ Free Browser-Based Tools

I run InovoTools, a site with over 1,700 free tools: calculators, unit converters, PDF tools, text utilities and developer tools like a JSON formatter and a JWT decoder. No accounts and no paywalls.

Building it taught me a few things I wish I'd known at the start. Here are the five that mattered most, in case you're building something similar.

1. Do the work in the browser

Most tools on the site run entirely client-side. That one decision paid off three ways:

  • Privacy. A PDF merger that uploads contracts and bank statements to a server is a liability. When Merge PDF copies pages inside the browser tab, there's nothing to store, secure or delete.
  • Cost. A tool that runs on the user's device costs nothing per use. With thousands of pages, that matters more than almost anything else.
  • Speed. No upload, no queue and no round trip. Results update as you type.

Even things that sound like server work are fine in the browser. The QR code generator runs Reed-Solomon error correction and the standard QR masking in JavaScript, then exports an SVG.

2. Thousands of pages change your hosting maths

This one hurt. The tool pages are prerendered, and on Vercel every CDN cache miss on a prerendered page counts as ISR reads, billed in 8 KB units. That sounds tiny until you look at a big file: a single uncached fetch of a 9.2 MB sitemap.xml costs around 1,178 units on its own.

Crawlers, cache misses and a large sitemap added up fast. The site went past the monthly ISR allowance, and Vercel paused the projects with a 402 until it reset.

The fix was moving InovoTools to a VPS running Docker, deployed automatically from GitHub. The lessons:

  • Before you add thousands of pages or large static files, work out what each cache miss costs on your host.
  • Split big sitemaps into a sitemap index so crawlers fetch smaller files.

3. Show the working on every page

Every tool page lists the formula, a worked example and the limits of the result. The percentage calculator, for example, shows result = value × percent ÷ 100 and walks through 15% of 80.

That does two jobs. People can check an answer before they rely on it, and each page has real content instead of being a thin wrapper around an input box. When you have thousands of pages built on similar layouts, that difference matters to search engines.

4. Translations need their own words

Tool pages are available in 10 languages. Early on, Google flagged many translated pages as duplicates and picked its own canonical, because they were mostly the same template with translated labels. Adding tool-specific copy to each translated page fixed it.

5. Release pages in batches

Instead of publishing every page on day one, new tool pages go live in weekly batches. Indexing stays steady, problems show up while they're still small, and Google isn't hit with a sudden flood of new URLs.

Try it

If you need a quick calculator, converter or PDF tool, everything is free at inovotools.com. And if there's a tool you wish existed, tell me in the comments. I'm always looking for the next one to build.

Top comments (0)