A few months ago I needed to convert a batch of product photos from PNG to Web (urlOriginally published at https://www.convertimagenow.com/blog/why-i-built-convertimagenow)Nothing complicated — just a routine task anyone doing web or e-commerce work runs into constantly. I opened the first "free online image converter" that came up in search results.
It asked me to create an account before it would let me download anything.
I closed the tab and tried the next one. That one worked without an account, but buried the actual download button under three banner ads, and added a faint watermark to the corner of every image — something the site had not mentioned anywhere before I uploaded my files.
By the fourth site, I had a folder of client photos sitting on servers I knew nothing about, run by companies I'd never heard of, with privacy policies I hadn't read and had no real way to verify. For a five-second task, that felt like a lot to hand over.
The part nobody mentions
Here's the thing that struck me afterward: none of this needed a server in the first place.
Modern browsers can already decode an image, redraw it in a different format, and hand you back a file — all without the image ever leaving your device. It's the same Canvas API that's been sitting in every browser for over a decade, mostly used for games and data visualizations. Nobody was using it for something as simple as "convert this JPG to a PNG."
So the upload step that every converter site makes you go through isn't a technical requirement. It's just how those sites were built — often because it's easier to add ads, accounts, and watermarks to something running on your server than to something running entirely in someone else's browser.
What I built instead
I put together a small tool that does the conversion locally, in the browser, using that same Canvas API. You drop in a JPG, PNG, WebP, or AVIF file, pick what you want it converted to, adjust the quality if you care about file size, and download the result. Nothing gets uploaded anywhere in the process — there's nothing to upload to, because the server never sees the file.
A few things came naturally out of building it this way:
No sign-up, because there's nothing to sign up for. There's no account system tracking usage, because there's no server-side processing to meter.
No file limits. Since the work happens on your own device, there's no bandwidth cost to the tool itself for converting one image or a hundred.
No watermarks. There was never a version of this where I planned to charge for a "clean" download later.
It's called ConvertImageNow, and it's free — convertimagenow.com, if a browser-based converter is useful to you the way it was to me.
The broader point
I don't think image conversion is a unique case. A lot of small, everyday web tools default to a server-upload model mostly out of habit, not necessity — and that habit quietly costs users privacy, speed, or both, for tasks that never needed a round trip to someone else's infrastructure in the first place.
If you're building something similar, it's worth asking whether the upload step is actually load-bearing, or just the way it's always been done.
Originally published at https://www.convertimagenow.com/blog/why-i-built-convertimagenow
Top comments (0)