> May I ask whats the equivalent for it in Chrome as majority of users are on Chrome for me. I think for Chrome it's under devtools: https://developer.chrome.c

> May I ask whats the equivalent for it in Chrome as majority of users are on Chrome for me. I think for Chrome it's under devtools: https://developer.chrome.com/docs/devtools/storage/cache/ https://developer.chrome.com/docs/devtools/storage/cache/ > what you say can even be done with the service worker API I mentioned above Well no, because service worker API is going to be subject to the same security policies as any other site. If I understand what it is you're asking for, you want the Web-equivalent of doing something like doing overnight pushes of software updates to the enterprise. I don't know your environment, but you might be better off solving this by pushing large cachable things to edge caches closer to your users. If they're on the public internet, then caching resources out of a public CDN might do the trick. If they're on private networks in offices, then perhaps deploying something to those offices to serve local cache might work. You don't necessarily need networking magic to make this happen - a service that can locate your users, and then issue HTTP redirects to a local cache server could possibly do it. eg: call https://cache-main.example.com/some/resource.js https://cache-main.example.com/some/resource.js, the server does a geo lookup on my IP, and issues a 301 to https://cache-some-remote-location.example.com/some/resource.js https://cache-some-remote-location.example.com/some/resource... Trying to automate things like updating a user's cache directly in their browser seems like a major pain. How do you handle them not being logged in/sleeping/having multiple browser profiles/etc etc etc.