Allowlist Framer domains
Learn how to allowlist the domains Framer needs to work on secure corporate networks
If your company uses a firewall or strict security policies, Framer may need access to specific domains to load correctly and work without interruptions.
Required domains
Allowlist the following domains on your network:
.framer.com.framerstatic.com.framercanvas.com.framerusercontent.com.framercdn.com.framer.app.jspm.io
Why these domains are needed
Framer uses these domains for core product functionality, including:
Loading the editor and interface
Hosting assets, fonts, and design files
Displaying project previews and published sites
Rendering the canvas and supporting real-time collaboration
Loading external package dependencies
Allowlisting these domains helps ensure the editor, published sites, assets, and supporting services load reliably.
What to do next
Share this domain list with your IT administrator or network security team so they can update your firewall, DNS, or network policies as needed.
If Framer still does not load correctly after allowlisting these domains, ask your IT team to verify that no additional firewall, proxy, or DNS restrictions are blocking access.
FAQ
Which domains should I allowlist for Framer?
Allowlist these domains:
.framer.com,.framerstatic.com,.framercanvas.com,.framerusercontent.com,.framercdn.com,.framer.app, and.jspm.io. These domains support core Framer functionality across the editor, hosting, previews, and dependencies.Why does Framer need multiple domains?
Framer uses different domains for different services, such as loading the editor, serving assets, rendering the canvas, and loading external packages. Allowlisting all of them helps prevent partial loading issues or broken functionality.
What should I do if Framer still does not work after allowlisting these domains?
Contact your IT administrator or network security team and ask them to review firewall, proxy, and DNS rules. They can confirm whether traffic to the required domains is still being blocked.
Updated