Offline access

1. What offline mode is

Offline mode means core HTML, JavaScript bundles, styles, icons, and a snapshot of the public tools list are stored locally after you opt in. The site can load from Cache Storage and show tool pages you have already cached. It does not upload your files to us as part of this offline package.

2. How files are stored

When you enable offline access, the app downloads the pages you choose to cache and saves responses the browser can replay later. Metadata such as whether offline mode is on, last sync time, and rough storage usage is kept separately from large structured data.

3. Storage technologies we use

IndexedDB

Structured snapshots (e.g. the public tools list) and room for larger offline payloads. Good for data you may query or extend later.

localStorage

Lightweight flags and metadata: offline enabled, last sync time, last known app/cache version, and tools list revision markers.

Cache Storage (service worker)

Network responses for HTML, JS, CSS, fonts, icons, and some API GET responses, coordinated with a versioned service worker for safe updates.

4. What is available offline

After setup, previously cached routes (home, marketing pages, tool pages included in the download, icons, and static chunks) can load without the network. Live-only features such as Google sign-in, admin dashboards, Firestore-backed dynamic tool discovery when no cache exists, analytics, chat widgets, and heavy assets loaded from third-party CDNs may still require connectivity.

5. When cache or storage is cleared

Browser settings that clear "cached images and files", "site data", or "all browsing data" can remove offline caches and IndexedDB contents for this site. After that, visit this page while online and run Enable offline access or Re-download offline data again.

6. Re-enabling offline files

Open this page on a working connection, then use the controls below (or the first-run prompt when it appears in a new session) to download the offline package again. If the service worker updated, accept the in-app update prompt to refresh the app shell safely.

7. How update detection works

While you are online, the app periodically checks a small manifest endpoint for the packaged app version and the newest tools timestamps, and asks the service worker to look for a new worker file. When something changes, you see a dialog to update now or later. Applying an update re-caches pages and can activate a waiting service worker so stale assets are not mixed with new ones.

8. Limitations

• First visit to a tool page while offline requires that page to have been cached earlier.
• Fonts loaded from Google Fonts may not render identically offline unless they were already cached by the browser.
• Tools that fetch large WASM or media from external URLs may not function fully until you are back online.
• Private browsing modes may restrict how much can be stored or how long it persists.

9. Feature coverage offline

Most standalone client-side tools should work if their JavaScript bundles were cached. Anything that depends on real-time admin data, remote configuration, or third-party-only scripts may degrade gracefully or show errors until connectivity returns.

10. Storage estimate

Typical installs land around tens of megabytes depending on how many tool routes you cache. The controls below show the last measured estimate from this browser after a completed download.

Install or save for quick access