Why is Google Play Games using so much disk space?
Google Play Games can store games and user data outside its launcher installation folder. Its Android environment may also contain a large userdata.img disk image. Check occupied space before treating the image capacity as the amount you could recover.
Measure the launcher and its managed data together
Scan the drive containing the Google Play Games installation or data.
Open Large installed apps in the Overview and find Google Play Games.
Expand the entry to see its measured installation and managed-data locations. Review the allocated sizes of the files in those locations.
SizeTrend recognizes supported registered Google Play Games installations and their managed data folders. The total is for storage visible on the scanned drive. It does not open the Android image to assign a separate size to every game inside it.
A huge userdata.img may occupy much less space
A sparse disk image can have a large logical size while only its populated regions occupy physical disk space. For example, an image with an 80 GB logical capacity might currently occupy only 6 GB. That is an illustration, not a fixed Google Play Games size.
Use allocated space when explaining how much of the Windows drive is occupied. SizeTrend 3.2 also improves NTFS measurement for complex sparse images whose allocation spans multiple filesystem records. Microsoft's sparse-file explanation describes why logical and allocated sizes can differ.
Remove games through Google Play Games
Open Tools | Game Libraries | Google Play Games when the launcher is detected, then use Google's library controls to manage or uninstall games. SizeTrend's application-row Manage action opens Windows application management for the launcher itself.
Do not delete userdata.img as if it were a temporary download. The image can contain several games and persistent data. Confirm how a game saves progress before removing it, and use Windows Installed apps if you intend to uninstall the entire Google Play Games application.
Why did removing a game not free the expected amount?
The SizeTrend row describes the detected launcher and managed data collectively. It is not a prediction of the bytes recovered by removing one game. Shared environment files and other games can remain.
After the removal finishes, run a fresh scan and compare allocated space and the drive's free space. If the managed image remains unexpectedly large, use Google's support options; SizeTrend does not compact or repair the Android image.
If Google Play Games is not listed
Check that you scanned the drive containing its data and that the Google client is registered. The ribbon shortcut depends on the detected launcher registration. Unsupported or relocated storage may still be visible in the folder tree without an attributed application row.
Follow the scanned path to identify its owner before taking action. An absent application row does not turn an image or folder into disposable cache.
Measure occupied space and let the game client manage its own data.
Use SizeTrend 3.2 or later for the features described in this guide.