Allowlist Framer domains
Learn how to ensure Framer runs smoothly in high-security environments.
If you’re using Framer on a corporate network protected by a firewall or strict security policies, certain domains must be accessible for Framer to function correctly.
To ensure optimal performance, whitelist the following domains:
.framer.com.framerstatic.com.framercanvas.com.framerusercontent.com.framercdn.com.framer.app.jspm.io
These domains are used across various Framer features, including:
Editor functionality and interface loading
Hosting of assets, fonts, and design files
Project previews and published sites
Canvas rendering and real-time collaboration
External package dependencies
Allowing these domains ensures that the Framer editor, published sites, assets, and supporting services load without interruption.
If you’re unsure how to whitelist domains on your network, contact your IT administrator or network security team and provide them with the list above.
Which domains should I allowlist to ensure Framer works correctly in a corporate network?
To ensure Framer works correctly, you should allowlist the following domains: .framer.com, .framerstatic.com, .framercanvas.com, .framerusercontent.com, .framercdn.com, .framer.app, and .jspm.io.
What Framer features rely on these allowlisted domains?
These domains are used for editor functionality and interface loading, hosting of assets, fonts, and design files, project previews and published sites, canvas rendering and real-time collaboration, and external package dependencies.
What should I do if allowlisting these domains does not resolve my issue?
If allowlisting still doesn’t resolve the issue, share the required domain list with your IT administrator or network security team so they can verify firewall and DNS policies.
Updated