Private Page

[async1551]

Select Topic Area

Question

Body

I have created a github.io page, and I want it for completely personal use, can I somehow make the source page proprietary and only I can see it? But at the same time the site works

[akilapilapitiya]

You can 2 repos
A private repo which maintains your code so can you can see and edit.

A public repo like username.github.io which has only the final output.

You build in you private repo, use GitHub actions to transfer build to public repo

[async1551]

I want my username.github.io code to be private, is that possible? Στις Τρί 24 Ιουν 2025, 5:24 π.μ. ο χρήστης Akila Pilapitiya < ***@***.***> έγραψε:

…

You can 2 repos A private repo which maintains your code so can you can see and edit. A public repo like username.github.io which has only the final output. You build in you private repo, use GitHub actions to transfer build to public repo — Reply to this email directly, view it on GitHub <#163884 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BO3TPYM4TISYDSGT3WY3LSD3FCZEJAVCNFSM6AAAAAB763TKI2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNJVGY3TINA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[akilapilapitiya]

If you have a GitHub Pro account, you can.

[Khushil-21]

Unfortunately, GitHub Pages sites must be public if they're using the free GitHub plan. GitHub requires the repository to be public in order to serve the website. If you try to make the repo private, the site will stop working.

✅ Solution Options

1. Upgrade to GitHub Pro
   If you upgrade to GitHub Pro, you can:

Make the repository private

Still use GitHub Pages to serve your site

👉 GitHub Pro pricing and features

2. Host Your Site Elsewhere
   If you want the code to stay private and don't want to upgrade, consider:

Hosting your static site on Netlify, Vercel, or Cloudflare Pages

You can deploy from a private GitHub repo with those services

🔒 Summary
Free GitHub Pages = must be public

Private GitHub Pages = requires Pro

Alternatives = use other hosting platforms

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[PRIYAtechky]

GitHub Pages requires the source repository to be public, which means anyone can technically view your code if it’s hosted there. If you want your site to remain personal/private while still working:

Options

• Option 1: Private repo with GitHub Pages (paid plans)
  With GitHub Pro or GitHub Team/Enterprise, you can publish GitHub Pages from a private repo.
  ➝ The site will still be public, but your source code stays private.

• Option 2: Deploy elsewhere
  If you want both the site and source code to remain private, host it on another platform such as Netlify, Vercel, or AWS S3. These allow you to keep your repo private while still serving the site.

• Option 3: Access restriction
  If you only want yourself (or specific people) to view the site, deploy it with GitHub Pages but add authentication (e.g., Cloudflare Access, Nginx password protection, Netlify Identity).

---

🔑 In short:

• Free GitHub Pages → repo must be public.
• Paid plan GitHub Pages → repo can be private, but the site is still public.
• For completely private access, use another hosting service with authentication.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬