An Outlook data file is a local file on your computer where Outlook stores mailbox information, and Outlook uses two main types, PST and OST. A PST is generally an independent file for storing or moving Outlook data, while an OST is a synchronized local copy of a mailbox.
You may be dealing with one without realizing it. A small business owner searches for a client message from several years ago, the laptop freezes, and the immediate worry is whether that email still exists. The answer depends less on the Outlook window than on which data file Outlook uses, where that file lives, and whether another copy exists elsewhere.
Microsoft says both PST and OST files can contain messages, contacts, appointments, tasks, notes, and journal entries. The files therefore hold far more than an inbox. For a professional firm, they may represent correspondence, calendar history, client relationships, and records that staff need after a computer is replaced or a mail system is moved.
Think of an Outlook data file as a filing cabinet that Outlook keeps on a computer. The folders and messages displayed in Outlook are organized inside that file, even though Outlook presents them as a familiar mailbox rather than as a database. Microsoft describes a PST as a structured binary format with folders, messages, and attachments, effectively making it a self-contained local store for Outlook content. Microsoft's technical description of the PST format explains that the file needs no external dependency to hold that structure.
The two names matter immediately:
Outlook may keep local access to:
That local copy helps Outlook remain useful when the internet connection is unavailable. It doesn't mean every local file is a complete, independent backup. An OST normally reflects information synchronized from a mailbox hosted elsewhere, while a PST may be the only copy of older or manually archived material.
Practical rule: A file that Outlook can open isn't automatically a file your firm has safely backed up.
The file's location determines who can access it and whether it survives a hardware failure. Its size affects how easy it is to manage. Its ownership determines whether a departing employee takes important correspondence with a laptop or leaves it behind on a shared system.
Before changing computers, retiring a server, or moving email to Microsoft 365, identify the data files connected to each Outlook profile. A replacement laptop may reconnect to a server mailbox and rebuild an OST, but it won't automatically recreate an independent PST archive that was stored only on the old machine.
The simplest comparison is ownership. A PST belongs to the file, while an OST belongs to the connection between Outlook and a mailbox. A user or administrator can open a PST independently, but Outlook generally rebuilds an OST from the hosted mailbox when the profile or local cache needs to be recreated.
| Attribute | PST, Personal Storage Table | OST, Offline Storage Table |
|---|---|---|
| Who creates it | A user, administrator, export process, or archive workflow | Outlook creates it as a mailbox cache |
| Main purpose | Export, backup, archive, or portable Outlook storage | Offline access to a synchronized mailbox |
| Account relationship | Can exist independently of a live mailbox | Tied to the mailbox and Outlook profile |
| Typical ownership | The person or organization managing the file | The organization or service hosting the mailbox |
| What happens after a computer failure | The file must be restored or opened from backup | Outlook can usually create a new cache after reconnection |
| Common extension | .pst |
.ost |
A PST is useful when a firm needs a durable file that can be opened separately from the original profile. Microsoft specifically identifies PST files for backup, export, and restoring data to a new computer. That makes a PST operationally important during staff changes, computer replacements, and records projects. If you need the practical steps for opening a PST file in Outlook, work from a copy first and preserve the original.
The account setup influences the result. Traditional POP configurations commonly place downloaded mail in a PST. Microsoft 365 and Exchange accounts use an OST in classic Outlook because Outlook maintains a local synchronized copy. IMAP and Outlook.com arrangements can also use an OST in supported Outlook configurations, although the synchronization behavior and folder support can differ from Exchange.
The names can confuse people because both files may appear to hold the same visible content. The important question isn't, “Which extension do I have?” Ask instead:
A PST is portable, but portability creates responsibility. Anyone who can copy it may be able to open sensitive messages, contacts, and attachments. An OST is less useful as a portable archive because it represents a synchronized local cache rather than a convenient standalone mailbox export.
On a Windows computer, the first place to inspect is the user profile. Classic Outlook commonly stores local data under %USERPROFILE%\AppData\Local\Microsoft\Outlook. Newly created PST files in classic Outlook may also appear under the user's Documents folder, commonly in Documents\Outlook Files.
Those are locations, not guarantees. An Outlook profile records the accounts, folders, and data files Outlook should use, so two people with similar accounts may have different paths. A PST might have been moved manually, inherited from an older computer, or attached from a departmental archive.
In classic Outlook, open the account or data-file settings and inspect the listed files. The Mail applet in Windows Control Panel can also expose the active Outlook profiles and their data files. Select the relevant profile, open its data-file settings, and record the complete path before moving anything.
A useful verification process is:
.pst files from .ost files.Don't move a data file merely because its name looks familiar. Confirm which profile uses it, then change the path through Outlook's supported settings.
Classic Outlook relies heavily on local files for caching, archives, and account data. New Outlook for Windows takes a more cloud-oriented approach and may not expose the same local-file workflow for every account or feature. That difference matters during a software refresh. Before you reinstall Microsoft 365, document the existing Outlook profile and preserve independent PST files separately.
Avoid placing active PST or OST files inside OneDrive, Dropbox, or another folder that synchronizes file changes continuously. Outlook and a sync client may attempt to work with the same changing file, creating conflicts or incomplete copies. A local fixed drive is the safer working location. Backup software should copy the file after Outlook closes, rather than turning a synchronized folder into the live storage location.
The protocol changes the meaning of the local file. With Microsoft 365 or Exchange, the hosted mailbox is normally the authoritative record, and classic Outlook uses an OST as a synchronized local copy. A message sent from another device can appear in Outlook after synchronization, and a folder change made in Outlook can propagate back to the server.
Microsoft's description of OST files is central here. An OST is a synchronized local copy used by Microsoft 365, Exchange, IMAP, and Outlook.com accounts. The local file supports offline work, but it shouldn't be treated as a transportable replacement for the hosted mailbox.
| Account type | Local file | Sync direction | Master copy | Offline access |
|---|---|---|---|---|
| Microsoft 365 or Exchange | OST in classic Outlook | Outlook synchronizes changes with the mailbox | Hosted mailbox | Available for cached local content |
| IMAP | Commonly an OST in supported Outlook configurations | Mail and supported folders synchronize with the provider | Hosted mailbox, subject to account behavior | Available for cached content |
| POP | Commonly PST | Outlook downloads mail, with behavior controlled by account settings | Local PST may become the only retained copy | Available from the PST |
| Outlook.com in supported classic Outlook setups | OST | Outlook synchronizes with the online mailbox | Hosted mailbox | Available for cached content |
Cached Exchange mode lets Outlook work with a local representation while the server handles the broader mailbox. Reading a message, creating a calendar item, or sending mail may involve local processing first, followed by synchronization. If the computer fails, reconnecting the account can usually produce a fresh OST, but unsynchronized changes may not survive.
Online mode behaves differently because Outlook relies more directly on the server. Either way, the server mailbox and the local cache have different roles. The OST is a working copy, not a convenient archive file for a migration project.
IMAP generally keeps mail on the provider's server and synchronizes supported folders. Folder behavior, sent-mail handling, flags, and other features may not match Exchange exactly. A firm using IMAP should test what Outlook synchronizes before treating the server as a complete record.
POP is the riskier arrangement for retention. Outlook commonly downloads messages into a PST, and account settings may remove or retain messages on the server. If the PST holds the firm's only historical copy, losing the computer can mean losing the mailbox history. When changing credentials or accounts, follow a documented process for updating an Outlook password and verify that the local file still opens afterward.
Older Outlook installations used a different PST format from modern versions. Outlook 98 through Outlook 2002 used ANSI PST files with a 2 GB maximum size, while Outlook 2003 introduced Unicode PST files and removed that specific 2 GB limitation. The historical PST and OST format overview describes this transition and why it mattered as mail archives expanded.
An ANSI PST may remain in a firm's environment after an archive is copied from an old computer. Its extension is still .pst, so a user may not realize that the underlying format is legacy. A file approaching its limit can become difficult to open or repair, particularly if the organization has no recent backup.
Unicode PST files support larger mail stores and a broader range of characters. That matters for firms handling multilingual correspondence, international names, or attachments and messages created across modern Outlook versions. The newer format is the normal choice when Outlook creates a current PST.
Removing the old 2 GB ceiling doesn't make unlimited growth harmless. A very large archive can take longer to search, copy, verify, and restore. It also creates a larger single point of failure. If one file contains years of client correspondence, a damaged archive affects more records at once.
Set an archive policy based on the firm's retention needs rather than allowing every user's PST to grow indefinitely. Separate completed matters, older correspondence, or exported projects into controlled archives. Keep the original file until the new copy has been opened, checked, and included in the backup process. Size management is not only about Outlook performance. It's about making recovery practical when someone needs a specific message quickly.
An accounting firm retiring a local file server may have years of client correspondence spread across active Outlook profiles, personal archives, and auto-archive folders. Moving mail to Microsoft 365 doesn't automatically preserve every independent PST. The firm needs an inventory before migration begins.
Start with the active profiles and list each PST path. Close Outlook, copy the PST files to protected storage, and preserve the originals as read-only working references where appropriate. Include exported folders and auto-archive locations, not just the PST visible in the main Outlook window. A backup is useful only if staff can identify it and restore it.
Microsoft provides built-in options to open, close, compact, and repair Outlook data files. Its guidance on repairing Outlook data files is relevant when Outlook reports that a PST or OST can't be opened. Repair the working copy first so the original remains available for comparison.
If an OST is damaged or missing, the usual recovery path is to reconnect Outlook to the Exchange, Microsoft 365, IMAP, or Outlook.com account and allow a new local cache to synchronize. The hosted mailbox remains the source for that process, subject to what had synchronized successfully.
A PST requires a different plan. The firm must restore the actual file, repair it if needed, and attach or import it into Outlook. During a tenant migration, administrators may upload PST content through Microsoft's supported import workflow or use a migration tool that fits the firm's compliance requirements. Keep a documented copy until the destination mailbox has been checked, folder mapping has been confirmed, and users can find the records they need.
For teams reviewing automated backup options, ask where the files are stored, how long versions are retained, who can restore them, and how the process handles encrypted or damaged archives. Migration is complete only when the firm can recover information, not merely when users can send new mail.
Most Outlook file incidents begin with a simple operational mistake. A computer shuts down while Outlook is writing, a user stores a live PST in a cloud-synced folder, or an employee leaves with the only archive on a laptop. The result may be a repair prompt, missing folders, conflicting copies, or an archive nobody can locate.
Treat the file as a business record, not as a disposable cache. A PST can hold messages, contacts, appointments, tasks, notes, journal entries, and attachments, while an OST can contain a substantial working copy of a hosted mailbox. Those contents deserve the same access controls applied to other confidential client records.
A quarterly review can reveal orphaned archives before a laptop is retired. It can also identify files that belong to former staff, folders that were never migrated, and backups that exist but haven't been tested. The exact schedule should match the firm's risk, retention obligations, and change rate.
The safest setup separates three responsibilities. Outlook needs a stable local working file. The firm needs an independent, recoverable backup. A manager or administrator needs documented ownership and access rules. When those responsibilities are clear, a failed laptop becomes a recovery task rather than a records emergency.
Cloudvara helps businesses host Microsoft applications and access company data files through a managed cloud environment, which can support firms moving away from isolated desktop storage. Review your Outlook file inventory, backup requirements, and migration plan, then visit Cloudvara to discuss a setup that fits your accounting, legal, or small business workflow.
