<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Mehdi Hassan</title>
    <description>The latest articles on DEV Community by Mehdi Hassan (@designify101).</description>
    <link>https://dev.to/designify101</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4246691%2F8beb780a-bed8-491e-9a72-4ce5b97b7e55.png</url>
      <title>DEV Community: Mehdi Hassan</title>
      <link>https://dev.to/designify101</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/designify101"/>
    <language>en</language>
    <item>
      <title>Export a Framer site as a static site with Vite</title>
      <dc:creator>Mehdi Hassan</dc:creator>
      <pubDate>Mon, 16 Nov 2026 01:23:21 +0000</pubDate>
      <link>https://dev.to/designify101/export-a-framer-site-as-a-static-site-with-vite-5609</link>
      <guid>https://dev.to/designify101/export-a-framer-site-as-a-static-site-with-vite-5609</guid>
      <description>&lt;p&gt;Framer can't export static files, but you can turn a published Framer site into one. Convert it with Deframer to the Vite target and you get a Vite and React project in TypeScript; &lt;code&gt;npm run build&lt;/code&gt; prerenders every page into &lt;code&gt;dist/&lt;/code&gt; as HTML, and that folder is the whole site. Upload it to Netlify, Cloudflare Pages, Vercel, GitHub Pages or an S3 bucket behind a CDN, with no server to run. Unlike a saved-page snapshot, it is a project you can keep editing and rebuild.&lt;/p&gt;

&lt;p&gt;Deframer is an independent tool and is not affiliated with, endorsed or sponsored by Framer. Downloading the code is for your own site or one whose owner allows it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Static snapshot or static build?
&lt;/h2&gt;

&lt;p&gt;There are two ways to end up with static files from a Framer site, and they are very different.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Saved HTML snapshot&lt;/th&gt;
&lt;th&gt;Vite project&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;How you get it&lt;/td&gt;
&lt;td&gt;Save the rendered pages with a crawler or "Save page as"&lt;/td&gt;
&lt;td&gt;Convert the site, then &lt;code&gt;npm run build&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What you edit&lt;/td&gt;
&lt;td&gt;Minified HTML and Framer's bundled scripts&lt;/td&gt;
&lt;td&gt;React components, CSS modules, JSON content&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Depends on Framer's scripts&lt;/td&gt;
&lt;td&gt;Usually, yes&lt;/td&gt;
&lt;td&gt;No: a small kit in the project replaces the runtime&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CMS&lt;/td&gt;
&lt;td&gt;Frozen in the HTML&lt;/td&gt;
&lt;td&gt;JSON files you edit, then rebuild&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Forms&lt;/td&gt;
&lt;td&gt;Post to Framer, which stops when the plan ends&lt;/td&gt;
&lt;td&gt;Post to a form service you choose&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Redirects&lt;/td&gt;
&lt;td&gt;Lost&lt;/td&gt;
&lt;td&gt;Carried over for common static hosts&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://deframer.co/blog/framer-to-html-or-nextjs" rel="noopener noreferrer"&gt;Framer to HTML or Next.js&lt;/a&gt; goes deeper on snapshots. This post is about the second column.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you export a Framer site with Vite?
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Sign in to Deframer and paste the published address.&lt;/li&gt;
&lt;li&gt;Choose &lt;strong&gt;Vite&lt;/strong&gt; in the framework menu.&lt;/li&gt;
&lt;li&gt;Pick the asset option. For a fully self-contained static site, choose &lt;strong&gt;Assets in the project&lt;/strong&gt; so images, fonts and videos are copied into &lt;code&gt;public/&lt;/code&gt;. The default keeps them on Framer's CDN, which makes the download smaller.&lt;/li&gt;
&lt;li&gt;Convert (free, up to 10 minutes) and review the notices.&lt;/li&gt;
&lt;li&gt;Verify ownership with the one-line meta tag and download. A verified download is 1 credit, or free with the lifetime deal.&lt;/li&gt;
&lt;li&gt;Build:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install
npm run build      &lt;span class="c"&gt;# vite build, then scripts/prerender.ts&lt;/span&gt;
npm run preview    &lt;span class="c"&gt;# serves dist/ the way a static host does&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The build needs Node.js 22.18 or later on your machine or CI. Production needs nothing but a static host.&lt;/p&gt;

&lt;h2&gt;
  
  
  What does &lt;code&gt;dist/&lt;/code&gt; look like?
&lt;/h2&gt;

&lt;p&gt;The prerender script writes every page as a flat file at its URL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;dist/
  index.html          /
  about.html          /about
  blog/
    first-post.html   /blog/first-post
  404.html            the 404 page
  assets/             scripts and stylesheets
  _redirects          for Netlify and Cloudflare Pages
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each page is styled before its scripts run, then hydrates in the browser. After that, links open the next page in the same document with React Router, so the layout template two pages share stays mounted.&lt;/p&gt;

&lt;p&gt;Netlify, Cloudflare Pages and GitHub Pages serve &lt;code&gt;about.html&lt;/code&gt; at &lt;code&gt;/about&lt;/code&gt; without extra settings. The project's &lt;code&gt;vercel.json&lt;/code&gt; turns on clean URLs for Vercel.&lt;/p&gt;

&lt;h2&gt;
  
  
  Redirects on a static host
&lt;/h2&gt;

&lt;p&gt;Framer sites often carry redirects from older URLs. The Vite project brings them as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;public/_redirects&lt;/code&gt;, read by Netlify and Cloudflare Pages;&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;vercel.json&lt;/code&gt;, read by Vercel;&lt;/li&gt;
&lt;li&gt;for hosts with neither, such as GitHub Pages, a small page at each old URL that sends the browser on.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Search engines handle server redirects best, so prefer a host that reads &lt;code&gt;_redirects&lt;/code&gt; or &lt;code&gt;vercel.json&lt;/code&gt; if your old URLs have rankings worth keeping. See &lt;a href="https://deframer.co/blog/seo-when-moving-off-framer" rel="noopener noreferrer"&gt;keeping SEO when moving off Framer&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Forms without a server
&lt;/h2&gt;

&lt;p&gt;A static site has nowhere to post a form to, so each native form posts to a form service instead. Set &lt;code&gt;VITE_FORM_ENDPOINT&lt;/code&gt; (or a form's own variable) to the service's URL when you build; Formspree and Basin are common choices. On Netlify, set it to &lt;code&gt;netlify&lt;/code&gt; and Netlify Forms receives the submissions. Because the value is read at build time, set it in your host's build environment, not only on your laptop.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a static site can't do
&lt;/h2&gt;

&lt;p&gt;Being static has a few consequences worth knowing before you choose:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CMS items added later&lt;/strong&gt; have no prerendered page until you rebuild. A new item renders in the browser from &lt;code&gt;404.html&lt;/code&gt; with a 404 status, so after editing the JSON, rebuild and redeploy. Adding items in Framer means converting again.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Split tests&lt;/strong&gt; need a server to assign variants, so the static build ships each tested page's original version only.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Anything per request&lt;/strong&gt;, such as sessions or personalized pages, needs a server. Pick &lt;a href="https://deframer.co/framer-to-nextjs" rel="noopener noreferrer"&gt;Next.js&lt;/a&gt;, &lt;a href="https://deframer.co/framer-to-astro" rel="noopener noreferrer"&gt;Astro&lt;/a&gt; or another server target for that.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where to host it
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Host&lt;/th&gt;
&lt;th&gt;What to set&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Netlify&lt;/td&gt;
&lt;td&gt;Build &lt;code&gt;npm run build&lt;/code&gt;, publish &lt;code&gt;dist&lt;/code&gt;; &lt;code&gt;_redirects&lt;/code&gt; works (&lt;a href="https://deframer.co/blog/host-a-framer-site-on-netlify" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cloudflare Pages&lt;/td&gt;
&lt;td&gt;Build &lt;code&gt;npm run build&lt;/code&gt;, output &lt;code&gt;dist&lt;/code&gt; (&lt;a href="https://deframer.co/blog/host-a-framer-site-on-cloudflare-pages" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vercel&lt;/td&gt;
&lt;td&gt;Framework preset Vite, output &lt;code&gt;dist&lt;/code&gt;; &lt;code&gt;vercel.json&lt;/code&gt; is read&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;GitHub Pages&lt;/td&gt;
&lt;td&gt;Deploy &lt;code&gt;dist/&lt;/code&gt; with Actions (&lt;a href="https://deframer.co/blog/host-a-framer-site-on-github-pages" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;S3 and CloudFront&lt;/td&gt;
&lt;td&gt;Upload &lt;code&gt;dist/&lt;/code&gt; (&lt;a href="https://deframer.co/blog/host-a-framer-site-on-aws-s3-and-cloudfront" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Checks before you switch the domain
&lt;/h2&gt;

&lt;p&gt;Run these against &lt;code&gt;npm run preview&lt;/code&gt; locally, then again on the host's preview URL:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Every page loads at its old URL.&lt;/strong&gt; Use the README's route list, including CMS detail pages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The 404 page answers with a 404 status.&lt;/strong&gt; &lt;code&gt;curl -I https://your-preview-url/does-not-exist&lt;/code&gt; should show it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Redirects work.&lt;/strong&gt; For each old URL in &lt;code&gt;public/_redirects&lt;/code&gt;, &lt;code&gt;curl -I&lt;/code&gt; should show a 301 or 308 to the right target on hosts that read the file.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forms reach the form service.&lt;/strong&gt; Submit each form from the deployed preview, not just locally, because the endpoint is baked in at build time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Breakpoints and animations&lt;/strong&gt; look right at about 1440, 768 and 390 pixels.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assets don't point at Framer&lt;/strong&gt; if you chose "Assets in the project". Search &lt;code&gt;dist/&lt;/code&gt; for &lt;code&gt;framerusercontent.com&lt;/code&gt;; with the default option, those references are expected.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;robots.txt&lt;/code&gt; and &lt;code&gt;sitemap.xml&lt;/code&gt;&lt;/strong&gt; name your production domain.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Updating the site
&lt;/h2&gt;

&lt;p&gt;Edit content in &lt;code&gt;src/cms/*.json&lt;/code&gt;, copy in &lt;code&gt;src/views&lt;/code&gt;, or styles in &lt;code&gt;src/styles&lt;/code&gt;, run &lt;code&gt;npm run build&lt;/code&gt;, and deploy &lt;code&gt;dist/&lt;/code&gt; again. Most hosts do this automatically on every push once the repository is connected. If you keep designing in Framer and want the changes, convert again and merge; &lt;a href="https://deframer.co/blog/maintaining-a-converted-framer-site-with-git" rel="noopener noreferrer"&gt;maintaining a converted site with Git&lt;/a&gt; shows how.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can Framer export a static HTML site?
&lt;/h3&gt;

&lt;p&gt;No. Framer hosts sites itself and has no file export. A converter that reads the published site, such as Deframer's Vite target, is the way to get static files you can host anywhere.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do animations still work in the static build?
&lt;/h3&gt;

&lt;p&gt;Yes. Pages hydrate in the browser, and animations and interactions run on &lt;code&gt;motion&lt;/code&gt; through the project's kit.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do I need Node.js on the server?
&lt;/h3&gt;

&lt;p&gt;No. Node.js 22.18 or later is only needed to build. The output in &lt;code&gt;dist/&lt;/code&gt; is plain files.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is the static export good for SEO?
&lt;/h3&gt;

&lt;p&gt;Every page is a full HTML document with its title, description and social image, and &lt;code&gt;robots.txt&lt;/code&gt; and &lt;code&gt;sitemap.xml&lt;/code&gt; come with the project. Use a host that applies &lt;code&gt;_redirects&lt;/code&gt; or &lt;code&gt;vercel.json&lt;/code&gt; so old URLs return real redirects.&lt;/p&gt;

&lt;h3&gt;
  
  
  How much does it cost?
&lt;/h3&gt;

&lt;p&gt;Converting is free. A verified download uses 1 credit; packs start at $10, and the $397 lifetime deal makes verified downloads free. See &lt;a href="https://deframer.co/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://deframer.co/blog/framer-static-site-export-with-vite" rel="noopener noreferrer"&gt;Deframer blog&lt;/a&gt;. Deframer converts a published Framer site into Next.js, Astro, React Router, TanStack Start, Vite, Nuxt or static HTML code.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>framer</category>
      <category>vite</category>
      <category>react</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How to convert a Framer site to React Router framework mode</title>
      <dc:creator>Mehdi Hassan</dc:creator>
      <pubDate>Mon, 16 Nov 2026 01:18:20 +0000</pubDate>
      <link>https://dev.to/designify101/how-to-convert-a-framer-site-to-react-router-framework-mode-4fnf</link>
      <guid>https://dev.to/designify101/how-to-convert-a-framer-site-to-react-router-framework-mode-4fnf</guid>
      <description>&lt;p&gt;To convert a Framer site to React Router, paste the published site's address into Deframer, pick React Router in the framework menu and convert for free. The result is a React Router 8 project in framework mode, written in TypeScript: one route module per page with its &lt;code&gt;meta&lt;/code&gt;, every page prerendered at its published URL, CMS collections as JSON and native forms as routes. A small &lt;code&gt;server.ts&lt;/code&gt; serves it on Node.js 22.22 or later.&lt;/p&gt;

&lt;p&gt;Deframer is an independent tool and is not affiliated with, endorsed or sponsored by Framer. You download the code of sites you own, or sites whose owner has given you permission.&lt;/p&gt;

&lt;h2&gt;
  
  
  Framework mode, not a single-page app
&lt;/h2&gt;

&lt;p&gt;React Router can be used in three ways: as a plain library inside your own app, as a data router, or as a full framework with route modules, server rendering and a build. The converted project uses &lt;strong&gt;framework mode&lt;/strong&gt;. That matters for a website:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every page is rendered on the server and prerendered at build time, so search engines and visitors get full HTML.&lt;/li&gt;
&lt;li&gt;Each route module exports its own &lt;code&gt;meta&lt;/code&gt;, so titles and descriptions belong to the page.&lt;/li&gt;
&lt;li&gt;The root route keeps each page in its layout template, so the navigation stays mounted between pages that share it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you know Remix, the shape will look familiar: framework mode is where Remix's features continue. &lt;a href="https://deframer.co/blog/framer-to-remix" rel="noopener noreferrer"&gt;Framer to Remix in 2026&lt;/a&gt; explains that history.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step by step
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Paste the published URL&lt;/strong&gt; (&lt;code&gt;*.framer.website&lt;/code&gt;, &lt;code&gt;*.framer.app&lt;/code&gt; or your custom domain).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Choose React Router&lt;/strong&gt; in the framework menu; Next.js is the default.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick where assets live&lt;/strong&gt;: on Framer's CDN (default) or in the project's &lt;code&gt;public/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Convert.&lt;/strong&gt; It's free and takes up to 10 minutes. Live progress shows each stage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review the notices&lt;/strong&gt; and, when live previews are on, the side-by-side compare view.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Verify and download.&lt;/strong&gt; Publish the one-line verification tag in Framer's Custom Code, click &lt;strong&gt;Check again&lt;/strong&gt;, and download for 1 credit (or nothing with the lifetime deal). Details: &lt;a href="https://deframer.co/blog/verifying-framer-site-ownership" rel="noopener noreferrer"&gt;verifying Framer site ownership&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run it:&lt;/strong&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install
npm run dev        &lt;span class="c"&gt;# react-router dev&lt;/span&gt;
npm run build      &lt;span class="c"&gt;# react-router build, then scripts/prerender.ts&lt;/span&gt;
npm start          &lt;span class="c"&gt;# server.ts on Node.js 22.22 or later&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What's inside the project?
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;src/
  routes/           Route modules: one index.tsx per URL, and the form routes
  routes.ts         Each URL pattern and the module that serves it
  root.tsx          The document, each page in its layout template
  entry.server.tsx  Server rendering
  views/            Pages, each with its .module.css
  layouts/          Layout templates: navigation and footer
  components/       Components, in the design project's folders
  cms/              CMS collections: &amp;lt;collection&amp;gt;.ts + &amp;lt;collection&amp;gt;.json
  lib/deframer/     The small kit that replaces Framer's runtime
scripts/
  prerender.ts      Prerenders every page at its published URL
react-router.config.ts
server.ts           Redirects, static files, then React Router
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  &lt;code&gt;src/routes.ts&lt;/code&gt;
&lt;/h3&gt;

&lt;p&gt;The route config lists every URL pattern and the module that serves it. Adding a page means adding a view, a route module and a line here.&lt;/p&gt;

&lt;h3&gt;
  
  
  Route modules
&lt;/h3&gt;

&lt;p&gt;Each &lt;code&gt;src/routes/**/index.tsx&lt;/code&gt; exports the page's &lt;code&gt;meta&lt;/code&gt;: title, description and social tags. CMS detail pages read theirs from a &lt;code&gt;head.json&lt;/code&gt; table, one entry per item, and the site's own head tags live in &lt;code&gt;src/site/head.ts&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;code&gt;src/root.tsx&lt;/code&gt;
&lt;/h3&gt;

&lt;p&gt;The document. It holds the site's tags, the custom code from Framer's site settings, the kit's styles and router, and the 404 page for unknown URLs and unlisted CMS items. It wraps each page in its layout template, taken from the route's &lt;code&gt;handle&lt;/code&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;code&gt;scripts/prerender.ts&lt;/code&gt; and &lt;code&gt;server.ts&lt;/code&gt;
&lt;/h3&gt;

&lt;p&gt;After &lt;code&gt;react-router build&lt;/code&gt;, the prerender script renders every page once, at the URL the site published it at. &lt;code&gt;server.ts&lt;/code&gt; then applies the site's redirects and URL forms, serves static and prerendered files, and hands everything else (such as form submissions) to React Router's handler.&lt;/p&gt;

&lt;h3&gt;
  
  
  Everything else
&lt;/h3&gt;

&lt;p&gt;Views, layouts, components with CSS modules, tokens, text styles, fonts, CMS JSON and the kit are the same code as in every other target. Animations and interactions run on &lt;code&gt;motion&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Forms
&lt;/h2&gt;

&lt;p&gt;Each native form gets a route in &lt;code&gt;src/routes/api/forms/&amp;lt;form&amp;gt;.ts&lt;/code&gt; that checks fields, applies a rate limit and a honeypot, and delivers to a webhook. Copy &lt;code&gt;.env.example&lt;/code&gt; to &lt;code&gt;.env&lt;/code&gt; and set &lt;code&gt;FORMS_WEBHOOK_URL&lt;/code&gt;, or a per-form variable, before you test. &lt;a href="https://deframer.co/blog/forms-after-leaving-framer" rel="noopener noreferrer"&gt;Migrating Framer forms&lt;/a&gt; covers webhooks and a parallel run.&lt;/p&gt;

&lt;h2&gt;
  
  
  Adding a new page
&lt;/h2&gt;

&lt;p&gt;Because routes are listed explicitly, adding a page takes three small steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create the view, for example &lt;code&gt;src/views/careers.tsx&lt;/code&gt; with &lt;code&gt;careers.module.css&lt;/code&gt;, reusing components from &lt;code&gt;src/components&lt;/code&gt; and the layout template your other pages use.&lt;/li&gt;
&lt;li&gt;Add a route module, &lt;code&gt;src/routes/careers/index.tsx&lt;/code&gt;, that renders the view and exports its &lt;code&gt;meta&lt;/code&gt; (title and description).&lt;/li&gt;
&lt;li&gt;Add the route to &lt;code&gt;src/routes.ts&lt;/code&gt;, then add the URL to the prerender list if you want it prerendered like the others, and to &lt;code&gt;public/sitemap.xml&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Copying an existing route module and its entry in &lt;code&gt;src/routes.ts&lt;/code&gt; is the quickest way to get the shape right.&lt;/p&gt;

&lt;h2&gt;
  
  
  Type-checking
&lt;/h2&gt;

&lt;p&gt;React Router generates route types with &lt;code&gt;react-router typegen&lt;/code&gt;, and the project's &lt;code&gt;npm run typecheck&lt;/code&gt; checks it with TypeScript. Like the other targets, the project's &lt;code&gt;tsconfig.json&lt;/code&gt; is not in &lt;code&gt;strict&lt;/code&gt; mode, because the site's code components were never type-checked in Framer. Errors are still reported, so you can fix them file by file. See &lt;a href="https://deframer.co/blog/framer-to-typescript" rel="noopener noreferrer"&gt;Framer to TypeScript&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Deploying
&lt;/h2&gt;

&lt;p&gt;The project needs Node.js 22.22 or later, which React Router 8 requires. Any Node.js host, a container or your own server works:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;What to do&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Render or Railway&lt;/td&gt;
&lt;td&gt;Build with &lt;code&gt;npm run build&lt;/code&gt;, start with &lt;code&gt;npm start&lt;/code&gt; (&lt;a href="https://deframer.co/blog/host-a-framer-site-on-render-or-railway" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Docker&lt;/td&gt;
&lt;td&gt;Base image with Node.js 22.22+, copy the build, run &lt;code&gt;npm start&lt;/code&gt; (&lt;a href="https://deframer.co/blog/self-host-a-framer-site-with-docker" rel="noopener noreferrer"&gt;guide&lt;/a&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Your own server&lt;/td&gt;
&lt;td&gt;Process manager plus Caddy or nginx in front&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Because every page is prerendered, most requests are file reads. The server still matters for redirects and forms, so a pure static host is not enough. If you want no server at all, &lt;a href="https://deframer.co/framer-to-vite" rel="noopener noreferrer"&gt;Vite&lt;/a&gt; is the static option.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checks before launch
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Every route in the README renders, including CMS items and the 404 page.&lt;/li&gt;
&lt;li&gt;The three breakpoints look right.&lt;/li&gt;
&lt;li&gt;Moving between pages keeps the shared navigation's state.&lt;/li&gt;
&lt;li&gt;Forms reach your webhook.&lt;/li&gt;
&lt;li&gt;Old URLs redirect as they did on Framer (check with &lt;code&gt;curl -I&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Canonical URLs, &lt;code&gt;robots.txt&lt;/code&gt; and &lt;code&gt;sitemap.xml&lt;/code&gt; use your production domain.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can I convert a Framer site to React Router?
&lt;/h3&gt;

&lt;p&gt;Yes. Deframer converts a published Framer site into a React Router 8 project in framework mode, in TypeScript, which you download as a &lt;code&gt;.zip&lt;/code&gt; and own.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is it a single-page app?
&lt;/h3&gt;

&lt;p&gt;No. It uses framework mode with server rendering, and every page is prerendered at build time. After the first page loads, links navigate in the browser like any React Router app.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which Node.js version do I need?
&lt;/h3&gt;

&lt;p&gt;Node.js 22.22 or later, which React Router 8 requires.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I add loaders and actions?
&lt;/h3&gt;

&lt;p&gt;Yes. The route modules are ordinary React Router route modules, so you can add &lt;code&gt;loader&lt;/code&gt; and &lt;code&gt;action&lt;/code&gt; exports as you would in any framework-mode project. Prerendered pages are rendered at build time, so data that changes per request needs a route that isn't prerendered.&lt;/p&gt;

&lt;h3&gt;
  
  
  How much does it cost?
&lt;/h3&gt;

&lt;p&gt;Converting is free. A verified download uses 1 credit, a download without verification 10, and the lifetime deal makes verified downloads free. See &lt;a href="https://deframer.co/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://deframer.co/blog/convert-a-framer-site-to-react-router" rel="noopener noreferrer"&gt;Deframer blog&lt;/a&gt;. Deframer converts a published Framer site into Next.js, Astro, React Router, TanStack Start, Vite, Nuxt or static HTML code.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>framer</category>
      <category>react</category>
      <category>javascript</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How to convert a Framer site to Astro</title>
      <dc:creator>Mehdi Hassan</dc:creator>
      <pubDate>Mon, 16 Nov 2026 01:13:01 +0000</pubDate>
      <link>https://dev.to/designify101/how-to-convert-a-framer-site-to-astro-2f9i</link>
      <guid>https://dev.to/designify101/how-to-convert-a-framer-site-to-astro-2f9i</guid>
      <description>&lt;p&gt;To convert a Framer site to Astro, you either rebuild it by hand in an empty Astro project or use a converter that reads the published site and writes the project for you. Deframer does the second: paste the site's address, pick Astro in the framework menu and convert for free. You get an Astro 7 project in TypeScript where every page is prerendered to static HTML and hydrates as one React island, with the site's animations, CMS content and forms carried over. Downloading the code needs proof that the site is yours.&lt;/p&gt;

&lt;p&gt;Deframer is an independent tool and is not affiliated with, endorsed or sponsored by Framer. It converts sites you own, or sites whose owner has given you permission.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Astro for a Framer site?
&lt;/h2&gt;

&lt;p&gt;Astro is a good fit when the site is mostly content: a marketing site, a portfolio, a blog. Its build writes every page to HTML ahead of time, so a visitor gets a finished document before any JavaScript runs, and the hosting side stays simple. Teams that already use Astro for docs or content sites also get one less framework to learn.&lt;/p&gt;

&lt;p&gt;The trade-off is that a Framer page is not a set of small, independent widgets. Its layout, scroll effects, hover states and page transitions depend on one another. That is why the converted project keeps each page as a single React island instead of splitting it into many: the page renders as it was published, and the island stays mounted between pages, so a shared navigation keeps its state.&lt;/p&gt;

&lt;p&gt;If your plan is to add app features such as accounts or a dashboard, read &lt;a href="https://deframer.co/blog/nextjs-vs-astro-for-a-framer-site" rel="noopener noreferrer"&gt;Next.js vs Astro for a converted Framer site&lt;/a&gt; before you pick.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need before you start
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The site's published address: a &lt;code&gt;*.framer.website&lt;/code&gt; or &lt;code&gt;*.framer.app&lt;/code&gt; address, or your custom domain. Not the editor link.&lt;/li&gt;
&lt;li&gt;A free Deframer account.&lt;/li&gt;
&lt;li&gt;The ability to publish the Framer site, or the owner's cooperation, so the verification tag can go live when you download.&lt;/li&gt;
&lt;li&gt;Node.js 22.18 or later on your machine, which the Astro project's server and scripts need.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step by step
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Paste the URL and pick Astro
&lt;/h3&gt;

&lt;p&gt;Sign in, paste the published address into the convert form and open the framework menu. Next.js is selected by default; choose &lt;strong&gt;Astro&lt;/strong&gt;. Then choose where assets live: &lt;strong&gt;Assets on Framer's CDN&lt;/strong&gt; (the default, smaller download) keeps images, fonts and videos loading from Framer's CDN, while &lt;strong&gt;Assets in the project&lt;/strong&gt; downloads them into &lt;code&gt;public/&lt;/code&gt; so nothing depends on Framer.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Convert
&lt;/h3&gt;

&lt;p&gt;Click Convert. Progress shows live: queued, fetching, modules, converting, packaging, done. A conversion can run for up to 10 minutes, and converting costs nothing, including a conversion that fails.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Review the result
&lt;/h3&gt;

&lt;p&gt;Read the notices on the result page. They point at files that couldn't be downloaded, components that render only in the browser, or redirects that weren't carried over. When live previews are on, the compare view shows the original and the conversion side by side at 1440, 768 and 390 pixels; previews may be paused, and you can always run the project locally instead.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Verify and download
&lt;/h3&gt;

&lt;p&gt;Downloading asks you to show the site is yours. Deframer gives you a one-line meta tag; paste it at the end of the &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt; in Framer's Site Settings, Custom Code, publish, and click &lt;strong&gt;Check again&lt;/strong&gt;. A verified download uses 1 credit, or nothing with the lifetime deal. The full walkthrough is in &lt;a href="https://deframer.co/blog/verifying-framer-site-ownership" rel="noopener noreferrer"&gt;verifying Framer site ownership&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Run it
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm install
npm run dev
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;npm run dev&lt;/code&gt; runs &lt;code&gt;astro dev&lt;/code&gt;. Edit a view in &lt;code&gt;src/views&lt;/code&gt; and the page updates.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Build and start
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm run build
npm start
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;astro build&lt;/code&gt; prerenders every page, CMS items included, and &lt;code&gt;npm start&lt;/code&gt; runs the project's &lt;code&gt;server.ts&lt;/code&gt; on Node.js 22.18 or later.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in the Astro project?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Path&lt;/th&gt;
&lt;th&gt;What it holds&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/pages/**/index.astro&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;One per URL, with its title, description, Open Graph and canonical URL in its head&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/pages/**/_route.tsx&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The page's React island, beside its &lt;code&gt;index.astro&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/site/document.astro&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The document every page renders into&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/site/root.tsx&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;What wraps each page: the kit's styles and router&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;src/views&lt;/code&gt;, &lt;code&gt;src/layouts&lt;/code&gt;, &lt;code&gt;src/components&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Pages, navigation and footer templates, design components, each with a CSS module&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/styles&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Color styles as CSS variables, text styles, &lt;code&gt;@font-face&lt;/code&gt; rules&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/cms&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Each CMS collection as a schema (&lt;code&gt;.ts&lt;/code&gt;) and records (&lt;code&gt;.json&lt;/code&gt;)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/pages/api/forms/&amp;lt;form&amp;gt;.ts&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;One API route per native form&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;src/lib/deframer&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;The small kit that replaces Framer's runtime&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;server.ts&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Redirects and URL forms (308), the prerendered pages, the form routes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;astro.config.ts&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;React, the Node adapter and the build&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;CMS detail pages take their titles and descriptions from a &lt;code&gt;_head.json&lt;/code&gt; table, and the site's own head tags sit in &lt;code&gt;src/site/head.ts&lt;/code&gt;. The pages, components and styles are the same React and TypeScript code the Next.js export uses; only the routes, the document and the server are Astro's.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do animations and page transitions work?
&lt;/h2&gt;

&lt;p&gt;Animations and interactions run on &lt;code&gt;motion&lt;/code&gt;, the open-source animation library, through the project's kit. When you click a link, Astro's router loads the next page and keeps the island, so the layout template two pages share stays mounted. An open menu stays open, and a navigation bar collapsed on scroll stays collapsed. Page transitions play as the browser's view transitions.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about forms?
&lt;/h2&gt;

&lt;p&gt;Native Framer forms post to the project's own API routes in &lt;code&gt;src/pages/api/forms/&lt;/code&gt;, with a rate limit, a honeypot and field checks. Copy &lt;code&gt;.env.example&lt;/code&gt; to &lt;code&gt;.env&lt;/code&gt; and set the webhook variables so submissions reach you; without one, they are only logged. More on mapping and testing in &lt;a href="https://deframer.co/blog/forms-after-leaving-framer" rel="noopener noreferrer"&gt;migrating Framer forms&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where can an Astro export be hosted?
&lt;/h2&gt;

&lt;p&gt;The pages are static HTML, but the project also runs &lt;code&gt;server.ts&lt;/code&gt; on Node.js for redirects and forms. That means any Node.js host, a container or your own server: see &lt;a href="https://deframer.co/blog/self-host-a-framer-site-with-docker" rel="noopener noreferrer"&gt;self-hosting a Framer site with Docker&lt;/a&gt; or &lt;a href="https://deframer.co/blog/host-a-framer-site-on-render-or-railway" rel="noopener noreferrer"&gt;Render and Railway&lt;/a&gt;. If you want a site with no server at all, convert to &lt;a href="https://deframer.co/framer-to-vite" rel="noopener noreferrer"&gt;Vite&lt;/a&gt; instead; the &lt;a href="https://deframer.co/blog/framer-static-site-export-with-vite" rel="noopener noreferrer"&gt;static export guide&lt;/a&gt; explains the differences.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to check before launch
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open every route listed in the README, including CMS items and the 404 page.&lt;/li&gt;
&lt;li&gt;Check three widths, roughly 1440, 768 and 390 pixels.&lt;/li&gt;
&lt;li&gt;Click between pages that share a navigation and confirm it keeps its state.&lt;/li&gt;
&lt;li&gt;Submit each form with the webhook set.&lt;/li&gt;
&lt;li&gt;Run &lt;code&gt;npm run typecheck&lt;/code&gt;, which runs &lt;code&gt;astro sync&lt;/code&gt; and checks the project with TypeScript.&lt;/li&gt;
&lt;li&gt;Confirm &lt;code&gt;robots.txt&lt;/code&gt;, &lt;code&gt;sitemap.xml&lt;/code&gt; and canonical URLs use your production domain.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Limits to know
&lt;/h2&gt;

&lt;p&gt;The result is close to the original but not guaranteed to be identical, so check every page. Code components and third-party embeds come across as the site's own source, not rewritten. Very large sites may not fit in a conversion; keeping assets on Framer's CDN makes the project much smaller.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Can I convert a Framer site to Astro for free?
&lt;/h3&gt;

&lt;p&gt;Converting is free, and so is reviewing the result. Downloading the code uses 1 credit with site verification, 10 without, or nothing with the lifetime deal for verified sites. See &lt;a href="https://deframer.co/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why is each page one React island and not many?
&lt;/h3&gt;

&lt;p&gt;A Framer page is one tree whose layout, effects and interactions depend on each other. One island renders it as published and keeps the shared layout mounted between pages.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is the Astro project fully static?
&lt;/h3&gt;

&lt;p&gt;Its pages are: &lt;code&gt;astro build&lt;/code&gt; prerenders every one. The project also runs a small &lt;code&gt;server.ts&lt;/code&gt; on Node.js 22.18 or later for redirects and form routes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I switch to Next.js later?
&lt;/h3&gt;

&lt;p&gt;Yes. Converting again for another framework is free, and the pages, components and styles are the same React code in every target.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does the Astro project depend on Framer?
&lt;/h3&gt;

&lt;p&gt;The code doesn't: there is no Framer runtime. With the default asset option, images, fonts and videos still load from Framer's CDN; choose "Assets in the project" to bring them in.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://deframer.co/blog/how-to-convert-a-framer-site-to-astro" rel="noopener noreferrer"&gt;Deframer blog&lt;/a&gt;. Deframer converts a published Framer site into Next.js, Astro, React Router, TanStack Start, Vite, Nuxt or static HTML code.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>framer</category>
      <category>astro</category>
      <category>react</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Next.js, Astro, TanStack Start, React Router or Vite: which should your Framer site use?</title>
      <dc:creator>Mehdi Hassan</dc:creator>
      <pubDate>Mon, 16 Nov 2026 00:43:28 +0000</pubDate>
      <link>https://dev.to/designify101/nextjs-astro-tanstack-start-react-router-or-vite-which-should-your-framer-site-use-4fig</link>
      <guid>https://dev.to/designify101/nextjs-astro-tanstack-start-react-router-or-vite-which-should-your-framer-site-use-4fig</guid>
      <description>&lt;p&gt;For most Framer sites, Next.js is the safest choice: it is the default, it has the widest hosting support and it suits sites that will grow into apps. Pick Vite if you want a static site with no server, Astro if your team works in Astro or wants prerendered content pages, React Router if you want the Remix-style route modules, and TanStack Start if your team uses the TanStack ecosystem. The pages, components, styles, CMS content and forms are the same React and TypeScript code in all five, so the choice is mostly about routing, hosting and what your team knows.&lt;/p&gt;

&lt;p&gt;Deframer, the converter this guide refers to, is an independent tool and is not affiliated with, endorsed or sponsored by Framer. It downloads code for sites you own or have permission to convert.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is the same in all five?
&lt;/h2&gt;

&lt;p&gt;Before comparing, it helps to know what does not change. Every export includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pages in &lt;code&gt;src/views&lt;/code&gt;, layout templates in &lt;code&gt;src/layouts&lt;/code&gt;, design components in &lt;code&gt;src/components&lt;/code&gt;, each with a CSS module, keeping the designer's folders, variants and hover states.&lt;/li&gt;
&lt;li&gt;Color styles as CSS variables, shared text styles as classes and &lt;code&gt;@font-face&lt;/code&gt; rules in &lt;code&gt;src/styles&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Each CMS collection as a schema (&lt;code&gt;src/cms/&amp;lt;collection&amp;gt;.ts&lt;/code&gt;) and JSON records.&lt;/li&gt;
&lt;li&gt;Animations on &lt;code&gt;motion&lt;/code&gt;, with a small kit in &lt;code&gt;src/lib/deframer&lt;/code&gt; instead of Framer's runtime.&lt;/li&gt;
&lt;li&gt;Titles, descriptions and social images per page, plus redirects, &lt;code&gt;robots.txt&lt;/code&gt; and &lt;code&gt;sitemap.xml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;A README listing every route.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only the routes, the document, the server (Vite has none) and the build are each framework's own.&lt;/p&gt;

&lt;h2&gt;
  
  
  The comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Next.js&lt;/th&gt;
&lt;th&gt;Astro&lt;/th&gt;
&lt;th&gt;TanStack Start&lt;/th&gt;
&lt;th&gt;React Router&lt;/th&gt;
&lt;th&gt;Vite&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Version&lt;/td&gt;
&lt;td&gt;Next.js 16, App Router&lt;/td&gt;
&lt;td&gt;Astro 7&lt;/td&gt;
&lt;td&gt;TanStack Start&lt;/td&gt;
&lt;td&gt;React Router 8, framework mode&lt;/td&gt;
&lt;td&gt;Vite with React Router 8&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Routes live in&lt;/td&gt;
&lt;td&gt;&lt;code&gt;src/app&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;src/pages&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;src/routes&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;src/routes&lt;/code&gt;, &lt;code&gt;src/routes.ts&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;src/routes&lt;/code&gt;, &lt;code&gt;src/routes.tsx&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Page metadata&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;metadata&lt;/code&gt; in &lt;code&gt;page.tsx&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;head of &lt;code&gt;index.astro&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;&lt;code&gt;head()&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;meta&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;&amp;lt;PageHead&amp;gt;&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pages prerendered&lt;/td&gt;
&lt;td&gt;CMS detail pages via &lt;code&gt;generateStaticParams&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Every page&lt;/td&gt;
&lt;td&gt;Rendered on the server&lt;/td&gt;
&lt;td&gt;Every page&lt;/td&gt;
&lt;td&gt;Every page, into &lt;code&gt;dist/&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Needs a server&lt;/td&gt;
&lt;td&gt;Yes (Next.js)&lt;/td&gt;
&lt;td&gt;Yes, &lt;code&gt;server.ts&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Yes, srvx&lt;/td&gt;
&lt;td&gt;Yes, &lt;code&gt;server.ts&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Node.js&lt;/td&gt;
&lt;td&gt;20.9+&lt;/td&gt;
&lt;td&gt;22.18+&lt;/td&gt;
&lt;td&gt;22.18+&lt;/td&gt;
&lt;td&gt;22.22+&lt;/td&gt;
&lt;td&gt;22.18+ to build only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Forms&lt;/td&gt;
&lt;td&gt;API route handlers&lt;/td&gt;
&lt;td&gt;API routes&lt;/td&gt;
&lt;td&gt;API routes&lt;/td&gt;
&lt;td&gt;Form routes&lt;/td&gt;
&lt;td&gt;A form service, or Netlify Forms&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Split tests&lt;/td&gt;
&lt;td&gt;Kept, served by the proxy&lt;/td&gt;
&lt;td&gt;Kept&lt;/td&gt;
&lt;td&gt;Kept&lt;/td&gt;
&lt;td&gt;Kept&lt;/td&gt;
&lt;td&gt;Original version only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Typical hosts&lt;/td&gt;
&lt;td&gt;Vercel, Netlify, Node, containers&lt;/td&gt;
&lt;td&gt;Node hosts, containers&lt;/td&gt;
&lt;td&gt;Node hosts, containers&lt;/td&gt;
&lt;td&gt;Node hosts, containers&lt;/td&gt;
&lt;td&gt;Any static host&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  A quick decision path
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Do you want no server at all?&lt;/strong&gt; Pick &lt;a href="https://deframer.co/framer-to-vite" rel="noopener noreferrer"&gt;Vite&lt;/a&gt;. It suits brochure sites, portfolios and landing pages whose content changes when you rebuild. Forms go to a form service.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Will the site grow into an app&lt;/strong&gt; with accounts, a dashboard or payments? Pick &lt;a href="https://deframer.co/framer-to-nextjs" rel="noopener noreferrer"&gt;Next.js&lt;/a&gt;, unless your team already standardizes on another React framework.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Does your team already use one framework?&lt;/strong&gt; Pick that one. A team fluent in Astro, TanStack or Remix will maintain the site faster in its own tool than in a "better" one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Is it a content site where every page can be prerendered?&lt;/strong&gt; &lt;a href="https://deframer.co/framer-to-astro" rel="noopener noreferrer"&gt;Astro&lt;/a&gt; or &lt;a href="https://deframer.co/framer-to-react-router" rel="noopener noreferrer"&gt;React Router&lt;/a&gt; both prerender every page and keep the layout mounted between pages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Still unsure?&lt;/strong&gt; Keep the default, Next.js.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Next.js
&lt;/h2&gt;

&lt;p&gt;The default target and the one with the broadest hosting support. Vercel, Netlify and many others run Next.js directly, and Cloudflare runs it through the OpenNext adapter. You get App Router routes, per-page &lt;code&gt;metadata&lt;/code&gt;, a &lt;code&gt;src/proxy.ts&lt;/code&gt; for redirects and URL forms, and route handlers for forms. Choose it if you expect to add server features later. Guide: &lt;a href="https://deframer.co/blog/how-to-export-a-framer-site-to-nextjs" rel="noopener noreferrer"&gt;how to export a Framer site to Next.js&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Astro
&lt;/h2&gt;

&lt;p&gt;Every page is prerendered to HTML by &lt;code&gt;astro build&lt;/code&gt; and hydrates as one React island, which stays mounted from page to page, so shared navigation keeps its state. A small &lt;code&gt;server.ts&lt;/code&gt; handles redirects and forms. Choose it if your team likes Astro's tooling or wants to add Markdown content pages beside the converted ones. Guide: &lt;a href="https://deframer.co/blog/how-to-convert-a-framer-site-to-astro" rel="noopener noreferrer"&gt;how to convert a Framer site to Astro&lt;/a&gt;, and the head-to-head &lt;a href="https://deframer.co/blog/nextjs-vs-astro-for-a-framer-site" rel="noopener noreferrer"&gt;Next.js vs Astro&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  TanStack Start
&lt;/h2&gt;

&lt;p&gt;File routes with &lt;code&gt;head()&lt;/code&gt;, typed routing from a generated route tree, built with Rsbuild and served by srvx on Node.js 22.18 or later. Choose it if your app already uses TanStack Router or Query. Guide: &lt;a href="https://deframer.co/blog/export-a-framer-site-to-tanstack-start" rel="noopener noreferrer"&gt;how to export a Framer site to TanStack Start&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  React Router
&lt;/h2&gt;

&lt;p&gt;Framework mode: route modules with &lt;code&gt;meta&lt;/code&gt;, a route config, server rendering and every page prerendered at build time. It is where Remix's React framework features continue. Choose it if your developers think in loaders and actions. Guides: &lt;a href="https://deframer.co/blog/convert-a-framer-site-to-react-router" rel="noopener noreferrer"&gt;converting to React Router&lt;/a&gt; and &lt;a href="https://deframer.co/blog/framer-to-remix" rel="noopener noreferrer"&gt;Framer to Remix in 2026&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vite
&lt;/h2&gt;

&lt;p&gt;A static site. The build prerenders every page into &lt;code&gt;dist/&lt;/code&gt;, and redirects come as &lt;code&gt;_redirects&lt;/code&gt; and &lt;code&gt;vercel.json&lt;/code&gt;, or as redirect pages on hosts that read neither. The trade-offs: forms need a form service, split tests ship the original only, and CMS items added later have no page until you rebuild. Guide: &lt;a href="https://deframer.co/blog/framer-static-site-export-with-vite" rel="noopener noreferrer"&gt;export a Framer site as a static site with Vite&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Does the choice affect SEO?
&lt;/h2&gt;

&lt;p&gt;Not much, if you check the basics. All five ship each page's title, description, social image and canonical URL, the site's sitemap and robots file, and its redirects. Server targets answer redirects with real HTTP status codes; on Vite, use a host that reads &lt;code&gt;_redirects&lt;/code&gt; or &lt;code&gt;vercel.json&lt;/code&gt; for the same effect. &lt;a href="https://deframer.co/blog/seo-when-moving-off-framer" rel="noopener noreferrer"&gt;Keeping SEO when moving off Framer&lt;/a&gt; has the full list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can you change your mind later?
&lt;/h2&gt;

&lt;p&gt;Yes. Converting is free, so you can convert the same site to two frameworks and compare the code before you download. Each download is its own project and uses a credit (1 with verification), or nothing with the lifetime deal for verified sites. Because views, components and CMS files are identical across targets, moving custom edits from one export to another is mostly copying &lt;code&gt;src/views&lt;/code&gt; and &lt;code&gt;src/components&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Which framework is best for a Framer site?
&lt;/h3&gt;

&lt;p&gt;Next.js for most sites, because it is the default, widely hosted and ready for app features. Vite if you want static files and no server.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which option is cheapest to host?
&lt;/h3&gt;

&lt;p&gt;Vite, because static files can be hosted on free or low-cost static plans. The others need a Node.js process or a platform that runs one.&lt;/p&gt;

&lt;h3&gt;
  
  
  Do all five keep Framer animations?
&lt;/h3&gt;

&lt;p&gt;Yes. Animations and interactions run on &lt;code&gt;motion&lt;/code&gt; through the project's kit in every target.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I use Tailwind or my own components in any of them?
&lt;/h3&gt;

&lt;p&gt;Yes. They are ordinary React projects. See &lt;a href="https://deframer.co/blog/add-tailwind-to-a-converted-framer-site" rel="noopener noreferrer"&gt;adding Tailwind to a converted Framer site&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is the code different between frameworks?
&lt;/h3&gt;

&lt;p&gt;Only routes, the document, the server and the build. Views, components, styles, CMS data and forms are the same.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://deframer.co/blog/which-framework-for-your-framer-export" rel="noopener noreferrer"&gt;Deframer blog&lt;/a&gt;. Deframer converts a published Framer site into Next.js, Astro, React Router, TanStack Start, Vite, Nuxt or static HTML code.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>framer</category>
      <category>nextjs</category>
      <category>astro</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
