Book an inspectionInspection
HTMLAstroVite
Wix public page → migration starter

Start your Wix rebuild
with the pages you have.

Get the public HTML and available design assets into your editor. See the Wix scripts and services that still need replacement before you move to your own hosting.

Free · no account · nothing changes on your live site

Use the published Wix page on your custom domain or wixsite.com. Editor and dashboard links cannot be exported.

What comes with you

Your Wix front end

  • Public server HTML

    The page markup the public URL returns. Browser-rendered sections may be absent.

  • Available design files

    Discoverable stylesheets, images, fonts and scripts, with local paths for successfully copied files.

  • A rebuild reference

    Editable project files and a dependency report to review Wix runtime scripts and embedded services.

Plan the rest of the move

Replacements to build

  • Browser-rendered content

    This tool does not execute JavaScript. Pages with little readable HTML are flagged for further capture or manual rebuilding.

  • Bookings, members and checkout

    These are migration tasks to review on your site; a public capture does not recreate Wix service behavior.

  • Runtime independence

    Copied Wix scripts can still call Wix. Verify every interaction rather than assuming the ZIP runs independently.

Wix documentation on external hosting
Built for the move

Your Wix move,
one step at a time.

  1. Capture a published page.

    Begin with your homepage or an important landing page. Review whether the server HTML contains the content you need.

  2. Inspect what came across.

    Run the project and compare it with the original. Check the report for missing assets, thin pages and Wix runtime dependencies.

  3. Rebuild the services you use.

    Replace bookings, forms, memberships or commerce as needed. Test the replacement site before changing your domain.

Questions,
answered.

Can't find what you need? You'll get an answer from an engineer within a day.

Talk to us
Is this a full Wix source-code export?

No. It captures public front-end HTML and available assets. Wix editor data, Velo backend code, accounts and proprietary services are not recovered.

Why might my Wix page be incomplete?

The exporter reads server HTML without running JavaScript. Content or styles loaded later by the browser may be missing, and copied scripts may still need Wix services.

Will I get the original PHP code, CMS database or a React rewrite?

You get the public front-end HTML, downloaded assets and a runnable project structure. PHP source, database content, user accounts and CMS workflows cannot be recovered from a public URL. Astro and Vite outputs retain editable HTML; they are not generated component rewrites.

Can the exported project work without the original hosting?

Downloaded assets and copied pages can be served locally. CSS imports, fonts and background images are followed and localized when available. Missing assets remain remote, while forms, embedded services and runtime scripts may still depend on the old host. The report identifies detected dependencies so you can rebuild them.

How much can I export free?

Choose one, three or five linked public pages. Each project is capped at 100 asset attempts, 5 MB per asset, 2 MB per page and 25 MB total fetched data. Query-based pages are kept distinct. Pages and assets beyond the caps are listed in the report. No account or card required; request limits apply.

Explore website to code export →