Discover public pages from site links and the sitemap.
Example: https://your-account.wixsite.com/your-site
Wix pages rely heavily on platform scripts. Stores, bookings, CMS, login, and some visual elements may not work away from Wix. Next.js export is in development.
What a Wix HTML export includes
FNJ can fetch public Wix page markup and accessible assets, but Wix sites often assemble visible content with platform scripts. An HTML capture may need substantial repair before it resembles the live site or works independently.
How to convert a Wix site to HTML
- 01 / Paste a public URL
Use a published Wix 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
Preview the result before downloading or publishing. Compare it with the original at multiple widths and check every menu, gallery and widget. Treat missing content or non-working interactions as blockers for a production migration.
Wix 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:
- Compare the preview with the published Wix page before deciding whether the capture is usable.
- Inspect script-built sections, mobile layouts, galleries and menus for missing content.
- Rebuild and test Wix CMS, booking, store or login flows before sending visitors to the static version.
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 →Wix to HTML: export and hosting FAQ
- Will the Wix page look identical after conversion?
- Not necessarily. Some Wix layouts depend on scripts and services outside the static markup. FNJ shows a preview so you can inspect what was actually captured.
- Are Wix CMS, bookings and store data included?
- No. Those are Wix-hosted services and need to be recreated or connected separately before the static page replaces your live site.
- Is Wix to HTML a guaranteed complete migration?
- No. Wix's script-built content and hosted services can limit a public HTML capture. Inspect the preview and rebuild missing layouts or features before replacing the original site.
- Can I edit the Wix 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 Wix do not automatically sync.
- Can I host the Wix 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 Wix 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 Wix HTML
Host your Wix HTML export on Cloudflare
Deploy Wix HTML to your own Cloudflare Pages account. Review the captured pages, upload assets, test dependencies and connect your domain.
Follow the workflow →Export your Wix HTML code to GitHub
Put your Wix 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 Wix 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