How to Gate a PDF Download in Webflow (and Collect Emails First)

If you want to gate a PDF download in Webflow, the goal is simple: a visitor gives you an email address, then gets the file. Webflow doesn’t have a single switch for that, so builders usually piece it together from a form, a CRM, or a membership tool. This guide covers why gated PDFs are worth doing, how each common approach works and where it falls short, and how to put an email gate on a file without changing its link.

Why gate a PDF at all

Some documents are a strong signal that someone is interested in buying. A person who downloads your price list, your product brochure, a white paper or your agency’s capability statement is telling you more than a person who read your homepage. If you can’t see who those people are, the download is the end of the conversation.

An email gate turns that download into a lead you can follow up. It works best for files that are genuinely useful and that a prospect would expect to trade an email for: a detailed spec sheet, an industry report, a pricing guide for a considered purchase. It works badly for things people simply need, which we’ll come back to below.

The usual ways to collect emails before a download in Webflow

There are three common approaches. Each one is a reasonable choice in the right situation, and each has a trade-off worth knowing before you pick.

1. A Webflow form that redirects to the file

This is the approach most people try first. You add a native Webflow form with an email field, upload the PDF to the Assets panel, and in the form’s Settings panel set the redirect to the file’s URL. Webflow lets a form redirect to a page on your site or to a URL you type in (Webflow help centre, checked October 2026). Submissions land in Site settings > Forms, and Webflow can email you a notification for each one (Form submissions).

It’s free with your site plan, it looks exactly how you design it, and it needs no extra tools. The trade-off is that the form guards the page, not the file. Webflow’s own documentation says that files uploaded to the Assets panel “are not restricted — that is, they are publicly available and discoverable” (Asset privacy, checked October 2026). The same article notes that password-protecting a page doesn’t protect the file link on it. So once anyone has the PDF’s URL, from a forwarded email, a bookmark or a search result, they can open it without seeing your form. You also need one form per file, or a hidden field, to know which document each person asked for.

2. HubSpot (or another marketing platform)

If your team already runs HubSpot, this is often the natural choice. HubSpot has an app in the Webflow Marketplace that can embed HubSpot forms on your pages or send your native Webflow form submissions to HubSpot (Webflow help centre). A HubSpot form can show a thank-you message or redirect to a page or URL after it’s submitted (HubSpot knowledge base), and you can send the file by follow-up email.

You get contact records, lifecycle stages and automation along with the lead. The trade-off is setup and cost: it’s a whole platform to run, and if the form simply redirects to a file, the file link is still a normal link that can be passed around.

3. A membership tool like Memberstack or Outseta

Membership tools put pages behind a login. They’re the route Webflow itself points people to now: Webflow retired its own User Accounts feature on January 29, 2026 and recommends Outseta and Memberstack for gated content (User Accounts sunset).

They’re the right tool for an ongoing members’ area, a course, or a client portal. For a single brochure, asking someone to create an account, often with a password, is more friction than most visitors will accept just to read a PDF.

How to gate a PDF download in Webflow with DocBeam

DocBeam puts the gate on the file’s link itself. When the gate is on, anyone who opens the link sees a short form first, whether they came from your site, a forwarded email or a bookmark. (The one exception is a visitor who has already filled it in for that file, in the same browser, within the last 30 days.) The link doesn’t change, there’s no code to add and no form to embed.

Install DocBeam and open it in the Designer. It runs as an app in the Webflow Designer. Our getting started guide walks through installing it and connecting your site.
Upload the PDF, or pick one you already host with us. DocBeam serves files from its own CDN, so downloads don’t count against your Webflow bandwidth (more on that in our bandwidth guide).
Turn on “Require email”. In the document’s ⋯ menu, choose Lead capture… and switch on Require email before download. The document is marked Gated. This setting is per document, so the rest of your files stay open.
Link to it as normal. Use Copy link or Insert here to add the link to a button or text link. If the link is already on your site, leave it as it is: the gate now sits on that same address.
Watch the leads come in. Leads appear against each document in your DocBeam dashboard. You can export them as a CSV, and on days you get new leads, a digest email summarises them.

Here’s what the visitor sees: the file’s name, an email field, optional name and company fields, and a consent box that names your site and is never pre-ticked. They enter an email, tick the box, and the file downloads. If they come back to the same file in the same browser, they aren’t asked again for 30 days.

Lead capture comes with paid plans only, and each plan includes a monthly allowance per site: Starter ($9/mo) includes 50 leads, Pro ($19/mo) includes 500, and Unlimited Sites ($49/mo, every site on your account) has no limit. The Free plan doesn’t include lead capture. An allowance isn’t a cap. If you go over it, every lead is still captured and you’ll see a prompt to upgrade. Full details are on the pricing table and in billing and plans.

This section is practical guidance, not legal advice. Check what applies to your business and your visitors.

Whatever tool you use, you’re the one collecting these details, so you’re responsible for them. A few principles hold up in most places:

Ask clearly, and don’t pre-tick. Under the GDPR, a pre-ticked box doesn’t count as consent (Recital 32). DocBeam’s consent box is never pre-ticked, and the file doesn’t download until the visitor ticks it.
Say who’s asking. The visitor should know whose list they’re joining. DocBeam’s consent box names your site.
Have a privacy notice. Your site needs a privacy notice that explains what you collect through the gate, why, and how people can contact you.
Keep newsletters separate. Someone who wants your brochure hasn’t necessarily agreed to a weekly newsletter. If you want to add them to one, ask for that separately.
Don’t ask for sensitive information. A download gate is for an email address and maybe a name and company, nothing more personal than that.

Our Terms set out your responsibilities when you use lead capture, and our Privacy Policy explains how we handle visitor data on your behalf.

When not to gate a PDF

An email gate costs you some downloads, because some visitors will leave rather than give an email. That’s a fair trade for a valuable file, but for many documents it’s the wrong one. Leave these open:

Policies and legal documents, such as terms, privacy policies and returns policies. People need to read them before they deal with you, and putting them behind a form helps nobody.
Menus, timetables and opening hours. Nobody wants to give an email to see what’s for lunch.
Public reports, such as annual reports, impact reports and anything you’ve committed to publishing openly.
Documents for existing customers, such as manuals, onboarding packs and invoices. You already know who they are.
Anything you want found in search. Search engines can’t read content behind an email form, so a PDF you’re relying on for search traffic should stay open, or you could publish a summary page that links to it.

A good rule: gate the files that start a sales conversation, and leave open the ones that serve people who have already decided.

The Quick Version

Gating a PDF works best for files that show buying intent: brochures, price lists, white papers and capability statements.
A Webflow form that redirects to the file is free and simple, but it guards the page, not the file: Webflow asset links are public. HubSpot suits teams already on HubSpot, and Memberstack or Outseta suit ongoing members’ areas.
DocBeam puts the gate on the file’s own link. Switch on “Require email” for one document, and the link, your buttons and your pages all stay the same.
Don’t pre-tick consent, have a privacy notice, and leave policies, menus and public reports ungated.

If you also need somewhere to keep large PDFs, see How to Host a Large PDF on Webflow.

Ready to see who’s downloading your brochure? See how lead capture works, start on Starter, or compare the plans first.