An AI website builder with code export gives you the pages, styles, scripts, and assets to host the site elsewhere. VoxelSite exports your last published site as editable PHP source or pre-rendered static HTML. Those files run without the Studio.
Code export and content export
A content export may transfer text and images into another CMS while leaving the design behind. A code export should give you the pages, styles, scripts, and assets needed to run the website. Check the archive, its hosting requirements, and any features that still depend on the original platform.
Wix does not offer a full website export for independent hosting. Squarespace exports some content, without the site design. Webflow supports HTML, CSS, JavaScript, and asset export on paid Workspace plans, with limits including CMS and ecommerce functionality. Check the export limits for the features your site uses.
See the comparison overview for links to the vendors’ own export documentation.
PHP and static HTML exports
| Format | Use it when | Check before moving |
|---|---|---|
| PHP website | You want editable PHP pages and shared partials on a PHP host. | PHP support, clean URL rewrites, form behavior, and file permissions. |
| Static HTML | You want pre-rendered pages on a static host or CDN. | HTML links, asset paths, and a separate plan for server-side forms. |
The PHP ZIP includes the published page files, partials, CSS, scripts, referenced assets, and portability helpers. It excludes the Studio and its Composer dependencies. The HTML export renders each published page to plain HTML and rewrites internal page links to .html files.
Both formats bundle the assets your site uses and leave out unused library images. Read the download and export documentation for the exact file list.
Contact forms after export
Downloads include a standalone submit.php handler and form schemas. On a PHP-capable host, that fallback handler validates submissions and stores them as JSON files. It does not provide every feature of the installed handler, such as its full database, uploads, rate limiting, and SMTP setup.
On a static host, connect forms to a submission service or a PHP endpoint that you configure. Test a real submission on the destination host before handing over the site.
Client handover checklist
- Publish first. The download includes the last published state. Publish your latest edits before downloading.
- Choose the destination. Use PHP hosting for the PHP export or a static host for HTML.
- Inspect the archive. Check pages, referenced images, CSS, scripts, and any custom external dependencies.
- Test on the new host. Follow internal links, submit forms, check mobile layouts, and verify redirects and metadata.
- Transfer responsibility. Give the client the files, hosting access, and a backup and maintenance plan.
Editing an exported website
The output uses standard PHP, HTML, CSS, and JavaScript. Open it in a code editor and make changes. The export excludes the Studio’s editing interface and revision history.
If you want to keep using VoxelSite’s AI and visual editor, retain the installation, make changes there, publish, and export again. Start with the self-hosting guide if you need help choosing that setup.