Make Laravel work offline
InstantPWA hosts a fallback service worker and manifest for Laravel, so pages you've already visited keep working offline without you writing cache logic yourself. Add the snippet to resources/views/layouts/app.blade.php via Blade layout <head>, alongside @vite or @mix directives and the worker registers automatically on first visit.
Steps
- 1
Open resources/views/layouts/app.blade.php
Go to Blade layout <head>, alongside @vite or @mix directives.
- 2
Paste the InstantPWA snippet
Drop the one-line async script tag in the Laravel head section — no build step or dependency install.
- 3
Let the service worker register
No manifest.json or sw.js to write — InstantPWA serves both and scopes the worker to your site's root.
- 4
Test offline mode
Visit a page once, then use DevTools → Network → Offline (or airplane mode on a phone) and reload to confirm cached pages still render.
- 5
Verify on a phone
Open your live Laravel URL on a mobile device (not the editor preview) to confirm the popup renders.
Constraints to know
- If you set a Content-Security-Policy header via middleware (common in Laravel Sanctum/Fortify starter kits), you must allow-list the InstantPWA script domain or it will be blocked.
- Run php artisan view:clear after editing the layout in environments where Blade view caching is enabled, or the change won't appear until the cache naturally expires.
FAQ
Do I need to write my own service worker?+
No — InstantPWA hosts a fallback manifest and service worker automatically if your site doesn't already ship one.
What happens to pages I haven't visited yet?+
They won't be available offline until visited at least once — InstantPWA caches on-visit rather than pre-caching your entire site.
Does offline mode change how Laravel serves pages normally?+
No — the service worker only intercepts requests when the browser is offline; online visits behave exactly as before.