BLACK FRIDAY −30% Until 30/11/2026 View offer
Software

How to Export a Virtual Tour and Hand It Over to a Client

November 10, 2026 • By SVT Team
How to Export a Virtual Tour and Hand It Over to a Client

Export a virtual tour by choosing the output that matches its destination, generating and downloading the archive, inspecting its contents and testing it in the recipient's environment. In SVT, distinguish standalone viewer delivery from a package intended for importing into another compatible installation.

Review scope: Published by the developer of Simple Virtual Tour. Official documentation and the local editor source were reviewed on 12 November 2026. Controls depend on release, permissions and plan; this is a documentation-based guide, not a report of device or customer performance tests.

Choose the correct output

  • Standalone: viewer and tour assets for a separate deployment. Check the actual package instructions and external dependencies.
  • Standalone (VR): the separate VR export option shown by the reviewed release. Its label is not a guarantee of compatibility with every headset or browser.
  • Importable: a package intended for importing into a compatible SVT installation, where the recipient needs the relevant account and permissions.

The export dialog and these mode labels were checked in the local application source. Export availability depends on release and account settings. A visitor link, a standalone viewer, an editable project package and an application backup are different deliverables.

Prepare the project

Finish the room route and verify source images, room names, initial views, return paths and information points. Check that media can be included and transferred under the relevant rights. Resolve temporary links and confirm which integrations the recipient expects to retain.

Follow the creation guide and hotspot guide for the core project. If the client only needs to display a tour you continue to host, the embed workflow may meet the brief without transferring a package.

Generate, inspect and deploy

  1. Open the tour-list export action. Confirm the correct project and that your account exposes the export option.
  2. Select the mode. Choose the viewer or importable output for the agreed destination.
  3. Wait for archive generation. Monitor the application's progress and download the completed file. Investigate reported failures before handing it over.
  4. Inspect the archive. Review its entry files and any supplied instructions. Keep folder relationships intact and identify external service dependencies.
  5. Test the destination. Deploy using the package's required HTTP(S) environment or import workflow. Do not assume opening files through file:// reproduces a web deployment.
  6. Review the result as the recipient. Test navigation, media, links, forms and requested device functions outside the original editor session.

Check what still depends on another service

A downloaded archive does not establish that every function works offline. External links, maps, communication, forms and other integrations may rely on a network, credentials or a running service. Document the functions actually tested in the exported build rather than promising parity with the editor.

Keep administrative access and credentials separate from the public viewer package. The hosting guide distinguishes serving tour files from operating the application. The VR guide covers the checks needed for requested immersive functions.

Provide a clear handover record

List the project version, included panoramas and media, selected export mode, deployment instructions, tested functions and unresolved dependencies. Agree who maintains hosting, changes contact details, pays recurring costs and updates or removes the tour.

If customers need editor accounts on your own platform, evaluate the SaaS workflow. That is a different arrangement from sending a standalone viewer. Review branding and licensing conditions before promising a particular presentation or distribution scope.

Keep a separate recovery plan

An export is not automatically a full backup of application files, configuration and database. Preserve recoverable backups and original media according to the operating model. Test restoration separately from viewer delivery.

Source context: official product information and visitor publishing options. Use the photographer workflow to include handover and operating work in the service quote.

Ready to build your own Virtual Tours?

Choose hosted Cloud or Self-Hosted on your server. Review features, prices and operating responsibilities before you start.