Apps can expose spectator, drone, or avatar views as Camera2 devices. Understand GPU lifecycle, formats and cost.

Direct answer

Meta VR OS Native SDK's Virtual Camera Publisher allows an XR application to publish virtual cameras visible to Android consumers via the Camera2 API. You can provide spectator, drone or avatar views, with up to three cameras and rates of up to 60 frames per second, using RGBA or YUV formats. The application must render only when a consumer opens the camera, synchronize frames and handle termination correctly to avoid idle GPU expenditure. The feature requires specific permission and validation on the device; The documentation states that testing via Link is not supported.

The virtual camera becomes a system contract

The consumer sees a Camera2 device. Identity, capacity, resolution, and state need to remain stable throughout the session.

Rendering must follow demand

Producing frames without a consumer wastes GPU and battery. Open resources at effective start and release everything after closing or error.

Format changes cost and integration

RGBA favors direct rendering; YUV can serve video and broadcast. Conversion, copying and synchronization should be part of the performance budget.

Multiple views expand production

Viewer, drone and avatar can feed recording, remote support or transmission, as long as privacy and consent are addressed.

Nexus Reading

Set resolution and fps by use case, measure GPU and latency, test repeated opening and closing, and maintain fallback when the camera is unavailable.

FAQ

How many virtual cameras can be published?

The documentation states support for up to three cameras per application.

What is the maximum rate?

The documented limit is up to 60 frames per second, subject to device and load.

Is it possible to validate via Meta Quest Link?

The documentation states that testing this feature via Link is not supported; use the compatible device.

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

Date reported by main source: official documentation consulted on September 27, 2026; feature available from SDK v204.