This document explains Looker pricing details. If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
Looker (Google Cloud core) pricing has two main components:
Every Looker (Google Cloud core) instance that you create has a billing account attached to it. Any charges incurred by creating a new instance and/or adding named users to that instance are billed to the attached billing account.
Looker (Google Cloud core) offer three platform editions:
Standard edition
The following table shows the cost of the Standard edition Looker (Google Cloud core) platform.
Commitment model | Cost | Details |
|---|---|---|
Annual commitment | Call sales | Work with sales to identify a solution that works for you. |
Enterprise edition
The following table shows the cost of the Enterprise edition Looker (Google Cloud core) platform.
Commitment model | Cost | Details |
|---|---|---|
Annual commitment | Call sales | Work with sales to identify a solution that works for you. |
Embed platform
The following table shows the cost of the Embed variant of the Looker (Google Cloud core) platform.
Commitment model | Cost | Details |
|---|---|---|
Annual commitment | Call sales | Work with sales to identify a solution that works for you. |
Each platform comes with ten standard users and two developer users included. Annual subscriptions are available in one, two, and three-year terms.
There are three different types of Looker user licenses:
Unless otherwise specified in a subscription to Looker (Google Cloud core), Google reserves the right to issue additional invoices or charges to Customer in arrears if Customer's use of Looker (Google Cloud core) exceeds allowed usage under the subscription, with the pricing listed at the Fees URL applying to that excess usage.
A detailed list of Looker (Google Cloud core) platform features and user entitlements can be found in the documentation.
Conversational Analytics in Looker
Conversational Analytics usage is measured in data tokens, which quantify the advanced data processing and model orchestration driving your insights. This includes translating the natural language into a Looker query, routing to specialized tools, and synthesizing secure context. Managed at the Looker instance level, usage is categorized into input data tokens (context, history, and metadata instructions) and output data tokens (visualizations and natural language response).
These input and output data tokens are the basis for calculating monthly usage.
Data token allocations are applied at the instance level as an aggregated pool shared across all authenticated users on that instance. Each Looker platform subscription comes with a monthly data token quota for usage of Looker's conversational analytics capabilities.
Platform Subscription Tier | Included Input Data Tokens (monthly) | Included Output Data Tokens (monthly) |
|---|---|---|
Standard | 60M | 1.2M |
Enterprise / Advanced | 300M | 6M |
Embed / Elite | 1.2B | 24M |
All non-production and add-on instances receive a flat, baseline allocation of 6M Input Data Tokens and 0.12M Output Data Tokens per month to support development and testing.
Data token allocations will reset every month and unused tokens will not roll over. These tokens are ring-fenced specifically to Looker and are not fungible across other Data Cloud surfaces.
As part of the Conversational Analytics in Looker launch, all users will enjoy unlimited access without quota limits or overage fees through September 30, 2026 (within fair usage limits). This enables customers to explore this new capability and establish their usage baselines for this new capability. Data token consumption is tracked and made available through Looker's System Activity dashboards and Explores to provide visibility into usage and consumption patterns to support effective future planning.
Quota enforcement and overage billing will take effect October 1, 2026. Customers will be given additional notice prior to this date.
After this date, usage that extends beyond the instance's included monthly data token allocation will be subject to overage fees. These will be billed at the end of each month based on actual usage during the billing period.