How I Caught and Eliminated Excess Chrome Writes on My SSD

Published Apr 17, 2026, 11:00 AM EDT

Afam's experience in tech publishing dates back to 2018, when he worked for Make Tech Easier. Over the years, he has built a reputation for publishing high-quality guides, reviews, tips, and explainer articles, covering Windows, Linux, and open source tools. His work has been featured on top websites, including Technical Ustad, Windows Report, Guiding Tech, Alphr, and Next of Windows.

He holds a first degree in Computer Science and is a strong advocate for data privacy and security, with several tips, videos, and tutorials on the subject published on the Fuzo Tech YouTube channel.

When he is not working, he loves to spend time with his family, cycling, or tending to his garden. 

I decided to pay more attention to my SSD after observing constant spikes in disk activity, even when I wasn't performing any intensive tasks. I looked through the Resource Monitor app, and I saw Chrome writing to my disk. Even though these were not big bursts, they were happening with barely any pause.

It became obvious that, in addition to storing cache files, Chrome was ceaselessly updating in the background. When I poked deeper, I realized a few simple steps can keep Chrome in check and seriously reduce the number of writes it makes.

Google Chrome is a cross-platform web browser developed by Google LLC, built for speed, security, and integration with Google services. It uses the Blink rendering engine (formerly WebKit) and supports extensions, tab sandboxing, synchronization across devices, and frequent updates.

Chrome writes to your SSD more often than you’d expect

The cache isn’t static—it’s constantly being updated

Like many people, I thought that my browser cache only gets stored once, after which it is reused several times. Resource Monitor showed me how wrong I was. When I opened the tool and navigated to the Disk tab, I could see several processes and tools writing to my disk. At this point, it wasn't clear how much Chrome contributed to these, so I clicked the Write column header to sort the processes in descending order.

I observed for several minutes, and throughout this time, the top two disk writes were made by the System process and Chrome. Chrome was writing about a million bytes per second. And at times, it had several processes writing simultaneously.

Then I checked Chrome's cache folder, and it was a total of 858 files and 220MB. As sites update assets, the cache folder is rewritten, so it is constantly changing.

But of all these, Chrome's idle behavior was the most surprising. The Task Manager I/O Write column for Chrome showed 900 million bytes written over the session. This was significant because it was all from normal browsing sessions. Although I wouldn't classify any of these as crazy or dramatic spikes, they are frequent occurrences and are easy to overlook.

Related

Don’t Let Chrome Gobble RAM—Activate This Hidden Setting

Google Chrome is wonderful, but one of its biggest issues persists.

Limit how much Chrome writes to disk

Capping the cache reduced write activity in my testing

Curbing how Chrome's disk cache grows had to be my starting point. There isn't a single setting for this, but if you open the Properties of Chrome's shortcut (right-click the Chrome shortcut), you can append the flag below to the end of the Target path.

--disk-cache-size=104857600

The value I added after the equals sign instructs Chrome to keep the cache under 100MB. The tweak is complete when you restart the browser and clear your cache to remove any accumulated data.

Chrome may not strictly follow this set limit, but it mainly remains close to it.

With this tweak, my browser cache remained in a range of about 100–150MB. But that wasn't all. Looking through Resource Monitor, I observed fewer writes ranging between 12,000 and 80,000B/s (≈12–80KB/s) while performing light tasks.

I feared that working with a smaller cache would cause some slowdown in everyday use, but I noticed no significant slowdown.

Move Chrome’s cache off your SSD

Redirecting it takes the load off your primary drive

Limiting the cache was just a first step. I did not want my SSD bothered with Chrome's cache any longer, so I also moved it off the SSD. For this, I had to add another flag to the path: --disk-cache-dir=This flag requires a full path (for example, --disk-cache-dir="D:\ChromeCache").

This is what my entire target path now looks like:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --disk-cache-dir="D:\ChromeCache" --disk-cache-size=104857600

D:\ChromeCache was a folder I created on a different drive. After a restart, it automatically started writing its cache to this path. The goal is to shift the write load and give the primary SSD less work to do.

In fact, you have a few options for where you can shift Chrome's cache:

1. Secondary HDD: Slower, but completely fine for cache data
2. Secondary SSD: Faster, but still spreads wear across drives
3. RAM disk: Fastest and avoids persistent writes, but resets on reboot

Moving the cache to a secondary drive has not completely silenced Chrome disk writes, but they've become considerably less frequent. On Resource Monitor, I observe writes of about 9,000 B/s. On a different computer, I recently set up a RAM disk on Linux, and my browser cache is one of the things I have successfully moved to RAM.

Double-check after changing Chrome's cache path, because it sometimes reverts to the default location.

Finally, I turned to less consequential elements. While they wouldn't have the same impact as handling the cache, they still help with background writes.

The first of these was disabling Continue running background apps when Chrome is closed in Chrome's settings. With this setting turned off, Chrome and installed extensions or apps would not write as much data after the browser closes. After that, I navigated to the Preload Pages setting and set it to Standard. This reduces aggressive page caching while keeping the browser fast.

Local data and history were other aspects I paid attention to, even though they aren't a heavy source of writes. They are elements like history, cookies, and favicons that end up written to small, regularly updated databases. These elements can't be fully disabled, but you have more perspective just by being aware of them.

Then there are extensions too. Although they don't write as much to the disk, a few maintain filter lists or logs. I removed all the ones I don't actively use. In the end, I wasn't saving gigabytes of storage space, but that wasn't the goal. I made Chrome leaner and achieved far fewer writes to my SSD.