Back to Blog

How to protect free downloads in an AI background remover

Background remover free credits abuse costs cents per image, until sellers run whole catalogs through repeat accounts. The arithmetic, and which fixes break.

The download gate was the best thing you shipped all year. Until August, anyone could drop a photo on your homepage and leave with a full-resolution cut-out, no account needed. That was 52,000 images a month, and at $0.013 each it cost you $676. So you built the gate: low-res previews for everyone, and 20 free HD downloads, once, for anyone who verified an email. September's GPU bill fell by exactly $676. You wrote it up in the changelog and felt good for about five weeks.

This is a scenario, and every number in it is an assumption you should swap for your own. In October your verified signups climbed from 200 a day to 700, and you took that as the gate paying off. Then at 7:35 a.m. on the 1st of November the GPU invoice arrives, and it says $5,616.

You open the download log. An account signs up, confirms its email, downloads exactly 20 files and never comes back. The files are called SKU-20418-front.png, SKU-20418-side.png, SKU-20418-back.png. The next account starts at SKU-20422. Someone is working through a product catalog in order, and your free plan is their photo editor.

That's background remover free credits abuse, and it hides well because each piece of it is so small. Start with one image. Assume a full-resolution cut-out takes 10 seconds of GPU for the mask, the hair and edge detail, and the upscale:

  • GPU: 10 seconds × $0.0012 a second = $0.012
  • Storing the files and serving the download: $0.001
  • One HD image: $0.013

Low-res previews cost about a tenth of that, so they're left out here. A free account that uses all 20 downloads costs you 20 × $0.013 = $0.26. Nobody loses sleep over 26 cents. Now run a catalog through it:

  • One catalog: 4,000 products × 5 photos = 20,000 images
  • Accounts it takes: 20,000 ÷ 20 = 1,000
  • Say 15 sellers do this in a month: 15 × 20,000 = 300,000 images
  • Accounts: 300,000 ÷ 20 = 15,000, which is those 500 extra signups a day
  • Cost: 300,000 × $0.013 = $3,900
Monthly GPU bill, illustrative0100020003000400050006000AugSepOctUS dollarsMonth
Monthly GPU bill, illustrative0200040006000AugSepOctUS dollarsMonth

The gate saved you $676 a month. What came through it costs nearly six times that.

Your 320 customers on a $19 plan bring in $6,080 a month. At 300 images each they cost $1,248. Real free users (6,000 accounts averaging 6 downloads) add $468. That was your $1,716 bill. Add the $3,900 and you've got $464 left for hosting, payment fees and yourself. Over a year, $3,900 × 12 is $46,800, more than seven and a half months of everything your customers pay you.

None of it comes back. Your GPU provider charges your card on the 1st while your $19 renewals trickle in across the month, so the cash leaves before the money meant to cover it arrives. You could delete all 15,000 accounts this morning and the GPU seconds would stay spent. The 300,000 transparent PNGs are already up on 15 storefronts.

Those were also your paying customers' GPUs. 300,000 images × 10 seconds is 833 GPU hours, more than half of the 1,440 that two GPUs give you in a 30-day month. A customer uploads 200 photos for a weekend sale. That batch normally takes about 17 minutes (200 × 10 seconds ÷ 2 GPUs). Behind a 3,000-image free run, it waits 4 hours and 10 minutes first (3,000 × 10 seconds ÷ 2 GPUs). Their message says, "Is this down? These listings go live at noon." They want their $19 back, and twelve cancellations like that is $228 a month.

So now you get to choose. Free HD is how people find out your product handles hair and glass properly, and it's what sells the $19 plan. Cut it to 5 downloads and a real seller gets one product's worth of testing, while the same 300,000 images simply take 60,000 accounts. Remove it and you stop finding new customers in the same week.

Why catalogs end up in your free plan

Here the whole reward is a file, and once it's downloaded the account has no further use to anyone. The 21st image just needs another account.

Sellers also have a job with a real end, and it has a price. On your plan, 20,000 images ÷ 500 downloads a month is 40 months at $19, or $760. Some of those sellers would never have paid that. Some would have.

The obvious fix is the one you already shipped, a per-account limit behind an email step, and it did its job. Every one of those 15,000 accounts stopped at exactly 20. A limit like that can only count inside one account. Work out what a free user costs you before you pick the next fix.

The basic fixes, and where each one breaks

Verification proves someone can open an inbox. A unique-email rule compares strings, and one mailbox can have many strings: Gmail ignores dots, and plus-tagged mail reaches the same inbox. That's simply how email works.

Email fixWhat it catchesWhat it missesWho it wrongly blocksWhat it costs to keep working
Email verificationTypos and dead inboxesAny real second inboxPeople whose code lands in spamSending and deliverability work
Unique emailsThe same address twiceEvery different addressAlmost nobodyVery little
Disposable-domain blocksKnown throwaway servicesNew domains and ordinary mailboxesPeople using privacy forwardingA list someone updates forever
Gmail dots and plus tagsOne inbox written several waysA second real mailboxPeople sharing one inboxUpkeep as mail services change

A CAPTCHA on the download button stops simple scripts. A seller's assistant clicking through 20 downloads by hand passes every time, and people using screen readers or old phones get stuck right when they're deciding if your cut-out is worth paying for.

Asking for a phone number or a card does cut casual second accounts. It's also a lot to ask of someone testing one photo, and a card wall costs you signups. Anyone with another number or card still gets through. Assume a text costs $0.05 and you've added 19% to the $0.26 you were protecting ($0.05 ÷ $0.26).

One account per IP address catches repeat signups on one connection and misses every other network. It also hits the photo studio or warehouse where six people share a connection, and those are the customers you most want. VPN blocks catch the ranges on your list, miss the rest, and turn away privacy-minded people and staff on company VPNs. Both leave you with exceptions to answer.

Rate limits protect your GPUs from bursts, so keep them. They just won't see this. 500 accounts a day × 20 downloads is 10,000 downloads a day, about 7 a minute, from accounts that each make 20 requests in total. A usage cap is what you already have, and it's why each account stopped so neatly. Shrinking the allowance lowers the cost per account and raises the number of accounts.

Manual review means a person reading new accounts. At 30 seconds each, 15,000 accounts is 125 hours a month, and by the time anyone looks, the file has gone.

Illustrative trade-off of the basic fixesEffective but costlyEffective and painlessCheap and easy to beatCostly and still beatenLow frictionHigh frictionStops littleStops moreVerified emailDisposable blockCAPTCHAPhone requiredCard requiredSmaller allowance
Illustrative trade-off of the basic fixesEffective butcostlyEffective andpainlessCheap and easyto beatCostly and stillbeatenLow frictionHigh frictionStops littleStops moreVerified emailDisposable blockCAPTCHAPhone requiredCard requiredSmaller allowance

The top-left corner is empty. Stack everything and your homepage asks for a verified email, a puzzle, a phone number and a card before anyone can test a photo. A seller with 20,000 images has plenty of reason to sit through that. Your honest users don't.

What to do about it this week

Run full resolution only on download. Previews stop at the cheap pass, so someone who leaves costs you a tenth of an image.

Give free jobs their own queue and a daily budget. Paying batches go first. A budget of 2,000 free images a day is $26 a day (2,000 × $0.013), or $780 a month, with room for the 1,200 a day real users need. A farm can still eat it and leave real users waiting until tomorrow, which beats a bill with no ceiling.

Keep bulk work on paid plans. No batch upload, ZIP export or API on the free plan. This slows a catalog down and doesn't stop it.

Sell the catalog job. A one-off 20,000-image pack costs you $260 to run. At $0.03 an image it's $600, less than the $760 your plan would take and $340 of margin to you.

Decide what a no looks like. Some of the people you turn away will be real, so offer a paid plan and a way to reach you.

Evaluate the claim before the GPU starts

Every fix above looks at one signup, one address or one account. None of them can say whether this claim for 20 free downloads looks like a repeat of the last thousand, and with a catalog in play that's where the $3,900 goes.

That's the job AbuseZero was built for. Before the free downloads are granted, your server makes one API call and gets a clear allow or deny, under rules you control. A new inbox doesn't start things over, because creating a fresh account isn't enough to erase previous activity. Your domain list goes stale and your unique-email rule compares strings, while AbuseZero checks mailbox aliases, disposable domains and mail routing, and recognizes repeat devices across new accounts, even when email addresses keep changing. An IP rule knows one address. AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence, and it blocks spammy bots, browser automation and malicious scripts while allowing genuine AI agents and assistants. It flags abuse that single checks miss and detects linked claims, with multi-layer AI risk analysis examining 140,000+ signals. Signals are read together, never one at a time. There's a proprietary algorithm in there too, with AI that checks the claim again.

You don't have to build your own abuse prevention system. Put the evaluation in front of the free grant and a denied claim never has to reach a GPU. Observe mode shows you what would be denied before anyone is blocked, so the studios and agencies you want as customers aren't your test. The quickstart gets your first benefit protected.

Frequently asked questions

How many free downloads should I give?

Enough to judge quality on a hard photo, such as hair or glass, and to finish one listing. There's more in how many free credits to give new users.

Can I take free downloads back after an abuse wave?

You can take back unused credits, but a downloaded file is gone and so is the GPU time. See how to take back free credits after an abuse wave.

Is every seller with several accounts abusing the free plan?

No. An agency may keep one account per client. Write down what you mean to give each person, and give agencies a paid route.

Where does the evaluation go in my download flow?

Right before you grant the free downloads. The protect a benefit guide shows how to act on AbuseZero's allow or deny.

Keep free HD downloads for people trying your product

Keep reading

Copying your prompt…

Copied the to your clipboard. Give it to your coding agent & it will handle the rest.