Hey Indie Hackers,
TinyPDF (https://tinypdf.cn/?utm_source=indiehackers&utm_medium=social&utm_cam
paign=pricing_thoughts&utm_content=indiehackers_pricing_2026-07-29) is 100%
free right now. No ads, no paywall, no account required. Just drag, drop,
compress to your target MB size, download.
A lot of people ask: "Will this always be free?" "How do you make money?"
"When are you adding a paid tier?"
Here's my current thinking, in public.
TinyPDF is a side project. I built it to solve my own pain (portfolio size
limits for job apps). I'm not dependent on it for income.
Keeping it free has real benefits:
I could throw up ads, but that would ruin the experience. I could add a
paywall, but that would defeat the original goal.
So for now: free.
What will always be free:
What might get a paid tier someday:
The idea is: free for individuals who need it occasionally, paid for
If you want to try it:
https://tinypdf.cn/?utm_source=indiehackers&utm_medium=social&utm_campaign=pri
cing_thoughts&utm_content=indiehackers_pricing_2026-07-29
Would love to hear your thoughts!
That's a problem solving
The pricing framework is already well covered here: add-ons over tiers, skip the ads, and Hire_Hivemind's API-over-batch argument is the sharpest thing in the thread. The piece nobody's answered yet is how you'd actually find out who your heavy users are, since no account required means you don't have the usual signals, signups, emails, company domains, to segment by.
Two things you could measure without breaking that promise. An anonymous device or browser id (cookie or
localStorage, not tied to identity) would show what fraction of compressions come from repeat visitors within a 30-day window, that alone tells you whether there's a cohort that comes back weekly at all, versus pure one-off traffic. And before building batch processing, check your existing logs for consecutive uploads from the same session or IP in a short window. If people are already manually re-uploading file after file, that's your latent batch demand showing up for free, and it's a much better signal than asking what someone would pay for a feature that doesn't exist yet.The "no account required" line is doing more work than you think — keep it. I run a few small products and the cleanest split I've found is: the thing an individual does occasionally stays free and anonymous, and you charge for the shape of use that only shows up when someone's doing it a lot — your batch processing and API are exactly that. That's paid add-ons, not freemium. Freemium quietly pushes you toward crippling the free tier until the "zero friction" you're describing disappears. On ads: I'd skip them entirely — the goodwill from a genuinely clean free tool is worth more than the ad revenue, and it's very hard to walk back once it's in. One question decides most of this: do you know yet whether your heavy users are individuals or people doing this for work? That answer basically picks your pricing for you.
One thing I'd keep an eye on is whether people become attached to TinyPDF being free or to TinyPDF being dependable.
Those lead to very different reactions when monetization eventually arrives.
The "compress to an exact target MB size" framing is your actual asset, worth noticing before the pricing question. Most compressors give you "small/medium/large" and you gamble. Yours hits a specific number, which maps to a specific pain: "my upload limit is 10MB and my file is 12." That's not a nice-to-have, it's a person stuck right now. Lead with the pain, not the feature.
On your questions:
Freemium vs add-ons: for this, paid add-ons beat a Free/Pro split. Your whole advantage is zero friction and goodwill, and a "Free plan" immediately makes people wonder what they're not getting and when the wall drops. Keep the core gloriously free, sell power-user features à la carte. The generosity is the marketing, don't compromise it with tier anxiety.
Pricing: batch processing is the wrong first paid feature to anchor on. People who compress 10 PDFs at once are rare. The ones who'd actually pay recurring are developers, which points at API access as your real revenue line. "Compress to exact size" inside someone's workflow is worth paying for predictably, and it doesn't dilute the free consumer goodwill at all. Build the API before batch.
Ads: don't. You said it yourself, ads ruin the experience, and the experience IS the moat. The moment TinyPDF looks like the sketchy ad-riddled PDF sites you're better than, you lose the thing that makes people tell their friends. Clean-and-free is your brand. Protect it.
The real question underneath all three: who's the paying customer, the occasional individual (stays free forever) or the developer/business with a recurring need? Answer that and the pricing model picks itself. My bet: free for humans, paid API for machines.
What's your usage pattern, mostly one-off individuals or people coming back weekly? That tells you if there's a paid business here at all.
This is a smart freemium positioning. On the "free plan vs pay-per-feature" question: the power here is that your free core (compress to exact size, no account, no watermark) is your distribution engine. Batch processing and API access are natural B2B/pro user upsells precisely because they solve workflow problems, not access problems. That makes them feel like genuine pro features rather than artificial gatekeeping. I'd lean toward separating them - batch at $5-10/mo feels right for professionals who process PDFs daily, while occasional users stay free. The "ad-supported version" probably dilutes your goodwill moat though. What matters is that the free tier is genuinely useful enough that users recommend it. That's your most powerful distribution channel.