Google Chrome is one of the most widely used web browsers in enterprise environments. On Windows Server 2019 Remote Desktop Services (RDS), dozens of users may access Chrome every day. While Chrome offers excellent performance and compatibility, it also generates a significant amount of temporary cache and browsing data that gradually consumes valuable disk space.
Many administrators discover that the Google AppData folder inside each user profile occupies several gigabytes. On servers with 20–50 users, Chrome cache alone can consume 50 GB to over 200 GB of storage.
The good news is that most of this storage can be reclaimed safely without affecting user settings, bookmarks, passwords, or browser extensions.
This article explains what can be safely removed, what should never be deleted, and how to automate Chrome cache cleanup using PowerShell.
Every Windows user has a Chrome profile stored under:
C:\Users\<Username>\AppData\Local\Google\Chrome\User Data
This folder contains all browser-related information, including:
Some of these files are essential, while many are simply temporary data.
Chrome automatically stores:
These files improve browsing speed but continuously grow over time.
Typical cache size per user:
| Number of Users | Approximate Cache Size |
|---|---|
| 5 Users | 5–15 GB |
| 20 Users | 20–70 GB |
| 50 Users | 70–200 GB |
For Remote Desktop Servers, this wasted storage grows rapidly.
The following folders only contain temporary data and can be safely deleted while Chrome is closed.
Cache
Code Cache
GPUCache
ShaderCache
GrShaderCache
Media Cache
Crashpad
DawnCache
Service Worker\CacheStorage
Deleting these folders does not remove:
Chrome automatically recreates these folders when launched again.
Administrators should avoid deleting the following folders unless performing a complete browser reset.
Default
Profile 1
Profile 2
Extensions
Bookmarks
Login Data
Preferences
History
Cookies
Web Data
Deleting these files may result in:
Yes.
An Administrator account can access any user profile directly.
Example:
C:\Users\John\AppData\Local\Google
No interactive login is required.
However, Chrome must not be actively running for that user.
Always:
✔ Inform users
✔ Perform cleanup during maintenance hours
✔ Close all Chrome sessions
✔ Verify no Chrome processes remain
taskkill /F /IM chrome.exe
or
Get-Process chrome | Stop-Process -Force
PowerShell is the preferred method for enterprise environments.
A properly written cleanup script can:
The script can also be scheduled using Windows Task Scheduler.
Organizations typically recover:
depending on server usage.
Other benefits include:
Microsoft recommends periodic cleanup of temporary files on Remote Desktop Servers.
Administrators should:
Besides Chrome, administrators can safely clean:
AppData\Local\Temp
Windows\Temp
SoftwareDistribution\Download
Microsoft\Windows\INetCache
CrashDumps
DeliveryOptimization
Regular maintenance significantly extends server storage life.
Generally, No.
Deleting:
AppData\Local\Google
removes:
Although Chrome recreates the folder, users effectively receive a fresh browser profile unless synchronization restores their data.
For production servers, deleting only cache folders is the safest approach.
Browser cache may contain:
Organizations handling sensitive information should include browser cache cleanup in their regular maintenance policy.
Most enterprises configure Windows Task Scheduler to execute the cleanup script:
Recommended maintenance window:
Automation eliminates manual intervention and ensures consistent server performance.
Avoid these practices:
Google Chrome's AppData cache is one of the largest contributors to wasted disk space on Windows Server 2019 RDS environments. Fortunately, administrators can safely reclaim substantial storage by deleting only temporary cache folders while preserving user profiles, bookmarks, passwords, and browser settings.
Using PowerShell automation and scheduled maintenance ensures a cleaner, faster, and more reliable Remote Desktop environment. By adopting regular cache cleanup as part of server maintenance, organizations can improve performance, reduce storage costs, and provide a better experience for all users.