# High cache storage usage on client browser

**URL:** <https://meta.discourse.org/t/high-cache-storage-usage-on-client-browser/166727>\
**Category:** Support\
**Created:** [October 9, 2020, 1:12am UTC](https://meta.discourse.org/t/high-cache-storage-usage-on-client-browser/166727 "2020-10-09T01:12:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![fireattack](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fireattack/32/196578_2.png) [@fireattack](https://meta.discourse.org/u/fireattack)\
**Post date:** [October 9, 2020, 1:12am UTC](https://meta.discourse.org/t/high-cache-storage-usage-on-client-browser/166727/1 "2020-10-09T01:12:45Z")

</div>

Today when I was checking my content settings on Chrome ( chrome://settings/content/all ), I noticed that a large portion of my local data storage come from discourse sites:

 ![screenshot](https://global.discourse-cdn.com/meta/original/3X/3/2/329b1035dfdf32c024f84f64a33150796335c8f6.png)

And I barely visit these sites, at most twice or thrice.  
(There is another which uses 1GB+ that I have already deleted before I screenshot.)

From the detail, most of them are “Cache storage”.

I’m not sure if it’s normal, but I think this should be addressed/improved. Using this much cache for a site that users don’t frequent doesn’t sound ideal.

---

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [October 9, 2020, 1:17am UTC](https://meta.discourse.org/t/high-cache-storage-usage-on-client-browser/166727/2 "2020-10-09T01:17:10Z")

</div>

This is a known behaviour of Chrome - please see this topic for more information:

> [@High local storage reported by Chrome](https://meta.discourse.org/t/high-local-storage-reported-by-chrome/165233/2):
>
> This is a know Chrome quirk where it misreports by a lot (100MB may be reported as 5GB). We are actively working on ways to mitigate this issue as we get frequent reports, but it is quite complicated as it involves assets served from CDNs. You can read more about it in [https://www.androidpolice.com/2019/09/16/google-chrome-site-settings-cache/#1](https://www.androidpolice.com/2019/09/16/google-chrome-site-settings-cache/#1)

---

<div class="post-metadata">

**Author:** ![fireattack](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fireattack/32/196578_2.png) [@fireattack](https://meta.discourse.org/u/fireattack)\
**Post date:** [October 9, 2020, 1:28am UTC](https://meta.discourse.org/t/high-cache-storage-usage-on-client-browser/166727/3 "2020-10-09T01:28:11Z")

</div>

Thank you for the quick reply.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [October 9, 2020, 3:39am UTC](https://meta.discourse.org/t/high-cache-storage-usage-on-client-browser/166727/4 "2020-10-09T03:39:59Z")

</div>