LayerPort

Webflow export

Webflow to static HTML.

Turn an authorized Webflow site into static HTML and local assets you can edit and host anywhere -- no Webflow account required to keep it running.

Real markup on disk

The output is readable static HTML, CSS, and media. You can inspect exactly what ships and change it directly if you want to.

Assets that travel

Images, fonts, and styles are rewritten to local paths so the static site does not depend on Webflow's servers to render.

Publish without the platform

Once it is static, hosting is trivial: preview, export a ZIP, or deploy to a static host with the included guide.

What the static folder holds

Pages
One HTML file per route, rendered as published
Assets
assets/{css,js,img,fonts,media}, every reference rewritten
Forms
Re-pointed to a first-party endpoint — Webflow's own form handler stays with Webflow
Host config
vercel.json, netlify.toml, _headers
What is not there
The Designer, the CMS, the editor — Content is rendered output, not a live collection

No build step, no runtime, no database. Anything that serves files with the right MIME types serves this.

The pre-flight, before you point DNS at it

  • Serve the folder locally and walk every route with the network off
  • Open the network panel and confirm nothing resolves to *.webflow.io
  • Submit each form once and check it arrives in the inbox you configured
  • Check the pages the navigation does not link to — they are the ones that get missed
  • Deploy to the host's preview URL first; move the domain only after that passes

FAQ

Does the static site still need Webflow?

No. Assets are localized, so it runs independently on any static host.

Can I edit the HTML afterwards?

Yes. Use the visual editor, or edit the exported files directly.

Features · Workflow · Pricing · FAQ