Taking the tour with you: a standalone copy, Facebook 360, and the raw export.
This drawer used to carry four different jobs. Three of them are now in the Front Desk, under Share: the switch that makes the tour public, the link you hand out, and the code that puts the tour inside a page on your own website.
They moved because publishing is something the person running the tour does, not the person building it, and the Front Desk is where that person works.
What is left here is the downloads, and they stayed for a reason: each one is built out of the tour as it sits loaded in the editor, with its photographs in memory. They are a production job.
Export Tour (editor bundle) downloads the raw build of the tour as a ZIP: a tour.json describing every point (names, numbers, connections, hotspots, view limits, map positions), every panorama saved as numbered JPEGs in a stops folder, the floor plan image, and a simple portable viewer page.
Click it and wait; there is no progress line for this one. When the bundle finishes, a toast reports how many points it packed and the size in megabytes, and the ZIP lands in your downloads named walkthrough-tour.zip. If the tour has no points yet, you get a message that there is nothing to export.
How it differs from the Standalone package: standalone is the polished offline viewer for handing to people; the editor bundle is the raw data plus original images, with clean numbered filenames that are easy to reuse elsewhere. Grab one before any big restructure of a tour, or whenever you want the photos out of the tour and into your hands as plain files.
The Downloads section of the Share drawer lets you take a tour beyond the web link. Standalone package (ZIP) builds a folder you can keep anywhere, double-click index.html inside it and the whole tour runs in any modern browser, no login and no internet required. 360 photo of selected point saves the point you are standing on as a single 360 photo, ready to post on Facebook where it displays as an interactive sphere. Export Tour (editor bundle) downloads the raw tour data and photos as a ZIP for backup or for handing the tour to another editor.
Preview opens the live customer tour in a new browser tab: the real published viewer, in public mode, with none of the editor chrome. What you see there is exactly what you ship.
Click it with a tour open. If the tour is not published yet, Preview refuses, tells you the tour is not published, and opens the Share drawer for you: switch Publish on, then click Preview again. If no tour is open at all, it asks you to open one first.
Use it after every meaningful change, especially opening views, floor tags and routing, and always before sending the link to anyone. Because Preview loads the real published tour from the cloud, a correct preview also confirms your latest edits actually synced.
Back at the top of the Share drawer closes the drawer and returns you to the tools rail. The Share row in the rail does the same thing as a toggle: click it once to open the drawer, again to close it.
Closing is always safe. Nothing in the Share drawer holds unsaved input: the Publish switch writes to the cloud the instant you flip it, the links are generated readouts, and the download buttons act immediately when clicked. The drawer also closes on its own if you open any other drawer, since only one drawer is open at a time.
Everything regenerates fresh on the next open: the drawer re-reads the publish state from the cloud and rebuilds the customer link and embed code for the active tour every time it opens.
Standalone package (ZIP) builds a complete, self-contained copy of the tour: an index.html with the entire StrollPoint viewer and its libraries baked in, every point's photo, the floor plan, and a short README. Unzip it anywhere and double-click index.html; the tour runs in any modern browser with no internet, no account and no StrollPoint at all.
Click the button and watch the status line under it: it prepares the package, counts through your points one by one as it packages each photo, packages the viewer, then builds and compresses the ZIP with a live percentage. When it finishes you get a ✓ Downloaded confirmation with the file name, your tour name plus -tour.zip. Photos come from memory and the local cache first and are fetched from the cloud only when needed, so a large tour on a slow connection takes a while; leave the drawer open until the checkmark.
If something goes wrong the same line shows Failed with the reason, and with no tour open it asks you to open one first. Expect real size: every photo ships at full quality, so photo-heavy tours can produce ZIPs of hundreds of megabytes.
Use it for client deliverables, kiosks and offline demos, and archives. It is a snapshot: edits you make later do not change copies already downloaded, so re-export after significant changes.
360 photo of selected point downloads the currently selected point's panorama as a JPEG stamped with the 360 metadata that Facebook and similar platforms read. Posted as a normal photo, it renders as an interactive look-around 360 instead of a flat stretched strip. The file is named strollpoint, then the point's name, then -360.jpg.
Select the point you want in the points list or on the map, then click the button. The status line shows Preparing…, then ✓ Saved with a reminder to post it. Upload the file to Facebook like any photo; the platform detects the embedded metadata by itself. If you cleaned the image with Magic Erase or a nadir patch, the edited version is what exports.
Two failure messages to know: Select a point first means nothing is selected, and this point has no photo loaded yet means the panorama is not on this machine; open the point once so its photo loads, then try again. The status line clears itself after a few seconds.
Use it as marketing: post your single best point with the customer link in the caption, rather than asking people to click through to the whole tour cold.