How to Move Google Chrome Cache to D Drive Safely in Windows and RDP Server

Quick Answer

Yes, Google Chrome’s main disk cache can be moved from the C drive to the D drive. On a managed computer or multi-user RDP server, the recommended method is Chrome’s DiskCacheDir enterprise policy.

Configure a dedicated, user-specific path such as:

D:\ChromeCache\${user_name}

The ${user_name} variable gives every Windows user a separate cache directory. This change does not move bookmarks, passwords, cookies, browser history, extensions or the complete Chrome profile. It also does not reduce Chrome’s RAM usage. Existing cache files on C: must be cleaned separately after the new location has been tested.

Complete Article

Why Move Chrome Cache to Another Drive?

Chrome stores downloaded website resources in a disk cache so that frequently visited pages can load faster. On systems with limited free space on the Windows drive, or on Remote Desktop Session Host servers used by many people, these cache files can consume significant space and create large numbers of small files inside user profiles.

Moving the cache can be useful when:

• The C drive has limited free space.
• A Windows or RDP server has many user profiles.
• User-profile backup or logon processing is slowed by cached files.
• The D drive is a local SSD with adequate capacity.
• Administrators want temporary browser data kept outside the main profile location.

Google’s guidance for virtual desktop infrastructure specifically describes using the DiskCacheDir policy to place cache folders outside Chrome’s normal user-profile directory. Google also notes that applying the policy does not remove older cached files automatically. Google Chrome VDI configuration guidance

What the DiskCacheDir Policy Does—and Does Not Do

The DiskCacheDir policy tells Chrome where to store its disk-cached web resources. A machine-level Windows policy can apply the same rule to everyone who uses that computer while a path variable creates a different folder for each user.

It does not relocate the complete Chrome User Data directory. The following information normally remains in the user’s Chrome profile:

• Bookmarks
• Saved passwords
• Cookies and sign-in information
• Browsing history
• Extensions and their settings
• Chrome preferences
• Open tabs and session information

Some supporting or component-specific Chrome data may also remain under AppData. Therefore, this change reduces future disk-cache usage on C: but should not be presented as moving every Chrome-related file.

Before You Begin

Check the following requirements before changing the cache location:

1. Sign in with an administrator account.
2. Confirm that D: is a permanent local NTFS volume.
3. Make sure the drive has sufficient free space.
4. Prefer an SSD. Moving cache from an SSD to a slow hard disk can reduce browsing performance.
5. Do not use the root of the volume, such as D:\, as Chrome’s cache directory.
6. Use a dedicated path and a separate subfolder for every Windows user.
7. Arrange a maintenance period and ask users to save their work and close every Chrome window.

Avoid removable drives and mapped network drives. A mapped drive may not exist when Chrome starts, and network latency can make browser caching slower or unreliable.

Recommended Cache Path for a Multi-User Computer

Use this path:

D:\ChromeCache\${user_name}

Chrome supports directory variables in path-based policies. On Windows, ${user_name} resolves to the user running Chrome. Other supported variables include ${profile}, ${local_app_data} and ${machine_name}. Chromium supported directory variables

For example, the policy may produce:

D:\ChromeCache\Accounts
D:\ChromeCache\Operator1
D:\ChromeCache\Support

Do not configure every RDP user to use one shared cache folder. Apart from permission and privacy concerns, simultaneous Chrome sessions should not compete for the same cache files.

Method 1: Configure Chrome Cache with PowerShell

This is the most direct method when Chrome Group Policy templates are not installed.

Step 1: Close Chrome

Ask every affected user to save their work and exit Chrome. On an RDP server, confirm through Task Manager that users no longer have active Chrome processes.

Avoid forcibly ending processes unless necessary because unsaved browser work may be lost.

Step 2: Open PowerShell as Administrator

Search for Windows PowerShell, right-click it and select Run as administrator.

Step 3: Create the Parent Cache Directory

Run:

New-Item -Path 'D:\ChromeCache' -ItemType Directory -Force

On a multi-user server, standard users must be able to create or use their own subfolder without receiving access to another user’s cache.

Administrators can either:

• Pre-create one folder for each Windows account and grant that account Modify permission only on its own folder.
• Configure advanced NTFS permissions using CREATOR OWNER, while retaining full control for Administrators and SYSTEM.

Do not grant all users unrestricted access to the entire cache tree. Browser cache can contain local copies of web content and should be protected like other user-specific data.

Step 4: Create the Chrome Policy

Run:

New-Item -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome' -Force

New-ItemProperty `
  -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome' `
  -Name 'DiskCacheDir' `
  -PropertyType String `
  -Value 'D:\ChromeCache\${user_name}' `
  -Force

The policy is stored under HKEY_LOCAL_MACHINE, so it applies at machine level. Administrator rights are required.

The single quotation marks around the policy value are important in PowerShell. They preserve ${user_name} as literal text so that Chrome—not PowerShell—expands the variable when each user starts the browser.

Optional: Suggest a Maximum Cache Size

On shared servers, administrators may also use Chrome’s DiskCacheSize policy. The following example requests a cache size of 300 MiB per user:

New-ItemProperty `
  -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome' `
  -Name 'DiskCacheSize' `
  -PropertyType DWord `
  -Value 314572800 `
  -Force

Treat this as a cache-management setting rather than a guaranteed storage quota. Select a value based on available D: space, the number of users and their browsing workload.

Google recommends leaving substantially more free disk space than the configured cache size. Google guidance on Chrome disk-cache sizing

Method 2: Configure the Cache Through Group Policy

This method is convenient for administrators who already use the official Chrome Enterprise policy templates.

1. Install the current Google Chrome Enterprise ADMX and ADML policy templates.
2. Open gpedit.msc for a local policy or Group Policy Management for a domain policy.
3. Go to:

Computer Configuration
  > Administrative Templates
  > Google
  > Google Chrome
  > Set disk cache directory

4. Open Set disk cache directory.
5. Select Enabled.
6. Enter:

D:\ChromeCache\${user_name}

7. Apply the policy.
8. Run gpupdate /force or wait for the normal policy refresh.
9. Completely close and reopen Chrome.

The official DiskCacheDir policy takes precedence over a --disk-cache-dir command-line value supplied through a Chrome shortcut. Chrome Enterprise DiskCacheDir policy

Why Policy Is Better Than Editing a Shortcut

Chrome can also accept a --disk-cache-dir command-line switch. However, a modified shortcut works only when Chrome is launched through that exact shortcut.

Chrome may also be opened through:

• The taskbar
• The Start menu
• A website link
• Another application
• A different user-created shortcut

For business computers and RDP servers, policy is more consistent because it applies regardless of how Chrome starts. It is also easier for administrators to verify centrally.

How to Verify That Chrome Is Using the D Drive

After restarting Chrome:

1. Enter chrome://policy in the address bar.
2. Click Reload policies.
3. Search for DiskCacheDir.
4. Confirm that the policy appears without an error.
5. Browse several websites.
6. Check whether the current user’s folder appears under D:\ChromeCache.
7. Confirm that the folder contains recently updated cache files.
8. On a shared server, test with a second Windows account and confirm that a separate folder is created.

Chrome’s policy page identifies whether a policy is applied at user or machine level and displays its source and status. Google: View a device’s current Chrome policies

You can also confirm the registry value from an elevated PowerShell window:

Get-ItemProperty `
  -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome' `
  -Name 'DiskCacheDir'

What to Do with the Old Cache on C Drive

Changing DiskCacheDir affects the location Chrome uses after the policy becomes active. Google states that administrators may need to clean the old cache because the policy does not remove it.

Test the new D: location first. Then close Chrome before removing old cache files.

A typical default-profile cache location is:

C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default\Cache

Additional Chrome profiles may appear as Profile 1, Profile 2 and similar folders.

Delete only confirmed cache folders. Never delete the complete Google\Chrome\User Data directory because it contains important browser-profile information.

When using Chrome’s Delete browsing data screen, select Cached images and files only if you do not want to remove cookies or sign users out of websites.

Troubleshooting

DiskCacheDir Does Not Appear at chrome://policy

• Confirm that Chrome was completely closed and reopened.
• Check that the registry path is exactly HKLM\SOFTWARE\Policies\Google\Chrome.
• Confirm that DiskCacheDir is a String value.
• Run PowerShell with administrator privileges.
• If Group Policy is used, run gpupdate /force.
• Check for another domain or cloud policy that may be setting a different value.

The Folder Is Not Created on D Drive

• Confirm that D: is online and writable.
• Check NTFS permissions on D:\ChromeCache and the user’s subfolder.
• Make sure the configured path is absolute.
• Do not use a mapped drive that is unavailable in the user’s session.
• Check chrome://policy for a policy error.

Chrome Still Uses Space Under AppData

This can be normal. The policy changes Chrome’s disk-cache directory; it does not move the complete browser profile or necessarily every supporting cache and storage component.

Old cached data can also remain on C: until it is cleaned manually.

Chrome Becomes Slower

Compare the speed and health of C: and D:. Moving cache from a fast SSD to a slower disk may increase page-loading time and disk latency.

Use a reliable SSD or roll back the policy if performance becomes worse.

Multiple Users Are Writing to One Folder

Confirm that the configured path contains the literal Chrome variable:

${user_name}

If PowerShell was used, confirm that the value was enclosed in single quotation marks. A shared cache directory should be corrected before normal multi-user operation continues.

How to Roll Back the Change

Close Chrome and run PowerShell as Administrator:

Remove-ItemProperty `
  -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome' `
  -Name 'DiskCacheDir' `
  -ErrorAction SilentlyContinue

If DiskCacheSize was also configured and is no longer required, remove it separately:

Remove-ItemProperty `
  -Path 'HKLM:\SOFTWARE\Policies\Google\Chrome' `
  -Name 'DiskCacheSize' `
  -ErrorAction SilentlyContinue

If Group Policy created the setting, change the corresponding policies to Not configured instead of deleting registry values manually.

Reopen Chrome and verify chrome://policy. Chrome will then return to its default cache location. Delete the D: cache folders only after rollback has been tested and while Chrome is closed.

Frequently Asked Questions

1. Can Google Chrome cache be moved from C drive to D drive?

Yes. The supported administrative method is Chrome’s DiskCacheDir policy, configured through Group Policy or the Windows policy registry.

2. Will moving the cache remove bookmarks or saved passwords?

No. Disk cache is different from Chrome profile data that stores bookmarks, passwords, preferences and browsing history.

3. Will this reduce Chrome’s RAM usage?

No. It changes disk storage only. Chrome memory usage depends mainly on open tabs, extensions, active websites, background processes and features such as Memory Saver.

4. Is this useful on a Remote Desktop server?

Yes. It can reduce future cache growth inside C:-based user profiles. Each RDP user should have a separate cache directory and correctly restricted NTFS permissions.

5. Can all RDP users share one Chrome cache folder?

No. Use a user-specific variable such as ${user_name} so simultaneous sessions do not use the same files and users cannot browse each other’s cached content.

6. Does the policy move existing cache files automatically?

No. It directs future cache activity to the new location. Existing cache on C: must be removed separately after verification.

7. Can I move the entire Chrome User Data folder instead?

It is technically possible to configure other Chrome profile-location policies, but moving the complete profile introduces greater compatibility, backup, concurrency and corruption risks.

Moving only disk cache is safer when the objective is reducing temporary data on C:.

8. Can I use a network share or mapped drive?

It is not recommended for browser cache. Network delay, disconnections and unavailable drive mappings can cause poor performance or write failures. Prefer a permanent local SSD.

9. Why does Chrome say “Managed by your organization” after this change?

Chrome may display management wording when an enterprise policy is configured, even on a standalone computer. Check chrome://policy to confirm which policy is responsible.

10. Will Chrome updates remove the cache policy?

Chrome normally continues reading the Windows policy while the registry or Group Policy setting remains in place. Administrators should still verify policies after major environment or management changes.

11. Can I limit the cache size as well as move it?

Yes. Chrome provides a separate DiskCacheSize policy. Size planning should consider the number of users, normal browsing activity and available space on D:.

12. Why do I still see Cache, Code Cache or GPUCache folders on C drive?

They may be old folders or supporting caches not fully covered by disk-cache relocation. Compare modification dates and do not assume that every Chrome data folder will move.

13. Is the shortcut command-line method safe?

The --disk-cache-dir switch can work, but it is less reliable for managed systems because users can start Chrome in other ways. Policy is the better choice for consistent deployment.

14. What happens if the D drive becomes full or unavailable?

Chrome may be unable to write cache normally, and performance can suffer. Monitor free space and drive health, especially on servers used by many people.

15. How can I confirm that separate users have separate caches?

Sign in with two different Windows accounts, start Chrome and confirm that two username folders are created under D:\ChromeCache.

Also verify that each user cannot access the other user’s folder.

Final Recommendation

Use Chrome’s machine-level DiskCacheDir policy with D:\ChromeCache\${user_name} for a Windows computer or multi-user RDP server.

Keep the Chrome profile in its standard location, use a fast local NTFS drive, enforce per-user permissions and verify the result through chrome://policy before cleaning the old C: cache.

This approach can free space and reduce temporary browser-cache activity on the Windows drive, but it should not be treated as a solution for high RAM or CPU usage. Those issues require separate Chrome tab, extension, background-process and server-capacity management.

#GoogleChrome #ChromeCache #MoveChromeCache #DiskCacheDir #Windows11 #Windows10 #WindowsServer #RDPServer #RemoteDesktop #ChromeEnterprise #GroupPolicy #PowerShell #WindowsRegistry #BrowserCache #CacheManagement #CDriveSpace #DDrive #DiskCleanup #ChromePolicy #SystemAdministration #ITSupport #ServerManagement #MultiUserServer #VDI #ChromeTroubleshooting #WindowsTips #NTFSPermissions #ChromePerformance #DiskCacheSize #EnterpriseIT #RDS #TechnicalGuide #BrowserManagement #SystemOptimization #CacheLocation