soft-shell crabvietnamese mud crab
2
3 Comments

Show IH: TinyPDF is 100% free, no ads, no paywall — here's why, and what might change

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.


Why it's free today

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:

  • Zero friction: People try it, like it, tell their friends. No "Sign up
    to continue" or "Upgrade to download."
  • Fast learning: I get real usage data and feedback quickly, without
    pressure.
  • Goodwill: People appreciate tools that are just… useful, without a
    catch.

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 might change (and what won't)

What will always be free:

  • The core feature: compress a PDF to an exact target size
  • No account requirement
  • No watermarks

What might get a paid tier someday:

  • Batch processing: Compress 10 PDFs at once to the same size
  • Cloud storage integration: Pull from Google Drive, save to Dropbox
  • API access: For developers who want to build this into their workflow
  • Pro features: Like PDF merging/splitting, OCR, etc. (though those feel
    outside the current scope)

The idea is: free for individuals who need it occasionally, paid for


What I'm not sure about (would love your input)

  • Freemium vs. paid add-ons: Is it better to have a "Free plan" and "Pro
    plan," or just have everything free and sell additional features separately?
  • Pricing: What would you pay for batch processing? $5/mo? $10 one-time?
  • Ads: Would you rather have a free, ad-supported version, or keep it
    completely clean and pay for extras?

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!

posted to Icon for group Show IH
Show IH
on July 29, 2026
  1. 1

    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.

  2. 1

    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.

  3. 1

    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.

Trending on Indie Hackers
Stop losing deals in the gap between "sounds good" and getting paid User Avatar 65 comments We scanned 50,000 domains. Your cold email list is really four systems. User Avatar 64 comments 787 tools for developers. 5 for nurses. Two weeks of tracking 14,000 indie launches. User Avatar 38 comments I Tested Agenmatic for Finding Customers in Communities — Here’s What I Learned User Avatar 35 comments Building in public: a chat assistant that runs your server so you don't have to live in the terminal User Avatar 27 comments How to rank #1 on ChatGPT? User Avatar 26 comments