ARCore
Augmented reality (AR) SDK software
Augmented reality software
Augmented reality (AR) development software
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if ARCore and its alternatives fit your requirements.
Pay-as-you-go
Free TrialFree version
Small
Medium
Large
- Retail and wholesale
- Accommodation and food services
- Information technology and software
What is ARCore
ARCore is an augmented reality SDK from Google for building AR experiences on supported Android devices. It provides motion tracking, environmental understanding, and light estimation so developers can place and anchor virtual content in real-world scenes. It targets mobile app developers using Android-native tooling as well as common game engines for AR use cases such as product visualization, interactive education, and location- or scene-based experiences. ARCore’s capabilities and device support are tied to Google’s Android ecosystem and certified device list.
Deep Android platform integration
ARCore integrates closely with Android and Google’s mobile platform services, which simplifies deployment for Android-first AR applications. It supports core AR functions such as tracking, plane detection, and anchors that are commonly required for mobile AR. This tight platform alignment can reduce integration work compared with more platform-agnostic AR stacks. It is well-suited to teams standardizing on Android tooling and release processes.
Mature core AR features
ARCore provides established capabilities for real-world tracking and scene understanding, including motion tracking and surface detection. These features support common AR patterns such as placing objects on detected planes and maintaining stable positioning as the camera moves. The SDK is designed for real-time mobile performance constraints. This makes it a practical baseline for many consumer and enterprise mobile AR scenarios.
Broad developer ecosystem support
ARCore is commonly used with mainstream mobile development workflows and widely adopted engines, which helps teams leverage existing skills and assets. Documentation, sample projects, and community knowledge are extensive due to the size of the Android developer ecosystem. This can shorten prototyping time and reduce implementation risk for standard AR interactions. It also supports integration with typical mobile app components (UI, permissions, camera pipelines).
Android-only runtime scope
ARCore targets Android devices, so teams building cross-platform mobile AR typically need a separate stack for iOS. This can increase engineering effort for feature parity, QA, and ongoing maintenance across platforms. Organizations with mixed-device deployments may need additional abstraction layers or engine-based approaches. As a result, ARCore alone does not cover full mobile platform requirements.
Device support variability
ARCore features depend on device certification and hardware capabilities, which can vary across Android models. This can lead to inconsistent user experiences across a heterogeneous device fleet, especially in enterprise BYOD environments. Teams may need device allowlists, runtime capability checks, and fallback behaviors. Testing requirements can increase due to fragmentation.
Limited out-of-the-box authoring
ARCore is primarily a developer SDK rather than an end-user AR content authoring or publishing platform. Non-technical teams typically need additional tools or custom pipelines to create, manage, and update AR content at scale. Features like content management, remote publishing workflows, and analytics often require third-party services or bespoke development. This can extend time-to-launch for content-heavy programs.
Plan & Pricing
| Plan / Component | Price | Key features & notes |
|---|---|---|
| ARCore SDK (core runtime & developer SDKs) | $0 — free to use | ARCore core SDKs (Android, iOS, Unity, Web) distributed with code samples under Apache 2.0 and site content under Creative Commons; download & use require agreeing to ARCore Additional Terms. |
Usage-based components (ARCore services that require Google Cloud / Google Maps Platform billing):
Pricing model: Pay-as-you-go (Google Maps Platform / Google Cloud billing for server APIs and Geospatial features).
Free tier / trial: Google Maps Platform provides free monthly usage caps per SKU (replaced the prior $200 monthly credit as of March 1, 2025); Google Cloud offers a 90‑day $300 new‑user free trial.
Example paid options:
- Google Maps Platform Subscriptions (self‑service tiers for Maps/Routes/Places/Environment): Starter — $100/month (50,000 combined calls/month), Essentials — $275/month (100,000 calls/month), Pro — $1,200/month (250,000 calls/month).
- Many ARCore server features (Geospatial APIs, Photorealistic 3D Tiles, Places lookups) are billed per‑request using Maps Platform SKUs or Google Cloud SKUs; exact per‑request SKU prices and volume discounts are published on Maps/Cloud pricing pages.
Quota notes: ARCore Geospatial API usage limits: 1,000 sessions started per minute or 100,000 requests per minute (per project); exceeding limits may return resource‑exhausted errors.
How these pieces relate: The ARCore SDK itself is provided free; however, certain ARCore capabilities that rely on server APIs or Google Maps/Cloud services (for example, Geospatial API, Places, Photorealistic 3D Tiles) require enabling billing in a Google Cloud project and incur pay‑as‑you‑go charges or can be used under Maps Platform subscription plans.
(Official sources: ARCore overview & downloads; Geospatial API docs; Google Maps Platform subscriptions & billing; Google Cloud Free Trial.)
Seller details
Google LLC
Mountain View, CA, USA
1998
Subsidiary
https://cloud.google.com/deep-learning-vm
https://x.com/googlecloud
https://www.linkedin.com/company/google/
