The module calculates intersections between rays and points, planes or meshes in the real environment. See precision, input, privacy, and fallback.
Direct answer
The WebXR Hit Test Module defines how an application requests intersections between a ray and the actual geometry understood by the device, returning poses for points, planes, or meshes. The most recent public version noted by the W3C is a Working Draft dated December 11, 2025. The API helps position AR content on the web, but support, surface stability, and accuracy vary; The product must confirm the location before creating an anchor or taking an action.
Lightning turns intention into pose
The app projects a direction from the camera or input and receives ordered intersections. The resulting pose allows to show a lattice coherent with the surface.
Flat, stitch and mesh do not have the same quality
Each type reflects a different understanding of the environment. A large floor may be stable, while a small detail changes as the mapping matures.
Preview must come before confirmation
Move an indicator while the results update and create the object only after conscious action. Display scale, orientation, and footprint to reduce mispositioning.
Excessive requests can be limited
The standard allows restrictions against abuse. Keep few sources active, cancel them when they are not needed, and only request geometry that is useful for the experiment.
Nexus Reading
Hit test is small in the API and decisive in the experience. A pilot must measure time to valid surface, repositionings, abandonment, and compatibility by browser and device.
FAQ
Hit test automatically creates an anchor?
No. It returns a pose; the application decides whether to create an anchor or just show a preview.
Does it work in any browser?
No. You must detect module support and provide appropriate fallback.
Does the position never change?
It may change as the device improves your understanding of the environment; confirm and follow the pose.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 15, 2026. The text is original and interprets practical implications for companies.
- W3C — WebXR Hit Test Module: pattern status, test hit sources, geometry types, results and privacy rules.
- Immersive Web — Hit Testing Explainer: use cases and relationship between radius, surface, input and positioning in the real environment.
Date reported by main source: Working Draft of December 11, 2025; analysis published on September 15, 2026.