How to self-host a Framer site
Yes — you can self-host a Framer website, even though Framer has no export button. The route: convert your published site to static HTML or a Next.js project, deploy it to a host you control, and point your domain there. Ten minutes end to end, and for most sites the ongoing cost is $0/month on Netlify or Vercel free tiers.
Why self-host at all?
- Cost. Framer's paid site plans bill per site, per month. A converted static site on a free tier costs nothing to serve.
- Ownership. Your site becomes plain files or a normal codebase — no builder subscription required to keep it online, no lock-in.
- Speed. The HTML export re-encodes images to WebP and removes trackers, which can improve Core Web Vitals.
- Flexibility. Add server logic, integrate with your stack, or hand the project to a developer — things a hosted builder can't offer.
The 4-step process
- 1Convert your published site
Paste your public Framer URL into the converter. Choose the HTML export for the fastest static bundle, or the Next.js export for a real code project.
- 2Preview and download
Check the live preview, then download the bundle (.zip) — or skip the download and deploy directly.
- 3Deploy to your host
One-click deploy to Netlify or Vercel with your own token, or drag the folder into Netlify Drop, Cloudflare Pages, GitHub Pages, or S3.
- 4Point your domain
Add your custom domain at the new host and update your DNS (usually one CNAME). Your Framer subscription is no longer needed to keep the site online.
Where to host (all work)
| Host | Free tier fits a converted site? | Notes |
|---|---|---|
| Netlify | Yes | One-click deploy from this tool; drag-and-drop also works. |
| Vercel | Yes | One-click deploy; natural home for the Next.js export. |
| Cloudflare Pages | Yes | Unlimited static requests on the free plan. |
| GitHub Pages | Yes | Good for the HTML bundle; push the folder to a repo. |
| S3 / shared hosting | Cheap | Any host that serves files works — no build step needed. |
Honest limitations
Password-protected Framer pages can't be converted — the tool reads public URLs only. Framer's built-in form backend stays with Framer, so repoint forms to a service like Formspree or Tally after migrating. And in HTML mode, heavy runtime effects (custom cursors, WebGL) are trimmed for speed — the Next.js export keeps them if you need exact behavior.
Self-hosting FAQ
Can you self-host a Framer website?
Yes. Framer doesn't offer code export itself, but you can convert the published site to static HTML or a Next.js project and host it anywhere — Netlify, Vercel, Cloudflare Pages, GitHub Pages, S3, or classic shared hosting.
Is self-hosting a Framer site free?
Static hosting can be free. FNJ's current flash sale includes unlimited Framer site conversions, downloading and lifetime access for $29 once through November 1, 2026. Once exported, the files can be hosted wherever you choose.
Do I keep my design and animations?
Yes. The HTML export preserves your layout, fonts, and breakpoints, and rebuilds appear/scroll animations in CSS. The Next.js export keeps Framer's runtime for exact behavior, including complex interactions.
What happens to my SEO when I move?
The converter preserves titles, descriptions, and your URL structure, and points canonicals at your new domain. Keep the same domain and paths and rankings carry over; if you change domains, add 301 redirects from the old one.
Can I still edit the site after leaving Framer?
Yes. The exported files are plain HTML or a normal Next.js codebase you can edit directly. An MCP-connected agent can also update supported site content and publish it.
What can't be self-hosted?
Password-protected pages (the converter only reads public URLs) and Framer-hosted form backends — swap forms to a service like Formspree or Tally. Everything rendered on your public pages comes along.
Start self-hosting in one minute
Example: https://your-site.framer.website