Skip to content

PICO-8 web export: the page and its JavaScript travel together

Package a PICO-8 HTML player with its companion JavaScript, and distinguish a hosted build from a local preview.

← All guides
Two folded-corner file outlines connected by two horizontal lines.
Two folded-corner file outlines connected by two horizontal lines.. Original editorial diagram by PixelGamesHub; not a game screenshot.

A playable link needs its companion file

The PICO-8 manual documents EXPORT MYGAME.HTML as producing an HTML player and a JavaScript file. Think of them as one delivery: the page provides the entry point, while its companion contains what that player needs to run.

For example, if you send only mygame.html to a tester, the missing companion can prevent play even though the HTML opens. Record which files you delivered before diagnosing the game's controls or rewriting a scene that never loaded.

A folder makes the handoff clearer

The documented -f option exports into a folder and uses index.html as the page name. That gives a small project a clear package boundary: distribute the folder's contents together instead of selecting a single attractive-looking file.

For itch.io, the manual describes zipping the export folder and marking the upload as browser-playable. Our discussion follows those documented steps; it does not claim that we exported or uploaded a PICO-8 cartridge for this article.

Hosting and mobile are separate checks

A public page opening is only the first check. Start the game from a fresh visitor session, try the stated inputs, and verify that the files loaded from the intended build rather than an older local copy.

The manual separately notes that a WebAssembly export must be served from a web server. Do not infer from one local-file failure that every web export is broken, or that a host's mobile-friendly switch proves the game's actual touch controls work.

Keep a build record

Keep the source cartridge, export date, filenames and public play URL in your release notes. If a tester reports a blank player, those details distinguish a packaging problem from a game-state bug.

The adjacent cartridge-image guide explains why a cart PNG is another kind of deliverable. Use our pixel editor for original visual assets and their previews; it does not compile Lua, generate a web player, or upload your exported package.

Official references

References checked: . Original editorial diagram by PixelGamesHub; not a game screenshot.

Put it into practice

Check the editorial standards, then prepare your submission. Signing in is required to submit; reading and browsing stay open.

Submit a game See how it works