Move your Framer site to clean Next.js code

Deframer converts a published Framer site into a clean Next.js project written in TypeScript, which you download as a .zip and own. Every page becomes a Next.js App Router route, components become React components with CSS modules, CMS collections become JSON files and native forms post to the project's own route handlers. There is no Framer runtime in the project, so it runs and deploys anywhere Next.js does.

Signed in, you can convert any published Framer site for free. It can be published on framer.website, framer.app or a custom domain: use the address visitors open, not the editor link. To download the code, the site must be yours, or its owner must have given you permission, such as a client. Verify for 1 credit, or confirm you have permission and download without verification for 10 credits.

You can convert it, but you can't download its code without the owner's permission. Deframer is for moving your own site to Next.js, Verify by asking the owner to publish your code for a 1-credit download, or confirm that you have their permission and download directly for 10 credits. Taking someone else's site without it breaks our terms, and we act on reports.

You add your personal verification meta tag to your Framer site's custom code and publish the site; Deframer then finds it on the live page.

1. Convert your site, then choose Download. Deframer shows your verification code, a one-line meta tag.
2. In Framer, open Site Settings → Custom Code and paste it at the end of the <head> tag.
3. Publish your site, then click Check again. Once verified, use 1 credit to unlock the download.

Prefer to skip verification? Choose Download directly, confirm you own the site or have permission, and use 10 credits.

Verification lets you download for 1 credit by showing you control the site. Only someone who can publish a site can put the code on it, so finding it shows you control the site. Your code is personal and works for all your sites. We check it on the live page before each verified download. You can also download without verification for 10 credits by confirming you own the site or have permission. The converted project never contains the tag.

You own the converted code of your own site, and Deframer claims no rights in it: its content, design and code stay yours (or your client's), as they were. It includes Deframer's small helper kit, which you may use and change as part of the project, and open-source packages under their own licences. It doesn't include Framer's runtime.

You need a free Deframer account to convert a site, and credits to download: 1 with site verification, or 10 without it. Credits come in packs on the pricing page ($10 for 1 credit, $25 for 5, $100 for 30) and never expire. Converting, the live preview and compare view when they're available, and downloading the same project again are free, so a conversion that fails costs nothing.

A conversion can run for up to 10 minutes and produce a project of up to 1 GB.

• 3 free conversions a day; 20 a day once you've bought credits (over a rolling 24 hours). Conversions that fail because the server was busy don't count.
• Up to 5 conversions per 10 minutes, with up to 2 running at once.
• Very large sites may not fit. Try again with "Include assets locally" off: images, fonts and videos then stay on Framer's CDN, which makes the download much smaller.
• Conversions run a few at a time. When it's busy, yours waits in line and the page shows its place. Conversions from accounts that have bought credits go first; a free one that has waited about 10 minutes goes ahead.

Each conversion is private to your account, and its project and .zip are deleted 7 days after the conversion finishes. Only you can open its download, and its preview and compare view when there are any. Once deleted it shows as expired, and you can convert the site again. A live preview, when there is one, closes 10 minutes after it is ready.

To convert your site, Deframer reads the files it publishes, the same ones a browser loads; nothing in your Framer account is touched. A password-protected site is read with the password you enter, which is used once and never stored. The details are in the privacy policy.

Leave it off unless you want the converted site to stop depending on Framer's CDN. Off (the default), images, fonts and videos keep loading from Framer's CDN: the download is small and the conversion fast. On, they are downloaded into the project's public/ folder, so the site no longer depends on Framer at all. That takes longer and makes a bigger zip.

The converted Next.js site is close to the original but not guaranteed to be identical: layouts, breakpoints, animations, interactions and CMS pages are carried over from the published Framer site. Check every page: in the compare view when a live preview is available, or by running the project. Code components and third-party embeds stay as the site's own code.

Yes, whenever you like, for free. Every conversion is its own project, so converting again (after you republish, for example) makes a new project, and downloading that one uses a credit too. If you convert the same published version with the same options within 30 minutes, you get the same project back, so a download you already paid for stays free.

Unzip it and run npm install, then npm run dev: it is a standard Next.js App Router project that needs Node.js and nothing from Framer. Deploy it anywhere Next.js runs: Vercel, Netlify, a container or your own server.

Protect your site to block Deframer conversions, downloads and previews while active: verify ownership, then activate for 10 credits once. Both download options follow this block. The optional inline helper deters some capture tools, but third-party services may ignore it and public source remains accessible. Report misuse at mehdi@deframer.co as described in our terms.

No. Deframer is an independent tool. It is not affiliated with, endorsed or sponsored by Framer. "Framer" is a trademark of its owner and is used here only to describe which sites the tool converts.