Quick verdict
Choose Tableau if your priority is flexible visual exploration by analysts, desktop authoring on Windows or macOS, self-hosting on Windows or Linux, or Salesforce integration. Choose Looker if your priority is governed metrics defined once in version-controlled code, queried live in a cloud warehouse, and reused across dashboards, embedded apps and other tools. Many organisations use both, since Google documents a Looker connector for Tableau Desktop.
Tableau, part of Salesforce, is built around visual exploration. Authors connect Tableau Desktop (Windows or macOS) or the web editor to a database or file, then drag fields onto a canvas to build views and dashboards, adding calculated fields and level of detail (LOD) expressions as needed. Content is published to Tableau Cloud or self-hosted Tableau Server. Licences are role based: Creator, Explorer and Viewer.
Looker is Google Cloud's enterprise BI platform. Developers model data in LookML (views, dimensions, measures and explores) in a browser IDE backed by Git, and business users explore those models; Looker generates SQL for each query and runs it on the connected database. It is sold as Looker (Google Cloud core) in Standard, Enterprise and Embed editions, or as Looker (original), which can be customer-hosted. It is not the same product as Google's free Data Studio (formerly Looker Studio).
Side by side
| Aspect | Tableau | Looker |
|---|---|---|
| Approach | Visual exploration first; modelling optional | Semantic model first (LookML); exploration on top |
| Authoring | Tableau Desktop (Windows, macOS) and web authoring | Browser only: LookML IDE, Explores and dashboards |
| Data access | Live connections or extracts; custom SQL (single SELECT) | Live SQL against the database for every query; SQL Runner for Developer users |
| Calculation language | Calculated fields, table calculations, LOD expressions | LookML dimensions and measures containing your database's SQL |
| Hosting | Tableau Cloud (SaaS) or Tableau Server on Windows or Linux | Looker (Google Cloud core) on Google Cloud; Looker (original) Looker-hosted or customer-hosted |
| Pricing | Published per-role prices (Creator, Explorer, Viewer), Standard and Enterprise editions, annual contracts | Platform edition plus user licences (Developer, Standard, Viewer); quote only |
| Embedding | Embedding API v3 for Tableau Cloud, Server and Public | Private embedding in all editions; signed and cookieless embedding in the Embed edition |
| Main trade-off | Fast, flexible exploration, but metric definitions can drift between workbooks | Consistent governed metrics, but needs LookML developers and a capable SQL database |
Key differences
Exploration first versus model first
With Tableau, an analyst can connect to a table and start building charts at once. Business logic lives in calculated fields inside a workbook or in a published data source that others reuse. LOD expressions let you fix the grain of an aggregation regardless of the view; this FIXED example from Tableau's help returns total sales per region:
-- Tableau calculated field (FIXED level of detail expression)
{FIXED [Region] : SUM([Sales])}With Looker, a developer first writes the model. Business users then pick dimensions and measures in an Explore, and every query uses the same definitions. A LookML measure, in the pattern shown in Looker's reference documentation:
# LookML (view file)
dimension: supplier_name {
sql: ${TABLE}.supplier_name ;;
}
measure: total_revenue {
type: sum
sql: ${sales_price} ;;
value_format_name: usd
}In our assessment, Tableau is faster to a first chart and better for open-ended analysis; Looker takes longer to set up but makes it harder for two dashboards to disagree about the same metric.
SQL access for SQL users
Tableau supports custom SQL on most database connections. Tableau documents that the query must be a single SELECT statement, that Tableau wraps it in an outer query to add filters and grouping (which can affect performance), and that parameters can replace only literal values. Data can be queried live or pulled into an extract.
Looker is SQL underneath: every dimension and measure contains SQL in your database's dialect, and Looker supports more than 40 dialects, including BigQuery, Snowflake, Redshift, PostgreSQL, MySQL, SQL Server, Databricks and Oracle. Developer users can also run ad hoc queries in SQL Runner. Because Looker keeps no extracts, query cost and speed depend on the warehouse, which matters on pay-per-query platforms.
Licensing and pricing
Tableau sells Creator, Explorer and Viewer roles in Standard and Enterprise editions on annual contracts. Creator includes Tableau Desktop and Tableau Prep Builder; Explorer authors in the browser on published data; Viewer interacts with dashboards. Tableau's licensing documentation also lists a Display role, usage-based licensing per analytical impression and capacity-based Viewer blocks from July 2026. Tableau+ bundles Tableau Cloud with Tableau Next.
Looker (Google Cloud core) charges a platform fee by edition plus user licences. Standard suits organisations with fewer than 50 users; Enterprise adds private connections, customer-managed encryption keys and VPC Service Controls; Embed adds signed embedding and the highest API limits. Each edition includes 10 Standard and 2 Developer users. Developer users write LookML and use SQL Runner; Viewer users can view, filter, drill, schedule and download, but cannot use Explore or SQL Runner. Google does not publish list prices.
Ecosystems and working together
Tableau sits in the Salesforce ecosystem. Salesforce describes Tableau Next as an agentic analytics platform built on the Salesforce Platform and Data 360, with Tableau Semantics as its semantic layer, available through Tableau+. Looker sits in Google Cloud, alongside BigQuery and Data Studio.
The two are not exclusive. Google documents a generally available Looker BI connector for Tableau Desktop, so Tableau users can build views on governed LookML models. In our view this is a reasonable pattern where data engineering standardises on Looker but analysts prefer Tableau's canvas.
Pricing and licensing
Tableau. Tableau publishes per-role list prices on its pricing page (Creator, Explorer and Viewer, billed annually); we could not load that page to confirm the current figures, so check them there. Creator is the most expensive role and Explorer and Viewer cost less per user, Enterprise edition costs more, every deployment needs at least one Creator, and Tableau Cloud and Server plans require annual contracts. Tableau+ and the usage-based and capacity-based options are quoted by sales. Prices exclude tax; confirm current figures on Tableau's page.
Looker. Google's Looker pricing page, checked 7 October 2026, describes platform pricing by edition plus user pricing by type and asks buyers to contact sales; no list prices are published. Trial instances of Looker (Google Cloud core) last 90 days. Instances created after 1 August 2026 no longer include 50 free Data Studio Pro licences. The warehouse bill for the queries Looker runs is separate.
Pricing checked on the vendors' official pages on 7 October 2026. Prices change; confirm before buying.
Where each one leads
Tableau strengths
- Fast visual exploration without building a model first
- Tableau Desktop runs on Windows and macOS
- Tableau Server can be self-hosted on Windows or Linux
- Published per-role prices and several licensing models
- Extracts reduce load on source databases when live queries are not needed
Looker strengths
- One governed semantic layer in LookML, readable by SQL users
- Git version control and Development Mode built in
- Live queries with no extracts to schedule
- BI connectors let Tableau, Power BI, Excel and Sheets reuse Looker models
- Browser-only authoring on any operating system
Limitations
Tableau limitations
- Metric definitions can drift between workbooks without careful data source governance
- Custom SQL limited to a single SELECT, wrapped in an outer query
- Annual contracts only, and higher list prices than some competitors
- Tableau Next and Tableau Semantics require the Tableau+ bundle
Looker limitations
- No published prices
- New data needs a LookML developer before business users can explore it
- Every query runs on the database, so warehouse cost and speed matter
- Signed embedding requires the Embed edition; Standard edition is capped at 50 users
When to choose each
Choose Tableau if
- Analysts need to explore varied data quickly and visually
- Some authors use macOS and want a desktop application
- You must self-host the BI server, including on Linux
- Your business runs on Salesforce
Choose Looker if
- You want governed metrics in code, reviewed and versioned in Git
- Your data is in a cloud warehouse such as BigQuery or Snowflake
- You are embedding analytics into a product
- Several BI tools need to share one semantic layer
When neither is right
- You are a Microsoft organisation with Fabric or Microsoft 365 E5: see Power BI vs Tableau and Power BI vs Looker.
- You want open source, self-hosted dashboards over SQL: see Metabase vs Apache Superset, Power BI vs Metabase and the best open source BI tools.
- You need free ad hoc reports on Google data: Data Studio (formerly Looker Studio) may be enough; see Looker vs Looker Studio.
Final recommendation
Tableau is the stronger choice for analyst-led, visual exploration, with cross-platform desktop authoring and self-hosting options. Looker is the stronger choice when consistency of metrics and a code-based, Git-managed semantic layer over a cloud warehouse matter most. If you cannot decide, consider whether your bottleneck is people asking new questions (favouring Tableau) or people getting different answers to the same question (favouring Looker). The warehouse design underneath matters for both; see data warehouse vs database.
Frequently asked questions
Can Tableau connect to Looker?
Yes. Google documents a generally available Looker BI connector for Tableau Desktop, so Tableau users can build views on LookML models. Administrators enable it in Looker's BI connector settings.
Is Looker cheaper than Tableau?
It is not possible to say from public information: Tableau publishes per-role list prices on its pricing page, while Looker pricing is a platform fee plus user licences quoted by Google sales.
Which is better for SQL users?
Both accept SQL. Looker models are written with SQL inside LookML and it supports more than 40 dialects, which suits engineers who want logic in code. Tableau supports custom SQL (a single SELECT) and its own calculation language, which suits analysts who prefer to explore visually.
Can Looker be self-hosted?
Looker (original) is available as a customer-hosted deployment as well as Looker-hosted. Looker (Google Cloud core) runs on Google Cloud. Tableau Server can be self-hosted on Windows or Linux.
Sources
- Tableau pricing
- Tableau help: Understanding license models
- Tableau technical specifications
- Tableau help: Connect to a custom SQL query
- Tableau help: FIXED level of detail expressions
- Tableau Embedding API v3
- Salesforce: Tableau Next
- Google Cloud: Looker pricing
- Looker docs: Looker (Google Cloud core) overview
- Looker docs: Editions and entitlements
- Looker docs: Supported dialects
- Looker docs: Dimension parameter
- Looker docs: Git version control
- Looker docs: BI connectors
Checked October 2026.
How we research comparisons: our editorial method.