How to export a Framer site to a Next.js project
By Jake Marsh · Updated
To export a Framer site to Next.js, open Sourceferry in your project, tick the pages on the Export tab, choose Next.js (React, TypeScript) under Format and click Download ZIP. Unzip it, run bun install and bun run dev, and open http://localhost:3000. You get an App Router project with a page.tsx and page.css for each Framer page, your design components in components/, and images in public/images/. It has no dependency on Framer.
What's in the project
| Path | What it holds |
|---|---|
app/page.tsx, app/<route>/page.tsx | One route per Framer page, with its own page.css |
app/blog/[slug]/page.tsx | A CMS detail page, as a dynamic route |
components/ | One React component file per design component |
public/images/ | Images saved from Framer, with their alt text in the markup |
content/ | One JSON file per CMS collection, if you ticked it |
README.md | How to run it, and notes from the export |
sourceferry-report.csv | Every layer that didn't carry over, and why |
Color styles become CSS variables, with their dark values under the visitor's dark mode. Text styles become classes like ts-heading-h1, with their sizes per breakpoint.
Steps
- Open Sourceferry in the Framer project and stay on Export.
- Tick the pages. CMS detail pages are marked "CMS layout".
- Pick Next.js (React, TypeScript) under Format.
- Choose Images. Save into the ZIP puts them in
public/images/; Keep Framer's image links leaves them on Framer's servers. - Tick CMS collections as JSON if you want the content in
content/. - Click Preview first page to check the layout at each breakpoint.
- Click Download ZIP, unzip it and run:
bun install
bun run dev
- Open sourceferry-report.csv and work through what didn't carry over.
CMS pages in Next.js
A Framer CMS detail page, such as /blog/:slug, becomes app/blog/[slug]/page.tsx. It uses generateStaticParams to read the slugs from the collection's JSON, so bun run build makes a page for every item. The layout is the one you designed; binding each field (title, image, body) to the item's JSON value is the part you write.
Links and routes
Links between your pages become Next.js paths like /about. Email, phone, in-page and outside links stay as they are. Anything Sourceferry couldn't resolve is listed in the report.
What you'll add by hand
- Effects (shadows, blurs), interactions, animations and hover states: Framer's plugin API doesn't expose them.
- Code components and components from other projects: each gets a placeholder element with its name and Framer URL.
- Instance property values on design components: components come out in their primary variant.
- Forms, search and page SEO metadata.
- Font files you uploaded to Framer.
For one section rather than whole pages, see how to export a Framer component as React code.
What it costs
Scanning your pages and the preview are free. The trial covers 5 exports of up to 3 pages over 7 days, no card needed. After that Sourceferry is $59 a month, $499 a year or $799 once per seat, for every project and page. See the Sourceferry page.
Sourceferry
Export a Framer project as code you edit: a static HTML and CSS site or a Next.js project, built from the canvas inside the plugin, with breakpoints, styles, images, fonts and CMS content $59 a month or $499 a year per seat, or $799 once.
Questions
Which Next.js router does it use?
The App Router, in TypeScript, with a page.tsx per route.
Can I deploy it to Vercel?
It's a regular Next.js project with a package.json, so any host that runs Next.js can build it. Sourceferry doesn't deploy it for you.
Does it use Tailwind?
No. Each page gets plain CSS in its own page.css, plus shared rules for styles and components.
Can I export again after the design changes?
Yes, but each export is a fresh project. Keep your own code changes in version control and compare, since a new export doesn't merge into edited files.
More Sourceferry guides
- How to export a Framer component or section as React code
- How to host a Framer site yourself with a static export