Framer to HTML, CSS and JavaScript, or Framer to Next.js, which do you need?
Framer doesn't export HTML, CSS and JavaScript. You can save a third-party snapshot of the published site: a frozen copy for archiving or cheap hosting that still leans on Framer's scripts, CDN and form service unless yo
Framer doesn't export HTML, CSS and JavaScript. You can save a third-party snapshot of the published site: a frozen copy for archiving or cheap hosting that still leans on Framer's scripts, CDN and form service unless you replace them. Or you can convert it into a Next.js project you keep editing, with components, CMS data and your own form routes. A snapshot copies output; a project produces it.
This post covers what Framer officially allows, what is actually inside an HTML, CSS and JS copy of a Framer page, what happens to assets, fonts, interactions and forms in that copy, and how to choose. Deframer, the tool behind this blog, writes projects (Next.js by default, or TanStack Start, Astro, React Router or Vite), and also a Static HTML download: the converted site built into HTML, CSS and JavaScript files, without Framer's runtime. We'll be fair to both.
What does Framer officially allow?
No HTML export. Framer's help center says "Framer does not offer HTML export for self-hosting", because "published sites are not fully static and cannot be exported as standalone HTML files for self-hosting"; Framer "uses dynamic backend services to optimize your website after it is published" (Framer Help). As of October 2026, what Framer does offer is:
- CMS content, which "can be exported using plugins into structured formats such as CSV or JSON" (Framer Help);
- reverse-proxy hosting through Advanced Hosting on Pro and Enterprise plans, which puts your infrastructure in front of Framer but still gives you no code (Framer Help);
- your own uploads: the images, videos and fonts you added are files you already have.
Framer also notes that "every Framer site is published as standard HTML, CSS, JavaScript, and static assets" (Framer Help). That's true of what a browser receives, and it's why snapshot tools exist. It isn't the same as a source project, as the next section shows.
Why the published HTML isn't an editable source project
The files a browser receives are the output of Framer's build, not the design you edit. We looked at a typical published Framer page (framer.com itself, in October 2026), and its HTML had:
-
CSS inlined in
<style>blocks in the page, with no separate stylesheet, using generated class names such asframer-1w39556; -
JavaScript as ES modules loaded from
framerusercontent.com/sites/<site-id>/, including Framer's runtime and React, preloaded with<link rel="modulepreload">; -
fonts declared with
@font-facerules pointing atframerusercontent.com/assets/β¦woff2; -
images served from
framerusercontent.com/images/withsrcsetsizes generated by Framer's image service; -
attributes such as
data-framer-nameanddata-framer-appear-idthat the runtime reads to run layers and appear animations.
None of that is the components, variants, breakpoints and CMS templates you built. Shared parts like the navigation are rendered into every page instead of written once. The scripts are minified bundles. You can edit the result, but you're editing compiled output.
What a static HTML, CSS and JS snapshot is
A static exporter visits each page of your published site and saves what the browser receives, laid out as folders a basic web server can serve:
index.html
about/index.html one HTML file per URL, styles inlined in <head>
blog/my-first-post/index.html CMS detail pages as they rendered that day
assets/ images, fonts and scripts, if the tool downloads them
Upload the folder to any static host and the pages load. It's a good fit when:
- the site is a landing page, an event page or a portfolio that's essentially finished;
- you want an offline archive of a site before you take it down;
- you need the cheapest possible hosting and will never edit the design again.
What happens to assets, fonts, interactions and forms in a snapshot?
Each part behaves differently, and the result depends on the tool you use. Check each of these in your copy before you take the Framer site down.
| Part | In a snapshot | What to check |
|---|---|---|
| Images and video | Links point to framerusercontent.com unless the tool downloads and rewrites them; responsive srcset sizes come from Framer's image service |
Whether every size in each srcset was saved locally, or still loads from Framer |
| Fonts |
@font-face URLs point to Framer's CDN unless rewritten |
That fonts load from your host, and that your font licence allows self-hosting |
| Interactions and animations | Hover states, menus, carousels and appear effects run from Framer's JavaScript modules; kept, they still load from Framer, and stripped, the page goes static | Open menus, hover states and scroll effects at each width, with Framer's domains blocked in the browser |
| Native forms | Submissions are handled by Framer's servers, which a copy you host doesn't control | Point each form at your own endpoint or a form service |
| CMS pages | Frozen as rendered; a new post means a new HTML file by hand | Whether search, filters or pagination still work |
| Redirects | Not in the files at all | Recreate them in your host's config |
The safe assumption is that a snapshot works while Framer's CDN keeps serving your files. If your goal is to leave Framer completely, every row above needs a fix.
What a Next.js project is
A converter that targets Next.js writes the source code that renders your pages, not the pages themselves. With Deframer, a converted project looks like this:
src/
app/ one page.tsx per URL, with its metadata
views/ page components, each with a CSS module
components/ design components in the designer's folders
styles/ color styles as CSS variables, text styles, fonts
cms/ each collection as <name>.ts (schema) + <name>.json (records)
site/forms.ts native forms, served by app/api/forms/<form>/route.ts
lib/deframer/ the helper kit that replaces Framer's runtime
public/ robots.txt and sitemap.xml as the site publishes them
Change the header component once and every page that uses it changes. Add a record to src/cms/blog.json and the detail page is prerendered on the next build, through generateStaticParams. Forms post to the project's own route handlers and deliver to a webhook URL you set. Animations run on the motion package, and there's no Framer runtime. Assets either stay on Framer's CDN (Assets on Framer's CDN, the default) or, with Assets in the project, are downloaded into public/. What you get in a converted Next.js project goes folder by folder.
A snapshot copies what the browser received; a project contains the source that produces it.
Side by side
| Static HTML snapshot | Next.js project (Deframer) | |
|---|---|---|
| What you get | The pages as rendered | The source that renders them, in TypeScript |
| Shared parts | Repeated in each file | React components, written once |
| Styles | Inline generated CSS | CSS modules, design tokens as CSS variables |
| Interactions | Framer's bundled scripts, or none | React and motion, in readable code |
| Editing text or layout | Edit generated markup | Edit a component or a JSON record |
| CMS | Pages frozen as they were | Collections as JSON with a schema, detail pages prerendered |
| Native forms | Need a new endpoint | One route handler per form, webhook delivery |
| Redirects | Depend on your host's config | Listed in next.config.ts
|
| Page metadata | In each HTML file |
metadata per route, metadataBase in the root layout |
| Hosting | Any static host | Anywhere Next.js runs: Vercel, Netlify, a container, your own server |
| Who maintains it | Anyone who can edit HTML | Someone comfortable with React and Next.js |
Note
A Next.js project can also be built into plain static files with
output: 'export', but that mode doesn't support redirects innext.configor route handlers that read the request (Next.js docs). A converted project uses both for redirects and forms, so you'd move those to your host and a form service first. Deframer doesn't do this for you.[!NOTE]
If what you want is prerendered HTML you can still edit as a project, Deframer's Astro, React Router and Vite exports prerender every page to static HTML at build time. Astro and React Router still run a small Node.jsserver.tsfor redirects and forms, so they are projects, not a folder of files; Vite's build is a folder of static files (dist/) for any static host, its redirects in the host's files and its forms posting to a form service. Deframer's Static HTML download is that folder, already built, for when you only want files to upload.
Where the snapshot wins
Simplicity. A folder of HTML has no build step, no dependencies to update and no Node.js version to think about. For a site that's finished, that's a real advantage, and a Next.js project would be more machinery than you need.
Where the project wins
Change. Most sites keep changing: a new case study, a pricing update, a form that should go to a CRM. In a project, each of those is a small edit in a file that says what it is. You can put it under Git, review changes on branches, and deploy previews before anything goes live. Maintaining a converted Framer site with Git shows that workflow.
It also leaves room to grow. A Next.js project can add an API route, authentication or a headless CMS without leaving the codebase. Adding a headless CMS to a converted Framer site is one example.
How to choose
- Will anyone change this site after the move? If not, a snapshot is enough.
- Must it run with no requests to Framer? Then a snapshot needs every asset, font and script rewritten, or a project.
- Does it have CMS collections that grow? Then a project, where records are data, will save repeated manual work.
- Does it have forms? Either route needs a destination for submissions. In a converted project that's an environment variable; see how Framer forms work after moving to Next.js.
- Who will maintain it? A Next.js project needs someone comfortable with React. If nobody is, consider staying on Framer, where editing stays visual.
- Does search traffic matter? Both can preserve URLs. A project also keeps your redirects, per-page metadata and canonical URLs in code you can check; keeping your SEO when moving off Framer has the list.
If you want React without Next.js, converting Framer to React covers the options.
What converting to Next.js costs
Converting is free. Downloading a converted project costs 1 credit when you verify the site by publishing a one-line meta tag on it, or 10 credits without verification after confirming you own it or have permission. Packs are one-time: $10 for 1 credit, $25 for 5 or $100 for 30, on the pricing page. Credits never expire, a failed conversion costs nothing, and re-downloading the same project is free for the 7 days the download is kept.
Deframer is an independent tool and is not affiliated with, endorsed or sponsored by Framer. It reads only the public files your published site serves; nothing in your Framer account is touched.
FAQ
Can I export my Framer site to HTML, CSS and JavaScript?
Not from Framer itself; its help center says it doesn't offer HTML export for self-hosting. Third-party tools can save a static copy of the published site. Deframer converts it instead: as a Next.js, TanStack Start, Astro, React Router or Vite project, or as Static HTML, the converted site built into files to upload, without Framer's runtime.
Does a Framer HTML snapshot still depend on Framer?
Usually, unless the tool rewrites it. Published pages load their scripts, fonts and images from framerusercontent.com, and native forms submit to Framer's service, so check each one in your copy.
Will animations and interactions work in an HTML export?
Only while Framer's JavaScript bundles still load. Without them, hover states, menus and appear animations stop working. A converted Next.js project replays them with the motion package instead.
Do Framer forms work in an HTML export?
No, they need a new destination. In a Deframer project each form posts to its own route, /api/forms/<name>, which delivers submissions to the webhook URLs you configure.
Is a static HTML export good enough for SEO?
It can be, if every URL stays the same and each page keeps its title, description and canonical tag. You'll need to recreate redirects on your new host. A converted Next.js project keeps redirects in next.config.ts and metadata in each route file.
Which is cheaper to host, HTML or Next.js?
A folder of static HTML can be hosted almost anywhere for very little. A Next.js project needs a host that runs Next.js, or a container or server of your own; see Framer hosting vs. self-hosting for how the costs are structured.
Originally published on the Deframer blog. Deframer converts a published Framer site into Next.js, Astro, React Router, TanStack Start, Vite, Nuxt or static HTML code.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.