Frequently asked questions
Short answers about GitSnap. The deep-dive pages below cover the same ground in more detail.
Do I need a paid GitHub plan to publish from a private repository?
No. GitHub Pages requires a public repository or a paid plan, but GitSnap reads the files you select through your own GitHub authorization and serves a snapshot of them, so the repository can stay private on a free plan.
Do viewers need a GitHub account?
No. A published link opens in any browser. Only links you restrict to email addresses or company domains ask viewers to identify themselves.
Does GitSnap publish my whole repository?
No. You tick individual files. Anything you did not tick is never copied and never served.
Which file types work?
HTML pages together with their CSS, JavaScript, images, fonts and other static assets render as a web page. Other files can be published as assets referenced by your pages.
Do published pages update when I push to the repository?
No, and that is deliberate. Snapshots are immutable, so nothing you push later leaks out. Press Update snapshot in your dashboard when you want viewers to see newer content; the link stays the same.
Can I revoke a link?
Yes. Every link has an instant off switch, and deleting the publication removes the snapshot entirely.
Can I limit a link to my client's company?
Yes. A link can be restricted to specific email addresses, to whole domains, or both.
Can I see who opened a link?
Each link keeps a view log in your dashboard, so you can confirm the recipient opened it and notice access you did not expect.
Will my published pages show up in Google?
Published links carry a random suffix and are never listed in the sitemap or any public index on this site. Only the marketing and policy pages are offered to search engines.
Can I revoke GitSnap's access to GitHub?
Yes, from your GitSnap dashboard or from GitHub's own applications settings. Existing snapshots stay published until you disable or delete them.