Grow with Google Play Games on PC

We're making all mobile games available on PC by default. For the best player experience, you can further optimize your game experience for PC. If you do not wish to distribute your mobile games on PC, you can opt out at any time.

You can express your interest in bringing your native PC games to Google Play Games on PC here. Once the interest form is submitted, our onboarding team will review your submission, verify that you’re a PC game developer, and reach out with next steps based on the above criteria.

Google Play Games on PC currently supports free-to-play native PC games that also have a Google Play mobile version. In 2025, we will add support for paid native PC games, as well as PC-only games.

If you’re interested in distributing your game with us, please let us know so we can review your specific requirements.

All native PC games on Google Play Games on PC qualify for the earnback program provided they meet program requirements.

This program has three tiers. The more revenue a title earns, the more you earn back on that title. The Earnback benefit applies only to the revenue from the PC version of your game on Google Play Games on PC.

Earnback	Criteria
5% of Play PC spend	[Tier 1] Title is Windows executable (.exe), and meets the earnback technical requirements
10% of Play PC spend above $5M	[Tier 2] Meets Tier 1 criteria plus Cumulative Play PC spend during the program over $5M, plus integration of applicable Tier 2 technical requirements, plus limited marketing commitments
15% of Play PC spend above $25M	[Tier 3] Meets Tier 2 criteria plus Cumulative Play PC spend during the program over $25M, plus limited marketing commitments

1. Technical Requirements for all native PC games

The following requirements apply to any native game published on the Google Play Games for PC platform, whether they are participating in the PC Earnback Program or not.

1.1 Integrate with the Native PC SDK

Games will be required to integrate with the Native PC SDK (staging devsite documentation). Older games using direct OAuth and REST API calls for identity and billing must migrate to this SDK in order to participate in the PC Earnback Program.

The Native PC SDK will automatically handle authentication for the game, leveraging the current active account in Google Play Games, and provide access to client-side Billing APIs.

2. Technical Requirements for PC Commercial Earnback Program

The following requirements apply to any native game published on the Google Play Games for PC platform that wishes to participate in the PC Commercial Earnback Program

2.1 Do not use fullscreen exclusive mode by default

Fullscreen exclusive mode (FSE) gives the game complete ownership over display rendering, and complicates the ability of Google Play Games to provide functionality to the game via an overlay (e.g. in-app purchase flow). To be able to provide these features to as many users as possible, games cannot use FSE mode by default, but are allowed to provide this as an option within their game settings.

2.2 Optimize store listing

Developers must optimize the Play store listing for their PC game by including a description of gameplay and uploading at least 3 high-resolution screenshots and/or videos.

2.3 List Play as a supported platform on primary game website and marketing assets

To qualify for the PC Commercial Earnback Program, any primary website or market asset that lists supported platforms for the game must include Google Play Games on PC as a supported platform.

2.4 Use of Voided Purchases API

Note: This requirement is only applicable to titles with a backend server that processes in-app purchases (e.g. live service titles), and is not applicable to games that are primarily single-player or offline, or games without in-app purchases. This requirement is only applicable for games at or above the 10% Earnback Tier.

The Play Voided Purchases API provides game developers with a server-side mechanism to find purchases that have been voided, such as a user refunding or issuing a chargeback. For games that manage their own entitlements (e.g. in-app currency), it is important that developers leverage this API to attempt to revoke access to the purchased products to prevent fraud.

2.5 Set account identifiers when launching purchase flow

Note: This requirement is only applicable to titles with an in-game identity system (e.g. live service titles), and is not applicable to games that are primarily single-player or offline, or games without in-app purchases. This requirement is only applicable for games with annual user spend over $100k on Play.

As a fraud detection mechanism, when launching a purchase flow, obfuscated in-game account identifiers should be added to the request.

These identifiers should be set when calling BillingClient::LaunchPurchaseFlow:

• obfuscated_account_id: an obfuscated string that is uniquely associated with the user's account in your app.

• obfuscated_profile_id: an optional obfuscated string that is uniquely associated with the user's profile in your app.

Yes, developers may enroll in both programs. The earnback program is applicable after the 15% service fee tier no longer applies (>$1M (USD) in earnings).