I built a tool that doesn't use AI (and it's better because of it)

Usman Hyder — Wed, 11 Mar 2026 18:16:37 +0000

Confession: I'm tired of AI.

Is it just me, or does every tool launch in 2026 feel like it's just a wrapper for a prompt?
I keep seeing "AI-Powered tools" that ask me to upload my files to a server, run them through a massive model, and charge me a monthly subscription—all to do something my browser has been able to do natively for years. It feels like we're using a sledgehammer to crack a nut.
I decided to push back against that trend. I built WebPit, a 100% client-side WebP converter. There are no LLMs, no "intelligent" upscaling, and—most importantly—no servers involved. Until a problem is simple and can be solved easily without AI there is no need for it to have AI. Dont get me wrong what AI is now capable of doing has made so many things easier. Write a prompt and you have a working app, write a prompt and generate images and videos. AI powered tools like antigravity, kiro, Claude code etc have made development much more accessible. But as I said not every small tool need it.

Why I chose logic over "intelligence"
As a web developer, I needed a fast way to convert and optimize images for my projects. I didn't need an AI to guess how to compress my PNG; I needed a deterministic algorithm that respected my privacy and didn't waste my time.
Here is why building a "simple" tool turned out to be the smartest move:
1. Privacy that doesn't ask for permission
By avoiding AI APIs, WebPit doesn't need to "phone home." The conversion happens entirely in your browser's RAM. Your images never leave your machine. In an era where data is constantly being scraped and stored, keeping your data local shouldn't be a premium feature—it should be the default.

2. Speed > Hype
We've traded "instant" for "intelligent." Most AI tools have a "thinking" state or a loading spinner while they query a server. WebPit has an "instant" state. Because it leverages the client's hardware (via the Canvas API and JavaScript), it's limited only by your CPU, not by an API queue or rate limits.

3. No black boxes
When you use an AI tool, you rarely know what's happening to your file behind the scenes. With WebPit, the logic is transparent. It's code, not magic. It does exactly what it says on the tin, nothing more.

Building for the "Boring" Era
My goal isn't to chase the latest LLM trend. It's to build high-performance tools that solve real problems with the least amount of friction possible.
WebPit is my first tool that I shipped for myself, not for a client. It's a 100% private, browser-based utility that does one thing perfectly. Sometimes, the best innovation is knowing what not to add.

What do you think?
Are we reaching a point where "No-AI" is actually a selling point? I'd love to hear from other devs who are focusing on local-first, high-performance utilities rather than wrapping APIs.

Check out the tool here: webpit.site

I built a 100% Client-Side WebP Converter because I’m tired of uploading my data

Usman Hyder — Sat, 07 Mar 2026 13:25:55 +0000

The Problem with Modern Image Converters
We’ve all been there: You need a quick WebP for a blog post or a project. You Google "PNG to WebP," click the first link, and then... you wait.

You wait for the upload. You wait for the server to process it. And most importantly, you give your data away. Most free tools are "black boxes"—you have no idea if your images are being stored or used to train models.

Introducing WebPit
I built WebPit to fix this. It’s a minimalist, high-speed utility that does one thing: converts your images to WebP without them ever leaving your browser.
Why Client-Side?
By moving the conversion engine to the user’s browser (using modern JS), we get three massive wins:

Privacy: Your images stay on your machine. Period.
Speed: No upload/download bottlenecks. It’s as fast as your local CPU.
Efficiency: It doesn't cost me (the dev) massive server fees, so it stays free for you.

The Tech Stack

Frontend: Next.js & Vercel
Core: Client-side canvas rendering for instant conversion.
Ethics: No signups, no tracking, no bloat.

Check it out here: webpit.site

Forem: Usman Hyder

I built a tool that doesn't use AI (and it's better because of it)

I built a 100% Client-Side WebP Converter because I’m tired of uploading my data