Make Framer work offline
InstantPWA hosts a fallback service worker and manifest for Framer, so pages you've already visited keep working offline without you writing cache logic yourself. Add the snippet to Custom Code via Site Settings → General → Custom Code → End of <head> and the worker registers automatically on first visit.
Steps
- 1
Open Custom Code
Go to Site Settings → General → Custom Code → End of <head>.
- 2
Paste the InstantPWA snippet
Drop the one-line async script tag in the Framer 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 Framer URL on a mobile device (not the editor preview) to confirm the popup renders.
Constraints to know
- Any paid Framer site plan supports Custom Code; the free plan can add it in the editor but it won't run on the framer.website preview domain.
- Framer redeploys the whole site on publish, so custom code changes take a few seconds to propagate, not instantly like content edits.
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 Framer serves pages normally?+
No — the service worker only intercepts requests when the browser is offline; online visits behave exactly as before.