VR motion sickness: comfort design rules that work

The short answer

VR discomfort comes mainly from a conflict between what the eyes see and what the inner ear feels, made worse by low frame rate. The reliable fixes are: never move the camera unless the user moved, hold the headset's target frame rate at all times, offer teleport and snap turning, avoid acceleration, and let each user choose their comfort settings. Apps that follow these rules are comfortable for most people.

Why it happens

Your balance system expects sight and motion to agree. In VR, if the view slides forward while your body stands still, the senses disagree, and many people respond with nausea, sweating, headache or dizziness. The effect is called virtual reality sickness and is related to motion sickness. Sensitivity varies widely. Some people feel nothing, and others feel ill within a minute. Many build tolerance with exposure, but you cannot rely on that for new users.

Technical faults add to it: dropped frames, delay between head movement and the image, and tracking that jitters or drifts.

Rule one: the user owns the camera

The head controls the view. The app must never move, rotate, tilt or shake the camera on its own.

• No camera shake for explosions or impacts. Shake the world objects or use controller haptics instead.
• No cutscenes that fly the viewer around. Fade to a fixed viewpoint, or let the viewer stand in the scene.
• No forced head turns to direct attention. Use sound, light and motion in the scene.
• No head bob while walking.
• When you must reposition the user, fade to black, move, then fade in.

Rule two: hold the frame rate

Frame rate is a comfort feature in VR. Standalone headsets expect apps to render at their display rate, 72 frames per second or higher on Quest devices, and dropped frames are felt directly as judder. Budget performance from the first day: limit draw calls and polygon counts, use simple lighting, apply fixed foveated rendering where available and profile on the real device, not in the editor. We explain the human side in frame rate and player experience and the engineering side in mobile game performance optimization.

Locomotion options

Offer teleport by default and smooth movement as an option. Experienced players often insist on smooth movement, and newcomers need teleport.

Making smooth movement tolerable

• Constant speed. Acceleration and deceleration are what the inner ear notices. Start and stop instantly.
• Moderate speed. Walking pace is easier than running.
• Vignette. Narrow the field of view during movement. Peripheral motion is the strongest trigger.
• Movement follows the head or hand, chosen by the user.
• No strafing surprises. Sideways and backward movement are harder to tolerate than forward.
• No slopes that tilt the horizon. Keep the view level on ramps and stairs, and consider gliding over steps.

Turning

Artificial rotation is a stronger trigger than movement.

• Snap turning rotates in fixed steps, such as 30 or 45 degrees, instantly. It is the comfortable default.
• Smooth turning should be optional, with adjustable speed.
• Physical turning is best where cables and space allow, which standalone headsets make easy.

World design

• Keep a visible, stable horizon or ground reference.
• Avoid low ceilings and narrow corridors rushing past the edges of vision.
• Use fixed reference frames, such as a cockpit, helmet or desk, during vehicle movement.
• Avoid large moving surfaces that fill the view, such as rotating rooms.
• Keep moving platforms slow and predictable.
• Scale matters. A world that is slightly the wrong size feels off even when nothing moves.

Interface comfort

• Place panels about one to two metres away, slightly below eye level.
• Do not fix interface elements rigidly to the head. Let them follow gently or sit in the world.
• Avoid text that is too close, which strains the eyes.
• Keep interactions within easy reach to avoid neck and arm strain. See hand tracking vs controllers.

Mixed reality is easier

When users see their real room through passthrough, their senses have a stable reference, and discomfort drops sharply. If your app does not need a fully virtual world, consider mixed reality. See mixed reality app development.

Settings to offer

1. Teleport or smooth movement.
2. Snap or smooth turning, with angle and speed.
3. Vignette strength.
4. Seated or standing mode with height adjustment.
5. Dominant hand.
6. Reduced effects, such as flashes and particles.

Ask the most important ones during first launch, and keep the rest easy to find.

Session design

Keep early sessions short and build up. Give natural stopping points every ten to fifteen minutes. Tell users to stop when they first feel unwell, because pushing through makes it worse and creates a lasting association. This matters most in training and education, where users did not choose VR for fun. See VR in education and VR safety training for construction.

Testing for comfort

• Test with people who have never used VR. Developers adapt and stop noticing.
• Test complete sessions, not two-minute demos.
• Record when discomfort begins and what was happening.
• Test on the lowest-performance headset you support.
• Retest after every change to movement or cameras.

A quick checklist

Stores also label apps by comfort level, and accurate labelling reduces refunds. See the Meta Quest store submission guide.

Getting help

We design and test VR for comfort as standard, and can review an existing app and list fixes. Packages are on the VR offer page.

Sources: Wikipedia: Virtual reality sickness · Khronos Group: OpenXR · Meta Horizon developer documentation. Checked November 11, 2026.

Related: VR game development · VR and AR packages · Get a quote