Skip to main content
A playtest lets a chosen group of players install a build of your game on XBOX consoles and PCs, before or after release, without certification or a Microsoft Store listing. This page takes you from uploading a build to sharing the playtest with testers. Playtest overview explains how playtests work. Most commands on this page are Experimental, so their options and output might change. See Experimental commands.

Before you begin

  • A Partner Center account set up to develop XBOX games, with a game in it. Playtests need no separate access request.
  • Age ratings for the game. Complete the International Age Rating Coalition (IARC) questionnaire once, on the game’s Age ratings page in Partner Center. A playtest can’t be published without them.
  • Permission to manage the game’s packages in Partner Center. Without it, the package and playtest commands fail with 403 package_permission_denied. Ask a manager of your Partner Center account for it, or pass --seller-id if the game belongs to another seller.
  • Sign in with xbox auth login, and choose a seller, as in Getting started.
A playtest runs in the RETAIL sandbox. If the build uses XBOX sign-in or other XBOX services, follow Use XBOX services in a playtest first. The examples use the Store ID 9N0000000000. Find your game’s Store ID with xbox game list --output table.

1. Upload a package

The CLI doesn’t upload packages. Upload the build with makepkg from the October 2026 XBOX Game Development Kit (GDK) or later. For a PC game whose build is in the layout folder:
The makepkg reference covers the other package formats. Partner Center then processes the package, which can take a while. To check on it:
The package is ready when STATE is Processed and PLAYTEST is true. Note its PACKAGE ID. The table doesn’t show validation results, so check in JSON that its validationItems contain no item with severity Error:
If STATE is ProcessFailed, PLAYTEST stays false, or there’s an Error item, check the package requirements in Prerequisites for a playtest.

2. Create an audience

An audience decides who can install the playtest. Partner Center calls it a customer group. In Partner Center’s Apps and games workspace, select Customer groups, then Create new group. Choose Known user group, add your testers, and save it. Or list your testers’ email addresses in testers.txt, one per line, and create it with the Experimental audience create command:
Note the audience’s id for when you add it to the playtest.

3. Create the playtest

If you created the audience with audience create, use the id it printed. If you created the group in Partner Center, find its ID:
If xbox audience list times out, a known issue, leave out --audience-id when you create the playtest. Afterward, in Partner Center, open the playtest from the game’s Playtest page under Services, choose the group from step 2, and save it without publishing. Create the playtest:
  • --pc-package-id takes the package ID from step 1. Use --console-package-id for a console package.
  • --audience-id takes the audience’s ID. Repeat it to add more audiences.
  • Testers can install the playtest from --start until --end. A date without a time means midnight UTC.
The command asks before it creates the playtest, then prints it as JSON. Note the playtest’s ID, which is playtestId under details. If the command exits with 3, it couldn’t tell whether the playtest was created. Retry with the command it prints, which won’t create a second playtest.

4. Publish it

Publish the playtest with the ID from step 3:
The command waits until the playtest is Live, or Scheduled if its start date hasn’t come yet, and exits with 0. Other exit codes mean the playtest isn’t published yet: See Publishing a playtest.

5. Share it

Once the playtest is live, testers in its audience can find it in their library:
  • On a console, in Full Library, under the Playtest filter.
  • On a PC, in the XBOX app’s Library, under the Access filter.
Newly added testers need to sign out and back in first. You can also send testers a link. On the game’s Playtest page in Partner Center, select Share on the playtest, and copy the link, which starts with msxbox://playtest/. The CLI can’t show this link yet. It works only for people in the playtest’s audience, and on a PC it opens the playtest in the XBOX app. See Share a playtest with testers.

Scripts and continuous integration

You can upload packages from continuous integration (CI) pipelines with a service principal. See Uploading packages. The xbox package and xbox playtest commands don’t accept a service principal yet, so they need a signed-in user. See Automation (service principal) authentication. In a script that runs while you’re signed in, pass --confirm to playtest create and playtest publish, because without a terminal they can’t ask you, and make no change. Read the JSON they print, and check their exit codes. To wait longer than 5 minutes for a publish, pass --timeout.
Last modified on November 18, 2026