Preview
$0
Free, always
To check that your site exports cleanly before you spend anything.
- Crawl any site you own
- Inspect the full file tree
- Download the home page
- One site at a time
Framer to static
Framer builds it.
You keep it.
Unframe exports any published Framer site to plain HTML, CSS and assets. Fonts, images and scripts all pulled local, every page and CMS entry included, ready to host anywhere you like.
Output
This is the whole thing. No runtime, no dependencies.
becomes
your-site/ ├── index.html ├── about/index.html ├── projects/index.html ├── blogs/index.html ├── 404.html ├── README.txt how to publish it └── assets/ ├── images/ 150 files ├── js/ 78 files incl. cms ├── fonts/ 36 files ├── media/ 1 file └── files/ 2 files
Counts above are from a real export. Unzip it and serve the folder,
with python3 -m http.server or anything else. Opening
index.html straight off disk shows the layout, but
browsers block JavaScript modules on file://, so the
animations stay dormant until something serves it.
Drag the folder onto Netlify, push it to a bucket, or hand the ZIP to a client. It is ordinary static hosting from here on, which means it is usually free.
- Pages per export
- up to 200
- Calls back to Framer
- none
- Kept on our server
- 1 hour
The awkward parts, mostly.
- Every page it can find
- The crawl reads your sitemap first, then follows links, because Framer CMS pages are not always reachable by link alone. Up to 200 pages.
- CMS collections
- Entries come down as static files, with a small shim so the site's own
?range=fetches resolve against them instead of Framer's API. - Fonts, self-hosted
- Every woff2 lands in
assets/fontswith the stylesheet rewritten to match. Nothing is fetched from Google or Framer's CDN at runtime. - Images, video and downloads
- Fetched, de-duplicated, and rewritten to relative paths. 25 MB per file and 250 MB per export; past that you get a partial ZIP and a note saying what was left out.
- Motion, as it was built
- Framer's runtime comes across intact, so scroll and hover effects still work. It arrives as minified chunks rather than readable source, and a
_headersfile ships when your host needs it to serve them as JavaScript. - Framer's telemetry, removed
- The editor bar and the telemetry beacon go every time. Your own analytics stay unless you ask for them to go, because those are yours to keep.
- It fails honestly
- A site behind a Cloudflare bot wall is detected and reported, not quietly exported as a challenge page. You get a plain sentence saying what happened.
- Nothing points back to us
- No Unframe script, no beacon, no licence check, and not one mention of our name anywhere in the output. Grep it yourself.
Preview free. Pay when you can see the files.
Most agencies pick this
Pro
$24 /month
Billed monthly
For the freelancer or studio shipping Framer sites on a regular basis.
- Unlimited exports
- Up to 200 pages per site
- CMS collections included
- Tracker stripping
- Priority in the queue
Agency
$79 /month
Billed monthly
For teams handing finished sites to clients under their own name.
- Everything in Pro
- 5 seats, shared history
- White-label handoff
- Bulk queue, 20 sites lined up
- API access
- Same-day support
Just the one site? A single complete export is $39, paid once, no subscription. Choose it at checkout.
Billing is not switched on yet. While Unframe is in beta every export is free and complete, with no account and no card. These are the prices when it lands.
Before you paste a URL.
Am I allowed to do this?
For a site you own, or one you built for a client who has asked you to move it: yes. The pages are already published on the public internet, and Unframe reads them the way any browser or archiving tool does.
It will not open anything behind a password, a paywall or a staging lock. If you are unsure how this sits with your own Framer plan, check its terms first; that agreement is between you and Framer.
Does the exported site keep updating when I edit in Framer?
No. An export is a snapshot of the site at the moment you ran it. Publish your changes in Framer, then run it again.
Download the ZIP and keep it somewhere: finished exports are deleted from our server an hour after they complete. We are not a backup service, and holding copies of your site longer than we need to is not something either of us wants.
What doesn't come across?
Anything that depends on Framer's own servers: the CMS editing interface, form submissions routed through Framer, A/B tests, and Framer analytics. Everything a visitor can actually see does come across.
Forms are the thing to plan for. The markup exports, but the submission endpoint does not, so point it at Formspree, Netlify Forms or your own handler once the files are yours.
Embeds that were always external (Spline, Vimeo, Shopify) stay external. That is how they were built.
Will it look the same?
That is the intent, and there is a fidelity harness in the engine that screenshots an export against the live site and pixel-compares them. Serve the folder and check it yourself before you point a domain at it. You have the whole thing, so you never have to take our word for it.
How large is a typical export?
Almost entirely down to images. A text-led site runs to a few MB. A photo-led one runs much further: a recent three-page export of an image-heavy template came out at 86 MB, nearly all of it full-resolution JPEGs.
There is a 250 MB ceiling per export. Hit it and you still get a ZIP, plus a note inside listing what was left out.
Can I use this on client work?
That is most of what it gets used for. Agency adds white-label handoff, so the export, the zip and the accompanying README carry your studio's name and not ours.
Paste a URL.
See the files.
Then decide.
Export a site
Free preview · no account · about ninety seconds