Built 90 browser tools in 115 days. All zero-upload. Am I crazy?

byโ€ข

Hey PH community, solo dev here.

115 days ago I built my first tool โ€” a PDF compressor. One rule:

the user's file never leaves their device. No uploads, ever.

That obsession snowballed. 115 days later, 90 tools across 10 categories:

๐Ÿ”น PDF: compress, merge, convert, extract

๐Ÿ”น Image: 19 tools, AI background remover, crop, resize

Video: compress, GIF maker, screenshot, audio extract

๐Ÿ”น Audio: format conversion, metronome, BPM detector

Text: fancy fonts, Morse code, JSON formatter, diff

๐Ÿ”น Creative: whiteboard, QR codes, pixel art, signature maker

๐Ÿ”น AI: Tarot, Text Adventure, Life Trajectory, Ex-Partner Chat

๐Ÿ”น Self-test: typing speed, reaction time, CPS, aim trainer

Everything runs in-browser via WebAssembly. Zero uploads. Zero accounts. Zero tracking.

People tell me I'm stubborn โ€” "who builds pure client-side tools in 2026? SaaS is the way."

But I believe some tools should just work: open, use, close. No traces left behind.

Site:

Would love your thoughts:

1. Do "use-and-leave" tools still have a place in 2026?

2. If you could request one tool, what would it be? I might build it this week.

3. 115 days in โ€” should I add a paid tier, or keep it all free?

Roast me, request features, tell me I'm wrong. All welcome.

8 views

Add a comment

Replies

Best

not crazy, that constraint is the whole product. we build on-device too (voice, nothing uploaded) and it forces better engineering, you can't paper over a slow model with a server. on the paid tier question: charge for the ones that need real compute (video, AI stuff) and keep the pure client-side utilities free forever, that split matches the trust story you're selling.