VRHow / XR Technology / Mixed-reality headset specs
Mixed-reality headset specs explained
Last checked October 11, 2026. This is a technical explainer based on manufacturer documentation and the OpenXR specification, not a hands-on comparison or product ranking. Manufacturer figures describe stated specifications and test conditions.
Start by asking how the real world reaches your eyes
Many mixed-reality headsets use video passthrough: cameras capture the surroundings, software processes the images, and displays show them alongside virtual content. That is different from optical see-through glasses, which let you look directly through a transparent optical path while adding light from a display. In a camera-mediated view, exposure, camera placement, image processing, latency and headset fit can all affect what you perceive.
Specifications do not always measure the same thing. For example, a maker may report pixels per degree for a camera view, while another reports the number of pixels in a display panel. Those values cannot be compared as if they were one image-quality score. If reading real labels or moving around is important, test those tasks in your own lighting rather than inferring quality from megapixels or marketing language. For a closer look at the camera view, see how color passthrough works.
Separate tracking, room mapping and anchoring
Tracking estimates the headset’s position and orientation. Room mapping estimates surfaces or geometry around you. Anchoring keeps virtual content associated with a position or surface as you move. They are related capabilities, but one does not automatically guarantee the others. OpenXR represents poses relative to a reference space; it does not promise a universal map of every room. A platform’s scene API may separately expose geometry and semantic labels, subject to its own permissions and implementation.
| Capability | What to check in documentation | What it does not prove |
|---|---|---|
| 3DoF orientation tracking | Whether the view follows head rotation. | That the headset knows where you are in the room. |
| 6DoF position and orientation | Whether translation as well as rotation is tracked, and in which supported space. | Perfect accuracy, persistent room memory or reliable occlusion. |
| Room or scene understanding | Which surfaces, meshes, planes or semantic labels an app can request and how consent is handled. | That every object or boundary will be recognized correctly. |
| Eye, hand or controller input | Which input methods are supported by the device and the specific app. | That every app supports the same interactions or that tracking works equally well for every user. |
For example, vendor documentation may list a depth sensor, room mapping, eye cameras or hand input. Treat these as evidence that a feature is part of the hardware or software stack—not as an independent measurement of precision, comfort or reliability. Read our tracking explainer for coordinate spaces and inside-out versus outside-in tracking for sensor-layout trade-offs.
Read display numbers in context
Per-eye panel resolution, field of view, refresh rate and lens type answer different questions. Panel resolution is not the same as the pixels an app actually renders, nor does it say how evenly sharp the image appears across the lens. Eye position, interpupillary distance, eye relief, lens sweet spot, distortion correction and app rendering all affect perceived clarity. A quoted field of view is also sensitive to fit and measurement method; compare its definition, not just the number.
Refresh rate is only one part of motion quality: stable frame delivery matters, and a higher target leaves less time for each rendered frame. Likewise, an OLED or Micro-OLED panel description identifies display technology, not measured contrast, brightness in your use, or text legibility through a complete headset. For deeper context, see display resolution, refresh rates, field of view and LCD, OLED and Micro-OLED.
Input and software determine what the headset can do
Head, hand, eye, voice and controller inputs can make different tasks easier, but hardware support is not the same as app support. Before judging a headset for gaming, remote work or creation, identify the exact applications you intend to use and check their platform, region, controller and tracking requirements. A general statement that a platform supports a type of app or input does not establish that every app has a polished spatial interface.
Also check what a feature requires: a particular device model, an accessory, a connected phone or computer, an account, internet access, or permission to use room or eye data. This is especially important for multi-window work and shared spaces. See mixed reality for productivity for examples of documented workflows and their limits.
Fit, power and safe use are part of the specification
Compare the complete wearing system, not the visor alone: headset weight and balance, face interface, adjustable fit, glasses clearance, prescription inserts, cable routing and battery placement. Battery duration is a manufacturer estimate under stated test conditions; the runtime for a game, video call or bright passthrough scene can differ. Consider whether you can tolerate the device for the length of the session you have in mind.
Use a clear play area, keep away from stairs and traffic, and stop if you feel discomfort. Samsung’s Galaxy XR setup guidance recommends taking a break at least every 30 minutes and longer or more frequent breaks when discomfort occurs; that is manufacturer safety guidance, not a universal clinical threshold. Follow the instructions for the exact device you use.
A practical comparison without a spec-sheet winner
- Name the task. Decide whether you need room-aware interaction, readable physical-world text, floating windows, immersive media or a specific app.
- Verify the full software path. Confirm the exact model, app listing, account or network dependency, input device, region and any accessory requirement.
- Check like with like. Separate camera-view measures from panel measures; distinguish per-eye resolution from rendered content; ask how field of view and battery life were measured.
- Try the real conditions. Where a demo or return policy permits, test small text, motion, hand interaction, room boundaries and your usual lighting. Check fit with your own glasses or prescription needs.
- Make uncertainty explicit. Treat untested comfort, image quality, latency and reliability as unknowns. Manufacturer specifications are useful inputs, not substitutes for independent testing.
Bottom line: there is no useful universal winner implied by the spec sheet alone. Compare the capabilities against your task, test the parts that depend on perception and fit, and verify software and regional support before choosing a device. For an explanation of the term itself, continue to what mixed reality means.
Sources and evidence scope
- Khronos OpenXR 1.1 Specification — poses, reference spaces and tracking capability.
- Meta Scene overview — room geometry, semantic labels, anchors and permissions.
- Meta passthrough documentation — passthrough setup and implementation details.
- Meta Quest 3S official specifications — example of manufacturer descriptions for passthrough, tracking, display and battery.
- Samsung Galaxy XR official product page — example of manufacturer descriptions for displays, sensors, weight and battery.
- Apple Vision Pro technical specifications — example of manufacturer descriptions for display, sensors, input, fit and battery test conditions.
- Samsung Galaxy XR setup and break guidance — device-specific safety and fit guidance.
Product specifications and software support change over time. This page does not claim independent measurement of passthrough quality, display clarity, comfort, tracking accuracy, latency or battery life.