Looker vs Looker Studio (Now Data Studio) Explained (2026)

Quick verdict

Short answer

Choose Looker when you need one governed definition of metrics, written in LookML and kept in Git, shared by many users, applications and embedded experiences, and you have a budget for an enterprise contract. Choose Looker Studio, now called Data Studio, when you need free, quick reports and dashboards on BigQuery, Google Analytics, Sheets or a SQL database, built by individuals and shared like a Google Doc. Many organisations use both: Looker as the semantic layer and Data Studio as a free front end through its Looker connector.

How we know: This comparison is research-based: product names, editions, licensing, connectors and SQL features were checked against Google Cloud's official Looker and Data Studio documentation, release notes and product pages, and Google's own announcement, in October 2026. We have not run either product.

Naming change. Google's free reporting tool was called Google Data Studio until Google renamed it Looker Studio in 2022. On 16 April 2026 Google's release notes recorded that "We've rebranded Looker Studio as Data Studio", and the paid edition Looker Studio Pro became Data Studio Pro. Google said existing reports, data sources and users moved over with no action needed, and that "Looker is Google's enterprise business intelligence platform and Data Studio is evolving to complement Looker, independently". This page keeps the Looker Studio name in its title because many people still search for it.

Looker is Google Cloud's enterprise BI platform. Developers describe data in LookML, a modelling language for dimensions, measures, joins and derived tables, and Looker generates SQL against your database at query time. Users explore data through Explores, dashboards and Looks, and applications can embed it or call its API. It is sold today mainly as Looker (Google Cloud core), a fully Google-managed service in Standard, Enterprise and Embed editions; the earlier Looker (original) also supports customer-hosted deployments.

Data Studio (formerly Looker Studio) is a free, browser-based report and dashboard builder. Google lists more than 500 connectors, including Google and partner connectors. Each report uses data sources that connect to a table or a custom SQL query, and reports are shared with Google account permissions. Data Studio Pro adds team workspaces, organisation-owned content, Google Cloud support and enterprise controls, billed per licensed creator through a Google Cloud project.

Side by side

Aspect	Looker	Looker Studio (now Data Studio)
What it is	Enterprise BI platform with a governed semantic model	Self-service report and dashboard builder
Current name	Looker (Google Cloud core); Looker (original)	Data Studio (called Looker Studio from 2022 to April 2026); paid tier Data Studio Pro
Price	Paid: platform edition plus user licences, annual contract by quote; 90-day trial instances	Free for creators and viewers; Pro is a per-licensed-user subscription with a 30-day trial
Modelling	LookML: dimensions, measures, joins and derived tables in version-controlled files	Per data source fields and calculated fields; no shared semantic model of its own
SQL access	SQL Runner for direct queries; SQL-based derived tables in LookML	Custom query option on BigQuery, PostgreSQL, MySQL and other SQL connectors (single statement)
Databases	Around 50 SQL dialects, including BigQuery, Snowflake, Redshift, PostgreSQL, MySQL, SQL Server, Databricks and ClickHouse	500+ connectors, strongest on Google sources (BigQuery, Google Analytics, Sheets) plus SQL databases and partner connectors
Hosting	Google Cloud managed (core); customer-hosted possible with Looker (original)	Google-hosted SaaS only
Embedding	Embed edition with signed embedding, custom themes and high API limits	Reports can be embedded in web pages; there is no equivalent of Looker's Embed edition
Main trade-off	Governed metrics and embedding, at enterprise cost and with LookML skills required	Free and fast, but logic lives in each report and data source, so definitions can drift (editorial)

Key differences

Semantic layer versus report builder

The core difference is where business logic lives. In Looker, developers define it once in LookML, and every Explore, dashboard and API call reuses those definitions. A short LookML example:

# LookML (Looker)
view: orders {
  sql_table_name: analytics.orders ;;
  dimension: status { type: string  sql: ${TABLE}.status ;; }
  dimension_group: created { type: time  timeframes: [date, month]  sql: ${TABLE}.created_at ;; }
  measure: total_revenue { type: sum  sql: ${TABLE}.amount ;; }
}

In Data Studio, each data source has its own fields and calculated fields, and a report author can connect straight to a table or query. That makes it fast for individuals, but in our view two teams can easily end up with different definitions of "revenue". Data Studio can also use Looker as a data source through its Looker connector, so the governed model and the free front end can work together.

Working in SQL

Looker provides SQL Runner, which Google describes as a way to "directly access your database". A SQL Runner query can be turned into an Explore or added to a LookML project as a derived table. Day-to-day users do not write SQL; Looker writes it from the model.

Data Studio lets you choose Custom query when creating a BigQuery, PostgreSQL or MySQL data source. Google's documentation says custom SQL may contain only a single statement; for MySQL it is used as an inner select for each generated query, and the PostgreSQL connector returns at most 150,000 rows per query.

-- Data Studio custom query on BigQuery (GoogleSQL)
SELECT DATE_TRUNC(order_date, MONTH) AS month,
       country,
       SUM(amount) AS revenue
FROM `my_project.sales.orders`
GROUP BY month, country

Who pays and how

Looker (Google Cloud core) charges for a platform edition (Standard for up to 50 internal platform users, Enterprise, or Embed) plus user licences by type, on one, two or three-year annual terms, with prices from Google's sales team. Each edition includes one production instance, 10 Standard users and 2 Developer users.

Data Studio is free for creators and viewers. Data Studio Pro needs a licence for each user who creates, edits or manages content in Pro team workspaces; viewers do not need one. Each subscription is linked to one Google Cloud project and billed through Cloud Billing.

Governance, security and embedding

Looker Enterprise and Embed editions add VPC Service Controls and Private Service Connect, and the Embed edition adds signed embedding, custom themes and the highest API allowances (500,000 query API calls a month). That makes Looker the option for customer-facing analytics inside your own application.

Data Studio Pro adds team workspaces and organisation ownership, so content does not disappear when an employee leaves, plus customer-managed encryption keys, customer-managed storage and data residency (added in June 2026), delivery schedules, alerts and Gemini in Data Studio. The free edition ties content to individual Google accounts.

Pricing and licensing

Looker. Google does not publish list prices. Looker (Google Cloud core) pricing combines a platform edition fee and per-user fees by user type (Developer, Standard, Viewer), on annual terms; contact Google Cloud sales. Trial instances last 90 days. Looker (Google Cloud core) instances created before 1 August 2026 include 50 complimentary Data Studio Pro licences by default; Google says these are not available for instances created after that date.

Data Studio (formerly Looker Studio). Free. Data Studio Pro is billed per licensed user, per Google Cloud project, through Cloud Billing, with a 30-day free trial. Google's Pro documentation refers readers to the Data Studio product page for the current price, which did not display a figure when we checked, so confirm the price in the Google Cloud console before buying.

Pricing checked on the vendors' official pages on 7 October 2026. Prices change; confirm before buying.

Where each one leads

Looker strengths

One governed semantic model in LookML, version-controlled in Git
Generates SQL against your database for around 50 dialects
Embed edition for customer-facing analytics with signed embedding
Enterprise network security options on Google Cloud

Looker Studio (now Data Studio) strengths

Free for creators and viewers
Over 500 connectors, with strong Google Analytics, Ads, Sheets and BigQuery support
Quick to learn; sharing works like other Google files
Can read governed Looker models through the Looker connector
Pro adds team workspaces and organisation ownership at a per-user price

Limitations

Looker limitations

No public pricing; annual contracts through Google sales
Requires LookML development skills to set up and maintain
Looker (Google Cloud core) does not support username and password login or LDAP
More than a small team needs for a handful of reports (editorial)

Looker Studio (now Data Studio) limitations

No shared semantic model, so metric definitions can drift between reports (editorial)
Custom SQL limited to a single statement, and some connectors cap rows per query
Free edition content is owned by individuals, not the organisation
Renamed twice in four years, so documentation and tutorials use three different names

When to choose each

Choose Looker if

Several teams must use the same metric definitions
You want to embed analytics in a customer-facing product
Your analytics engineers can maintain LookML in Git
You need enterprise network controls on Google Cloud

Choose Looker Studio (now Data Studio) if

You need free dashboards quickly, especially on Google marketing data or BigQuery
Report authors are individuals or small teams without a modelling layer
You already have Looker and want a free, flexible front end on its models
Budget rules out an enterprise BI contract

When neither is right

You are a Microsoft-centred organisation: see Power BI vs Looker and Power BI vs Tableau.
You want visual analytics outside Google Cloud with a large analyst community: see Tableau vs Looker.
You want open source BI you can self-host: see the best open source BI tools and Metabase vs Apache Superset.
Your data is not yet in a warehouse: read data warehouse vs database first.

Final recommendation

Bottom line

These are not competing versions of one product. Looker is the governed, paid, enterprise semantic layer and BI platform; Looker Studio, now Data Studio, is the free report builder. Start with Data Studio if you need dashboards now and your logic is simple. Move to Looker when inconsistent metrics, governance or embedding become the problem, and keep Data Studio as a free front end over Looker models if your users like it.

Frequently asked questions

Is Looker Studio the same as Looker?

No. Looker is Google Cloud's enterprise BI platform with the LookML semantic model, sold by contract. Looker Studio was the 2022 to 2026 name of the free reporting tool formerly called Google Data Studio; Google renamed it back to Data Studio in April 2026.

Is Looker Studio still free?

Yes. Data Studio (formerly Looker Studio) is free for creators and viewers. Data Studio Pro, formerly Looker Studio Pro, is a paid per-user subscription for teams that need team workspaces, organisation-owned content and Google Cloud support.

Why was Looker Studio renamed Data Studio?

Google's April 2026 announcement said Data Studio is "evolving to complement Looker, independently", with a home page that also gives access to BigQuery conversational agents and data apps built in Colab. Existing reports and links moved over without any action needed.

Can Looker Studio use Looker models?

Yes. Data Studio has a Looker connector that reads Looker Explores, so report authors can use governed LookML definitions in a free report builder.

Do I need to know SQL for either tool?

Not as an end user. Looker developers write LookML, which contains SQL expressions, and can use SQL Runner. In Data Studio you can connect to tables without SQL, or write a single-statement custom query on BigQuery, PostgreSQL, MySQL and similar connectors.

Sources

Checked October 2026.

How we research comparisons: our editorial method.