Skip to content
ESC

Searching...

Quick Links

Type to search • Press to navigate • Enter to select

Keep typing to search...

No results found

No documentation matches ""

Download & Export.

Download your published website as a PHP or static HTML ZIP file. Deploy anywhere without VoxelSite.

Feb 22, 2026

Download & Export

Download your entire published website as a ZIP file. Choose between PHP source or static HTML — both run independently without VoxelSite.

How to download

Click the Download button in the status bar at the bottom of the Studio. A modal presents two options:

  • PHP Website — your complete source files, ready for any PHP hosting
  • Static HTML — every page pre-rendered to plain HTML, ready for any web server or CDN

Click either card to start the download. The ZIP is generated on the server and streamed to your browser.

Note: The export reflects your last published version. If you have unpublished changes, a warning will appear with a link to publish first.

PHP Website export

The PHP export gives you the exact files your site runs on. Upload to any shared hosting with PHP support and your site works immediately.

What's included

Category Files
Pages All published .php page files (index.php, about.php, etc.)
Partials Shared includes (_partials/header.php, nav.php, footer.php, schema.php)
Styles assets/css/style.css, assets/css/tailwind.css
Scripts assets/js/main.js, assets/js/navigation.js, assets/js/form-handler.js
Data JSON configuration files from assets/data/
Images & fonts Only the files your pages actually use (see Smart asset bundling)
.htaccess Apache rewrite rules for clean URLs, MIME types, caching, and security headers
robots.txt Crawler rules (Studio-internal rules are stripped)
llms.txt AI discovery file describing your site for language models
mcp.php MCP server endpoint for AI agents (read-only tools work standalone)
favicon.ico Your site favicon, if uploaded

What's not included

  • The _studio/ directory (VoxelSite itself)
  • The vendor/ directory (Composer dependencies)
  • submit.php and form submission handling
  • Unused library images, icons, and fonts

Static HTML export

The HTML export pre-renders every page to plain HTML. No PHP required — open the files directly in a browser or deploy to any static host, CDN, or file server.

How it works

  1. VoxelSite fetches each published page through an internal HTTP request
  2. The rendered HTML is captured with all styles and scripts inlined
  3. Internal links are rewritten from clean URLs (/about) to file references (about.html)
  4. Remote images referenced in your pages are downloaded and bundled locally

What's included

The same assets as the PHP export, but with .html files instead of .php files and no server-side features (no .htaccess, no mcp.php, no robots.txt).

Smart asset bundling

Both formats use smart asset bundling to keep the ZIP lean. CSS and JavaScript directories are always included in full, but images, library photos, fonts, uploads, icons, and data files are selectively included — only files that are actually referenced in your page content, CSS, or JavaScript are bundled.

This means if your image library has 130 curated photos but your site only uses 9, the export contains just those 9.

Relationship to publishing

The export always reflects your last published state. Edit your site, publish, then download. If you need to make changes to the exported files, edit them in the Studio, publish again, and re-download.

Deploying the exported files

PHP export

  1. Download the PHP ZIP
  2. Extract the contents
  3. Upload to your web server via FTP, SFTP, or file manager
  4. Point your domain to the extracted directory
  5. Your site is live

The included .htaccess handles clean URLs (/about instead of /about.php) on Apache servers. For Nginx, you'll need to configure URL rewriting manually.

Static HTML export

  1. Download the HTML ZIP
  2. Extract the contents
  3. Upload to any web server, CDN, or static host (Netlify, Vercel, Cloudflare Pages, GitHub Pages, S3, etc.)
  4. Your site is live

No server configuration needed — the HTML files work as-is.

Related