An offline virtual tour is a 360° tour that opens and runs without a live internet connection. It does this because every panorama, hotspot, script and media file is already on the device, or on a local machine the device can reach. You have three practical ways to get there: package the tour as static files on a drive, cache it in the browser with a service worker, or host it yourself on a local server. This guide covers all three, along with what breaks and how to test it.
TL;DR
- An offline tour needs all of its files on the device or local network before the connection drops. Nothing can be fetched on demand.
- Static hosting (plain HTML, JavaScript, images) is the simplest base. You can then serve it online, from a local server, or from a drive.
- Do not double-click an HTML file and expect it to work. Browsers often block local files from loading other local files, so use a small local server for testing and kiosks.
- Offline tours trade away live sessions, analytics and e-commerce. Decide which matters more for the venue or client.
- Self-hosting gives you the control that offline delivery depends on. We built Simple Virtual Tour with that deployment model in mind.
Table of Contents
- What an offline virtual tour actually is
- When you need one
- How static hosting fits in
- Three ways to make a tour work offline
- Why a tour works online but fails when opened locally
- How to build an offline-ready tour: a step-by-step workflow
- Devices and browsers to test
- Limits you should plan around
- Our perspective: own the files, own the experience
- Choosing Simple Virtual Tour for offline-minded projects
- FAQ
- Sources
What an offline virtual tour actually is
A normal virtual tour is a web page. Your browser downloads the viewer code, then pulls panoramas as you move from room to room. Lose the connection and the next room never loads.
An offline tour removes that dependency. One description of offline tour software puts it simply: users create and experience 3D tours without an internet connection. In practice, "offline" covers three different situations:
- Cached offline. The visitor opens the tour once with a connection, the browser stores everything, and later visits work without one.
- Local network. The tour sits on a laptop, mini PC or router-attached storage at the venue. Devices connect to it over Wi-Fi, with no internet involved.
- Standalone files. The tour is copied to a USB drive or tablet and opened from there.
These are not interchangeable. Which one fits depends on where the tour will be shown and who controls the device.
When you need one
Most people searching for this have a specific problem. The common ones:
- Trade shows and conferences. Convention center Wi-Fi is famously unreliable, and a stalled tour on a booth screen looks worse than no tour.
- Museum and gallery kiosks. A touchscreen in a gallery should not depend on the building's network.
- Real estate open houses and sales offices. Rural properties, new developments and basements have weak signal, and agents still want to show a tour on a tablet.
- Classrooms and training sites. Schools and field sites often restrict or lack connectivity.
- Data-sensitive projects. Some clients, such as architects with unreleased designs, do not want assets on a public cloud. The Modelo team argues that keeping assets local to the device offers higher security than cloud-based solutions. That is the vendor's view, so weigh it against your own security requirements.
A fifth reason is speed. Serving content from a local cache means fewer round trips to a server for each interaction, which is why even online visitors often get a snappier tour when assets are cached.
How static hosting fits in
People who search for static hosting for virtual tours are usually halfway to an offline setup without realizing it. A static tour is made of files that need no server-side processing: HTML, CSS, JavaScript, 360° images, audio and video. Because the files are self-contained, you can put them almost anywhere.
- Static web hosting. AWS documents that Amazon S3 can host a static website. The same page recommends AWS Amplify Hosting when you want a managed CDN and a public HTTPS URL for static content.
- Your own web server. Any ordinary web server serving a folder works.
- A local machine. The same folder served from a laptop on the venue's network is an offline tour.
- Removable storage. The same folder on a drive, served by a tiny local server or opened in a kiosk browser.
If you want the full picture of servers, storage and CDNs for tours that are online, we cover it in our guide to hosting virtual tours.
What a static tour folder contains
Whatever tool created the tour, an offline-ready folder usually includes:
- the viewer page (an index HTML file) and its JavaScript and CSS;
- a configuration file describing scenes, hotspots, initial view angles and links between rooms;
- the panorama images, ideally equirectangular files sized for the screen you are targeting;
- any audio, video, floor plan images and logos;
- fonts and icons, which people forget, because they are often loaded from a third-party CDN.
That last item causes more offline failures than any other. If a single stylesheet or font points to an outside address, the tour may load with missing icons or a blank interface when the network is gone.
Three ways to make a tour work offline
Option 1: Cache it in the browser (PWA approach)
A Progressive Web App uses a service worker, a script that sits between the page and the network. MDN's PWA caching guide describes two main benefits of local caching: offline operation and responsiveness. The service worker precaches resources during its install step, then serves them from cache when requested.
For a tour, that means listing every panorama, script and media file in the precache list. Another documented example of this pattern is pre-caching every slide, image and audio file when content is opened with a connection, after which it runs offline.
The catch is that the visitor must open the tour online first. This suits staff tablets, which you can load at the office, and returning customers. It does not suit a stranger who clicks a link on a plane. Large tours also hit browser storage limits, so test with your real file sizes. If you want to understand why this kind of delivery matters beyond tours, this interactive content SEO guide touches on PWA technology for reliable offline delivery.
Option 2: Serve it from a local server
This is the most dependable approach for kiosks and events. You copy the static tour folder to a small computer, run a lightweight web server, and point the display's browser at the local address. No internet is needed, and no visitor has to preload anything.
It also avoids the most common trap, covered next.
Option 3: Open files directly from a drive
This is the option people try first and the one that fails most often. It works only for tours built as a single self-contained file, or with viewers designed to run from the file system. For multi-file tours, it usually breaks.
Why a tour works online but fails when opened locally
If your tour loads fine on a website but shows a blank screen from a USB stick, the cause is usually browser security. MDN explains that many browsers treat local files as opaque origins by default, so a page cannot fetch other local files the way it would from a server. The recommended fix for local testing is to set up a local server instead of opening files directly.
A quick troubleshooting list:
- Blank screen or console error mentioning CORS. Serve the folder over
http://localhostinstead offile://. - Panoramas load but the interface looks broken. Check for fonts, icons or libraries loaded from outside URLs, and copy them into the folder.
- Map or video elements are empty. Embedded maps, YouTube or Vimeo players and any external widget cannot work offline. Replace them with local files or remove them.
- First room loads, the rest do not. Your precache list or copied folder is missing files. Compare the scene list in the configuration with the files on disk.
- Works on your laptop, not on the tablet. Check the tablet's browser version and storage space.
- Tour works once, then fails after a restart. The cache was cleared or the service worker was not registered. Reload online and confirm the worker is active.
How to build an offline-ready tour: a step-by-step workflow
This is the workflow we recommend, whichever tool you use.
- Decide the delivery mode first. Cached PWA, local server, or drive. It changes how you build.
- Capture and stitch your panoramas. Export equirectangular images. For a kiosk, a 4K-wide panorama is often plenty. Larger files increase load time and storage with little visible gain on small screens.
- Build the tour with local assets only. Upload your own audio, video and logos instead of linking to hosted ones.
- Use hotspots that work without a network. Scene-to-scene links, image and text pop-ups, and local video are fine. Links that open external web pages are not. See our guide to virtual tour hotspots for the types and when to use each.
- Remove external dependencies. Search your tour's files for
http://andhttps://addresses and judge each one. - Package or deploy. Copy the folder to the target machine, or publish it and register the service worker.
- Test with the network truly off. Turn off Wi-Fi, use airplane mode, or unplug the cable. Do not rely on developer tools alone.
- Test on the real hardware. Same browser, same screen, same touch input.
- Keep a fallback. A second copy on a drive, or a short video walkthrough, saves an event when something fails.
Devices and browsers to test
There is no universal compatibility list, because it depends on your viewer and delivery mode, so test rather than assume. Prioritize these:
- Desktop Chrome, Edge, Firefox and Safari. Local file rules differ between them, so a tour that opens from a drive in one browser may fail in another.
- iPhone and iPad (Safari). Storage limits and memory use matter for large panoramas. Test the biggest scene.
- Android Chrome. Check how it behaves after the device sleeps and wakes.
- Kiosk setups. Test the exact browser mode you will use, including full screen and touch gestures.
- VR headsets. If you plan to support them, load and test the tour in the headset's own browser.
Check after every browser update, since caching and security behavior changes over time.
Limits you should plan around
Offline delivery is not free. Here is what you give up compared with a hosted, online tour:
| Capability | Online tour | Offline tour |
|---|---|---|
| Live guided sessions | Possible | Not possible without a network |
| Visitor statistics | Collected centrally | Limited or none until synced |
| E-commerce and booking links | Work normally | Need a connection |
| Embedded maps and external video | Work | Must be replaced with local files |
| Content updates | Instant for everyone | Must be re-copied or re-cached |
| Sharing a link | One URL | Requires physical or first-visit delivery |
| Data control | Depends on host | Strong, since files stay local |
The update problem is the one that catches teams out. If a price, a floor plan or a furnishing changes, every offline copy is out of date until you replace it. Keep a version number in the folder name and a short checklist of which devices hold which version.
A good compromise for many businesses is a hybrid: publish the tour online for the public, and keep an offline copy for events and kiosks.
Our perspective: own the files, own the experience
We built Simple Virtual Tour around the idea that you should decide where your tours live. That is why it comes in two forms: a cloud-hosted subscription, and a self-hosted version where you own the full source code and carry no ongoing software cost. Self-hosting is not only a pricing choice. It is what makes offline and local delivery realistic, because you control the server, the folder structure and the network the tour runs on.
In our experience, most people who ask about offline tours do not need a different kind of tour. They need a reliable way to show the same tour in a room with bad Wi-Fi, or a way to keep sensitive assets off a third-party platform. Start with a well-built online tour, keep external dependencies to a minimum, and then decide whether the venue calls for a cached, local-server or drive-based copy.
If performance is your concern even online, our guide to virtual tour performance covers image sizing and loading habits that also make offline packages lighter.
— Andrea
Choosing Simple Virtual Tour for offline-minded projects
If you want to control where your tours run, look at the self-hosted deployment option. The self-hosted CORE software is a one-off $79 purchase, with optional plugins: PLUGIN SAAS at $269 one-off, GSV PLUGIN at $59 one-off, and A.I. TOOLS PLUGIN at $39 one-off. If you would rather start in the cloud, there is a Free Forever plan, and paid plans run from €2.99 per month (XS) through €5.99 (S), €9.99 (M), €19.99 (L) and €49.99 (XL). You can compare them all on our plans page.
FAQ
Can a virtual tour work without internet?
Yes, if every file it needs is already on the device or on a local network. That can be a browser cache filled during a first online visit, a local server at the venue, or files copied to a drive. Anything that calls an outside service, such as a map or hosted video, will not load.
Can I host a virtual tour as static files?
Yes. A tour made of HTML, JavaScript, configuration and image files can be placed on any static host, including Amazon S3 static website hosting. The same files can also be served from a local machine, which is the basis of most offline setups.
Why does my tour show a blank page when I open it from a USB drive?
Browsers often block pages from reading other local files, so a multi-file tour fails when opened directly. Serving the folder through a local server fixes it in most cases. MDN recommends exactly that for local testing.
What features do I lose in an offline tour?
Anything that needs a live connection: live sessions, central analytics, e-commerce links, embedded maps and external video. Content updates also become manual, since each copy must be replaced. Many teams keep an online version for the public and an offline copy for events.
Sources
- Revolutionizing Your Virtual Experience: Offline Virtual Tour Software (Modelo)
- Offline Mode (Immersia)
- Hosting a static website using Amazon S3 (AWS documentation)
- Reason: CORS request not HTTP (MDN)
- Caching, Progressive web apps (MDN)