
I reverse-engineered Framer's React runtime to export sites as static HTML
I had a Framer site (nocodetalks.co) running for 2 years. $10/month for hosting a static website. No dynamic content, no CMS, no forms. Just HTML on Framer's servers. When I looked into moving it to Vercel (free tier, same performance), I hit a wall: Framer has no code export. Their help center says it flat out. You can build on Framer, but you can't take your files and leave. I talked to a few friends who were in the same spot. Same frustration. They all wanted to move to Vercel or Cloudflare Pages but had no way to get their code out. So I built a tool to do it. What started as a script for my own site turned into a product. Here's what I learned about how Framer works under the hood, and why "just saving the HTML" doesn't work. Why View Source doesn't work Framer sites look like normal HTML when you right-click and View Source. But they're React apps. The server sends pre-rendered HTML, then the client loads a JavaScript bundle that calls hydrateRoot() to take over the DOM. If you s
Continue reading on Dev.to Webdev
Opens in a new tab


