I built 80+ free browser tools — no signup, no ads, no paywalls (here's what I learned)

Mohammad Ameer — Sun, 02 Aug 2026 18:10:35 +0000

A few months ago I got frustrated.

I needed to compress a PDF quickly. Found a tool online — it asked me to create an account first. Found another — it had so many ads the actual button was invisible. Found a third — it uploaded my file to their servers and I had no idea what happened to it after.

I thought: this shouldn't be this hard.

So I built EazyStudio — a suite of 80+ browser-based tools where everything runs 100% in your browser, no signup, no intrusive ads, no files ever leaving your device.

What's inside

Here's a snapshot of what's available:

PDF tools

Compress, merge, split, rotate PDFs
PDF to Word, Excel, JPG and back
Add watermarks, protect with passwords

Image tools

Background remover (runs locally in browser)
Image compressor, resizer, converter
AI image upscaler
Color palette extractor, color picker

Developer utilities

JSON formatter/validator
Base64 encode/decode
URL encoder, HTML entity converter
Regex tester
JWT decoder
API tester (Postman-lite)
CSS gradient generator, box shadow generator

Finance & math

EMI calculator, SIP calculator
GST calculator, compound interest, tip splitter
Unit converters (length, weight, temperature, data)

And more

QR code generator
Password generator
Text tools (word counter, case converter, lorem ipsum)
Device preview tool

The technical approach: browser-first

The biggest design decision was: nothing gets uploaded to a server.

For PDF operations I use PDF.js and pdf-lib running in the browser. For image tools it's canvas + WebAssembly (WASM) modules. For background removal I'm using a WASM-based segmentation model that loads client-side.

This has three benefits:

Speed — no upload round-trip, works on large files instantly
Privacy — your files never touch my server
Cost — zero storage, zero egress bandwidth

The downside: WASM modules add initial load time. I worked around this with lazy-loading — the WASM only loads when you first use that specific tool.

What I learned building this

1. People hate signups more than I expected

I knew signups were friction, but the feedback I've gotten since launching confirms people actively avoid tools that require them, even for completely free tiers.

2. "Free" needs to actually mean free

Ad-supported is fine. But hiding features behind a paywall while calling the product "free" breeds distrust fast. Every single tool on EazyStudio is fully functional with no locked features.

3. Performance is a feature

A tool that takes 3 seconds to respond feels broken, even if it works. I spent significant time optimizing load times — lazy imports, service workers for caching, pre-compiling WASM.

4. Solo building forces good scope discipline

When you're a one-person team, you can't build everything. I deliberately kept each tool minimal — do one thing, do it well, no feature creep.

What's next

More AI-powered tools (currently have background remover + upscaler)
Better mobile experience for image tools
A browser extension for quick access

If you've built something similar or have thoughts on browser-based tooling I'd love to hear it. And if you want to try it out: eazystudio.com

What's your go-to strategy for getting developers to discover new utilities?

I built 80+ free browser-based tools — here's why "zero uploads" changes everything

Mohammad Ameer — Fri, 08 May 2026 01:02:48 +0000

A while back I got frustrated with online tools that upload your files to a server, make you sign up, and then quietly keep your data. So I built TRE — a collection of 80+ tools that run entirely in your browser using JavaScript. Your files never leave your device.

Why "zero uploads" actually matters

When you drag a photo into an online image compressor, most tools upload it to their server, compress it there, then send it back. That means a third party now has a copy of your file. For personal photos, business documents, invoices, or anything sensitive — that's a real risk most people don't think about.

With TRE, everything runs client-side. The compression, conversion, PDF merging — all of it happens locally in your browser tab. Nothing touches a server.

What's inside TRE

🖼️ Image Tools (11 tools)

Image Compressor — reduce file size up to 80% in-browser
Image Resizer, Cropper, Format Changer
AI Image Upscaler, Background Remover
Color Palette Generator, SVG↔PNG Converter
Favicon Generator, QR Code Generator, Watermark Tool

🎵 Audio Tools

Audio Compressor, Format Changer, Audio Crop
Audio Sprite Generator (great for game dev!)

📄 Document Tools

PDF Compressor, Merger & Splitter
Word↔PDF Converter, Image to PDF, PDF to Image
Resume Builder, Invoice Maker

💻 Developer Tools

JSON Viewer, Base64 Encoder/Decoder
Code Minifier, JWT Decoder, Meta Tags Generator
CSS Grid Generator, JS/CSS Beautifier

💰 Finance & Calculators

EMI Calculator, GST Calculator, SIP Calculator
Currency Converter, Income Tax Calculator
Word Counter, BMI Calculator, Unit Converter

🎮 Game Dev Tools

Bitmap Font Generator, Texture Packer
Physics Editor, PixiJS Text Style Editor
Flow Diagram Builder, Multi Device Preview

The tech stack

Vanilla JS with no heavy frameworks — this keeps pages fast and lightweight. A few specialized libraries power specific tools: browser-image-compression for images, pdf-lib for PDF operations, and ffmpeg.wasm for audio/video work (all running in-browser via WebAssembly).

What I learned building this

Crawl budget is real. When I submitted my sitemap with 99 URLs at once, Google's crawl queue backed up and most pages went into "Discovered – currently not indexed." Don't bulk-submit sitemaps — let Google find pages gradually.

Client-side processing has limits. Very large files (100MB+ videos) can freeze the browser tab. I had to implement chunked processing and WebWorkers to handle heavy operations without blocking the UI.

Users care about privacy more than they say. The "zero uploads" messaging drove more word-of-mouth sharing than any feature I built. People share tools they trust.

What's next

I'm working on a video editor, more AI tools, and a browser extension that lets you use TRE tools directly from your right-click menu on any image or file.

Would love feedback from the dev community — what tools are missing? What would make you actually use (and share) a tool like this?

👉 Try TRE free at tre.dev — no account needed.

DEV Community: Mohammad Ameer

I built 80+ free browser tools — no signup, no ads, no paywalls (here's what I learned)

What's inside

The technical approach: browser-first

What I learned building this

What's next

I built 80+ free browser-based tools — here's why "zero uploads" changes everything

Why "zero uploads" actually matters

What's inside TRE

The tech stack

What I learned building this

What's next