Where Are Extracts Stored on Tableau Server?

Knowing where your Tableau Server extracts are physically stored is one of those technical details that seems minor until it suddenly becomes a critical piece of information. Whether you're troubleshooting a failed extract refresh, managing disk space, or planning a backup strategy, understanding the "where" and "why" behind extract storage is essential for any Tableau administrator.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

This article will break down exactly where Tableau Server stores its extracts, how the location differs based on your setup, and why this information is so fundamental to maintaining a healthy and performant server environment.

Why Does the Location of an Extract Even Matter?

Before we jump into specific file paths, it’s helpful to understand the practical reasons for knowing where your .hyper files live. It's not just trivia for server admins, it has real-world implications for:

• Performance Troubleshooting: If extract refreshes are slow or failing, knowing the storage location lets you investigate potential I/O bottlenecks, disk latency, or permissions issues on the underlying storage volume.
• Backup and Recovery Strategy: The Tableau Server backup process (tsm backup) automatically includes the File Store where extracts are housed. However, understanding this relationship is key to feeling confident in your disaster recovery plan and knowing what components are being backed up.
• Disk Space Management: Extracts can be massive, sometimes consuming hundreds of gigabytes of disk space. Being able to go to the source lets you confirm which data sources or workbooks are the biggest offenders when your server's disk space alerts start going off.
• Server Migrations and Upgrades: During a hardware migration or a significant upgrade, having a clear picture of the server’s file structure helps you ensure all critical assets are accounted for and moved correctly.

The Heart of Storage: The Tableau Server File Store

The single most important component to understand when discussing extract storage is the Tableau Server File Store. This isn't just a simple folder - it's a core Tableau Server process responsible for storing all the content and assets that users have published.

Think of it as the server's primary library. While the Tableau Server Repository (a PostgreSQL database) acts as the card catalog, storing all the metadata about your content (like workbook names, user permissions, and extract refresh schedules), the File Store is where the actual books - the extracts, workbooks, and data sources themselves - are kept.

Therefore, when you're looking for an extract, what you're really looking for is the location of the File Store on your server's file system.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Finding the Default File Store Location

The exact file path for the File Store depends on several factors, primarily your operating system and whether you installed Tableau Server in the default location. With modern versions that use Tableau Services Manager (TSM), the paths have become standardized but are buried deep within the Tableau data directory.

On a Windows Server:

For a default installation of Tableau Server on a Windows machine, you can typically find the File Store in the following directory:

C:\ProgramData\Tableau\Tableau Server\data\tabsvc\filestore\

A few key points about this path:

• The C:\ProgramData folder is hidden by default in Windows. You'll need to enable "Show hidden items" in File Explorer to navigate to it.
• Inside the filestore directory, you won't see neatly named .hyper files that correspond to your data source names. Instead, you’ll see a series of folders with seemingly random character names. Tableau uses its own internal system to manage and map these files to the content you see in the web UI. Directly manipulating these files is strongly discouraged and can corrupt your entire Tableau instance.

On a Linux Server:

For a default Linux installation, the File Store path follows a similar structure:

/var/opt/tableau/tableau_server/data/tabsvc/filestore/

Like the Windows version, the contents of this directory are managed by Tableau Server. You won't find a direct Sales_Data_Q1.hyper file here. Browsing this directory is purely for diagnostic or informational purposes.

If You Used a Custom Installation Path

If you specified a non-default installation path - say, to a D: drive with more storage - the beginning of the path will change accordingly. The core sub-directory structure, \data\tabsvc\filestore\, generally remains consistent.

For instance, if you installed to D:\Tableau\, the File Store would likely reside at:

D:\Tableau\Tableau Server\data\tabsvc\filestore\

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

What About Clusters and High-Availability Environments?

In a multi-node Tableau Server cluster, the File Store's behavior becomes more sophisticated to ensure high availability. When you configure a second node to also run the File Store process, Tableau Server automatically takes care of replicating the extract data between the nodes.

This means if your primary node goes down, the second node has an identical, up-to-date copy of all the extracts and can continue serving user requests without interruption. This replication happens automatically in the background. As an administrator, you don’t need to manually copy or sync files between the machines, Tableau manages the entire process itself.

The Future is Flexible: The External File Store

With businesses moving more infrastructure to the cloud, Tableau introduced a game-changing option: the External File Store. This configuration allows you to completely detach the File Store from your Tableau Server's local disks and host it on a cloud-based storage service instead.

How it Works

You can configure your Tableau Server to use one of the following as its File Store:

• Amazon S3 Bucket
• Azure Storage Container

In this architecture, when an extract is refreshed or published, it’s not saved to the server’s local hard drive at all. Instead, it’s sent directly to the configured S3 bucket or Azure container.

Key Benefits

Using an external file store is quickly becoming best practice for large, enterprise-level deployments, especially those running on cloud platforms like AWS or Azure. The advantages include:

• Separation of Storage and Compute: You can scale your Tableau Server compute resources (workers, VizQL processes) independently of your storage, which can be much more cost-effective.
• Enhanced Durability and Backups: Cloud storage is inherently durable and redundant. Managing backups can also be simplified, as you can leverage the native snapshot and backup tools of your cloud provider.
• Simplified Server Upgrades: By externalizing the stateful parts of your server (data), spinning up new server nodes for an upgrade becomes faster and simpler.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Special Case: In-Memory Data with the Data Cache

Finally, it's worth mentioning the role of cache. When a user opens a dashboard that uses an extract, Tableau Server doesn't necessarily read the entire .hyper file from the disk every single time. To provide fast load times and interactive performance, the most frequently queried data from the extract is loaded into system memory (RAM). This is handled by the Data Cache process.

So, while the permanent, authoritative copy of the extract is always in the File Store (whether local or external), temporary, performance-optimized copies or pieces of that data will exist in the server's RAM during active user sessions. This is a critical performance feature, but it doesn't change the fact that the ultimate source of truth is always the on-disk File Store.

Final Thoughts

So, where are your extracts stored? The shortest answer is "in the Tableau Server File Store." That File Store, however, can live on a local disk in a clearly defined (though deeply nested) path, be automatically replicated across multiple nodes in a cluster, or even exist entirely outside the server in a service like Amazon S3.

Mastering these storage options is a big part of running an efficient Tableau environment, but for many marketing and sales teams, the goal isn't to become server experts. It's about getting real-time insights from all their data sources. That's why we built Graphed. We connect directly to your marketing and sales platforms - like Shopify, Google Analytics, or Salesforce - and use AI to create live dashboards from simple, plain-English conversations. There are no extracts to manage and no storage locations to worry about, just consistently up-to-date reports when you need them.