Uploading from the command line, and test branches

The upload tool

Open My games, then Upload tool. Download the tool, create an upload token, and run the command shown there with your game's id and the folder that holds index.html. It needs Node.js 18 or newer.

• Only files that changed since your last checked version are sent, so a small change to a large game takes seconds.
• The new version goes through the same malware scan and start-up check as any upload.
• Add --wait to wait for the checks, --no-publish to check without going live, --windows file.zip for a download.
• You give the tool your token once per terminal window, with the first line of the example on the Upload tool page, and then run the upload command. On a build server, store the token as a secret named GAME_UPLOAD_TOKEN.
• You do not need the tool: the upload page on each game does the same in the browser.

Upload tokens

A token lets the tool list your games, upload versions of them and move test branches. A version uploaded with the tool goes live when its checks pass, unless you add --no-publish or --branch. A token cannot sign in, change settings or reach your money, and signing out of all devices ends your tokens too. It is shown once. Revoke a token you no longer use, or one that may have been seen by someone else.

Test branches

A branch is a named link to one version, such as beta. Give the link to your testers. When you point the branch at a newer version, copy the new link from the Release tab: the old one stops working, so testers cannot stay on an old build by accident. Removing a branch ends its link. Set branches on the game's Release tab, or upload straight to one with --branch beta.

Anyone who has a branch link can play that version, also when the game has a price, so share it only with people you trust.