Take your published Framer pages
into a codebase you own.
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.
Packing your site…
·
Your Framer front end
Published page markup
Server-provided HTML, text, navigation and layout markup from the pages visitors can reach.
Available design assets
Discoverable CSS, images, fonts and scripts, including nested stylesheet resources, with local paths when copied.
A source project and route map
Editable files and run commands, local links between captured pages, plus reports of skipped resources and detected dependencies.
Replacements to build
Canvas components and overrides
Public page output does not recover the original Framer component tree, editor settings or override source.
Animations and runtime behavior
JavaScript was not executed during capture. Review hydration, scroll effects and dynamically loaded modules in the running project.
Forms, CMS and hosted services
Move structured content and replace submission handlers or other hosted behavior separately. Copied scripts can still contact Framer.
Your Framer move,
one step at a time.
- Pick a published design to preserve.
Start with a landing page that includes your typography, navigation and important sections. Export a small linked-page sample.
- Run the captured design locally.
Open the project in your editor, review downloaded assets and compare the page with the published site at desktop and mobile widths.
- Replace the Framer dependencies.
Inspect the migration report, rebuild hosted features and verify animations and forms before moving your domain.
Questions,
answered.
Can't find what you need? You'll get an answer from an engineer within a day.
Talk to usIs this the original Framer React source?
No. 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.
Will my Framer animations work after export?
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.
Can I move the Framer CMS with this tool?
Public content present in captured HTML comes across as page output. A complete structured CMS export, relationships and editing workflow require separate migration.
Will I get the original PHP code, CMS database or a React rewrite?
You get the public front-end HTML, downloaded assets and a runnable project structure. PHP source, database content, user accounts and CMS workflows cannot be recovered from a public URL. Astro and Vite outputs retain editable HTML; they are not generated component rewrites.
Can the exported project work without the original hosting?
Downloaded assets and copied pages can be served locally. CSS imports, fonts and background images are followed and localized when available. Missing assets remain remote, while forms, embedded services and runtime scripts may still depend on the old host. The report identifies detected dependencies so you can rebuild them.
How much can I export free?
Choose one, three or five linked public pages. Each project is capped at 100 asset attempts, 5 MB per asset, 2 MB per page and 25 MB total fetched data. Query-based pages are kept distinct. Pages and assets beyond the caps are listed in the report. No account or card required; request limits apply.