Choose a static host
A static host serves files such as HTML, CSS, JavaScript, images, and audio. Choose a provider that supports your project size, file types, bandwidth needs, and terms. Check its current limits before moving a large game library; limits and dashboards change over time.
Connect a domain you control
- Add the domain in the hosting provider’s domain settings and follow its ownership check.
- At your DNS provider, add only the records the host specifies. The required record type and target depend on that host.
- Keep existing mail and verification records unless you know they are no longer needed.
- Wait for DNS changes to propagate, then enable the host’s HTTPS certificate.
Use relative links and test both entry points
Links such as games.html and games/sample-game/index.html usually survive a domain change. Hard-coded links to an old host do not. Search the project for the old hostname before switching, then test the root page, nested pages, game assets, sign-in, and any connected services on the new address.
Keep a recoverable copy
Keep a local copy of the source and assets, plus a separate backup of the repository history if you use Git. Confirm that large files and Git LFS objects are included in the backup. A deployment is not a backup, and a Git remote is not the only place to keep project files.