Google Chrome is one of the most popular browsers and is used by a large percentage of users. However, it has one significant drawback – it does not allow users to delete files from the cache. This applies to Windows and macOS. Specifically, on Windows, these files are located in C:\Users\\AppData\Local\Google\Chrome\User Data\Default\Code Cache\Js, while on macOS they are located in ~/Library/Caches/Google/Chrome/Default/Cache/Js.
For example, one user stated that on his main MacBook Pro , he recently discovered 124,000 files dating back to mid-2020 and ranging from a few hundred bytes to a few hundred kilobytes. The entire folder is about 600MB in total. So, he started checking if it was true that clearing the cache did not delete these files. He also noticed that these files were slowing down Chrome , so he tried deleting them. Then he noticed that Google Chrome started working faster after deleting these files. Then, he was looking for a way to delete these files without having to “dig” in the system . What he discovered may “free the hands” of many Windows users. Specifically, he says that he found a way, which may sound strange. This method involves installing CCleaner Pro, which is not free, as well as installing a free third-party add-on called CCEnhancer and then using it to delete files from the cache. As for macOS users, there is currently no way to clear the cache. For these users, the only tool is the Finder.
Does clearing the cache “hide” disadvantages?
So far, no disadvantages have been found regarding clearing the cache, however, caution is needed from any user who attempts to do it, since unexpected problems may arise. Also, every time a user goes to delete files, there is a risk of deleting the wrong object, which can prove detrimental, especially for any user who does not have a backup.
In summary, Google Chrome can store hundreds of thousands of files on your computer, in the cache, but it does not give you the ability to delete them. However, it appears that clearing this cache somewhat improves Google Chrome's performance.
