> ## Documentation Index > Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt > Use this file to discover all available pages before exploring further. # Use Playtest during Preview > Set up and run prerelease XBOX playtests during Preview: request access, create audience groups, distribute packages, and share deep links with testers. Playtest is in **Preview**. The Preview supports prerelease games on XBOX for PC. Capabilities, requirements, and the Partner Center experience might change before general availability (GA). To join the Preview, contact your XBOX representative or request access from the Playtest landing page in Partner Center, located under **Services** in the product-level left navigation. This article explains how to use the capabilities available during Preview. For the long-term product vision, see [Playtest overview](/publishing/game-publishing/concepts/playtest). Playtest is a publishing flow in Partner Center that enables prerelease game content to run on XBOX endpoints for a controlled audience of players. You can run a playtest without certification, a product details page (PDP) in the Microsoft Store, or a generally available product. Although a playtest removes most standard retail publishing requirements and makes publishing fast and easy, a few requirements still apply, most notably, the game the playtest is associated with must have valid [age ratings](/publishing/game-publishing/concepts/age-ratings). Playtest is built for studios that need to put in-development builds in front of real players, on real XBOX hardware, in a controlled and revocable way. Typical scenarios include: * Internal QA across distributed teams. * Closed playtests with selected partners, press, or invited communities. * Replacing sandbox-based workarounds, duplicate "test" products, or testing flows that live outside the publishing pipeline. During Preview, Playtest is only available for XBOX on PC. XBOX console support is planned for Fall 2026. This article provides information about: * What you can do with Playtest * How to enable and create a playtest * How to manage and update a playtest * How a playtest interacts with your game's XBOX services. For answers to common questions, see [Frequently asked questions](#frequently-asked-questions). ## What you can do during Preview Using Playtest in Partner Center, you can: * Create, edit, publish, and shut down playtests. * Distribute prerelease packages. * Packages are encrypted and licensed independently of your main game and don't affect the game you prepare for release. * Control playtest access by using **audience groups**, so only invited players can install and play the build. * Share the playtest with testers by using a **deep link**. * Iterate without disruption: update the package, playtest dates, or audience, and publish changes without recreating the playtest or inviting testers again. * Run multiple playtests simultaneously for the same product. ## Get started Before you can create your first playtest, you must: * Request Preview access in Partner Center. * Review the prerequisites for a playtest. ### Request access to Playtest in Partner Center Preview access is approved at the Partner Center account level. To request access: 1. Sign in to Partner Center. 2. Select the **Apps and games** workspace. 3. Select a game product. 4. In the product-level navigation, expand **Services**, and then select **Playtest**. 5. On the Playtest landing page, submit your access request. After your request is approved, the **Playtest** page displays the playtest gallery and options for creating and managing playtests. ### Prerequisites for a playtest Before you create a playtest, make sure that: * Your Partner Center account is approved for Playtest Preview access. * You create an XBOX **Game** in Partner Center. For more information, see [Create a game and configure game setup](/publishing/game-publishing/tutorial-xbox-managed/how-to-create-a-title-and-configure-game-setup). * You complete the **age ratings** module for the game. * Build a **package** and upload it to any branch in the [Packages](/publishing/game-publishing/concepts/game-package-management) module. * If the playtest needs XBOX sign-in or other XBOX network features, enable full XBOX services and publish the game's **XBOX services - Gameplay settings** to the RETAIL sandbox. Full XBOX services aren't required to publish a playtest. * **Important:** Before you publish XBOX services, review the considerations in [XBOX services and Playtest](#xbox-services-and-playtest). * You know who your testers are and you have, or can create, an **audience group** which includes them. For more information, see [Manage your playtest audience](#manage-your-playtest-audience). ## Playtest gallery When you select **Playtest** on your game's page navigation, you go to the Playtest gallery. This page displays the playtests that are created for the game. For each playtest, you can view: * The [playtest status](#state-reference) * The start and end dates * The audience type and audience groups * The game package name and version Select **view** to view a playtest's configuration. Other menu options are available when you select the **...**: * **Edit:** Change the playtest's configuration. * **Share:** Get the deep link that testers can use to access the playtest on their device. * **Delete:** Delete the playtest. ## Create a new playtest You create and publish playtests entirely in Partner Center. It typically takes less than 5 minutes to set up a playtest after you meet the prerequisites. The **Create new playtest** page contains all settings for a playtest. Configure the basic information, game art, package, and audience on this page. You can save an incomplete playtest as a draft or publish it when the required information is complete. 1. Sign in to **Partner Center**. 2. Select the **Apps and games** workspace. 3. Select the game you want to associate the playtest with. 4. Under **Services** in the left navigation, select **Playtest**. 5. Select **Create new playtest**. 6. In **Basic information**, provide the playtest details: * **Playtest name:** The name of the playtest. This name is visible to testers. We recommend choosing a name that's different from your main game, so testers know which playtest build they're installing. * **Playtest description:** A description of the playtest. * **Start date and time:** The date the playtest is accessible by testers. * **End date and time:** The date the playtest is no longer accessible by testers. * For a long-running playtest, select **No end date**. You can still end the playtest manually at any time. * For more information about what the **Start** and **end** dates control, see [Playtest lifecycle and states](#playtest-lifecycle-and-states). The Playtest setup page showing the fields to complete 7. In **Packages**, choose the package you want to put in front of testers: * Select the [branch](/publishing/game-publishing/concepts/branches) that contains the package. * Select the package. * During Preview, only **msixvc** packages for XBOX on PC are available. * Playtest packages are encrypted and licensed independently of your main game. You can update the package later without recreating the playtest. For more information, see [Update and iterate on a playtest](#update-and-iterate-on-a-playtest). 8. In **Audience**, choose an existing customer group. Only members of an assigned group can install and launch the playtest package. * If you need a new group, select **Manage or edit in customer groups**, and then select **Create new group**. * Enter a group name, select **Known user group**, and add your testers. During Preview, **Known device groups** aren't supported. * Select **Save**, return to the playtest configuration, and select the customer group you created. * For more information about playtest audiences, see [Manage your playtest audience](#manage-your-playtest-audience). 9. Review the basic information, package, and audience. Address any errors or warnings shown on the page. If your game isn't released, we recommend that you configure [XBOX Embargo](/publishing/game-publishing/concepts/xbox-services#embargo-date) in your game's XBOX services. If you don't configure XBOX Embargo, information about your XBOX services, including your XBOX achievements, is visible to players. If you publish without an embargo date, you might expose your content before the intended release, risking leaks of confidential information, spoiled announcements, or a compromised launch strategy. 10. At the top of the page, select one of the following actions: * **Save as draft:** Save the playtest without publishing it. You can return to complete or publish it later. * **Save and publish:** Validate and publish the playtest. If you select **Save and publish**, the playtest enters the **Publishing** state. When the publish completes, the playtest moves to **Published**. Depending on the start date you configure, the playtest shows as **Scheduled** or **Live**. If the publish fails, review the error details shown in Partner Center, correct the configuration as necessary, and select **Save and publish** to retry. If the error persists, share the error details with your XBOX representative. After the playtest is published, share it with your testers. ## Share a playtest with testers After you publish a playtest, your testers install and launch it via a **deep link** that you share with them. During Preview, testers access a playtest only through the deep link you share. Playtests aren't discoverable in the Microsoft Store. Integration with the Library is planned for Fall 2026. 1. Go to the **Playtest** page for your game. 2. Select the **...** icon for the playtest. 3. Select **Share**. 4. Copy the **deep link**. Partner Center generates a deep link that uses the following form: `msxbox://playtest/?productId={ID}` ### Share and use the deep link Distribute the link to your testers however you prefer: email, an internal portal, or any other channel. * The link only works for testers who are members of an assigned audience group. Anyone else who opens the link sees the **Product Not Found** screen in the XBOX app. * The deep link isn't a credential on its own, but treat it as sensitive. Enter the deep link as a target in **Run** (Win+R) on a Windows PC. Opening the deep link launches the XBOX app, and the playtest displays automatically. ## Manage your playtest audience Audience groups control who can install and launch a playtest build. Every playtest is associated with one or more audience groups. Only members of those groups have access. ### How Playtest controls access * Audience groups (also called **Customer Groups** in Partner Center) are the access-control mechanism for playtests. * Each playtest is associated with one or more audience groups. * Each audience group can be selected for multiple playtests. * Only members of the assigned audience group or groups can install and launch the playtest build. ### What testers see Members of an audience group included in a playtest can use the deep link you share to install and launch the playtest. For more information, see [Share a playtest with testers](#share-a-playtest-with-testers). The XBOX app on PC validates the tester's audience-group membership and installs the playtest build. Anyone who isn't a member of an assigned audience group sees the **Product Not Found** screen in the XBOX app when they open the deep link. All playtests for a product share the same package family name (PFN). A tester can be a member of multiple playtests for the product, but only one playtest build can be installed at a time. Switching to another playtest updates the installed package to that playtest's build. ### Audience size Playtest supports audiences of up to 10,000 players. Certification isn't required. For more information, see [Comparing prerelease testing options](/publishing/game-publishing/publishing-processes/managed-creators/publishing-processes-prerelease#comparing-beta-distribution-options). ## Update and iterate on a playtest A published playtest can be updated as necessary. Common changes, such as updating the package, modifying the playtest dates, or adjusting the audience, don't require you to recreate the playtest or invite testers again. Existing testers receive the new build through the standard update flow on XBOX. ### What you can edit * **Title** and **description**. * **Dates:** Modify the start or end date of the playtest. * **Package:** Assign a newer (or different) package. * **Audience:** Add or remove audience groups. You can't change the game the playtest is associated with. To move to a different game, create a new playtest. ### How to update a playtest 1. Go to the **Playtest** page for your game. 2. Select the **...** icon for the playtest. 3. Select **Edit**. 4. Edit the playtest as necessary. 5. At the top of the page, select **Save and publish** to publish the changes. The playtest enters the **Publishing** state while the update publishes. When the publish completes, depending on the start date you configure, the playtest shows as **Scheduled** or **Live**. If the publish fails, review the error details shown in Partner Center, correct the configuration as necessary, and select **Save and publish** to retry. If the error persists, share the error details with your XBOX representative. ### What testers experience * If you publish a new package, testers who already installed the previous version receive the new package through the standard update flow in the XBOX app. They don't need to reinstall or reaccept the deep link. * Playtest checks audience membership approximately every 10 minutes. Testers added to a newly assigned audience group receive access after the updated membership is detected. * If you remove a tester from an audience group, Playtest stops issuing new licenses after the updated membership is detected. An existing license can remain valid for up to 30 minutes, so an in-progress session or launch might continue during that lease period. ### Create or update an audience group 1. Sign in to Partner Center. 2. Select the **Apps and games** workspace. 3. Select **Customer Groups** on the page's navigation menu. 4. Select **Create new group**, or select an existing one. 5. Configure the group members. You can add or remove members as necessary. 6. Select **Save**. The group is now available to select when you configure a playtest. ## Shut down a playtest A playtest ends in one of two ways. Both paths revoke access for testers and reset the playtest's availability. * It ends **automatically** when its configured end date passes. * It ends **manually** when you delete it from Partner Center. Use the end date when the playtest is time-bound, for example if you operate the playtest in a defined test window. For a long-running playtest, select **No end date** when you create or edit it. You can still end it manually at any time. You can also delete a playtest after it finishes if you want to remove it from your product. ### How to delete a playtest 1. Go to the **Playtest** page for your game. 2. Select the **...** icon for the playtest. 3. Select **Delete**. 4. Confirm the playtest's deletion. An unpublished draft is deleted immediately. A playtest that was previously published enters the **Deleting** state while content access is revoked and availability is reset. Wait for the delete operation to complete before creating a replacement playtest with the same configuration. ### What happens to testers after shutdown * Playtest stops issuing new licenses. An existing license can remain valid for up to 30 minutes. * The installed package remains on the tester's device until they uninstall it. After the existing license expires, the build no longer runs. ### Can a deleted playtest be restored? No. Once a playtest is deleted, it can't be restored. If you want to test the same build again, create a new playtest. ## Playtest lifecycle and states This section is the reference for the states a playtest moves through, what each state means, what actions are possible, and what testers see. ### Operational states vs. display states A playtest has three **operational states**: * **Draft** * **Published** * **Deleted** When a playtest is **Published**, Partner Center shows a **display sub-state** computed from the playtest's start and end dates: * **Scheduled:** The playtest start date is in the future. * **Live:** Current time is within the active date range. * **Ended:** The playtest end date is in the past. The display sub-states are displayed relative to the current time and date. When you publish or delete a playtest, a transient state is displayed: * **Publishing:** A publish or republish is in progress. * **WaitingOnIngestion:** The selected package is still being ingested. Publishing continues after package ingestion completes. * **Deleting:** A shutdown is in progress. There's one error state: * **PublishFailed:** an error occurred during publish. ### State reference | State | What it means | What you can do | What testers see | | ------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | **Draft** | The playtest is created and saved. It's fully editable. | Edit, publish, or delete. | Not visible. | | **Publishing** | Publish workflow in progress. | Wait. | Not yet installable. | | **WaitingOnIngestion** | The selected package hasn't completed ingestion. | Wait for package ingestion to complete. | Not yet installable. | | **Published / Scheduled** | Published. The playtest start date is in the future. | Edit and republish. | Can't install. | | **Published / Live** | The playtest is active. | Edit and republish, or shut down. | Can install and play. | | **Published / Ended** | The playtest end date is in the past. | Edit and republish (extending dates) or delete. | Can't install. | | **PublishFailed** | Publish workflow failed. | Correct the configuration as necessary, and retry publishing. | Not installable. | | **Deleting** | Shutdown of a previously published playtest is in progress. | Wait. | No new licenses are issued. An existing license can remain valid for up to 30 minutes. | | **Deleted** | Removed. | Create a new playtest. | Can't get a new license. An existing license can remain valid for up to 30 minutes. | ### How does Playtest affect your main game * A playtest **doesn't** modify your main game's, such as its **Store listing**, or **Pricing and availability**. Existing XBOX app integrations are untouched. * A playtest **doesn't** grant or revoke access to players of your main game, unless they're included in an audience group selected for a playtest. ## XBOX services and Playtest Full XBOX services aren't required to publish a playtest. If your playtest uses XBOX sign-in or other XBOX network features, enable full XBOX services and publish the associated main game's **XBOX services - Gameplay settings** to the RETAIL sandbox. Before you publish XBOX services, think carefully about whether playtesters should see the configuration. ### XBOX services and the RETAIL sandbox A playtest publishes to the **RETAIL** [sandbox](/publishing/game-publishing/concepts/sandboxes), which is the same live, production environment that players use for released games. During a playtest, XBOX services behave exactly as they do for a generally available game: * Playtesters sign in using their real XBOX account * XBOX network features, including presence, friends and social activity, achievements and gamerscore, and leaderboards, are active. * These features might be visible to players outside your playtest. For more information, see [Hide unfinished features with XBOX embargo](#hide-unfinished-features-with-xbox-embargo). ### Hide unfinished features with XBOX embargo Because a playtest shares XBOX services with the main game, anything visible in your **XBOX services - Gameplay settings**, such as achievements, presence strings, or new content, is also visible to playtesters and other XBOX players. To hide unfinished or confidential content, configure **XBOX embargo**. Embargo also prevents screenshot and video capture, and prevents the game from appearing in presence, which is useful for confidential builds. For more information, see [Configure embargo dates](/publishing/game-publishing/tutorial-xbox-managed/how-to-configure-xbox-services#configure-embargo-date). ### Achievements All achievements published to the RETAIL sandbox, including achievements published for use in a playtest, must comply with the XBOX Requirements (XRs) for achievements and gamerscore. After an achievement is published to the RETAIL sandbox, it can't be removed, and its unlock rules and rewards can't be changed. Text strings (name, description) and artwork (icons, background) can still be modified. If you need to iterate on achievement design during a playtest (adding, removing, or changing unlock rules and rewards), contact your XBOX representative to request a **development-time validation override** for your game. The override lets you publish achievement changes that would usually be prohibited in the RETAIL sandbox. Without the override, only achievement text and art can change after you publish the achievements to the RETAIL sandbox. This override must be removed before you submit the game for certification. If your achievements are final, but you don't want them to be visible when you start playtesting, configure [XBOX embargo](/publishing/game-publishing/tutorial-xbox-managed/how-to-configure-xbox-services#configure-embargo-date) for your game. For more information about the XRs for achievements, see [Achievements and Awards](/publishing/certification/xbox-requirements#achievements). ### Sandboxes Playtests publish to the **RETAIL** [sandbox](/publishing/game-publishing/concepts/sandboxes). There's no separate sandbox setup step. ## Playtest vs. other prerelease options Playtest is one of several ways to run prerelease content on XBOX endpoints for testers. Use the following comparison to pick the right tool for your scenario. For the full set of prerelease testing options, see [Prerelease testing options](/publishing/game-publishing/publishing-processes/managed-creators/publishing-processes-prerelease). | Feature | Private Audience | Package Flighting | Development sandbox testing | **Playtest** | | ------------------------------------- | ---------------- | ----------------- | --------------------------- | ----------------------------------- | | Main game publish to RETAIL required? | Yes | Yes | No | **No** | | Certification required? | Yes\* | No | No | **No** | | Enables multiple simultaneous tests? | No | Limited | No | **Yes** | | Requires entitlement to main game? | Yes | Yes | No | **No** | | Audience management | Customer Groups | Customer Groups | Test accounts | **Customer Groups\*\*** | | When in the product lifecycle | Pre-public only | Full lifecycle | Full lifecycle | **Pre-release only during Preview** | \* Only applies to Private Audience configurations with a restriction end date. \*\* Redeemable-token enrollment is planned for GA. See [Audience size](#audience-size). ### When to choose Playtest Choose Playtest for prerelease testing if: * You want to put a prerelease build in front of testers **without** publishing your main game, submitting for certification, or configuring a PDP in the Microsoft Store. * You want to publish a prerelease build on PC without updating the supported platforms on your PDP. * You want to run **multiple parallel** tests for the same product. * You want to **iterate fast** by updating builds without recreating a test program or inviting testers again. * Your audience has up to 10,000 players. ### When to choose alternative options | Private Audience | Package Flighting | Development Sandboxes | | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | You want a restricted audience to validate the final, certification-approved retail product and Microsoft Store acquisition flow before broader availability. | You publish a base package in the RETAIL sandbox and you want to test post-launch changes in a new package, with a subset of players. | You need an isolated environment for internal development or automated testing with test accounts. Not suitable for distribution to external players. | ## Frequently asked questions This section provides answers to some common questions about Playtest. If your question isn't covered here, contact your XBOX representative. ### Do you need to publish your main game in the Microsoft Store to create a playtest? No. Playtest works independently of your main game. You don't need to publish a PDP in the Microsoft Store, or publicly release your game before you create a playtest. Standard XBOX publishing requirements, such as age ratings, still apply in the playtest's associated main game. ### Does a playtest package appear in the XBOX Store or in players' libraries? During Preview, no. Access to playtest builds is through a deep link only. See [Share a playtest with testers](#share-a-playtest-with-testers). ### Do XBOX services work during a playtest? Yes. Full XBOX services aren't required to publish a playtest, but they're supported in the RETAIL sandbox. If your playtest uses XBOX sign-in or other XBOX network features, enable full XBOX services and publish the associated main game's gameplay settings to RETAIL. See [XBOX services and Playtest](#xbox-services-and-playtest). ### Does publishing a playtest affect your main game or its PDP in the Microsoft Store? No. A playtest is additive. Packages are encrypted and licensed independently of your main game. Store listings and XBOX app integrations are untouched. ### Can you change achievements after publishing them for use in a playtest? A playtest publishes to the RETAIL sandbox, so achievements you publish must comply with the XRs for achievements and gamerscore. After you publish achievements to the RETAIL sandbox, you can only change text and art. You can't change achievement unlock rules or rewards, and you can't remove achievements. If you need to iterate on achievement design during a playtest, contact your XBOX representative about a development-time validation override. See [Achievements](#achievements). ### Do you have to declare PC support on your main game to run a PC playtest? No. If your main game currently only supports XBOX consoles, you can run a PC playtest without adding PC support to the public product configuration. ### Can you run multiple playtests for the same product at the same time? Yes. A tester can be a member of audience groups selected in multiple playtests, but only one playtest build for a product can be installed at a time. To switch playtests, the tester opens the deep link for the other playtest, which updates the installed package to that playtest's build. ### How long does it take to shut down a playtest? An unpublished draft is deleted immediately. A previously published playtest uses an asynchronous delete operation and remains in the **Deleting** state until the operation completes. Playtest stops issuing new licenses, but an existing license can remain valid for up to 30 minutes. See [Shut down a playtest](#shut-down-a-playtest). ### What happens if a playtest publish fails? Review the error details, correct the playtest configuration as necessary, and select **Save and publish** to retry. If the error persists, share the error details with your XBOX representative. See [Create a new playtest](#create-a-new-playtest). ### Is there a limit on audience size? Playtest supports audiences of up to 10,000 players. Certification isn't required. See [Audience size](#audience-size). ### Can you monetize a playtest? No. Playtests are for unmonetized prerelease distribution. ### Does Playtest collect feedback, ratings, or crashes from testers? During Preview, Playtest doesn't collect in-product feedback or analytics. Potential future capabilities are evaluated separately through the public Playtest roadmap. ### Is there a cost to use Playtest? No. Playtest functionality is provided at no extra cost. ### Can QA or publishing teams use Playtest for internal dev testing? Yes. Any audience that makes sense for your studio can use Playtest. Child accounts aren't supported. ### What happens if a deep link is shared with someone outside of the intended audience? Anyone who isn't a member of an assigned audience group sees the **Product Not Found** screen in the XBOX app when they open the deep link. See [Share a playtest with testers](#share-a-playtest-with-testers). ### How do you become eligible to use Playtest? During Preview, your Partner Center account must be approved for Playtest. Request access from the Playtest landing page in Partner Center. At the product level, expand **Services**, and then select **Playtest**. See [Get started](#get-started). ### What additional Playtest capabilities are planned? XBOX console support and Library integration are planned for Fall 2026. Redeemable-token audience enrollment is planned for GA. Plans and timing might change. Other potential capabilities are evaluated through the public Playtest roadmap. ## Related content ## Related topics - [Playtest overview](/publishing/game-publishing/concepts/playtest.md) - [Prerelease testing options](/publishing/game-publishing/publishing-processes/managed-creators/publishing-processes-prerelease.md) - [Run custom script during VM creation (preview)](/services/playfab/multiplayer/servers/vmstartupscript.md) - [FMA: XR-117 Beta/Game Preview Notification](/publishing/certification/fma/xr-117.md) - [XBOX Game Preview](/publishing/game-publishing/publishing-processes/managed-creators/publishing-processes-xbox-game-preview.md)