How to password-protect a web page you want to share
You want to share a page — a proposal, an internal doc, a draft — but only with the right people. Putting it behind a password sounds simple, and it can be, but the “right” way depends on whether you’re a developer, what you’re protecting, and how much you want to know about who opened it. Here are the real options.
Your options, from most to least technical
1. Your host’s password feature
Platforms like Vercel and Netlify can put a password in front of a deployed site — but it’s a paid-plan feature, and you still need a project and a deploy step to get the page up in the first place. Good if you’re already hosting there; heavy for a one-off.
2. Basic auth / .htaccess
On your own web server you can add HTTP basic authentication (an .htaccess file and a password file). It’s genuinely a real password and free if you already run a server — but it’s a developer task, easy to misconfigure, and gives you no analytics.
3. An “unguessable” link
Sharing a long, random URL is technically not a password at all — it’s security by obscurity. It keeps a page out of search results and away from casual visitors, but anyone the link reaches can open it, and links leak through forwarding, history, and referrers. Fine for low-stakes things; not for anything sensitive.
4. A purpose-built sharing tool
Tools like Shareable are built for exactly this: paste the HTML, choose a password, and share. No server, no paid tier, no code. And because it’s built for sharing, you also get options a raw password can’t give you — invite specific people by email, or require any viewer to verify one, so each visitor is identified and you can see who opened it.
Side by side
| Host password | Basic auth / .htaccess | Unguessable link | Shareable | |
|---|---|---|---|---|
| Real password | Obscurity only | |||
| No coding / server config | ||||
| Free | Paid tier | Your server | ||
| Identify each viewer | Email / invite | |||
| View analytics |
◑ = depends on your setup. Host pricing tiers change; check current plans.
Password, or something better?
A shared password is the right tool when everyone should have the same access and you don’t care who’s who. But if you want to revoke one person, see who viewed the page, or stop a password from being forwarded, inviting people by email beats a shared secret — every viewer is identified, and you can tell exactly who opened it.
Frequently asked questions
Can I password-protect a web page for free?
Yes. Developer hosts like Vercel and Netlify charge for password protection on paid plans, but a sharing tool such as Shareable includes a page password on its free tier — along with other access modes like inviting specific people or requiring a verified email.
Is an unguessable link as safe as a password?
No. A long random URL hides a page from search engines and casual discovery, but anyone the link is forwarded to can open it, and it can leak through browser history, chat apps, or referrer headers. For anything sensitive, use a real password or invite specific people.
How do I password-protect a page I made with ChatGPT or Claude?
ChatGPT and published Claude artifacts have no password option. Export the page’s HTML and host it on a tool with built-in access control like Shareable, where you can set a password (or restrict it to specific people) in a couple of clicks.
Can I give different people different levels of access?
A single shared password treats everyone the same. If you need to know who’s who — or revoke one person — invite people individually by email or require each viewer to verify an email, so every visitor is identified rather than sharing one secret.
What’s the easiest way to password-protect a shared page?
Host the page on a sharing tool with a built-in password. With Shareable you paste the HTML, choose the password option, and share the link — no server config, paid plan, or code required.
Share your next AI-made page in seconds
Paste the HTML or publish from your AI — get a link with access control, analytics, and a heads-up when it’s opened.