My Games
←back to documentation

My Games

Create, organize, collaborate on, and publish your Portals games.

Publish Your Game

Publishing makes a player-facing version of your game available. Treat it as a release step, not the first time you check whether the game works.

Before you publish

Complete a player test from the beginning of the game:

  1. Join at the intended spawn point.
  2. Follow the main path without builder knowledge.
  3. Try every portal, goal, and reset path.
  4. Check that any score or leaderboard behavior matches your game’s rules.
  5. Ask a second person to try it without instructions if possible.

If anything is unclear, fix it in the working game and test again.

Prepare the player-facing details

In the game’s settings in My Games, make the basics clear:

  • Title — say what players are opening.
  • Description — explain the activity or goal in plain language.
  • Thumbnail — choose an image that shows the game’s real experience.
  • Visibility and release details — review these before the game goes live.
  • Player support — declare singleplayer or multiplayer, with the max player count and competitive/co-op mode for multiplayer. Publishing requires it, and parties find multiplayer games through it; see Declare player support.

Avoid promising a feature players cannot reach in the current version. A short, honest description is more useful than a list of ideas you plan to add later.

Publish the tested build

Open the game from My Games, review its settings, then use the publish or production release control for that game. Wait for the release process to finish before testing the player-facing destination.

Verify after publishing

  1. Open the game as a player in a fresh browser session.
  2. Confirm the title, thumbnail, and first player experience are correct.
  3. Complete the most important interaction or loop.
  4. Keep the working game as the place to make and test the next change.

Updating a live game

Build and test changes before you make another release. If the update changes a player’s route, spawn, or rules, repeat the full player test rather than checking only the item you changed.

See First-game checklist for a release-ready test list.