Capture your public page markup and available design assets as an HTML, Astro or Vite project. Start your move with the design you already built and a report of Framer runtime dependencies to review.
Free sample · up to 5 linked public pages · HTML, Astro or Vite
Your Framer site moves into source files you own.
Framer does not offer a native HTML bundle for self-hosting. Capture the published front end as a rebuild reference, then review animations, forms and hosted content before changing your domain.
Framer documentation on HTML export and hostingServer-provided HTML, text, navigation and layout markup from the pages visitors can reach.
Discoverable CSS, images, fonts and scripts, including nested stylesheet resources, with local paths when copied.
Editable files and run commands, local links between captured pages, plus reports of skipped resources and detected dependencies.
Public page output does not recover the original Framer component tree, editor settings or override source.
JavaScript was not executed during capture. Review hydration, scroll effects and dynamically loaded modules in the running project.
Move structured content and replace submission handlers or other hosted behavior separately. Copied scripts can still contact Framer.
Both start with an inspection and end with code you own. The difference is who writes it.
Build on your exported code with Claude Code or Codex. We review it, fix what breaks, move the data and users, and ship it. You keep the speed of AI; we take the risk out of launch.
We plan the move, rebuild the app, move data and users, and launch. You review each milestone and own the repository from the first commit.
Movers walk through the house before they quote. So do we. Then we do the heavy lifting, and the move takes weeks, not months.
1 Inspection. We list every page, data type, workflow and integration, flag what needs care, and send a plan and a quote. It costs $500.
2 Plan. We agree the stack, the hosting, the working model and the milestones. Nothing starts until the scope is signed.
3 Move. The app is rebuilt in code, by you with Claude and reviewed by us, or by our team. Data and users come across in rehearsed runs.
4 Launch. Redirects, DNS and a cutover window your users will not notice, with a rollback ready until it is stable.
5 Aftercare. Fixes, small features and handover notes, so your team or the next developer can carry on without us.
Can't find what you need? You'll get an answer from an engineer within a day.
Talk to usNo. The export contains public HTML and available assets in a runnable project. It does not recreate the original component tree, canvas settings or override code.
Some behavior may survive through copied scripts, but runtime imports and browser-loaded content are not rebuilt automatically. Compare the exported project with the live site and replace dependencies as needed.
Public content present in captured HTML comes across as page output. A complete structured CMS export, relationships and editing workflow require separate migration.