Own Your Framer Site as Real Next.js Code

No. Framer has no built-in code export — published sites stay on Framer's hosting. This converter fills that gap: it turns your published Framer site into a real Next.js App Router project you own and can deploy anywhere.

A complete, deployable Next.js project: your sections as named React components under src/sections, one view per Framer page under src/views, an App Router route per page, plus package.json, tsconfig, and config. Run npm install && npm run build and it deploys like any Next.js app.

Yes — exactly, because each page keeps Framer's own runtime and CDN assets intact. The Next.js project just wraps and serves the original page verbatim, so every animation, hover, and interaction behaves identically to the source instead of being approximated.

No. Only the public published URL is needed — no Framer account access, no Framer API key, no plugin, nothing to install. You do sign in to an account here so your conversions are saved to your dashboard, but that's an account with us, never with Framer.

Yes. Each exported page keeps its title, description, and Open Graph tags. The Hybrid (HTML) mode additionally rewrites canonicals to your new domain and runs a full SEO pass.

Yes. It's a standard Next.js project, so it deploys to Vercel or Netlify in one click from this tool (or anywhere Next.js runs, including Cloudflare). You can also download the .zip and use your own pipeline.

Choose Next.js when you want a real Next.js App Router project — package.json, TypeScript config, npm install && npm run build — with your page split into editable React components that still render every animation and interaction exactly as authored. Choose the HTML export when you want plain static files with zero framework, or when maximum Lighthouse score matters more than fidelity, since that mode strips Framer's runtime and rebuilds for speed. You can run both and compare.

Yes, for your own site. The converter only works with public published URLs, and you should only convert sites you own or have permission to export. It never bypasses logins or accesses private drafts.

No. This is an independent, third-party developer tool — it isn't affiliated with, endorsed by, or sponsored by Framer. Framer has no official code export; this fills that gap using each site's own public published URL.

Usually under a minute. Multi-page sites are discovered and converted automatically; larger sites can take a few minutes.

No — converting needs a plan, from $15/month at launch, and there is no free tier or pay-as-you-go. What costs nothing is everything after: the exported project is yours to keep, and a static host like Cloudflare Pages can serve it free with no bandwidth cap. There are no per-site fees.

Not necessarily, and we'd rather tell you that upfront than oversell it. This export keeps Framer's own runtime intact so animations and interactions stay exactly as authored — which means it carries over the same JS/image weight the original had. We tested this directly across 10 real templates and published the honest results. If maximum Lighthouse score matters more than pixel-perfect fidelity for your site, use the Hybrid HTML export instead, which strips the runtime and rebuilds for speed.

Yes. Run npx framer-to-nextjs <your-framer-url> in a terminal and the same converter writes the full Next.js project straight to disk — or the runtime-stripped static bundle with --mode hybrid. It works from a published Framer URL you own or are authorized to convert, with no login or plugin, and being a normal npm package, it's scriptable in CI or a nightly rebuild job.

Yes. Each page is split into named React component files — Hero.tsx, Pricing.tsx, Footer.tsx — taken from the section names you already gave them in Framer, composed by one page file per route. This genuinely used to be impossible: decomposing the markup broke Framer's runtime hydration, and we said so here for a long time. What changed is the cause, not a workaround — Framer's hydration markers turned out to be ordinary React Suspense boundaries, so once each pair becomes a real boundary the components re-render the original DOM exactly. On the sites we've measured, every element matches the source: 100% parity, animations and interactions included. To be clear about what it is: your own markup organised into files you can read, edit, and diff — not a hand-written rewrite. Framer's runtime and its inline styles come across as authored, so treat this as fidelity plus editability, not as a performance rebuild.