Guides

Deploy a plain HTML/JS game

Vanilla HTML, JavaScript, and canvas/WebGL games work as-is — zip and drop, no build step required.

A plain front-end app — handwritten HTML, JavaScript, and assets, or a canvas/WebGL game — is the easiest case. There’s nothing to build and usually nothing to configure.

Use relative paths

As long as your index.html references assets with relative paths, it’ll work at any URL:

<link rel="stylesheet" href="style.css" />
<script src="game.js"></script>
<img src="sprites/player.png" />

Avoid leading slashes (/style.css), which assume the domain root. If you’ve already got root-absolute paths, don’t worry — App To Page rewrites them on upload — but relative is cleanest.

Zip and drop

  1. Make sure index.html is at the top level of your folder.
  2. Zip the folder’s contents.
  3. App To Page → Apps → drop the zip → pick a URL like /snake → Create draft.
  4. Preview to play-test it privately, then Publish.

Your game is live at your-site.com/snake, running standalone with no theme styles bleeding in.

What’s supported

App To Page serves the file types games actually use, with the right content types — including wasm, fonts, audio, and 3D formats (stl, glb, gltf). Hashed asset files are cached aggressively, so repeat loads are fast.

Big game? The entry HTML is revalidated on each load while immutable hashed assets are cached long-term, so updates show up without players hard-refreshing.