Use Cloud Anchors to create multiplayer or collaborative AR experiences that Android and iOS users can share.
How Cloud Anchors work
Cloud Anchors let you make ARKit and/or ARCore anchors available to multiple devices in the same environment.
Users in the same environment can add Cloud Anchors to the AR scene that they see on their device.
Your app can render 3D objects attached to the Cloud Anchors, letting users see and interact with the objects simultaneously.
To make these shared AR experiences possible, the ARCore SDK uses Google servers to host and resolve anchors. Clients must have a working internet connection in order to access Google servers.
When you host an anchor, ARCore sends relevant visual mapping data from a user's environment to Google servers. Once this data is uploaded, it is processed into a sparse point map, similar to an ARCore point cloud.
Resolving a Cloud Anchor lets multiple devices in a given physical space use previously hosted anchors to establish a common frame of reference.
A Cloud Anchor resolve request sends visual feature descriptors from the current frame to the server. The server attempts to match the visual features to the Cloud Anchor's sparse point map. This lets your app situate resolved anchors with the same position and orientation relative to the environment for each device.
Data storage and access limitations
Cloud anchors have the following data storage and access limitations:
Cloud anchors can be resolved for twenty-four hours after they are hosted.
Raw visual mapping data uploaded to the cloud when hosting an anchor is discarded after seven days.
Anchors are resolved on the server side against the stored sparse point map.
- The sparse point map can be used for Cloud Anchor resolution requests for twenty-four hours after it is generated.
- Previously uploaded mapping data is never sent to a user's device.
It is not possible to determine a user's geographic location or to reconstruct any images or the user's physical environment from the sparse point map.
Visual feature descriptors from a request to resolve an anchor are never stored.
To start using Cloud Anchors, see the Cloud Anchors quickstart.
If you are new to working with anchors, see Working with anchors for an introduction.