Why I Built a Free Image Tools Site (And How Free Can Actually Work)

gpszxtzys — Sun, 28 Jun 2026 04:14:56 +0000

I saw the "I built 184 free browser tools" post on HN last week — 88 points, solid discussion. A lot of comments were asking the same questions: "How do you make money?" "Why would you do this for free?" "What's the catch?"

I built SmartImgKit, a free online image tools site with 20+ tools — compressor, converter, resizer, background remover, watermark tool, meme generator, GIF editor, and more. All browser-based, no uploads, no signup.

I've been thinking about the same questions. Here's where I landed.

The gap in the market

The image editing market is split between heavy desktop software (Photoshop, GIMP, Affinity) and SaaS tools with monthly subscriptions. Neither works well for the person who needs to crop one image, remove a background from another, and convert a HEIC file to JPEG in the same hour.

Desktop tools require installation and updates. SaaS tools require signup and often upload your files to their servers — a genuine privacy concern for sensitive images.

Browser-based tools handle all of that. WebAssembly makes it possible to run complex processing — background removal with ONNX models, HEIC decoding, image upscaling with smart interpolation — entirely in the browser. Your files never leave your machine.

How free can work

A few sustainability models I've seen work in this space:

The Pro plan model. Free tier handles 80% of use cases. Paid tier adds batch processing, higher resolution output, or API access. This is what most online image tools do, and it works.

The enterprise model. Free for individuals, paid for teams with SSO, audit logs, and compliance features. Figma made this famous.

The adjacent-product model. Free tools drive awareness for a paid product in a related space. Not applicable to every project, but powerful when it fits.

I'm still figuring out the right model for SmartImgKit. But one thing I'm sure about: if the tools are genuinely useful and respect user privacy (no uploads, no unnecessary tracking), people will use them. Monetization can come later.

What I'd love to hear

What's the line for you between "this should be free" and "I'd pay for this"?

Is it volume (more than X images per month)? Features (batch processing, API access, higher resolution)? Or something less obvious like support, SLA, or white-label options?

Drop your thoughts in the comments. I'm genuinely curious where the community draws that line.

I switched 23 sites from JPEG to WebP/AVIF last month — here's what I learned

gpszxtzys — Sun, 28 Jun 2026 03:19:29 +0000

I spent last month migrating 23 client sites from JPEG/PNG to WebP and AVIF. Here's what I wish someone told me before I started.

AVIF vs WebP: the real numbers

AVIF is about 30% smaller than WebP at the same quality level. But Safari support is still patchy — if your traffic is 40%+ iOS, you need <picture> tags with WebP fallback. No way around it.

The biggest win wasn't the format

The single biggest reduction came from capping max image width at 1200px and setting quality to 80. One site went from 9.4MB to 318KB per page — a 97% reduction — just from those two settings plus lazy loading.

The format switch was the cherry on top, not the cake.

Tools I used daily

SmartImgKit — quick batch conversions in the browser. No uploads, no signup, drag and drop. Handles the 80% case where you don't need a CLI pipeline. Supports JPG, PNG, WebP, AVIF, GIF, BMP, TIFF.

ImageMagick — server-side batch jobs for when you need automation.

Squoosh — one-off fine-tuning with visual comparison.

Sharp (Node.js) — build pipeline integration.

The HEIC surprise

Every iPhone user's photos are HEIC. Most web tools crash on them. You need a converter that handles them before the pipeline — SmartImgKit's HEIC converter works locally in-browser, no uploads.

The 80/20 rule

Format + max width + lazy loading = 80% of the gain. Everything else is diminishing returns. Don't over-engineer it.

DEV Community: gpszxtzys