3Sixty Studio Docs

Docs Publishing

Preview, export & publish

Run shows you the finished tour inside the app. Export packs it into a ZIP you can publish. Both rebuild the tour from your latest changes first.

Preview with Run

Press Run in the editor sidebar (or the play button in the compact top bar). A loading screen shows each step:

  1. Checking project template… Older projects get their tour player (index.html) upgraded to the latest version. See Template upgrades.
  2. Building tour… The panoramas, hotspots, actions, tour map, 3D scenes and settings from WTMProject.wtm are written into index.html.
  3. Starting preview server… A small web server starts on your device (only reachable from the device itself) and the tour opens full screen.

The back button is the only control on top of the preview; it returns you to the editor and stops the server. If a step fails, the error is shown with a Try again button.

Differences from the published tour: Mouse Look is disabled in the preview, and page zooming is blocked so dragging the panorama feels smooth. On mobile the preview reloads by itself if the app returns from the background or the system frees its memory.

Export

Press Export ZIP (desktop) or Export (mobile).

  • Desktop: a save dialog opens. The suggested name is your project name with spaces replaced by underscores, plus a timestamp, for example My_Hotel_1767225600000.zip. Save it outside the project folder; saving inside it is refused so the ZIP does not include itself.
  • Mobile: the ZIP is created in a temporary folder and the share sheet opens, so you can save it to Files, send it by e-mail, upload it to Drive, and so on.

The ZIP contains the whole project with index.html at the top level (no wrapping folder): the tour player, WTMProject.wtm and every media folder.

Publish on the web

An exported tour is a static website. It needs no database and no server-side code, so it runs on almost any host.

  1. Unzip the exported file.
  2. Upload everything inside it (index.html and all folders) to your web host, for example into a folder called tour.
  3. Open the address in a browser, for example https://example.com/tour/.

Options that work well:

  • Any shared hosting with FTP or a file manager (cPanel, Plesk…).
  • Static hosts such as Netlify (drag the unzipped folder onto its deploy page), Cloudflare Pages or GitHub Pages.
  • Your own server (Apache, Nginx, IIS).

To put the tour on an existing website, link to it or embed it with an iframe:

<iframe src="https://example.com/tour/" width="100%" height="600"
        style="border:0" allow="fullscreen; autoplay" allowfullscreen></iframe>

Test the export on your computer

Opening index.html by double-clicking it may show a black screen, because browsers restrict pages opened from file://. Serve the folder with a local web server instead. For example, with Python installed, run this inside the unzipped folder and open http://localhost:8000:

python3 -m http.server 8000

Template upgrades

Each project carries its own copy of the tour player, taken from the app when the project was created. When you Run or Export an older project, 3Sixty Studio replaces the player code with the newest version and carries over your project's content. Before changing anything it saves the old file as index.before-upgrade.html in the project folder. After an upgrade you see "Project template was upgraded to the latest version".

If the old file has an unexpected structure, it is left untouched and the build continues with it.