Discover public pages from site links and the sitemap.
Example: https://your-site.webflow.io
Webflow CMS, forms, checkout, and accounts need a replacement backend. We are improving Next.js fidelity; HTML is available now.
What a Webflow HTML export includes
FNJ captures the public version of your Webflow pages, including the HTML, stylesheets and assets it can reach. You can edit the resulting files in FNJ or download them for a static host. The Webflow Designer project is not exported.
How to convert a Webflow site to HTML
- 01 / Paste a public URL
Use a published Webflow page you own or are allowed to convert. A private project link cannot be captured.
- 02 / Choose the scope
Capture one page, or discover linked public pages and pages exposed in the site's sitemap. Review the capture report for omissions.
- 03 / Preview and export
Check the HTML preview, then edit, download or deploy the captured files according to your FNJ access.
What FNJ captures
FNJ saves public page markup and accessible styles, images and other assets. You can capture one page or let it discover linked public pages. Uncopied assets and external scripts may still load from the original service.
Before you publish
Open the published Webflow URL, not a Designer preview. After conversion, compare the result with the live site and test menus, animations and every form. Webflow scripts may remain external, and hosted services need a replacement before you switch domains.
Webflow migration checks
A static export captures public pages, not the builder account or its hosted workflows. Check these before directing visitors to the new host:
- Open each captured CMS item URL and confirm its content is present; collection data will not update automatically.
- Submit a test form and complete a test checkout on the new host before moving your domain.
- Check interactions and animations with the original Webflow site closed; external Webflow scripts may still be required.
Keep your pages findable after the move
Keep important URLs and page titles where possible. If a path changes, redirect its old URL to the matching new page. Review canonical URLs and your sitemap on the final domain, then check indexing and crawl errors in Search Console. The export cannot guarantee that a search ranking will stay the same.
Follow the edit and deployment guide →Webflow to HTML: export and hosting FAQ
- Does this export my Webflow CMS?
- Public CMS item pages can be captured as pages when the crawler finds them. Collections, the CMS editor and future dynamic publishing do not move into the static files.
- Will Webflow forms and ecommerce keep working?
- No independent form or checkout backend is created. Connect replacements or keep the original service before publishing the HTML elsewhere.
- Is this a Webflow Designer project export?
- No. FNJ captures the published page output. You receive editable HTML and assets, not a Designer project, Webflow CMS database or account configuration.
- Can I edit the Webflow HTML and CSS after downloading?
- Yes. The captured HTML, CSS and accessible assets are editable files. Work in your code editor or use supported FNJ MCP tools with a connected agent. The export is a snapshot; changes made later in Webflow do not automatically sync.
- Can I host the Webflow HTML export on Cloudflare?
- You can deploy the static files to your own Cloudflare account or another compatible static host. Preview every page and reconnect hosted forms, payments and other services first. A GitHub repository can hold the source files; pushing code is separate from configuring its hosting.
- Is the Webflow converter free or does it need an account?
- Converting requires a signed-in FNJ account and the access shown in current FNJ pricing. You can read this guide without signing in. Check the pricing page for current purchase terms; no builder subscription or private account access is used to fetch public pages.
Need the next step? Connect your agent through MCP, copy a site editing prompt, or check current FNJ pricing.
Where to take your Webflow HTML
Host your Webflow HTML export on Cloudflare
Deploy Webflow HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Webflow HTML code to GitHub
Put your Webflow HTML export in your own GitHub repository. Choose the right files, review the fnj-export branch and plan updates and hosting.
Follow the workflow →Make your Webflow export work for you
Practical guides for editing the captured HTML, reconnecting services and checking the result before launch.
Edit with MCP →
Connect an agent to FNJ MCP, inspect the correct route, change content and review the draft before publishing.
Reconnect forms →
Audit form actions, connect your own submission service and verify delivery, validation and error feedback after moving hosts.
CMS & content →
Separate captured article pages from the original CMS, inventory content and choose a tested publishing workflow for future updates.
URLs & SEO →
Map old and new routes, check canonical tags and metadata, test redirects and review indexability on the final domain.
Mobile layout →
Compare narrow and wide previews, fix overflow and navigation, and verify touch, keyboard and reduced-motion behavior.
Images & fonts →
Find failed asset requests, correct relative paths, inspect external dependencies and preserve typography on the new host.
Export troubleshooting →
Separate URL access errors, capture limits, missing content and deployment problems using a small reproducible conversion.
Explore related converters