What this workflow gives you
A deployed static version of your captured Wix pages in your own Cloudflare account. Cloudflare hosting does not fix content that was missing from the Wix capture. Compare galleries, mobile layouts and menus before launch. Stores, bookings, CMS and login need replacements or retained services; treat missing core behavior as a blocker for moving the domain.
- Input
- Published Wix URL
- Output
- Static HTML and reachable assets
- Your account
- Cloudflare Pages
From HTML export to a live site
- 01
Convert and review the public pages
Open the Wix HTML converter and use a published URL you own or are authorized to convert. Review the capture report and preview before proceeding. Evaluate one public Wix page first. Script-built sections can be absent or incomplete in a markup capture; a successful request is not proof that the exported site is usable.
- 02
Prepare the static folder
Keep index.html, page files and their referenced assets together. For a downloaded ZIP, extract the files first and locate the folder containing index.html. Do not upload a Next.js source folder or accidentally place the site inside an extra nesting folder.
- 03
Connect your own Cloudflare account
From the saved site in FNJ, use Deploy with token and choose Cloudflare. Enter a Cloudflare token with Pages: Edit permission for the account you intend to use directly in FNJ. Follow the dashboard result to the deployment URL. You can also deploy your extracted HTML independently using Wrangler.
- 04
Test on the preview URL
Compare the preview with Wix at two screen widths and verify galleries, booking links and important page content before switching traffic. Open important nested pages directly and refresh them. Inspect failed asset requests and follow each form or purchase action to its real destination before treating a successful upload as a usable website.
- 05
Connect the final domain
Add your domain through the Cloudflare Pages project's custom-domain settings and follow its DNS instructions. Confirm the domain is active and serves the reviewed version. Keep important paths; configure redirects for changed URLs and check canonical tags on the final address.
Deploy the downloaded folder with Wrangler
If you use the command line instead of FNJ's deploy action, sign in to your own Cloudflare account. The following example uses wix-site as a project name and ./site as the extracted folder containing index.html; replace both with your own values.
npx wrangler login
npx wrangler pages project create wix-site
npx wrangler pages deploy ./site --project-name=wix-siteWrangler uploads the static directory, not the ZIP. Choose Direct Upload or Git integration when setting up the Pages project; Direct Upload projects cannot later switch to Git integration without creating a new project.
Checks specific to Wix
- 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.
Wix to Cloudflare Pages: questions
- Can I host a Wix site on Cloudflare without moving the builder account?
- You can host the reviewed static HTML output. Cloudflare hosting does not fix content that was missing from the Wix capture. Compare galleries, mobile layouts and menus before launch. Stores, bookings, CMS and login need replacements or retained services; treat missing core behavior as a blocker for moving the domain. A builder account, database or editing workspace is not part of that deployment.
- Does this workflow need a Next.js build?
- No. This page covers an exported HTML bundle with a top-level index.html. Upload the static files. A Next.js source project needs its own build and deployment setup; do not upload application source as if it were prebuilt HTML.
- What should I test before switching my Wix domain?
- Compare the preview with Wix at two screen widths and verify galleries, booking links and important page content before switching traffic. Also test direct visits to nested URLs, mobile layouts and any changed redirects on the final domain.
- Does FNJ host this site or manage the Cloudflare bill?
- The deployment uses your Cloudflare account. You control hosting settings and any charges under its current plan. FNJ's conversion access and the hosting provider's terms are separate; check each before purchasing.
Continue with the right setup
Converting requires a signed-in FNJ account and current conversion access. Review FNJ pricing for purchase terms. For help using your own agent, follow the deployment guide and prompt library.
Cloudflare: upload a static site