Front tracking delivers updated poses and mesh, but does not support anchors or hit testing. See how to design reliable filters and soft proofs.

Direct answer

ARCore's Augmented Faces works with the front camera and provides center pose, face regions, vertices, normals, and UV coordinates of the mesh. The API does not allow creating anchors or raycast hit testing in this mode. Indexes and UVs can be reused throughout the session, while poses, vertices and normals change per frame; The application must keep track of TrackingState and hide or stabilize content when tracking is lost.

Face mesh is dynamic

Vertices and normals track expression and movement; rendering needs to use the current frame and tolerate occlusions.

Static data can be reused

Indexes and UVs remain stable across the session, reducing copying and unnecessary work.

Anchor of the world does not apply

Front face mode does not support anchors or hit tests; Mixing these contracts leads to error and fragile architecture.

Tracking loss needs to have UX

Content should disappear, freeze with warning, or gradually return, without remaining displaced on the face.

Nexus Reading

Use explicit acquisition, tracking and loss states, test face diversity and lighting, and treat virtual proofing as visual estimation.

FAQ

What camera does Augmented Faces use?

The front camera, in a session configured for this feature.

Is it possible to create anchors on the face?

No. The API states that anchors and hit tests are not supported in this mode.

What data changes per frame?

Central pose, poses of regions, vertices and mesh normals.

Essential guides to delve deeper into the decision

Primary sources and references

This editorial analysis was produced by Nexus from the official sources below, consulted on October 31, 2026. The text is original and interprets practical implications for companies.

Date reported by main source: official documentation consulted on October 31, 2026; technical analysis.