Work with documents offline

After a production visit caches the application shell, LocalDocu can load without a network for supported local workflows.

What works offline

• App shell (HTML, JS, CSS, icons) via the service worker
• Local PDF and Word operations that do not need the network
• Informational pages that are part of the cached client app

Refresh while offline

• A normal reload can still open LocalDocu from the service worker cache after the first visit
• Hard refresh (Shift+Reload / Ctrl+Shift+R) bypasses the service worker and usually fails while offline
• Refreshing always clears in-memory documents and in-progress work in this browser session

What may vary

• First visit still needs a network to download and cache the app
• Folder access, save pickers, and other browser APIs differ by browser and device
• On Android Chrome, Add to Home Screen / install usually works after the first visit
• On iOS Safari, use Share → Add to Home Screen; service worker offline has tighter limits than Android
• Updates to the app require a connection when a new version is published

Offline is a product capability, not an error. Trust indicators show offline status without treating it as failure. Mobile browsers are best for select-files → run → download; full folder and native Save As remain strongest on desktop Chrome or Edge.

• Browser & device support
• Privacy model
• Future desktop capacity