How to Password Protect
a Framer Page
Learn how to add real, server-side password protection to any Framer page in under 2 minutes. No coding required.
Why You Need Real Password Protection
Most Framer password components are completely insecure
JavaScript Protection
- Content visible in page source
- Bypass with browser DevTools
- Disable JavaScript to view
- Password stored client-side
PageLock (Server-Side)
- Content on hidden server URL
- Cannot be bypassed by disabling JS or View Source
- No content until authenticated
- Secure server validation
Step-by-Step Guide
Password protect your Framer page in 5 simple steps
Create a Free Account
Sign up at proofly.ae. No credit card required. Free plan available forever.
Create a Page Lock
In your dashboard, create a new lock. Choose password, email, or PIN protection.
Run on Your Page
Open your Framer project, run the plugin, and select the page to protect.
Publish & Done
Publish your site. Your page is now protected with real server-side security!
PageLock vs Framer's Built-In Password Protection
Framer ships with site password protection. For some sites it is enough. Here is where it stops.
Framer built-in password
- Covers the whole site, not individual pages
- One shared password for every visitor
- No per-page or per-client control
- No member accounts or email logins
PageLock
- Lock individual pages while the rest stays public
- Different credentials per page or per client
- Password, PIN, or email OTP login per lock
- Multiple users per lock, revocable any time
The built-in option is the right call when your entire site is private and one shared password for everyone is acceptable, for example a site that is still in production. It becomes the wrong tool the moment your marketing pages must stay public while a proposal, portfolio piece, or client area needs a gate, because Framer's password covers everything or nothing. PageLock works at the page level: your homepage stays indexed and public while /proposal-acme asks for a password, and each client can have their own credentials you revoke when the project ends.
Choosing an Authentication Type
Every lock can use one of three login methods. Pick by audience, not by taste.
Password
The classic. One shared secret you send to your audience. Best for client previews and internal pages where rotating a single password now and then is fine. Credentials are stored as salted hashes on Proofly servers, never in the page itself.
PIN
A short numeric code entered on a keypad. Fastest to type on a phone, which makes it popular for event pages and gated downloads shared over chat. Same server-side verification as passwords, just a friendlier input.
Email OTP
Visitors enter their email address and receive a one-time code. No shared secret to leak: access follows the inbox. This is the closest thing to a light Framer membership flow without running a membership platform, and it gives you a record of who requested access.
Multiple users per lock
A single lock can hold several users, each with their own credential. Onboard a new client contact or revoke a departed one without touching anyone else's access.
Beyond One Page: CMS Locking, Member Areas, Paywalls
Password protecting a single Framer page is the starting point. The same server-side gate extends to the rest of your site as it grows.
Framer CMS locking
PageLock can protect dynamic CMS collection pages, not just static ones. That means a whole set of gated content in Framer, like course lessons or client deliverables stored as CMS items, sits behind one login.
Member areas and client portals
Combine locked pages with per-user credentials and you have a working member area or client portal without an external platform. See the guides to member areas in Framer and client portals in Framer.
Simple paywalls
A paywall is a gate plus a way to hand out credentials after payment. Many creators sell access through their existing checkout (Stripe payment links, Gumroad, Lemon Squeezy) and deliver a PageLock password or OTP access on the confirmation page. The content itself stays server-side protected in Framer.
Cost and limits
PageLock is free on Framer staging domains, so you can build and test the whole flow before paying anything. Locking a custom production domain needs a paid plan; see pricing for live plans, and the PageLock product page for the full feature list.
Common Questions
Is PageLock really secure?
Yes. Unlike JavaScript solutions, PageLock uses server-side protection. The protected content is removed from your published page and stored on Proofly servers, so the page visitors load contains only the login form. There's nothing to bypass because the content isn't in the page, and after a visitor logs in the server returns the content only for that authenticated session. Credentials are stored as salted hashes.
Do I need to know how to code?
No coding required. The entire process is point-and-click through our dashboard and Framer plugin.
How much does it cost?
PageLock is free on Framer staging domains. To lock a custom production domain, upgrade to a paid plan. See current pricing for live plans and prices.
Does it work with custom domains?
Yes! PageLock works with any Framer site - custom domains or framer.website subdomains.
Keep reading
Ready to set it up? Head to the PageLock product page for features and pricing. Wondering why a plugin beats hand-rolled code? Read PageLock vs custom JavaScript. Building something bigger than a single page? See the guide to member areas in Framer.