How to stop free upload abuse in a chat with PDF app
Every free PDF is parsed, embedded and stored before anyone pays. What a free upload really costs, which basic fixes break and how to cut the bill.
One free PDF costs you about 80 cents before anyone has asked it a question. Add up the rest of the free plan and the sum gets worse with every line:
1 page parsed, embedded and summarized $0.008
1 PDF of 100 pages x $0.008 $0.80
5 free uploads x $0.80 $4.00
40 free questions x $0.01 $0.40
1 free account, fully used $4.40
30 accounts for one person x $4.40 $132
15 people a month x $132 $1,980
12 months x $1,980 $23,760Those prices are assumptions for a scenario, so replace them with your own. Here the page figure is $0.004 for parsing and OCR, $0.001 for embeddings and $0.003 for the summary your app writes on upload. The bottom half of that list is chat with PDF free tier abuse, and 30 accounts for one person isn't strange in this product. Someone with a 15,000-page archive needs exactly 30 free accounts at 500 pages each, and then the whole archive answers questions for nothing.
Stay in the scenario for a Tuesday morning. At 10:35 a.m., a paralegal on your $12 plan writes in: "This has been stuck on 0 of 312 pages for 40 minutes. I need the bundle for a filing at 11. Should I use something else?"
You're in a call and don't see it until 11:05, and by then there's a second message: "Never mind, we filed without it. Please cancel my plan."
You open the job queue. Ninety free accounts, all opened this week, started uploading at 9 a.m., in files named like archive_part_117.pdf. It looks like three archives of 15,000 pages each, and your workers clear 300 pages a minute:
- 90 accounts × 500 pages = 45,000 pages
- 45,000 ÷ 300 = 150 minutes, so the queue was going to run until 11:30
A customer who pays you was waiting behind all of it. You cancel the rest of the free jobs, refund the paralegal's month and apologize, and then you work out what the morning cost. In the 125 minutes since 9, your workers got through 37,500 pages (125 × 300). At $0.008 a page, that's $300 already spent. Your parsing provider billed per page and your model provider billed per token, at the moment the work ran. Delete all 90 accounts and the invoice doesn't change by a cent. The $1,980 a month in that sum goes out before any revenue can cover it, and matching it takes the whole subscription of 165 customers on your $12 plan ($1,980 ÷ $12).
Then there are the files. The people who uploaded them got their answers on day one and haven't logged in since, and you're still paying to keep the originals, the vector index and the backups. Assume that's $0.0002 per page per month.
- 15 people × 30 accounts × 500 pages = 225,000 new pages a month
- 225,000 × $0.0002 = $45 a month, for as long as you keep that month's pages
- By month 12: 12 × $45 = $540 a month
- Across the year: $45 × 78 (that's 1 + 2 + ... + 12) = $3,510
Together that's $27,270 in a year ($23,760 + $3,510). If your company spends $12,000 a month, you've handed over more than two months of runway ($27,270 ÷ $12,000 = 2.27) to people who finished what they came for and left. The paralegal hasn't replied to your apology. So now you're looking at the free plan that brought in nearly every customer you have, and working out how much of it you can afford to cut.
Why chat with PDF apps pay for free users up front
Most free plans cost you as people use them. A chat with PDF app does its expensive work before the first question, because the product promises answers seconds after the upload. Every page gets parsed, embedded and often summarized, whether the person goes on to ask 40 questions or none.
The job is short, too. People arrive with one lease, one textbook or one tender pack, and once it's answered they have no reason to stay. When upload six gets refused, a new account is the easiest next step. They give up nothing by opening one, because each document stands alone and there's no history worth keeping.
Here's one fully used free account, with illustrative numbers:
The obvious fix is a lower limit, so say you cut files to 20 pages. That archive now needs 150 accounts instead of 30 (15,000 ÷ (5 × 20)). The pages still cost $120 (15,000 × $0.008), and if every account uses its 40 questions, those go from $12 to $60. That one person now costs you $180 where they used to cost $132. Your honest free user pays for it in a different way: their 60-page lease comes back with an error, on the one upload that was going to show them your product works.
The basic fixes for free upload abuse, and how each one breaks
What you'd like to know at upload time is whether this person has already had their free pages. Each basic fix answers something narrower than that, and email is where the gap's easiest to see. A unique-email rule compares text, and one mailbox can be written many ways: Gmail ignores dots, and plus-tagged mail reaches the same inbox. That's how email works.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any real second inbox | People whose code lands in spam | Sending and deliverability work |
| Unique emails | The same address twice | Every different address | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains and ordinary mailboxes | People using privacy forwarding | A list someone updates forever |
| Gmail dots and plus addressing | One inbox written several ways | A second real mailbox | People who sort their mail with plus addresses | Upkeep as mail services change |
| CAPTCHA | Simple upload scripts | Someone signing up by hand | People using screen readers | Fees and lost signups |
| Phone requirement | Casual second accounts | Anyone with another number | People without a reliable mobile number | A charge for every text |
| Card requirement | Casual second accounts | Anyone with another card | A student with one PDF and no reason to pay yet | Fewer signups |
| One per IP address | Repeat signups on one connection | Any other network | A whole campus the week before finals | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Everything off your list | Law firms and finance teams on company VPNs | Another list to maintain |
| Rate limits | Bursts from one account | 30 accounts each under the limit | A paralegal uploading a whole case at once | Tuning per endpoint |
| Usage caps | One account going over | Each new account's fresh cap | Anyone halfway through a long document | Deciding when your product stops |
| Shorter trials | Slow, long use | A job finished in an afternoon | People who need a second week | Fewer people reach paying |
Manual review is harder here than in most products, because the files are someone's contracts and medical letters and you shouldn't be opening them to judge intent. Even at 2 minutes an account, 450 new accounts a month is 15 hours (450 × 2 ÷ 60). Stack the rest of that table and your signup asks for a confirmed email, a puzzle, a phone number and a card from someone who wanted to ask one question about a lease.
How to make a free PDF upload cost less
None of this stops a second account, but it shrinks what each one costs.
Run nothing costly until the email is confirmed. An account that never confirms then costs you one email instead of $0.80 a file.
Stop summarizing on upload. Write the summary when someone asks for it, and run OCR only on pages with no text layer. At $0.003 a page, a full account's 500 pages save you $1.50, about a third of its $4.40.
Give paying uploads their own queue. Reserve 60 pages a minute for paid jobs and the paralegal's 312 pages finish in about 5 minutes.
Put a daily budget on free processing. When it's spent, free uploads wait until tomorrow and paying ones carry on. A hard spending cap puts a ceiling on a bad day.
Expire the index on quiet free accounts. Tell people in your plan details, drop the vectors after 30 idle days and rebuild them if someone comes back, at $0.001 a page. If the index is most of your per-page storage, the bill levels off near one month of pages, about $45, where it would have reached $540. Test your delete job too, because a deleted row can leave its vectors behind.
Do all five and the bill drops and your paying customers stop waiting. A full account still costs $2.90, though ($4.40 minus $1.50), and 30 accounts still collect 30 allowances.
Decide before the parser runs
Everything above limits the damage once free pages have been granted. What's left has to come first, before page one is paid for: should this claim get the free allowance, or does it look like a repeat? A list of domains or a count of connections can't tell you.
AbuseZero is built for that decision, so you don't have to build your own abuse prevention system. You get multi-layer AI risk analysis that examines 140,000+ signals, detects linked claims and flags abuse that single checks miss. You also get a proprietary algorithm, with AI that checks the claim again. Where your domain list goes stale in a week, AbuseZero checks mailbox aliases, disposable domains and mail routing. Your one-per-IP limit can only count connections, while AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. It recognizes repeat devices across new accounts, even when email addresses keep changing. Creating a fresh account isn't enough to erase previous activity.
Your server makes one API call before a file reaches the queue and gets a clear allow or deny, under rules you control. Your free allowance becomes a benefit with eligibility you set, such as once per user or once every 30 days, and Observe mode shows you what would be denied before anyone is blocked. Your app still runs the uploads, the page limits and the queue. The quickstart gets your first benefit protected.
Frequently asked questions
Should I delete files from inactive free accounts?
Yes, if you say so up front and warn people first. Dropping only the index is the gentler step.
Is someone with two accounts always abusing the free tier?
No. People keep work and personal accounts. Write down what your free plan is meant to give each person.
Should I just remove the free plan?
Try the cost steps first, because a free upload is often how people find out your product works. AbuseZero's evaluation lets you keep the plan and decide each claim. Removing it is a bigger call.
Keep your free uploads for people with a PDF to read
Start with Builder
Pay as you go. Evaluate your first free upload claim today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High-volume credits and custom terms.