Move your Framer site onto hosting you own
Export the published site once, deploy it to a host you control, and stop paying a monthly fee to keep a finished page online. Twelve deploy guides, ten migration paths, and the checks that stop a move from costing you rankings.
Export your Framer site
Paste the published URL. Preview the full site free, download the bundle when you are ready to move.
Pick where it lands
Every host serves static files, and every host breaks a Framer export in its own particular way. These pages cover the deploy command, the config file, and the failure you would otherwise find after moving DNS.
Anyone who wants the closest thing to Framer's own publish button, with previews on every change.
Non-technical owners — this is the only mainstream host where a working deploy is genuinely one drag.
Sites with real traffic, where bandwidth overage on a metered host would cost more than the export did.
Archival and portfolio sites where free-forever matters more than deploy ergonomics.
Teams already inside AWS who want the site under the same account, billing, and IAM as everything else.
Owners who want one annual invoice covering the domain, the hosting, and mailboxes.
Or rebuild it somewhere else
Rated honestly — including the destinations where an export is only a starting point and anyone promising a one-click conversion is overselling.
A static export is not a WordPress theme, and anyone promising a one-click conversion is selling you a wrapper.
Webflow has no HTML import.
This is the cleanest destination of the set.
The most forgiving destination for an exported site, because an .astro file accepts unmodified HTML.
Product pages, cart, and checkout must be Shopify's — that part is not negotiable and not something an export can replace.
A good destination when the site is mostly content and the owner wants files in Git rather than rows in a database.
Work out whether it is worth it
A structural breakdown of recurring Framer costs versus a one-time export plus static hosting, and when each one is the right call.
The order of operations that avoids downtime: export, deploy, verify, move DNS, then cancel. With the checks that catch problems before the domain moves.
The eleven things that silently break rankings during a host migration, and how to verify each one before and after the DNS change.
Hand a client the actual files instead of a seat on your Framer account. Ownership, invoicing, and the handoff checklist.
Ship a Framer build as owned code so the invoice closes and the project ends. Scoping language and delivery checklist included.
Get the marketing site out of a design tool and into your repo, so engineering can ship changes and diligence finds nothing odd.