What are the differences among Tableau Desktop, Tableau Server, and Tableau Cloud?
Tableau Desktop is the authoring and analysis application, Tableau Server is a centrally managed, customer-hosted platform, and Tableau Cloud is Salesforce’s separately licensed, managed service for publishing and governing Tableau content. Together, they support a workflow from local development to organization-wide publishing and consumption.
Read full answerHide full answer
Applies toTableau Desktop, Tableau Server, and Tableau Cloud (current releases)
Core Differences
| Capability | Tableau Desktop | Tableau Server | Tableau Cloud |
|---|---|---|---|
| Primary purpose | Create and explore workbooks locally | Publish and share workbooks in an organization | Publish and share workbooks through a managed service |
| Hosting | Installed on each analyst’s computer | Hosted on infrastructure controlled by the organization | Hosted and operated by Salesforce |
| Typical user | Analyst, report developer, business user | Analysts, executives, dashboard consumers | Analysts, executives, dashboard consumers |
| Data connections | Connects directly to Excel, databases, APIs, and other supported sources | Provides centralized, governed connections to enterprise data | Provides centrally managed connections subject to cloud connectivity restrictions |
| Publishing | Publishes to Server, Cloud, or Tableau Public | Hosts published content and manages access | Hosts published content and manages access |
| Administration | Limited administration of local settings | Full administration of users, permissions, licences, schedules, and security | Administration of users, permissions, licences, schedules, and security by the customer and Salesforce |
| Scale | Primarily a single-user desktop application | Designed for concurrent organizational use | Designed for concurrent organizational use |
How the Products Work Together
-
An analyst creates a workbook in Tableau Desktop.
-
The analyst connects to the required data source and builds views, dashboards, filters, actions, and calculated fields.
-
The workbook is saved locally as a
.twbfile or as a packaged.twbxworkbook. -
The analyst selects Server → My Content → Publish in Tableau Desktop and chooses Tableau Server or Tableau Cloud as the destination.
-
Administrators assign permissions and configure data-source credentials, refresh schedules, subscriptions, and site settings.
-
Consumers open published content through a browser without installing Tableau Desktop.
The calculation and visualization logic remains the same when a workbook is published. Moving from Desktop to Server or Cloud changes hosting, access, administration, and refresh infrastructure—not Tableau’s calculation syntax.
Data Connections and Refresh
Tableau Desktop can work with local files such as Excel and CSV or establish live connections to supported databases.
After publishing, two common approaches are available:
-
Live connection: Tableau queries the source through the Server or Cloud environment. Centralized credentials and network configuration become important.
-
Extract connection: Tableau stores a snapshot of the source data. Extracts can be refreshed on Server or Cloud and may perform better for large or frequently accessed dashboards.
Server is commonly deployed on an organization’s on-premises network or on infrastructure managed by that organization. Cloud provides managed infrastructure, but source connectivity can be limited by firewalls, private networking, and supported connector requirements.
Business Example
Suppose an analyst has the following sales data:
| Region | Quarter | Sales |
|---|---|---|
| Central | Q1 | 120,000 |
| North | Q1 | 150,000 |
| West | Q1 | 180,000 |
The analyst uses Tableau Desktop to create a dashboard with:
-
SUM(Sales)as the sales measure. -
Regionas a discrete dimension. -
A dashboard filter for the selected quarter.
-
A published extract for predictable dashboard performance.
In Tableau Cloud, regional managers access the dashboard through a browser and see:
| Region | Displayed Sales |
|---|---|
| Central | 120,000 |
| North | 150,000 |
| West | 180,000 |
The expected result is total sales of 450,000, with regional totals available through filters or dashboard actions. In Tableau Server, the same workbook can be hosted internally when data must remain under the organization’s direct control.
Adjacent Product: Tableau Prep
Tableau Prep provides data preparation and transformation. Analysts can clean files, reshape data, combine sources, and create flows before publishing the resulting data source to Tableau Server or Tableau Cloud. It complements Desktop; it does not replace Desktop’s visualization capabilities or Server and Cloud’s publishing and administration.
Best Practices and Pitfalls
-
Choose Tableau Server when the organization requires direct infrastructure control, private-network connectivity, or specific administrative control.
-
Choose Tableau Cloud when managed hosting, straightforward provisioning, and Salesforce-managed infrastructure are priorities.
-
Use Tableau Desktop for report development and local exploration, not as the primary organization-wide dashboard distribution platform.
-
Prefer extracts for frequently accessed dashboards or demanding queries, but monitor extract size and refresh frequency.
-
Centralize sensitive data-source credentials in Server or Cloud rather than embedding them in workbooks.
-
Test filters, aggregations, and LOD expressions after publishing because source connectivity and extract refreshes can affect execution behavior.
-
Do not confuse Tableau Cloud with Tableau Public. Tableau Public is primarily for sharing visualizations publicly; Tableau Cloud supports private organizational content and governed sharing.