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.
Top comments (0)