Password-protected HTML hosting compared: Netlify, Vercel, Cloudflare Access, Tiiny Host, GitHub Pages

Quick answer

Convika password protects one HTML page for $5 paid once (30 days, the Pro pass) or $12 a month on Pro: choose “Only people with the password” as you publish, and Convika's server checks it before it sends the page. Netlify needs Pro at $20 a month. Vercel adds $20 a month per protected project to Pro's $20. Cloudflare Access emails each viewer a one-time PIN, free up to 50 users, and Tiiny Host starts at Solo, $18 a month.

Password protect my page

Pro pass: $5 once for 30 days, no renewal. Pro: $12 a month.

On this page

You have an HTML page, maybe a board report, a client proposal, or a tool Claude Code built, and only the people you hand a password to should open it. On Convika that is one choice in the publish dialog: upload the file, pick Only people with the password, type the password, and pay $5 once for 30 days. Convika's server checks the password before it sends any of the page, and each fix you publish goes live at the same link with the password still on.

That is all the setup there is. Each other way on this page needs one more thing: Netlify its Pro plan, Vercel Pro plus a charge for each protected project, Cloudflare an Access application and email PINs, Tiiny Host its Solo plan, GitHub Pages Enterprise Cloud, Basic authentication a server running Apache, and StatiCrypt a fresh encryption of the file on every update. Below are each host's plan, price, setup, and what your viewers do, from the host's own docs and pricing pages, read on November 18, 2026, between 13:33 and 13:41 JST. Each quote links to its page, and the sources list the date each page shows.

Password protection on 8 hosts: plan, price, and setup

HostPlan and price for a passwordSet up inWhat your viewer doesWhere the password is checkedAfter an update: link and password
ConvikaPro pass, $5 once for 30 days, no renewal; or Pro, $12 a monthThe publish dialog: upload the HTML file, choose Only people with the password, type itTypes the password once; that browser opens the page without asking again until 30 days pass without a visitConvika's server, before any of the page is sentSame link, password kept: each new version goes live where viewers already go
NetlifyPro, $20 a month (pricing); “isn’t available on Credit-based Free and Personal plans” (docs)Project visibility settings: choose Password, enter it, saveTypes a shared password into “a generic password prompt”Netlify: viewers “must know and enter a shared password to access the site deploy”The password covers “all versions of your site” with Production and previews
VercelPro, $20 a month, plus “$20 per month per protected project”; “Not available on Hobby” (docs)Project settings, Deployment Protection: turn on Require Password, enter it, save, confirm the chargeTypes the password; “a cookie is set in your browser for that deployment URL”Vercel: it “checks every request before it reaches your application”“existing and future deployments” keep the password
Cloudflare Pages or Workers + AccessNo shared password. Access: Free plan $0 with a “50 user limit”, then $7 per user a month, paid annually (Access)A Zero Trust organization (payment details even on Free), an Access application for the hostname, One-time PIN as a login method, each viewer's email in a policyEnters an allowed email address, gets a PIN by email, pastes it within 10 minutesCloudflare: it “checks every HTTP request to your application for a valid application token”The Access application stays on the hostname
Tiiny HostSolo, $18 a month or $156 a year; “Available on Solo and above” (help)Access gate at upload: Password protect, type it, PublishTypes the password on a password screenA password screen “in front of your project”“Your link name, QR code and custom domain all stay the same”
GitHub PagesNo password; private publishing needs GitHub Enterprise Cloud, Enterprise at $21 per user a month (pricing)Repository Settings > Pages: private visibility, in an organizationSigns in to GitHub with read access to the repositoryGitHub: only “people with read access to the repository”The same private *.pages.github.io address
Rental server, Basic authenticationComes with an Apache server you rent or runhtpasswd for a password file, .htaccess with AuthType Basic (Apache)Types a user name and password into the browser's sign-in boxYour web serverThe password covers the whole folder
StatiCryptFree, MIT License (GitHub)Encrypt the file on its web page or with npx staticrypt, then host the output anywhereTypes the password into the page's own promptIn the browser: “decryption happening in javascript client side”Encrypt each new version again and upload it

Convika: a password on one page, chosen as you publish

Convika hosts HTML pages, each at its own link, and the password belongs to the page. Upload the file on the dashboard with Upload an HTML file, or let Claude Code save it: run claude mcp add --transport http convika https://mcp.convika.com once, then ask Claude Code for a preview of the page. Click Publish page, and under Who can open this page? choose Only people with the password and type the password. Click Next, and the next button reads Pro pass: publish with a password, 30 days for $5. It is paid once at Stripe and doesn't renew, and the page goes live behind the password as soon as the payment goes through. Under it, Or subscribe to Pro monthly is $12 a month for a page that stays up. If you write within 14 days of paying for the pass, you get a full refund.

Your viewers see a password screen at the page's address, yourpage.convika.page or your own domain. That screen carries nothing from the page behind it: no title, no text, no script, and it tells search engines not to index it, while the page stays out of the address's sitemap. The right password opens the page, and that browser keeps opening it with no prompt; it asks again only after 30 days without a visit. Convika keeps only a salted hash of the password, never the password itself.

A fix is a new version of the same page. On the page's screen, Update from an HTML file takes the new file, and Publish v2 at the same link (the number counts up) puts it live where your viewers already go, password still on; until then they keep seeing the version before. To lock someone out, change the password under Page password in Page settings: everyone who entered the old one meets the password screen on their next visit, and the link stays the same. Each page has its own password, so a staff version and a client version of one tool can sit side by side. A form on the page sends entries to your dashboard and by email, from viewers who are past the password, and the visitor stats count each visit that gets past it.

Try it with your file now. Drop it into the box below for a free preview link; when you keep the page, you choose the password as you publish.

Netlify: Pro at $20 a month, one password for the project

Netlify's Password Protection docs (last updated October 7, 2026) say “Basic password protection for your entire site is available on all Pro plans” and “Password protection isn’t available on Credit-based Free and Personal plans.” Netlify's pricing page lists Pro at “$20 /month with unlimited members”. On Free and Personal, the docs offer a private project instead, and “a private project is visible only to the Team Owner.”

On Pro, the password lives in the project's visibility settings: Project configuration > General > Visitor access > Project visibility, then Edit visibility, Password, the password, and Production and previews to cover the live site as well as previews. The password covers the whole project, and Netlify sets one per project: “There is not an option to set a default shared password. You will need to set a password per project instead.” Visitors meet “a generic password prompt” and “must know and enter a shared password to access the site deploy.”

For one folder instead of the whole site, a Basic-Auth rule in a _headers file asks for a password on the URLs under it. Netlify's Basic authentication doc says “This feature is available on all Pro and Enterprise plans.” Netlify's free plan, in full covers what Free includes.

Vercel: $20 a month per protected project, on top of Pro

Vercel's Deployment Protection docs (last updated September 15, 2026) list Password Protection as “Available on Pro for $20 per month per protected project and included on Enterprise at the team level. Not available on Hobby.” Vercel's pricing page shows Pro at “$20 /mo.” and Password Protection at “$20 / project / month”, so one protected project runs $20 for Pro plus $20 for the password, each month.

The Password Protection doc gives the steps: in the project's Deployment Protection settings, “turn on Require Password, choose which deployments to protect, enter a password, and select Save. If your Pro team pays per project, confirm the $20 monthly charge.” From then, “All your existing and future deployments will be protected with a password for the project”, and after a viewer enters it, “a cookie is set in your browser for that deployment URL.” On Hobby, the doc points to Vercel Authentication, which “asks visitors to log in with a Vercel account that has access, instead of entering a password.”

Cloudflare Pages and Workers: Access, with a PIN by email

Cloudflare Pages' own access setting doesn't cover the live site. Its preview deployments doc (last updated October 12, 2026) says enabling it “will only protect your preview deployments … and not your *.pages.dev domain or custom domain.” For the live site you put Cloudflare Access in front of it, and there is no shared password: each viewer proves an email address.

The one-time PIN doc (last updated August 31, 2026) describes what a viewer does. On the Access login page they “enter your email address and select Send login code”, and “If the email is allowed by an Access policy, you will receive a PIN in your inbox. This secure PIN expires 10 minutes after the initial request.” To let someone in, you “add their email address to an Access policy.”

The setup takes four parts:

  • A Zero Trust organization. Cloudflare's setup doc (last updated October 12, 2026): “Complete your onboarding by selecting a subscription plan and entering your payment details. If you chose the Zero Trust Free plan, this step is still needed but you will not be charged.”
  • An Access application for the hostname. For a pages.dev address, Pages' known issues (last updated November 6, 2026) give the steps: Enable access policy in the project's settings, then edit the Access application and delete the wildcard from its subdomain so it covers the production address. A custom domain gets its own application: Zero Trust > Access controls > Applications > Create new application > Self-hosted and private. On Workers, Access can protect “one Worker's production workers.dev URL, preview URLs, or both.”
  • One-time PIN as a login method. “OTP is no longer added automatically”: add it under Zero Trust > Integrations > Identity providers > Add new identity provider > One-time PIN.
  • A policy with each viewer's email address.

Cloudflare's Access page lists the Free plan at “$0 forever” with a “50 user limit”, “Best for teams under 50 users”, and Pay-as-you-go at “$7 per user/month (paid annually)”.

Tiiny Host: Solo at $18 a month

Tiiny Host's help article How to password protect your project (updated November 10, 2026) opens with “Available on Solo and above.” Its pricing plans article (updated October 20, 2026) lists Solo at $18 a month or $156 a year.

You set the password as you upload: open the Access gate dropdown, choose Password protect, type the password, and click Publish. For a live project, it's Update > Customize project > Access Settings > Access Mode > Password Protect. Changing the password works the same way, and “Your link stays the same.” A new upload keeps the address too: “Your link name, QR code and custom domain all stay the same when you update a project,” per If I update a project, does the link change? The article adds that password protection “works for websites, PDFs, presentations and portfolios, but not for projects that run server code, like PHP, Python, Node.js or React apps.”

Custom domains start on Solo too: “Available on Solo and above. Solo includes 5 domains,” per Tiiny Host's custom domain article (updated November 13, 2026). The rest of Tiiny Host's plans are in Tiiny Host's free plan, compared.

GitHub Pages: private sites on GitHub Enterprise Cloud

GitHub's doc Creating a GitHub Pages site warns: “GitHub Pages sites are publicly available on the internet, even if the repository for the site is private.” Keeping a site to some people takes private publishing, and per About privately published GitHub Pages sites, “To publish a GitHub Pages site privately, your organization must use GitHub Enterprise Cloud.” Then “A privately published site can only be accessed by people with read access to the repository the site is published from.”

That means every viewer needs a GitHub account with access to the repository, in an organization on Enterprise, which GitHub's pricing page lists at $21 per user a month. GitHub's limits doc adds that Pages sites “shouldn't be used for sensitive transactions like sending passwords or credit card numbers.” The plan-by-plan details are in Can you use GitHub Pages with a private repo for free?

A rental server with Basic authentication

If you already rent a server that runs Apache, Basic authentication costs nothing extra. Apache's authentication guide makes a password file with htpasswd -c /usr/local/apache/passwd/passwords rbowen, and says the file “should be placed somewhere not accessible from the web.” An .htaccess file in the folder you protect then reads:

AuthType Basic
AuthName "Restricted Files"
AuthBasicProvider file
AuthUserFile "/usr/local/apache/passwd/passwords"
Require user rbowen

The server has to allow it with AllowOverride AuthConfig. Viewers get the browser's own sign-in box, and the guide warns that “Basic authentication sends the password from the client to the server unencrypted,” so the site needs HTTPS (“unless accompanied by mod_ssl”). The password covers the folder, so a new file you upload there is protected the moment it lands.

StatiCrypt: encrypt the file, decrypt it in the browser

StatiCrypt is free under the MIT License. Its README: “StatiCrypt uses AES-256 and WebCrypto to encrypt your HTML file with your long password, and returns a static HTML page showing a password prompt that you can now safely upload anywhere.” You encrypt “online in your browser (client side)” or run npx staticrypt in a terminal, then host the output file anywhere.

The whole encrypted page sits in that file, so the README asks for a strong password: “Because your full encrypted file is accessible client side, brute-force/dictionary attacks would be easy to do at a fast pace: use a long, unusual password. We recommend 16+ alphanum characters.” Each edit means encrypting the new file and uploading it again.

A password in JavaScript is readable in the source

The snippet most tutorials show compares what the visitor typed with a password written inside the page:

<script>
  var password = prompt("Enter the password");
  if (password !== "letmein") {
    document.body.innerHTML = "Wrong password";
  }
</script>

The browser downloads the whole file before that script runs, so the password and the text it hides are already on the visitor's computer, one View Source away. In Convika's test on October 13, 2026, a page with this snippet, fetched with curl, returned both the password and the sentence the script was meant to hide. MITRE files the mistake as CWE-602, Client-Side Enforcement of Server-Side Security.

A password holds only when a server checks it before sending the page, as Convika, Netlify, Vercel, Cloudflare Access, and Basic authentication do, or when the page is encrypted, as StatiCrypt does. How to password protect an HTML page walks through each method.

Password protect an HTML page on Convika in 5 steps

Upload the HTML file

Sign up at app.convika.com with no credit card. Click Upload an HTML file, drop the file onto Upload a file or paste the code under Paste code, and click Create my preview. From Claude Code, run claude mcp add --transport http convika https://mcp.convika.com once and ask for a preview of the page instead.

Choose the password as you publish

Click Publish page. Under Who can open this page?, choose Only people with the password, type a password of 8 to 128 characters, and click Next.

Pay once for the Pro pass, or subscribe to Pro

Click Pro pass: publish with a password, 30 days for $5: paid once at Stripe, no renewal. For a page that stays up, click Or subscribe to Pro monthly, $12 a month. The page goes live behind the password once the order goes through. Already on Pro, the dialog's button reads Publish with password.

Email the link and text the password, or post the link in the team channel and give the password in person. Anyone who has only the link meets the password screen.

On the page's screen, use Update from an HTML file, then Publish v2 at the same link (the number counts up). The password stays on, and your viewers open the new version at the link they already have.

Skipbox

Cheap & fast GitHub Actions runners, unlimited for $39 a month

Your own machine keeps Docker layers and package caches between jobs. Switch by changing one runs-on line.

Start a free Skipbox trial⁠

Frequently asked questions

Does Netlify password protection work on the free plan?

No. Netlify's docs, last updated October 7, 2026, say “Password protection isn’t available on Credit-based Free and Personal plans” and that it is “available on all Pro plans”, which Netlify's pricing page lists at $20 a month. On Free, the alternative is a private project, “visible only to the Team Owner.” On Convika, a password on one page comes with the Pro pass, $5 once for 30 days.

Is Vercel password protection free?

No. Vercel's docs, last updated September 15, 2026, say Password Protection is “Available on Pro for $20 per month per protected project” and “Not available on Hobby”, and Pro itself is $20 a month. Hobby has Vercel Authentication, where visitors log in with a Vercel account instead of typing a password. Convika puts a password on a page with the Pro pass ($5 once for 30 days) or Pro ($12 a month), with no charge per page.

Can I put a password on a Netlify Drop site?

No, not one you choose on Netlify's free plan. Netlify's Drop quickstart, last updated July 28, 2026, says that if you drop without signing in, “your project URL is protected with a temporary password until you claim it”; a shared password of your own needs Netlify Pro. On Convika, drop the HTML file into the upload box, then choose Only people with the password as you publish.

Can GitHub Pages be password protected?

No. GitHub's docs say “GitHub Pages sites are publicly available on the internet, even if the repository for the site is private.” The way to limit who opens a site is private publishing on GitHub Enterprise Cloud ($21 per user a month), and then only “people with read access to the repository” get in, each with a GitHub account. To put a password on the same HTML, publish it on Convika with Only people with the password.

Can Cloudflare Pages be password protected?

No, not with a shared password. Pages' own access setting “will only protect your preview deployments”; for the live site, Cloudflare Access emails each allowed viewer a one-time PIN that “expires 10 minutes after the initial request.” Access's Free plan has a “50 user limit”, and setting up the Zero Trust organization asks for payment details even on Free. Convika gives the page one password that you send to whoever needs it.

Does Tiiny Host support password protection and custom domains?

Yes, both from Solo, $18 a month or $156 a year. Tiiny Host's help says password protection is “Available on Solo and above” and that “Solo includes 5 domains.” Convika puts a password on a page from $5 once with the Pro pass, at yourpage.convika.page or your own domain.

Is a password written in JavaScript safe?

No. The password and the text it hides arrive in the same file, so View Source or curl shows both, as Convika's test of October 13, 2026 found. A password holds when a server checks it before it sends the page, as Convika does, or when the file is encrypted with a tool such as StatiCrypt.

Do I set the password again after I update the page?

No. On Convika, a new version published with Publish v2 at the same link keeps the page's password and its link, so your viewers open the fix with the browser they already unlocked.

Can each page have its own password?

Yes, on Convika each page has its own password, set when you publish it or changed later under Page password in Page settings. Netlify sets one password for a whole project, and Vercel charges for each protected project.

Do viewers type the password every time they open the page?

No. On Convika, a browser that entered the right password opens the page with no prompt, and asks again only after 30 days without a visit, so people who use the page often type the password once. Changing the password signs everyone out at once.

Sources

Read on November 18, 2026, 13:33 to 13:41 JST (04:33 to 04:41 UTC). Dates in parentheses are the page's own.

Next step

How to share an HTML file as a link that opens on any phone

Upload the file to a host and send its link; email and Google Drive send the code. 8 hosts compared, from Convika to Netlify Drop, with 4 steps.

Related articles

Compare with other hosts

Share this article

Put a password on your HTML page today

Upload the file, choose “Only people with the password” as you publish, and send the link. Convika's server checks the password before it sends the page.

Password protect my page

Pro pass: $5 once for 30 days, no renewal. Pro: $12 a month.