This document shows you how to publish your game on Google Play Games on PC using Play Managed Installation.
With Play Managed Installation, Google Play manages the installation, update, and uninstallation of the game using the game files and metadata you provide in a Windows app bundle (WAB) file.
Before you begin
Integrate the Google Play Games SDK into your game. To start onboarding, emailgoogle-play-games-pc@google.com for assistance with the next steps.
Package your game as a WAB file
To create a Play Managed Installation WAB file, follow these steps:
Download the Play publishing tool. You can run this tool on the Windows command line or Powershell.
Create the Play publishing config file, with any name. For example,
play_publishing_config.xmlwith the following format:<?xml version="1.0" encoding="UTF-8"?> <play-publishing-config version="1.0"> <!-- Application metadata: This section contains basic information about your game. --> <application> <package-name>PACKAGE_NAME</package-name> <version-name>VERSION_NAME</version-name> </application> <!-- Game files: This section specifies which game files to include in the bundle and how to treat them. --> <game-files> <file-set> <root-folder-path>PATH_TO_ROOT_FOLDER</root-folder-path> <!-- absolute or relative to the parent directory of the config xml --> <!-- Exclusions: A list of files or folders to exclude from the bundle. This is useful for removing development files, temporary data, or redundant assets. --> <exclusions> <file-path>REGEX_PATTERN_OF_EXCLUDED_FILES</file-path> <file-path>PATH_TO_BE_EXCLUDED</file-path> </exclusions> <!-- File attributes: Define special handling for certain files during installation and updates. --> <file-attribute value=FILE_ATTRIBUTE_VALUE> <file-path>PATH_TO_FILE</file-path> <file-path>REGEX_PATTERN_OF_FILE_ATTRIBUTE_FILES</file-path> </file-attribute> </file-set> </game-files> <!-- This file represents the startup process for this game. Google Play Games for PC should start this process when user clicks on "Play" on this game. --> <launch-command> <path>PATH_TO_LAUNCH_FILE</path> <arguments>ARGUMENTS</arguments> </launch-command> <!-- Lifecycle operations: Custom actions to be performed during the game's installation and uninstallation. --> <lifecycle-operations> <!-- Install operations: These actions run when the game is installed. 'requiresElevation="true"' will trigger a UAC prompt for administrator rights. There are three types of install operations that can be specified. An instance of each is listed below. --> <install-operation requiresElevation=INSTALL_OPERATION_REQUIRES_ELEVATION> <operation-identifier>OPERATION_IDENTIFIER_STRING</operation-identifier> <execute-file> <path>PATH_TO_INSTALL_EXECUTE_FILE</path> <arguments>ARGUMENTS</arguments> </execute-file> </install-operation> <install-operation requiresElevation=INSTALL_OPERATION_REQUIRES_ELEVATION> <operation-identifier>OPERATION_IDENTIFIER_STRING</operation-identifier> <update-registry baseKey=BASE_KEY> <sub-key>SUB_KEY_PATH</sub-key> <value-name>VALUE_NAME</value-name> <value type=REGISTRY_VALUE_TYPE>VALUE_TEXT</value> </update-registry> </install-operation> <!-- Uninstall operations: These actions run before the game is uninstalled. --> <uninstall-operation requiresElevation=UNINSTALL_OPERATION_REQUIRES_ELEVATION> <execute-file> <path>PATH_TO_UNINSTALL_EXECUTE_FILE</path> <arguments>ARGUMENTS</arguments> </execute-file> </uninstall-operation> </lifecycle-operations> </play-publishing-config>
Replace the following:
PACKAGE_NAME: The package name for your game. This is the unique identifier that will be associated with your game on Google Play. For example,com.yourcompany.yourgame. The package name must adhere to the following rules:- It must have at least two segments (one or more dots).
- Each segment must start with a letter.
- All characters must be alphanumeric or an underscore (
[a-zA-Z0-9_]).
VERSION_NAME: The game's version string. This can be an arbitrary string, but it must be unique across all uploaded WABs for your game. For example:1.0,1.0.1-beta,2025.11.24,v1.rc1.PATH_TO_ROOT_FOLDER: The path to the root folder containing your game files. All files in this folder, except those mentioned in exclusions, are added to the bundle. This path can be absolute or relative to the directory containing theplay_publishing_config.xmlfile.exclusions: (Optional) Specifies file paths or patterns for files withinPATH_TO_ROOT_FOLDERto exclude from the bundle. You can include multiplefile-pathelements within theexclusionselement. A path can be represented in one of two ways:- As a file path: Path to the file to exclude.
- As a regex string: All files that match the regular expression string are excluded from the bundle. Use RE2 syntax.
file-attribute: (Optional) Defines attributes for specific files or files matching a regular expression pattern.FILE_ATTRIBUTE_VALUE: Can be one of the following:SKIP_UPDATE: During an update, this attribute tells the system to copy the file only if it's not already present, preserving any changes to an existing file.MODIFIED_ON_DEVICE: Use this for files that must be updated, but could be modified on the device after installation. The system downloads the full new file and overwrites the installed version during an update. If this file is different from the installed version during installation integrity checks, the installation is not considered corrupted.
file-path: Identifies files for this attribute. You can include multiplefile-pathelements within eachfile-attributeelement. Each path can be represented in one of two ways:- As a file path: Path to the file to associate this attribute with.
- As a regex string: All files that match the regular expression string are associated with the attribute value. Use RE2 syntax.
PATH_TO_LAUNCH_FILE: Path to the executable file used to launch the game.ARGUMENTS: (Optional) Command-line arguments. The<arguments>element is used to pass arguments to an executable file specified in<launch-command>,<install-operation>, or<uninstall-operation>. Each use of the<arguments>element applies only to the executable it is defined alongside, allowing you to specify different arguments for different executables.- If an executable has multiple arguments, separate them with a space.
- Prepend arguments with
--or-if the executable requires it. Example:<arguments>--package_name --version_name</arguments>
lifecycle-operations: (Optional) Custom actions to perform during game installation or uninstallation.install-operation: An action to run when the game is installed. You can specify two types of install operations:execute-fileandupdate-registry.uninstall-operation: An action to run before the game is uninstalled.update-registryoperations are automatically reverted during uninstallation.INSTALL_OPERATION_REQUIRES_ELEVATION: Indicates whether the install operation needs to run with administrator privileges.- "true": Run as Administrator.
- "false": Run as the current user. This is the default if unspecified.
UNINSTALL_OPERATION_REQUIRES_ELEVATION: Indicates whether the uninstall operation needs to run with administrator privileges.- "true": Run as Administrator.
- "false": Run as the current user. This is the default if unspecified.
operation-identifier: A unique string to identify aninstall-operation.execute-file: Runs an executable file.PATH_TO_INSTALL_EXECUTE_FILE: Path to an executable to run during installation.PATH_TO_UNINSTALL_EXECUTE_FILE: Path to an executable to run before uninstallation.
update-registry: Creates or updates a Windows registry entry.BASE_KEY: Defines the root key to be used in the Windows registry. Accepted values:HKEY_CLASSES_ROOT,HKEY_CURRENT_CONFIG,HKEY_CURRENT_USER,HKEY_LOCAL_MACHINE,HKEY_PERFORMANCE_DATA, andHKEY_USERS. When performing anupdate-registryoperation, setrequiresElevation="true"on the parentinstall-operationbased on thebaseKeyused:HKEY_LOCAL_MACHINEorHKEY_CURRENT_CONFIG: SetrequiresElevation="true".HKEY_CURRENT_USER:requiresElevation="true"is not needed.HKEY_CLASSES_ROOT: SetrequiresElevation="true"only if writing to machine-wide sections; it is not required for user-specific sections.HKEY_USERS: Contains profiles for all users. SetrequiresElevation="true"when modifying profiles other than the current user's (e.g., other users or.DEFAULT).
SUB_KEY_PATH: This represents the path to a specific key within the Windows Registry, nested under the mainbaseKey.VALUE_NAME: This specifies the name of the data entry you want to modify within the designated sub-key.REGISTRY_VALUE_TYPE: This attribute specifies the data type of the value being written to the registry. Supported values areSTRINGfor a string orDWORDfor a 32-bit number.VALUE_TEXT: Data to be stored in the registry key.
How to use regular expressions
You can use RE2 syntax regular expressions in
file-pathtags to apply exclusions or file attributes to a group of files. Remember to use forward slashes/for directory separators, and to escape special regular expression characters with a backslash\. For example, use\.to match a literal dot., or\dto match a digit.Here are some common examples:
- Match all files with a specific extension (For example, .log) in any directory
Use
.*\.logto match any path ending with.log, likegame.logorlogs/errors.log.<file-path>.*\.log</file-path>
- Match all files and subdirectories within a specific folder (For example, 'temp')
Use
temp/.*to match all paths that start withtemp/, liketemp/data.txtortemp/saves/file.sav.<file-path>temp/.*</file-path>
- Match files matching a pattern in a specific folder
Use
assets/level\d\.datto matchassets/level1.dat,assets/level2.datbut notassets/other.dat.<file-path>assets/level\d\.dat</file-path>
- Match a folder name when it appears anywhere in the path
Use
.*/cache/.*to match files under any directory namedcache, likegame/cache/file.txtortemp/cache/other.log.<file-path>.*/cache/.*</file-path>
- Match files with one of several extensions (For example, .ini, .cfg, .sav)
Use
.*\.(ini|cfg|sav)to match any file ending in.ini,.cfg, or.sav, likesettings.ini,config.cfg, orsaves/slot1.sav.<file-path>.*\.(ini|cfg|sav)</file-path>
- Match files with a specific extension in specific directories (For example, .ogg in music/ or sfx/)
Use
(music|sfx)/.*\.oggto match any.oggfiles that are located under either themusic/orsfx/directories, but not elsewhere. Matchesmusic/level1.oggorsfx/explosion.ogg, but notvoice/intro.ogg.<file-path>(music|sfx)/.*\.ogg</file-path>
Example Play publishing config file
Here is an example
play_publishing_config.xmlfor a game calledTestGame:<?xml version="1.0" encoding="UTF-8"?> <play-publishing-config version="1.0"> <application> <package-name>com.test.package</package-name> <version-name>1.0</version-name> </application> <game-files> <file-set> <root-folder-path>C:\Users\Username\game-files</root-folder-path> <exclusions> <file-path>mock_game\d\.exe</file-path> <!-- exclude files using a regex --> <file-path>deprecated_graphics</file-path> <!-- exclude a folder --> <file-path>.*\.log</file-path> <!-- recursively exclude all files with .log extension --> </exclusions> <file-attribute value="SKIP_UPDATE"> <file-path>settings.ini</file-path> </file-attribute> <file-attribute value="MODIFIED_ON_DEVICE"> <file-path>game_assets\d\.zip</file-path> <!-- define the path using regex --> </file-attribute> </file-set> </game-files> <launch-command> <path>launcher_test_game.exe</path> <arguments>--launch-arg</arguments> <!-- optional --> </launch-command> <lifecycle-operations> <install-operation requiresElevation="true"> <operation-identifier>elevated-execute-file</operation-identifier> <execute-file> <path>install_file.exe</path> <arguments>--arg</arguments> <!-- optional --> </execute-file> </install-operation> <install-operation requiresElevation="true"> <operation-identifier>elevated-update-registry</operation-identifier> <update-registry baseKey="HKEY_LOCAL_MACHINE"> <sub-key>SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TestGame</sub-key> <value-name>InstallLocation</value-name> <value type="STRING">C:\Program Files\TestGame</value> </update-registry> </install-operation> <uninstall-operation requiresElevation="true"> <execute-file> <path>uninstall.exe</path> <arguments>--test-arg</arguments> <!-- optional --> </execute-file> </uninstall-operation> </lifecycle-operations> </play-publishing-config>
Run the Play publishing tool on the Windows command line or Powershell, using the
build-bundlecommand:playpublishingtool.exe build-bundle --input=PLAY_PUBLISHING_CONFIG_PATH --output=WAB_OUTPUT_PATH
To overwrite an existing WAB file with the same name, use the
--forceargument.playpublishingtool.exe build-bundle --input=PLAY_PUBLISHING_CONFIG_PATH --output=WAB_OUTPUT_PATH --force
Replace the following:
PLAY_PUBLISHING_CONFIG_PATH: The path to the Play publishing config. For example,path\to\play_publishing_config.xml.WAB_OUTPUT_PATH: The path to the WAB file. For example,path\to\output_bundle.wab.
How to use Play publishing tool
If you have
playpublishingtool.exe,play_publishing_config.xml, and your game files ingame_files/in the current working directory:.\ ├── game_files/ ├── play_publishing_config.xml ├── playpublishingtool.exe
To create
pmi_bundle.wabin the same directory, run:playpublishingtool.exe build-bundle --input=play_publishing_config.xml --output=pmi_bundle.wab
While the tool builds the bundle, you will see a progress bar on the terminal:
Building bundle: [==== ] 40%
On success, you should see output similar to the following:
Building bundle: [===========] 100% Successfully built the managed install bundle at pmi_bundle.wab
Find the WAB file in the folder:
.\ ├── game_files/ ├── pmi_bundle.wab ├── play_publishing_config.xml ├── playpublishingtool.exe
Publish the game using Play Console
After you create the WAB file for your game, upload it to Play Console and configure its settings and requirements. Open Play Console, select your app, and follow these steps:
Enable Windows native distribution
- In Play Console, go to Test and release > Advanced settings > Form factors and platforms.
- In the Windows section, click Add Windows.
Configure PC requirements, store listing assets, and review policy
- Set PC hardware requirements (RAM, GPU, and storage) and upload Google Play Games on PC store listing assets (screenshots and an optional video).
- Return to Test and release > Advanced settings > Form factors and platforms and click Agree to review policy to confirm compliance with the Google Play Games on PC quality guidelines.
Test your game on the internal testing track
- Go to Test and release > Testing > Internal testing and select the Google Play Games on PC track.
- Select up to 100 testers (you can configure a separate tester list from
Android), upload your Windows App Bundle (
.wab), and click Save and publish. - Share both the Play Console opt-in web link
(
https://play.google.com/apps/internaltest/...) and the client deep linkgoogleplaygames://deeplink/details?id=PACKAGE_NAME(replacingPACKAGE_NAMEwith your app's package name) with your testers. Testers must first open the opt-in web link and click Accept invite, and then pastegoogleplaygames://deeplink/details?id=PACKAGE_NAMEinto a Windows browser address bar orWin+Rto open the game's details page in the Google Play Games on PC client and install the build.
Publish to production
- Go to Test and release > Production and select the Google Play Games on PC track.
- Select your target countries (which must match or be a subset of your Android country targeting).
- Create a new release or promote your internal test release, and submit your release for review. Reviews take up to seven days.
- Use Managed publishing on the Publishing overview page to control when your approved release goes live.