Download any tour as a self-contained folder of HTML, JavaScript, CSS and images. Drop it on Netlify, an S3 bucket, a corporate intranet, or the nginx box under your desk. It's a web page, and it's yours.
HTML export is included on every paid plan and in the Desktop License.
Managed hosting is the easiest way to publish and update most tours. HTML export adds another delivery option for projects that need a standalone copy.
A hosted link is ideal for fast sharing. A static folder also gives a client a concrete deliverable they can store, move, or run on their own infrastructure.
Keep a versioned copy of the complete tour next to the rest of a project's source material, ready to serve again whenever it is needed.
Trade show booths, museum kiosks, secure sites and ships may not have public internet. A static bundle can run there from a local server.
The exported bundle uses the same viewer as our hosted tours, packaged as self-contained static files.
Export streams you a zip. Unzip it, keep the structure, and every file the tour needs is already sitting next to index.html.
The runtime, the stylesheet and the fonts are all bundled. The tour loads nothing from us, from a CDN, or from a font provider.
Exports carry no 360Creator badge, logo, or analytics. There is no platform branding to remove, because none is ever put in.
Serve the folder from a laptop at a trade show or a kiosk with no uplink. Everything the visitor sees is already on the machine.
Hotspots, scene links, floorplans, the thumbnail carousel, VR mode and your nadir logo all survive the export intact.
manifest.json is versioned and complete. Import the folder back into the editor to keep working, then export again.
No surprises, no phone-home, no build step. Six things, and you can read every one of them.
index.htmlThe tour itself. Serve it and it runs — the tour data is inlined, so there's no config to fill in.viewer.jsThe 360° runtime as a single bundle. No CDN, no framework to install, no external scripts.viewer.cssStyles with the fonts inlined, so the page never reaches out to a font host.manifest.jsonThe complete tour: scenes, links, hotspots, settings and branding. Import it back to keep editing.assets/Your panoramas and their resolution tiers, stored byte-for-byte rather than re-compressed.README.txtHow to host the folder, and how to preview it locally.Upload the folder to any static host and open index.html. Nothing else is required — no server-side code, no database, no configuration.
Every paid plan. On the hosted side that's Creator and Studio; buying once, it's the Desktop License, which includes every feature. The free plan is for trying the editor out and doesn't include export.
No — and this surprises almost everyone the first time. Browsers refuse to let WebGL load textures on pages opened from the file system (file://), so the panoramas won't render. Run a local web server from inside the folder instead: `python3 -m http.server 8000` or `npx serve .`, then open the address it prints. On a real host it just works.
No. The hosted viewer injects our badge and logos as optional slots; the export renders the same viewer without them. Exported bundles are completely unbranded and include no tracking or analytics.
Anywhere that serves static files: Netlify, Vercel, GitHub Pages, Cloudflare Pages, an S3 bucket with static hosting, or nginx, Apache or Caddy on a server you run. There is no server-side code to deploy and no database to provision.
The runtime is small and fixed; the panoramas are everything. Because the images are already compressed, the zip stores them as-is rather than deflating them again — so a bundle is roughly the size of its panoramas plus a few hundred kilobytes.
Yes. Keep manifest.json next to its assets folder and import the pair back into the editor. Scenes, links, hotspots, floorplan markers and branding are all restored, and the bundled images are reused rather than re-processed.
Yes. An exported tour is a folder of static files on a host you control. Nothing in it checks a license, calls our API, or expires.