Skip to content
VoxelSite

Download & export

Export your published site as PHP or static HTML. Check included files and the limits of forms, actions and MCP without Studio.

Updated October 23, 2026 3 min read

Export the published website as PHP source or rendered HTML. The archive records its source version, included files and dependencies. Draft edits do not enter a published export.

How to download

Open Download in the Studio status bar and choose PHP Website or Static HTML. Inspect the source version and dependency information before downloading. Publish first if you want recent draft changes in the archive.

Studio MCP export tools can select an explicit draft or published version. They prepare an archive for review, retain its hash and provide a short-lived download grant. An export does not publish or change the website.

PHP website export

PHP exports include managed pages, including nested paths, shared partials, mutable assets and referenced shipped resources. The archive can include:

Content Behavior
PHP pages and partials Keep the directory layout and host on PHP 8.2+
CSS, JavaScript, images, fonts and public data Taken from the selected source version
Referenced library images and icons Included when the exporter resolves the source reference
Published discovery files Included when present in the managed source
mcp.php Standalone read-only business tools when site data is available
submit.php and form schemas Basic standalone form fallback when forms are present
.htaccess Clean URLs and protection for standalone submission storage
EXPORT-README.txt Source, dependencies and deployment limits

Exports exclude the Studio application, credentials, private submissions and private authoring files memory.json and design-intelligence.json. Studio MCP is never part of a portable website archive.

Forms and Actions

The standalone form handler needs PHP 8.2+, writable _submissions/ storage and optional host mail(). It stores JSON submissions. It has no Studio inbox, upload handling, SMTP configuration or Studio rate limiting. On Nginx, block _submissions/ before accepting data.

Actions require the original Studio installation. Export removes the supplied Actions Bar scripts and styles. Adapt any custom Action controls before deploying the archive elsewhere. The exported public MCP endpoint is read-only.

Static HTML export

The exporter renders the selected PHP pages, including nested pages, into HTML. It rewrites supported local links and asset URLs for those known pages, preserving query strings and fragments. It copies the selected assets and removes shared PHP partials from the rendered output.

A static page needs no PHP runtime. If forms are present, the archive still includes the standalone PHP form handler; that handler cannot run on a static-only host. Public MCP is omitted from HTML exports.

Remote URLs remain remote. Export lists them as dependencies; it does not download them. Check external availability and usage rights yourself. Unsupported rendering or dependencies can stop preparation with a diagnostic instead of silently using live files.

Review the archive

Check EXPORT-README.txt, the file inventory and archive hash. Test nested navigation, images, fonts, dynamic JavaScript and forms on the destination host. Source scanning cannot prove every URL assembled at runtime works.

Preparation has file, byte, memory and request-time limits. The review reports the effective limits for your host. If preparation exceeds them, reduce the selected content or use a host with sufficient resources. A retained export result does not certify the destination host or mail delivery.

Deploying the exported files

  1. Download and extract the archive into a separate directory.
  2. Read EXPORT-README.txt and configure the destination host.
  3. Upload the complete directory layout.
  4. Open the pages and check navigation, assets and interactions.
  5. Test a deliberate form submission if the destination supports PHP.

Use the export as a portable website, not as a VoxelSite application backup or upgrade package. Keep separate backups of Studio data and business records.

Found a mistake in these instructions? Open an issue.

Download VoxelSite