Description: Resolution caps, "we delete it after 2 hours (trust us)", paywalled buttons, and why your browser can now do all of this by itself.
You need one transparent PNG of a product photo. Five minutes, tops. You google "remove background online", click the first result, upload, and watch the progress bar do its little dance.
Let's talk about why "free online image tools" is mostly a vibe, not a price tag, and about the genuinely interesting engineering reason this whole category is overdue for a rewrite.
🧾 Receipts policy: every limit I quote below comes from the tool's own documentation or pricing page. No hot takes without sources.
remove.bg is the poster child, and to their credit they say it out loud in their own FAQ: the free website version is for low-resolution images, up to 0.25 megapixels. Full resolution (up to 50 MP) lives behind premium plans and credits.
A modern phone photo is 12 MP. That's roughly 48× more pixels than what the free tier hands back. The preview on screen looks sharp because your screen is small. The file is where the shrinkage happens.
Fair play: servers cost money, GPUs cost more, and freemium is a legit business model. But "free" and "free at thumbnail size" are not the same product.
Here's the thing most people never think about. For the typical online tool, the architecture is:
Take iLoveIMG: the files go to their servers, and they say uploads get deleted within about two hours. That's a reasonable policy, honestly. But notice what it actually is: a promise, not a property of the system. You can't verify it. You're trusting a privacy page.
For a meme? Whatever. For an ID scan, a client's unreleased product shots, your kid's school photo, a screenshot with a token in it? That's a bigger ask than the "drag & drop" button makes it look like.
You open Canva, find the Background Remover button right there in the Edit panel, click it, and get the upgrade prompt. The feature is a Canva Pro thing. You get a limited free taste, and then it's subscription time.
TinyPNG is a great compressor and I will defend that. But the free web version tops out at 20 images per session, 5 MB per image, and 3 conversions. Paid tiers raise that to 75 MB (Pro) and 150 MB (Ultra).
Real task: "Make this product photo web-ready, transparent, under 200 KB, as WebP."
That's 4 uploads, 4 privacy policies, 4 free-tier limits, and 3 extra lossy re-encodes (every JPEG save throws away a bit more detail; it's called generation loss). You didn't edit an image. You ran a relay race with your pixels. 🏃
Historically: the browser couldn't do the heavy part. Segmentation models needed GPUs and big runtimes, so the model lived on a server, and your photo had to travel to it. Server costs → limits → upsell → "download HD for 1 credit."
| Then | Now | |---|---| | JS is too slow for ML | WebAssembly runs near-native code in the tab | | No runtime for neural nets | ONNX Runtime Web runs real models in-browser | | Models are 500 MB+ | Good segmentation/inpainting models ship in the 5 – 180 MB range | | Can't cache big files | Cache Storage keeps a model after the first download |
Any tool that claims "100% client-side" should survive this 20-second test: Open DevTools → Network tab. Clear it. Load an image and run the tool. Look for any request that carries your image bytes.
A real on-device tool shows no image upload. (You'll see one-time downloads of the model files, because the AI has to come from somewhere, but those flow to you, not from you.) Try this on whatever you use today. It's genuinely eye-opening.