Framer offers Advanced Hosting, which lets you use reverse proxy functionality directly within Framer—without relying on third-party hosting tools or infrastructure. Advanced Hosting is ideal if you want reverse proxy capabilities with a fully managed Framer setup.
Advanced Hosting is currently an Enterprise only feature, with a closed beta signup for Pro and Scale plans.
You can also use reverse proxy hosting to integrate a Framer site with your own existing hosting provider or infrastructure. This approach gives you full control over headers, authentication, delivery, and more; while keeping Framer as the content origin.
Reverse proxy hosting is available as an add-on with the Scale plan and is included with Enterprise plans.
With reverse proxy hosting, your server requests pages directly from your Framer site and serves them to visitors. This removes the need to download and upload files after every update.
Your hosting platform forwards a visitor’s request to the Framer site, applies any custom logic you’ve configured, caches the response, and serves it to the client. Future requests are typically served from the cache, improving performance and reliability.
This setup gives you more control over how your site is delivered, while Framer continues to manage the content.
Reverse proxy hosting enables advanced setups, including:
Custom routing to host multiple sites on a single domain.
Custom domains and SSL certificates.
Custom HTTP security headers and redirects.
A custom CDN for localized performance improvements.
Fine-grained caching behavior.
A custom WAF for security management.
Edge functions for authentication, analytics, or request handling.
Customers typically use reverse proxy hosting to:
Consolidate multiple websites under one domain using path-based routing.
Add authentication, analytics, or cookies before requests reach Framer.
Create a server-side analytics or optimization layer.
Add an additional caching layer for performance and reliability.
Route traffic through approved enterprise infrastructure.
Framer doesn’t support reverse proxy setups that:
Modify or remove tags in <head>. Some <head> tags are managed by Framer’s JavaScript. Changing or removing them can cause unpredictable behavior or break future updates. Adding tags is supported.
Add, modify, or remove content inside <div id="main">. This element contains the site’s React-managed content. Changes here can break the site. Modifying <body> outside of <div id="main"> is supported, as long as Framer scripts remain unchanged.
Reverse proxy hosting works with any platform that supports reverse proxies. Follow these steps in order for a reliable end-to-end setup.
Add a custom domain to your Framer site. Point your proxy at a custom domain you own (for example origin.example.com) or a *.framer.website domain. Don't use a *.framer.app domain as the origin—framer.app domains aren't indexed by search engines, which will negatively affect SEO, and can produce unexpected results with features like Staging.
Configure your reverse proxy. Any platform that supports reverse proxies will work. We provide step-by-step guides for supported providers:
Set the Canonical URL. In your site's General settings, set the Canonical URL to the public URL visitors will see (for example https://example.com). This step isn't mandatory, but sites without a Canonical URL perform worse in search: setting it avoids SEO issues and ensures search engines index the right domain for your content. A Canonical URL is available with the Advanced Hosting add-on.
Align paths when using subpaths. If you're serving Framer under a subpath (for example example.com/products/*), your Framer project pages must use matching paths (/products/<page>). Client-side routing depends on this alignment.
Avoid trailing slashes. Configure your proxy to redirect or rewrite trailing slashes to non-trailing paths. Framer's client-side routing expects consistent paths—URLs like /pricing/ can break navigation or create duplicate routes.
Be cautious when using a custom Content Security Policy. A strict or incomplete CSP can break site functionality. We recommend avoiding a custom CSP unless you’re familiar with its implications.
If you proceed:
Allowlist all required Framer domains.
Include worker-src 'self' blob: so the anti-bot system can run during form submissions.
Test thoroughly in a staging environment before deploying to production.