Autorotate makes a 360° panorama turn slowly on its own, so a visitor sees the room before they touch anything. Done well, it signals "this is interactive" and shows off the space. Done badly, it makes people dizzy, fights their drag gestures and slows the page. The settings that work are a slow speed, a short start delay, an instant stop on touch, and a visible pause button. This guide covers each of them, plus the loading side of the story, because a tour that rotates beautifully but loads late never gets seen.
TL;DR
- Autorotate is best used as a gentle invitation: about 2 rotations per minute, starting after a couple of seconds of idle time, and stopping the moment the visitor interacts.
- Anything that moves by itself for more than five seconds should give the visitor a way to pause or stop it, which is a basic accessibility requirement.
- Rotate at the horizon, not at the ceiling or floor, and use it on the first scene rather than on every scene.
- Loading matters as much as motion: show a static preview first and load the heavy viewer only when the visitor asks for it (lazy loading).
- Test on a real phone, with reduced-motion settings on, before publishing.
Table of Contents
- What autorotate actually does in a virtual tour
- Why autorotate is worth using
- The settings that matter
- Accessibility: motion needs an off switch
- Loading comes first: lazy loading and page speed
- A practical setup checklist
- Where autorotate fits by use case
- Our perspective: control belongs to the person publishing the tour
- Build and publish your tours with Simple Virtual Tour
- Common mistakes to avoid
- FAQ
- Sources
What autorotate actually does in a virtual tour
A virtual tour viewer renders a spherical panorama, usually an equirectangular image, inside a window. The visitor drags to look around. Autorotate adds a camera that moves by itself, panning horizontally at a fixed speed until something stops it.
Most viewers treat it as a small set of parameters. The open-source Photo Sphere Viewer, for example, documents its autorotate plugin as a rotation that can start automatically on idle or through a button, with a configurable delay, speed and vertical angle. Its defaults (a 2000 ms delay and a speed of 2 rpm) are a sensible reference point even if you use a different viewer, because they show what a conservative starting configuration looks like.
There are three common behaviors:
- Start on load. The tour begins rotating as soon as it appears.
- Start on idle. The tour waits for the visitor to stop interacting, then resumes rotating after a short pause.
- Start on request. A button toggles rotation, and nothing moves until it is pressed.
Each has a place. The rest of this guide helps you pick.
Why autorotate is worth using
A still panorama looks like a flat photo until someone drags it. Many visitors never do, especially on a quick scroll through a listing. Slow movement tells the eye that the image is a space, and it reveals more of the room than a single framed view can.
The broader case for interactive tours is well documented in real estate. One compilation of real estate photography statistics reports that visitors view virtual tours about three times longer than static photo slideshows. Treat figures like this as indicative, since they come from secondary roundups, but the direction matches what agents and venue owners tell us: people spend longer in a space they can move through.
Autorotate is the cheapest nudge toward that behavior. It needs no extra content, only a setting.
The settings that matter
Speed: slower than you think
The most common mistake is rotating too fast. A full turn in ten seconds feels like a carousel. A full turn in 30 seconds (2 rpm) feels like someone slowly looking around. Start at 2 rpm and only go faster for small, simple spaces such as a closet or a single product display, where a quick sweep is enough.
Speed also depends on field of view. On a narrow phone screen, the same angular speed looks faster because less of the scene is visible. If your viewer lets you set different values for mobile, drop the speed a notch.
Start delay: a couple of seconds
If the tour starts rotating the instant it loads, the visitor often has no idea where they are before the view has already moved. A delay of about two seconds gives the eye time to settle on the first frame. For idle restarts, use a slightly longer pause, around three to five seconds, so that a visitor who stops dragging to read a hotspot label does not get yanked away mid-sentence.
Interaction: stop instantly, restart politely
The rule is simple: any touch, click, scroll gesture or keyboard input stops the rotation immediately, with no easing out. Nothing frustrates people more than a viewer that keeps drifting while they try to steer it.
Restarting is a judgment call. Restarting on idle suits kiosks, lobby screens and exhibition displays, where nobody is around to press a button. For a normal website visit, consider not restarting after the visitor has taken control. If they stopped it, they probably wanted it stopped.
Direction and pitch: keep to the horizon
Rotate at the pitch where the room is interesting, usually just around eye level. Rotating while looking at the ceiling or at the tripod patch on the floor shows the weakest part of the image. Some viewers also support "keypoints": a set of positions the camera visits in order, pausing at each. That is excellent for guided showcases, such as pointing to the kitchen island, then the window wall, then the staircase.
Pick one direction and keep it consistent across scenes, so the tour feels intentional.
Which scenes get it
Use autorotate on the opening scene and on scenes where the visitor arrives without a clear direction, such as a lobby or a large open-plan room. Skip it on scenes where visitors have just clicked a hotspot to look at something specific. Moving the camera away from what they wanted to see feels like the tour is ignoring them.
| Setting | Recommended starting point | When to change it |
|---|---|---|
| Speed | About 2 rpm | Slightly faster for tiny spaces; slower on mobile |
| Start delay | About 2 seconds | Longer if the first scene has text overlays |
| Idle restart | Off on websites, on for kiosks | On for lobby screens and trade-show displays |
| Pitch | Horizon or slightly above | Aim at a feature, such as a view or a mural |
| Scenes | First scene and open spaces | Off after a hotspot click |
| Pause control | Always visible | Never remove it |
Accessibility: motion needs an off switch
Automatic movement is not just a style choice. It can make some visitors feel unwell, and it makes reading or clicking harder for others. The Web Content Accessibility Guidelines address this directly in criterion 2.2.2: moving content that starts automatically and lasts more than five seconds must offer a way to pause, stop or hide it. A rotating panorama falls squarely into that category.
In practice that means:
- Show a clearly labeled play/pause button on the viewer, not hidden in a menu.
- Make it reachable by keyboard and readable by screen readers.
- Respect the operating system's reduced-motion preference where your viewer or page allows it, by leaving autorotate off for those visitors.
- Never let autorotate be the only way to discover that a tour is interactive. A visible "drag to look around" cue helps everybody.
These choices belong to a wider usability picture, and the principles in this guide to usability and motion preferences apply neatly to tours: avoid disorienting automatic movement, give people control, and let the experience earn their attention.
If you publish tours for public venues, schools, museums or government-related organizations, accessibility expectations are often stricter, so check what applies to your client before you decide to default autorotate on.
Loading comes first: lazy loading and page speed
Autorotate only helps if the tour appears quickly. Readers who search for autorotate often also ask about lazy loading, and the two are linked: both are about when the viewer is allowed to do work.
The issue is how tours are embedded. As one practitioner write-up explains, a raw iframe initializes heavy viewer dependencies as soon as the page loads, whether or not the visitor ever touches the tour. The same source notes that adding autoplay preloading, gyroscope tracking for mobile and fallback image layers increases the weight further. A rotating tour that starts on load is the heaviest possible version, because it has to download and render the panorama immediately.
The usual remedy is a lazy-load facade:
- Show a static, high-quality thumbnail of the tour's best view, with a play button on top.
- When the visitor clicks, insert the real viewer into the page.
- Start autorotate after the viewer has loaded and the first frame is visible.
This defers the cost to people who actually want the tour. It also gives you a natural trigger for autorotate: the visitor has just asked for the experience, so motion is expected rather than imposed. Another guide for property marketers describes the same facade approach for slowing-page problems with embedded tours.
Some further steps that make a measurable difference:
- Compress panoramas sensibly and use modern formats such as WebP where your viewer supports them.
- Use tiled or multi-resolution panoramas for large images, so the viewer loads a low-resolution version first and sharpens as needed.
- Load only the first scene up front. Fetch neighboring scenes when the visitor approaches a hotspot.
- Avoid placing several tours on the same page. Use one facade per tour, or link to a dedicated tour page.
We go deeper on this in our article on virtual tour performance optimization.
A practical setup checklist
Run through this before you publish a tour:
- Pick the opening scene. Choose the view that sells the space, and rotate from its best angle.
- Set speed and delay. Start at 2 rpm with a two-second delay.
- Set the pitch. Aim at the horizon or the main feature, not the ceiling.
- Add a visible pause button. Confirm it works by keyboard.
- Make the first interaction stop rotation. Test drag, tap, pinch and scroll.
- Decide on idle restart. Off for websites, on for kiosks.
- Embed with a facade. Check that nothing loads until the click.
- Test on a mid-range phone on a cellular connection. If the first frame takes more than a few seconds, reduce image size.
- Test with reduced motion enabled. The tour should still make sense without any movement.
Where autorotate fits by use case
Real estate. Autorotate on the first scene of a listing tour, then manual navigation. Buyers are comparing many listings quickly, so a fast first impression matters. Our guide to virtual tour software for real estate covers the features agents should look for beyond rotation.
Hotels and restaurants. A slow turn in the lobby or dining room communicates atmosphere well. Keep it off in room-detail scenes where guests are checking bed layouts and views.
Museums and galleries. Use keypoints to lead visitors to key works, with a pause at each. Keep idle restart on for in-gallery screens.
Education. Keep rotation optional. Learners often need to study details, and constant movement works against that.
Car dealerships and retail. A gentle rotation inside a vehicle or showroom works, but stop it as soon as a shopper opens a product hotspot.
Our perspective: control belongs to the person publishing the tour
At Simple Virtual Tour, we think autorotate is a good example of a small feature that reveals a bigger question: who controls the experience? A tour published for a client should behave the way the client's audience needs, not the way a template decided. That is why we build around customization, an intuitive backend that does not require technical skills, and the choice between cloud hosting and a self-hosted installation.
Performance is part of that control. When you self-host, you decide where your panoramas live, how they are served and how your pages embed them. When you use the cloud version, you get a ready-to-publish setup without managing servers. Either way, we encourage the same habits we describe above: gentle motion, visible controls, lightweight first loads.
Our advice to anyone building their first tours is to resist the urge to make everything move. A tour is a place the visitor walks through, and the best autorotate is the one they barely notice, because it simply helped them understand the space before they took the controls.
— Andrea
Build and publish your tours with Simple Virtual Tour
If you want to try these settings on your own panoramas, Simple Virtual Tour lets you create unlimited interactive tours, with 360° photo and video support, custom branding and statistics, and a choice of deployment. The cloud plans are published as Free Forever, XS (Starter) at 2.99 € per month, S (Creator) at 5.99 € per month, M (Professional) at 9.99 € per month, L (Business) at 19.99 € per month and XL (Enterprise) at 49.99 € per month. If you prefer to own the software, the CORE self-hosted product is a one-off 79 $, with optional plugins such as the GSV plugin for Google Street View publishing at 59 $ and the A.I. Tools plugin at 39 $.
You can compare the plans and start with the free option, or see how the pricing models differ in our guide to virtual tour software pricing.
Common mistakes to avoid
- Rotating on every scene. It turns the tour into a slideshow and removes the sense of exploration.
- Hiding the pause control. This creates an accessibility problem and annoys everyone else.
- Fast rotation on mobile. The narrow field of view exaggerates speed.
- Loading the tour with the page. Visitors who never open it still pay the loading cost.
- Skipping tests on real devices. Desktop previews hide the stutter that mid-range phones show.
- Using autorotate to hide weak images. If stitching errors or a poor nadir are visible, motion draws attention to them. Fix the source images instead.
FAQ
What is the best autorotate speed for a virtual tour?
Start around 2 rotations per minute, which is a full turn in about 30 seconds. That is the default used by Photo Sphere Viewer's autorotate plugin. Go slower on phones and in large rooms, and only speed up for very small spaces.
Should autorotate start automatically?
Usually after a short delay, not instantly. Waiting about two seconds lets the visitor see the first frame before it moves. If the tour is embedded behind a click-to-load preview, starting rotation once the viewer opens feels natural, since the visitor has just asked for it.
Is autorotate an accessibility problem?
It can be if there is no way to stop it. WCAG success criterion 2.2.2 says that automatic moving content lasting over five seconds needs a pause, stop or hide control. Add a visible button, support keyboard use, and leave rotation off for visitors who have reduced motion enabled.
What does lazy loading mean for virtual tours?
It means the heavy viewer and panoramas load only when needed. A common method is to show a preview image with a play button and insert the real viewer only after a click. This keeps pages fast for visitors who never open the tour.
Sources
- AutorotatePlugin, Photo Sphere Viewer documentation
- 2.2.2 Pause, Stop, Hide (Level A), WCAG
- How to Embed 360 Virtual Tour Renders Without Killing Page Speed, 360 Archviz
- Getting More Out of a Finished Matterport Tour, Adostrophe
- 90+ Real Estate Photography Statistics, ZipDo