3dCMS Knowledge Base
Open the editor
Publishing & Hosting

Download your site (static export)

Export a published site as a self-contained zip that runs on any static web host — plus the older scene.json / GLB export path.

Open in the interactive manual →

The interactive version has full-text search, a table of contents, and light/dark themes.

Your published site doesn't have to live only on 3dcms.info. Publish a scene, open the share dialog, and hit Export site (.zip) — you get a single zip containing the whole thing: the 3D viewer, your scene, and every model, image, audio file and texture it references.

Hosting the zip

Unzip the folder and upload it — keeping its structure — to any static web host: nginx or Apache, S3/CloudFront, GitHub Pages, Netlify, an FTP web root. It works from a domain root or from a subfolder, because every link inside the bundle is relative. Then open the URL of index.html.

It has to be served over http(s) Double-clicking index.html from your desktop won't work — browsers block JavaScript modules on file:// addresses. Any real web server (or a local one-liner static server) is fine.

What's inside

  • index.html — the 3D viewer; start here.
  • scene.json — your scene's content.
  • assets/ — the viewer code plus your uploaded media.
  • textures/, backdrops/, draco/ — the built-in files your scene happens to use.
  • README.txt — the same hosting notes, packed alongside.

Honest limitations

  • It's a snapshot. Republishing on 3dcms.info does not update a copy you already downloaded — export again for a fresh one.
  • Anything that needs the 3dCMS server is inactive in the copy: reactions, view stats, and the report button.
  • 3D text glyph fonts are still fetched from a CDN the first time text renders, exactly as they are on the live site, so viewers need internet access for 3D text.
  • Videos or images pointing at other websites still load from those websites.
  • The bundle has one entry point. In-world page travel works while exploring, but reloading a deep /3d/… address gives your host's 404 — link people to the root URL.
  • Very large sites are refused (there's a size ceiling in the hundreds of megabytes). If you hit it, trim heavy videos or models, republish, and retry.

Only the site's owner can export it, and the button appears once the scene has actually been published.

The older export path

If you'd rather run your own build, Settings ▸ Deployment still has the raw exports:

  • Export scene.json — saves your scene so you can run a build and deploy the output to any static host.
  • Export GLB — downloads the whole scene as a single GLB model.
  • Deploy target — optionally point at a Netlify or Vercel build/deploy hook (or a custom endpoint) so an export can kick off a deploy.
You probably don't need the build path Published 3dCMS sites are already plain, cacheable HTTPS with no special CDN or container required. Rolling your own build is for teams with an existing pipeline they'd rather keep — if you just want your site somewhere else, the zip above is the shortcut.
Spotted something off, or want a topic covered? Email buck.rackley@gmail.com.