API records video, IMU and metadata to MP4 to play scenarios. See benefits, differences and care with sensitive data.

Direct answer

ARCore's Recording and Playback API records an MP4 session with camera video, IMU data, API events, and optional metadata. The recording can be played back repeatedly to reduce travel and make regressions more consistent. It is not a deterministic copy of the world: trackables, poses, and timings may vary between plays, and files may contain sensitive device, sensor, and location information.

Recorded scenery reduces field variability

The same camera pass helps you compare builds and reproduce failures without returning to the location for each change.

Reproduction is not absolute determinism

Algorithms can produce different poses and trackables. Tests should use tolerances and observable results, not byte-for-byte equality.

Metadata connects world and business rules

Own events can mark expected steps, objects and results, creating more useful regression cases than just the video.

Test file may be data sensitive

Device image, motion, location, and signature require consent, access control, short retention, and authorized environments.

Nexus Reading

Create a library versioned by scenario, device, light and objective; combine fast replay with final acceptance on-site and on real hardware.

FAQ

Is the file a regular MP4?

Yes, with video and additional tracks; Supported players can display the video, while ARCore interprets the session data.

Does replay always generate the same pose?

No. The documentation warns that trackables, timing and poses may differ.

Can I record any environment?

Only with authorization and appropriate policy, because the session may contain camera, sensors and location.

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 24, 2026. The text is original and interprets practical implications for companies.

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