PWA Cache Budget Calculator
Enter the URLs in your PWA precache manifest and set your cache budget to calculate total cache size, GZIP and Brotli savings for each asset type, and get specific recommendations for which assets to exclude to stay within budget. Runs entirely in your browser — no network requests, no signup required.
Enter the URLs in your PWA precache manifest and set your cache budget. The calculator estimates total cache size, shows GZIP and Brotli savings per asset, and recommends which assets to exclude to stay within budget. Runs entirely in your browser — no network requests, no signup required.
Leave "Known size" blank to use typical sizes for each asset type. Enter the actual file size in KB for more accurate results.
Why Use Our PWA Cache Budget Calculator?
Instant Cache Budget Calculation
Paste your precache URL list, set your budget, and instantly see total cache size, GZIP and Brotli savings, and which assets to exclude — all in one click.
Secure PWA Cache Budget Calculator Online
All calculation runs entirely in your browser. No URLs are fetched and no data leaves your device — safe for analyzing internal, staging, or production manifests.
Smart Exclude Recommendations
When your precache exceeds the budget, the calculator recommends which assets to move to runtime caching — prioritizing critical HTML, CSS, and JS over large media files.
100% Free Forever
Calculate as many PWA cache budgets as you need, completely free. No account, no subscription, no limits, and no ads.
Common Use Cases for PWA Cache Budget Calculator
PWA Precache Manifest Planning
Before deploying a new service worker, use the pwa cache budget calculator to ensure your precache stays within the 50 MB storage quota recommended for mobile devices.
First Install Performance Budget
Calculate how much data users download on first PWA install — identify large assets that should be lazy-loaded rather than precached to speed up the install event.
Cache Storage Quota Debugging
Diagnose why your PWA is hitting storage quota limits — identify which asset types consume the most cache space and get specific recommendations for each file type.
Workbox Configuration Review
Review your Workbox precache configuration before deployment — estimate the impact of adding or removing assets from the manifest on total cache size and budget compliance.
Compression Strategy Audit
Identify which assets in your precache list are not benefiting from HTTP compression — get specific Brotli and GZIP recommendations for each file type to reduce transfer size.
CDN Bandwidth Cost Planning
Estimate the bandwidth cost of serving your precache assets with and without compression — calculate monthly savings from enabling Brotli on your CDN for PWA delivery.
Understanding PWA Cache Budgets
What is a PWA Cache Budget Calculator?
A PWA cache budget calculator calculates the total storage consumed by a list of URLs in a service worker precache manifest and compares it against a configurable budget — showing which assets should be excluded to stay within the limit. Our free pwa cache budget calculator runs entirely in your browser, detects each asset type from the URL extension, applies typical compression ratios, and recommends which assets to move to runtime caching when the budget is exceeded.
How Our PWA Cache Budget Calculator Works
- Enter Your URLs and Budget: Paste the URLs from your service worker precache manifest — one per row. Set your cache budget in MB (default 50 MB). Optionally enter the known file size in KB for each URL.
- Instant Browser-Based Calculation:Click "Calculate Cache Budget" — the tool detects each asset type, applies typical compression ratios, calculates total cache size, and compares it against your budget. No network requests are made.
- Review Exclude Recommendations: Assets that push you over budget are marked for exclusion — prioritizing critical HTML, CSS, and JS while recommending large media files for runtime caching instead.
What Gets Analyzed
- Asset Type Detection: URL extensions classify each asset as HTML, CSS, JS, JSON, raster image, SVG, font, audio, video, or binary.
- Compression Ratios: Each asset type has typical GZIP and Brotli compression ratios — text assets compress 70–85%, while binary formats gain almost nothing from HTTP compression.
- Budget Enforcement: The calculator sorts assets by priority (critical → high → medium → low) and marks the lowest-priority assets for exclusion when the total exceeds your budget.
- Per-Asset Strategy: Each asset gets a specific recommendation — from enabling Brotli to switching to WOFF2 for fonts or WebP for images.
PWA Cache Storage Quotas
Browsers impose storage quotas on service worker caches. Chrome and Edge allow up to 60% of available disk space, but the practical recommendation is to keep your initial precache under 50 MB for a good user experience on mobile devices. Large precache manifests delay the service worker install event and can cause quota errors on low-storage devices. Use this pwa cache budget calculator to keep your precache lean — move large audio, video, and non-critical images to runtime caching instead of precaching them.
Related Tools
JSON Key Shortener
Shorten verbose JSON keys to single letters or abbreviated forms — shows size reduction and provides a downloadable key mapping file for restoration. Free online JSON key shortener.
JSON vs MessagePack Size Comparison
Compare JSON byte size vs MessagePack encoding for any payload — shows exact savings, type-by-type breakdown, and MessagePack hex preview. Free online JSON vs MessagePack comparison.
String Decompressor (GZIP/LZ)
Decompress GZIP+Base64, DEFLATE+Base64, and LZ-String compressed payloads back to readable text — supports all three LZ-String variants. Free online string decompressor.
ZIP File Extractor
Extract files from any ZIP archive client-side — browse contents, preview text files, download individual files or all at once. Free online ZIP extractor, no signup required.
Frequently Asked Questions About PWA Cache Budget Calculator
A PWA cache budget calculator calculates the total storage consumed by a list of URLs in a service worker precache manifest and compares it against a configurable budget — showing which assets should be excluded to stay within the limit. Our free online pwa cache budget calculator runs entirely in your browser — no network requests are made and no data leaves your device.
No. The pwa cache budget calculator estimates sizes based on the URL file extension and typical sizes for each asset type. If you know the actual file size, enter it in the "Known size (KB)" column for a more accurate estimate. This approach works without network access and is safe for internal or staging URLs.
Yes, complete privacy is guaranteed. All calculation runs entirely client-side in your browser. No URLs are fetched and no data leaves your device — safe for analyzing internal, staging, or production URLs that may contain sensitive path information.
Yes. The pwa cache budget calculator is 100% free with no signup, no subscription, no URL limits, and no ads. You can calculate as many PWA cache budgets as you need.
The practical recommendation is to keep your initial precache under 50 MB for a good user experience on mobile devices. Chrome and Edge allow up to 60% of available disk space, but low-storage devices may have much less. Large precache manifests also delay the service worker install event, which can hurt first-load performance.
The pwa cache budget calculator sorts assets by priority — HTML, CSS, and JS are considered critical and kept first. JSON and SVG are high priority. Raster images and fonts are medium priority. Audio, video, and binary files are low priority and are the first candidates for exclusion when the total exceeds your budget.
Raster images (JPEG, PNG, WebP, AVIF) and audio/video files are already compressed using their own codecs — applying HTTP compression on top adds almost nothing and wastes CPU. WOFF2 fonts are already Brotli-compressed internally. For these asset types, the tool recommends format-level optimizations instead (e.g. WebP for images, WOFF2 for fonts).
If you use Workbox, the precache manifest is generated during your build process — look for the workbox-precache-manifest.*.js file or the injected manifest in your service worker. For manual service workers, list the URLs you pass to cache.addAll() in your install event handler.
Assets marked for exclusion should be moved from precaching to runtime caching. In Workbox, use registerRoute() with a caching strategy like StaleWhileRevalidate or CacheFirst for these assets. Runtime caching stores them on demand as the user navigates, rather than downloading everything upfront during the install event.