You've zipped up the files — maybe a set of Lightroom presets, a folder of source code, a bundle of templates — and now you need to charge people for it. The usual options all have the same problem: password-protect the zip and email the password after someone Venmos you (easy to forget, easy for one buyer to leak to ten friends), or upload it to a locked Google Drive folder and hope people actually pay before you grant access. None of that is a real paywall. It's an honor system with extra steps.
A genuine paywall means the file simply doesn't exist for the buyer until payment clears — no password to manage, no manual access-granting, no trusting a stranger's word. This guide covers how to put an actual payment gate on a ZIP file, what a "good enough" password-and-email workaround gets wrong, and what happens to the file security-wise once someone does pay.
Key Takeaways
- A password-protected ZIP isn't a paywall — it still requires you to manually collect payment and hand out the password yourself, and one shared password breaks the whole system
- PayRequest Upload turns any ZIP file into a payment-gated link in under a minute: drop the file, set a price, publish
- The file is genuinely inaccessible until payment confirms — there's no separate step where you "release" it manually
- What's inside the ZIP doesn't matter to PayRequest — source code, presets, fonts, project files all work the same way, since only the outer .zip is checked
- Every download link is tokenized to one purchase, with optional limits and expiry, so a leaked link doesn't mean infinite free downloads
What "Paywall a ZIP File" Actually Means
Put simply, paywalling a ZIP file means nobody can download the actual archive until they've paid for it. That sounds obvious, but most of the common workarounds don't actually do this — they gate *access to information about how to get the file*, not the file itself.
A Google Drive link set to "anyone with the link" isn't locked at all — it's a paywall only in the sense that you haven't told anyone the link yet. Once shared, there's no payment checkpoint between the click and the download; you're relying entirely on buyers being honest about paying first. A password-protected zip is closer, but the password itself becomes the actual gate — and a text string is trivially easy to forward, screenshot, or post in a Discord server.
A real paywall puts the *payment* between the buyer and the file, not a piece of information you're hoping stays secret. That's the difference between "I trust you paid" and "the system already confirmed you paid."
Zipping is usually less about security and more about packaging — bundling multiple files (a set of presets, several source files, a folder of assets) into a single download. It also happens to be one of the most universally supported archive formats, opening natively on Windows, macOS, and virtually every mobile OS without extra software. If you're selling more than one file at once, a zip is almost always the right container — the question is just how you gate access to it.
How to Add a Paywall to a ZIP File With PayRequest Upload
PayRequest Upload is built specifically for this: turning a single file — including a zip — into a payment-gated link without a product wizard or store setup first.
Go to payrequest.me/upload and drag your .zip into the upload box, or click to browse. PayRequest accepts zips up to 250MB and automatically detects the file category (it'll show as "Software & Code" or similar). The title field pre-fills from your filename — edit it if you want something more descriptive than `final_v3_actually_final.zip`.
Enter what you're charging. Your account's currency symbol appears automatically, and there's no minimum setup or subscription required to publish a single paid file.
Click Generate Payment Link. If you're not signed in, you'll be prompted to sign in or create a free account — this only happens at the final step, so you can fill out the whole form and see your price before committing to anything. Once published, your link is live immediately at `payrequest.me/[handle]/[filename]` and ready to share anywhere: a bio link, a Discord announcement, a tweet, an email to your list.
What Happens After Someone Pays
Behind the scenes, PayRequest Upload creates a standard digital product and a Smart Link — nothing exotic, and both are fully visible and editable from your dashboard afterward. When someone pays, the file unlocks through a tokenized download link tied specifically to that purchase, not a static, shareable URL.
You can cap how many times a single purchase can be downloaded (useful if you're worried about a buyer re-downloading indefinitely and passing the link around) and set an expiry window. If someone loses their copy and needs it again within reason, you can reissue a fresh token from the order page in one click — no need to re-send the whole file manually over email.
Unlike a password you hand out once, the download link itself is single-purpose. Even if a buyer forwards their download link to a friend, that link is tied to their specific token limits — it doesn't grant the friend a separate, unlimited copy of your product page.
Common Ways People Try to Paywall a ZIP (and Where They Fall Short)
| Method | Payment collected first? | Delivery automatic? | Risk of leaking |
|---|---|---|---|
| Password-protected zip + manual payment | No — relies on honesty | No — you send the password | High — one shared password unlocks it for everyone |
| Google Drive / Dropbox link + "pay first" note | No — pure honor system | No | Very high — link often just works for anyone |
| WeTransfer + invoice sent separately | No — file transfers regardless of payment | No | High — WeTransfer doesn't gate on payment at all |
| Discord role-gate (paid role sees channel) | Depends on bot setup | Sometimes | Medium — still requires ongoing role management |
| PayRequest Upload payment link | Yes — payment required before unlock | Yes — instant, tokenized | Low — links are single-purchase and limited |
The pattern across the first four rows is the same: the *file* isn't actually protected, only the *information about where to find it* is. That's fine for casual sharing, but it's not a real business model if you're actually trying to charge for the download.
What Can (and Can't) Go Inside the ZIP
For security, PayRequest Upload won't accept raw executable or script files as the *uploaded file itself* — no bare .exe, .py, or similar. But a .zip is just a container, and PayRequest only validates the outer archive, never opening or inspecting what's packed inside it. That means source code folders, project files, font collections, preset packs, and document bundles all work exactly the same way once they're zipped — the archive is delivered to the buyer byte-for-byte, exactly as you uploaded it.
Frequently Asked Questions
Upload the .zip to PayRequest Upload (payrequest.me/upload), set a price, and publish. PayRequest generates a payment link — buyers only receive the download after paying, and the zip itself never needs a password or manual gatekeeping.
No. A password stops casual snooping, but you still have to collect payment separately (email, DM, invoice) and manually send the password to each buyer — and once one buyer shares it, the password protects nothing. A payment-gated link removes the file from public access entirely until payment clears.
Anything — source code, project files, presets, fonts, documents, sample packs. PayRequest only validates the outer .zip container; it never opens or executes what's inside, and delivers it to the buyer exactly as uploaded.
PayRequest Upload accepts zips up to 250MB. For larger bundles, PayRequest's full Digital Products flow supports much larger files — create a product manually from your dashboard instead of using the Upload shortcut.
Every download link is tokenized to that specific purchase and can be limited to a set number of downloads or an expiry window. If a link leaks, you can revoke or reissue it from the order page — unlike a shared password, which can't be un-shared.
Bottom Line
A password and an honor system might work for a handful of friends, but the moment you're actually selling a ZIP file to strangers, you need payment to happen *before* the file becomes reachable — not a piece of information you're hoping stays secret. PayRequest Upload turns any zip into a real payment-gated link in about the same time it takes to drag the file into a browser window.
Try PayRequest Upload on your next file, or see how it fits into full Digital Products delivery if you're selling more than one item.