Free WebP to JPG Converter
Convert image folders online, up to 1,000 images per batch
Over the past few weeks, I shipped Free WebP to JPG Converter.
At first glance it looks like another image converter, but the real motivation wasn't "convert WebP to JPG." It was fixing a workflow that I kept running into.
Most online converters are optimized for one or two images. As soon as you have a project folder with hundreds of assets, the experience starts falling apart. Batch limits, repeated uploads, long waits, and sometimes the browser simply gives up.
I wanted something that could handle real workloads without requiring users to install desktop software.
Building the backend
I chose Go because concurrency is one of its biggest strengths.
Instead of treating every upload as a blocking request, large conversion jobs are processed in background goroutines. The API immediately returns a job ID, and the frontend subscribes to progress updates using Server-Sent Events (SSE). That lets users see each file being processed in real time without the complexity of WebSockets.
Another design decision was to avoid keeping large uploads in memory. Files are streamed to disk and processed from there, which makes handling large batches much more predictable.
Today the tool supports:
Up to 1,000 images per batch
Folder and ZIP uploads
WebP, JPG, PNG, GIF, SVG, PDF, and ICO conversion
ZIP download of converted files
The business side
This isn't an attempt to build a huge startup overnight.
I wanted to build a genuinely useful utility, learn from real users, and see whether a focused tool can grow through SEO, community sharing, and word of mouth instead of paid acquisition.
The first feedback has already been encouraging. Someone on Reddit uploaded an entire project folder and said they appreciated that the filenames were preserved. They also suggested adding an option to strip image metadata during export—a feature I hadn't considered but is now on the roadmap.
It's a reminder that people often tell you what to build next if you simply put something in front of them.
This is only the beginning, and I'm looking forward to seeing where it goes.
If anyone here has experience building developer tools or utility websites, I'd love to hear how you've approached growth once the product was live.
3 Comments
The full-project-folder usage is probably more interesting than the metadata request itself.
It’s early evidence that someone encountered the product with the kind of workload you specifically designed around, rather than just using it as another single-image converter.