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

Hosting Virtual Tours Explained: Self-Hosted, Cloud, and Static Export

October 24, 2026 • By SVT Team
Hosting Virtual Tours Explained: Self-Hosted, Cloud, and Static Export

Review date: 12 November 2026. This guide is published by the SVT developer and was checked against the cited documentation and relevant application source.

Hosting a virtual tour usually comes down to two different models: a static export you place on your own web space, or a managed cloud service where the provider hosts the editor account and tour delivery. In SVT’s published documentation, Cloud is provider hosted and Self-Hosted runs on your own PHP/MySQL server; both can deliver tours, but they are not the same operationally. Method note: this article is based on documentation review and source inspection, not hands-on testing.

If you are deciding between the two, start with how you want to handle editing, storage, traffic, backups, and domain control. For a broader framing, see Self-hosted vs cloud and How to host your own virtual tours.

What “hosting” means for a virtual tour

A virtual tour is not just one image file. It typically includes panorama images, viewer assets, room-to-room connections, POIs, optional maps, and the HTML/CSS/JavaScript needed to display the experience. In SVT, the Publish → Tour area provides an existing permanent visitor link and embed output; the viewer link is separate from the editor login.

That matters because “hosting” can mean two different things:

  • Static hosting: you upload the exported tour files to web hosting and serve them like other website assets.
  • Managed cloud hosting: the tour platform stores and serves the tour from its own infrastructure while you manage the tour through your account.

Static hosting is mostly about reliable file delivery and website configuration. Managed cloud hosting also includes editor access, plan limits, and account management. For the feature-level difference between tour structure and delivery, see How to create a virtual tour and How to export a virtual tour.

Self-hosted: what you operate yourself

In the Self-Hosted model, you run the software on a server you control. The research notes that this requires an operated PHP/MySQL environment. That means your responsibilities are broader than uploading files once and forgetting them. You need to handle the server, domain, HTTPS, storage, backups, and recovery planning.

For tour files, that usually means thinking in terms of:

  • Storage: enough space for panorama files, preview assets, and generated tour output.
  • Traffic: enough bandwidth for visitors loading panoramas and related assets.
  • Backups: regular backups of the tour files and the data that defines the tour structure.
  • Recovery: a documented way to restore the site if the server or deployment fails.

The exact size of those requirements depends on the number of tours, image dimensions, visitor volume, and whether you use extras such as floor plans or forms. SVT does not publish a universal resource formula, so capacity planning should be based on representative content rather than a single headline number.

If you are evaluating the hosting side specifically, pair this article with Virtual tour file formats and Best self-hosted virtual tour software.

Cloud hosting: what the provider handles

SVT’s Cloud model is provider hosted and includes the subscriber’s own editor account. That is important: a cloud subscription gives you editing access and plan-based resources, but it is not a substitute for operating your own customer SaaS platform. The platform manages the hosting layer for the service; you manage the content and settings inside your account.

Cloud plans can differ by tour count, storage, monthly views, watermarking, and billing cycle. Because those details are plan-specific and can change over time, the safest workflow is to confirm the current plan details before committing. If you need pricing context, use Virtual tour software pricing rather than assuming every deployment includes the same limits.

For a managed-hosting workflow, the main practical advantages are reduced server administration and a single editor environment. The tradeoff is that platform rules, permissions, and release options may limit which features are available on a given plan.

What to host yourself, and what not to over-engineer

For most tour projects, the important question is not “Can I host everything myself?” but “Which parts actually need my control?” A useful split is:

  • Own your source media: keep original panoramas and working files in your archive.
  • Control your delivery: decide whether the tour is served from your own web host or through a managed platform.
  • Protect your access: use the platform’s visibility or protection settings where appropriate.
  • Plan recovery: know how to restore the tour if a file or server is lost.

SVT’s published material also distinguishes between visitor access and editor access. A tour link can exist independently of the editor login, and access controls affect who can view the tour without implying that the tour is unpublished. For access planning, see Password-protected virtual tours and Virtual tour lead generation.

Domain, HTTPS, and embeds

When a tour is embedded on a website, the parent page and the tour frame must both allow embedding. The viewer link and the editor login are separate concerns, so do not treat a published tour as the same thing as a logged-in editing session. In practice, you should verify three things together: the domain configuration, the HTTPS setup, and the page embedding policy.

That is especially relevant if you are integrating the tour into a property page, hotel site, or portfolio. For those use cases, review How to embed a virtual tour on a website and White-label virtual tour software.

Backups and recovery: practical planning

Backups are not just a server task; they are part of tour ownership. If you run self-hosted, keep copies of the panorama files, tour configuration, and any additional assets you have added. If you use cloud hosting, keep your original media and a record of the tour structure so you can rebuild or migrate if needed.

A sensible recovery plan includes:

  • where the original panoramas are stored;
  • who can access the host account or editor account;
  • how often backups are made;
  • how you would verify that a restored tour still loads correctly.

That last step matters because a backup is only useful if it can be restored into a working tour. The documentation reviewed here does not claim automatic recovery guarantees, so plan for restoration as an operational task rather than an assumed feature.

Features that affect hosting choices

Some tour features change the hosting conversation because they add assets or account dependencies. Floor plans and maps add image assets and room-point assignments; forms add submission handling and notification requirements; live-guided tours and lead-capture flows may require additional configuration. If you use AI-assisted editing tools, confirm whether the tool is available on your chosen deployment before relying on it in production.

Useful feature references include Virtual tour with floor plan, Virtual tour lead generation, and Live guided virtual tours.

How to choose

If you want the least server work, managed cloud hosting is the simpler operational model. If you want direct control over the server, domain, and deployment, self-hosting is the more flexible model, but it also means taking responsibility for the environment that serves the tour.

A practical rule is to choose based on ownership and operations, not just feature lists:

  • Choose cloud if you want a provider-hosted editor account and less server administration.
  • Choose self-hosted if you need to run the software on infrastructure you control.
  • Choose static export if your goal is simply to place the tour on your own website and manage the hosting stack yourself.

For the underlying creation flow, see How to create a virtual tour. For deployment comparisons, Self-hosted vs cloud is the most direct companion page.

Primary documentation reviewed for this article includes the SVT guides on creation, rooms, markers, floor plans, publish settings, and forms, plus the product listing and related platform references. The article does not claim hands-on testing, performance benchmarks, or unpublished behavior.

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.