For most of the last two years, the honest answer to "where do I watch high-end VR travel?" was awkward: on an Apple Vision Pro. That is where our app lives natively, that is where the library looked its absolute best, and that is where it was named Apple's App of the Year 2025 on visionOS. It is also a headset most people do not own.
That gap always bothered us. We film real places in 16K VR180 so that somebody can stand in them, and telling the majority of headset owners that they were on the wrong hardware was a strange way to run a travel library. So we moved the library into the browser.
What changed
Every experience in the library now streams through the browser that is already installed in your headset. Meta Quest 2, Quest 3, Quest 3S and Quest Pro. PICO 4 and PICO 4 Ultra. Samsung Galaxy XR. If it has a modern browser and can render an immersive session, it can play our library.
There is no store listing to find, nothing to sideload, and no separate account system to learn. You type explorepov.com, press play, then press Enter VR. The trailer of every experience plays without an account at all, which means you can test the whole idea on your own headset before deciding whether you like it.
Open your headset browser, go to explorepov.com/vr, press play, then Enter VR. Step-by-step instructions for Quest specifically are in how to watch VR travel on Meta Quest.
Why the browser, and not four separate apps
We could have built a native app for each platform. We chose not to, and the reasoning is worth stating plainly because it affects what you get.
Native apps are excellent at using a specific headset perfectly and terrible at keeping four versions of anything in sync. Every time we add a place to the library, an app-per-platform approach means four submissions, four review queues and four sets of stale installs in the wild. The browser gives us one library that updates for everyone at once, and it means a link to a specific place actually works: you can send somebody a valley in Switzerland and they can open it, in their headset, without installing a thing.
The trade is real and we will not pretend otherwise. A native app can squeeze out slightly better decode performance and slightly faster start-up than a browser can. What the browser gives back is reach, sharing and immediacy, and for a travel library those matter more.
What Quest and PICO owners actually get
The same library, the same masters and the same capture. We do not keep a better version somewhere else. Every experience is filmed in 16K VR180 with real stereo depth, then encoded into a quality ladder so your headset and your connection can take the highest tier they can sustain.
On a Quest 3 or a PICO 4 Ultra on decent Wi-Fi, that is a genuinely striking picture. On older hardware or a weaker connection, the ladder steps down gracefully rather than stalling. Either way, nothing about the browser path is a cut-down edition of the library.
Headset-specific notes live on the device pages: Meta Quest, PICO, Samsung Galaxy XR, and Apple Vision Pro for the native app.
What we did not change
It is worth being clear about the things that stayed exactly as they were, because "now it works everywhere" is the kind of sentence that usually hides a compromise.
The capture did not change. Every experience is still filmed the way it always was, in VR180 with two lenses at human eye spacing, at a resolution well beyond what any headset can currently display. Nothing was reshot at a lower spec to make browser delivery easier, and nothing was cropped. The reasoning behind those choices is set out in how we film in 16K VR180.
The audio did not change either. We record the sound of the place we are standing in rather than laying music over it, and that is a large part of why a quiet scene feels quiet rather than merely looking quiet. Headset speakers handle it fine, though it is noticeably better with the volume higher than you would expect to need.
And the library did not fork. There is one library, one set of masters and one place where new experiences appear. Everyone gets the same additions on the same day, whichever headset is on their head, which was one of the main reasons for going down the browser route in the first place.
What it costs to try
The trailer of every experience plays with no account and no payment details, in your own headset, which we think is the only fair way to sell something you have to feel to understand. Creating an account unlocks more of the library, and a subscription unlocks all of it. Current pricing lives on the pricing page, and the FAQ covers the usual questions about accounts and devices.
Does the Vision Pro version still matter?
Yes, and we still develop it. The native visionOS app remains the most polished way to watch, and the recognition it received was for that experience specifically. What has changed is that it is no longer the only door. If you own a Vision Pro, use the app. If you own anything else, you now have a route that did not exist before.
Where to begin
Start with somewhere calm rather than somewhere spectacular. VR180 depth takes a few seconds to land, and quiet scenes let that happen. Our relaxing collection is the easiest entry point, and our picks are collected in the best relaxing VR experiences.
If you would rather chase a specific place, the destinations index covers everywhere we have filmed, and collections group the library by mood and landscape instead. For the technical background on why we shoot the way we do, there is how we film in 16K VR180 and the format explainer at what is VR180.
And if you are entirely new to the category, start at the complete guide to VR travel, which covers formats, hardware and what quality really depends on, or read watching VR in a browser for the mechanics.