How to Open OST Files in Different Versions of Outlook

An Outlook OST file is an Offline Outlook Data File that stores a synchronized local copy of mailbox data for certain Exchange, Microsoft 365, Outlook.com, and IMAP-style account configurations. It allows Outlook to keep working when the computer is temporarily offline and then synchronize changes when the connection returns.

One of the most common misunderstandings is that an OST file can be opened or imported the same way as a PST file. It cannot. Microsoft’s current support documentation explains that an OST is generally a local synchronized cache associated with an Outlook profile and server mailbox. If the OST is lost or damaged while the mailbox still exists on the server, Outlook can usually create a new one by synchronizing the mailbox again.

A PST file is different. PST files can be used for exports, archives, and data that can be opened or imported into supported Outlook versions. That distinction is why instructions that say “open Import/Export, choose PST, browse to the OST, and import it” are incorrect.

This guide explains what OST files are, how they differ from PST files, how Outlook uses them, what to do when you have access to the original mailbox, what to do with an orphaned OST, how to export mailbox data to PST correctly, and when a third-party OST to PST Converter may be considered.

What Is an OST File?

OST stands for Offline Outlook Data File.

When cached mode is used with a supported account, Outlook keeps a local copy of mailbox content such as:

email;
folders;
calendar items;
contacts;
tasks;
notes in supported configurations; and
other synchronized mailbox data.

The main mailbox remains on the mail server. The OST is designed to help Outlook work quickly and support offline access.

What Is a PST File?

PST stands for Personal Storage Table, commonly shown in Outlook as an Outlook Data File (.pst).

PST files can be used for:

exporting mailbox data;
archiving mail;
moving data between certain Outlook profiles;
storing local-only Outlook content; and
opening historical email data in classic Outlook.

Unlike an OST, a PST is intended to function as a portable Outlook data file.

OST vs. PST

Feature	OST	PST
Main purpose	Offline synchronized mailbox cache	Portable/archive/export data file
Usually tied to profile/account	Yes	No in the same way
Can be opened directly through Outlook data-file commands	Not generally	Yes in supported classic Outlook
Can normally be recreated from server	Yes, if mailbox still exists	No, if PST is the only copy
Typical backup priority	Lower when fully synchronized with server	High if it contains unique local data

Why Outlook Creates an OST File

Without local caching, Outlook would need to retrieve more mailbox data over the network every time you open a folder, search recent messages, or review previously synchronized content.

The OST improves usability by allowing much of that work to happen locally.

When the computer reconnects, Outlook synchronizes local changes with the server.

Can You Double-Click an OST File to Open It?

Normally, no.

An OST is not intended to be opened as an independent portable mailbox file. Outlook expects it to belong to a specific account/profile configuration.

If you locate an old OST in a Windows folder and double-click it, Outlook will not treat it like a PST that can simply be attached.

Can You Import an OST With the Import/Export Wizard?

No. This is one of the major errors in many old tutorials.

Outlook’s Import/Export Wizard supports PST operations, but it does not provide a normal “import this OST” option.

If you still have access to the mailbox associated with the OST, the correct approach is usually to open the mailbox normally in Outlook and then export the mailbox or selected folders to PST.

Scenario 1: The Mailbox Still Exists and Outlook Opens Normally

This is the easiest situation.

If Outlook can still access the account and the mailbox data you need is visible, you do not need to “convert the OST” directly.

Instead, use Outlook’s export function to create a PST from the accessible mailbox.

How to Export an Accessible Mailbox to PST in Classic Outlook

Microsoft’s exact interface can vary by Outlook version, but the general classic Outlook process is:

Open Outlook.
Select File.
Select Open & Export.
Select Import/Export.
Choose Export to a file.
Select Outlook Data File (.pst).
Select the mailbox or folder you want to export.
Enable subfolders if you need the full hierarchy.
Select the destination path.
Choose the desired duplicate-handling option.
Complete the export.

This exports the mailbox data Outlook can access. It is not importing the OST file itself.

Check Synchronization Before Exporting

If the mailbox is using cached mode, make sure the data you need has synchronized.

Depending on configuration, Outlook may cache only a specified period of email locally, while older mail remains available from the server.

If you export while the computer is offline or before all required folders have synchronized, the resulting PST may not contain everything you expected.

Scenario 2: The OST Is Corrupted but the Server Mailbox Still Exists

If Outlook has synchronization problems or the OST appears damaged but the mailbox still exists on Microsoft 365 or Exchange, the usual solution is not to rescue the OST.

Microsoft treats the OST as a replaceable synchronized copy.

A typical troubleshooting approach may involve:

closing Outlook;
confirming the mailbox works in Outlook on the web where applicable;
repairing or recreating the Outlook profile;
renaming or removing the damaged OST according to supported procedures; and
letting Outlook create a new synchronized OST.

Do not delete a file blindly until you confirm that the server mailbox contains the required data.

Why Rebuilding the OST Often Works

If the server is the authoritative source, the OST is essentially a local cache.

Creating a new cache can resolve problems caused by:

local file corruption;
failed synchronization state;
bad search indexing;
profile configuration problems; and
local cache inconsistencies.

It will not fix a problem where the data no longer exists on the server.

Scenario 3: You Have an “Orphaned” OST

An orphaned OST is an informal term for an OST file whose original mailbox/profile is no longer accessible.

This may happen when:

an employee account was deleted;
an Exchange server was decommissioned;
a Microsoft 365 account was removed;
the organization changed tenants;
the user left the company;
the local profile was lost; or
the mailbox no longer exists but the old computer still contains an OST.

This situation is much more difficult because the normal server relationship is gone.

Can Outlook Open an Orphaned OST Directly?

Generally, no.

Outlook does not provide a supported built-in command for attaching an arbitrary orphaned OST as though it were a PST.

If the original mailbox can be restored by the Microsoft 365 or Exchange administrator, that is usually the cleanest recovery path.

Check Microsoft 365 Retention Before Using Recovery Software

If the account was recently deleted, administrators should first investigate server-side recovery options.

Depending on licensing, retention policies, litigation holds, inactive mailbox configuration, backup systems, and how recently the account was deleted, data may still be recoverable through Microsoft 365 administration.

Do not assume the local OST is the only remaining copy.

Scenario 4: The Employee Has Left the Company

Organizations should have an offboarding process that preserves business records before deleting accounts.

Possible approaches include:

placing the mailbox under appropriate retention;
converting to a shared mailbox where licensing and policy allow;
granting authorized access to another employee;
exporting required records through approved administrative methods;
using eDiscovery or retention tools where appropriate; and
preserving data under legal-hold requirements.

Relying on a laptop’s OST as the company’s offboarding archive is poor records management.

Scenario 5: You Changed Computers

If the mailbox still exists, do not normally copy the OST from the old computer and try to attach it to the new profile.

Configure the account on the new computer and let Outlook synchronize a new OST.

This is cleaner and avoids profile-binding problems.

Where Are OST Files Stored?

The default location depends on Windows and Outlook versions, but Outlook data files are commonly stored within the user profile under an AppData path.

You can use Outlook’s account settings or data-file settings in classic Outlook to identify the active file location rather than guessing.

File locations can also vary in managed enterprise environments.

Should You Back Up OST Files?

Microsoft generally treats OST files as replaceable because they are copies of server data.

If every item is synchronized and the server mailbox is protected appropriately, backing up the OST itself is usually less important than:

server retention;
Microsoft 365 backup strategy;
legal retention;
PST files containing unique data;
local archives; and
other non-synchronized files.

However, before rebuilding an OST during a troubleshooting or recovery case, confirm whether it might contain unsynchronized local changes.

What About Unsynchronized Items?

If Outlook had local changes that never reached the server, rebuilding the OST could remove the only local copy of those changes.

Examples might include:

messages composed or moved while offline;
items stuck in synchronization conflicts;
local changes made shortly before account failure; or
content in special local folders depending on configuration.

In a high-value recovery case, preserve a copy of the existing OST before making destructive changes.

PST Export Limitations

Exporting to PST is useful, but it does not necessarily capture every Microsoft 365 feature.

Modern cloud mailboxes may contain information that does not map completely to PST, such as certain online archive configurations, permissions, retention metadata, group content, or other cloud-specific features.

PST is an email-data format, not a full Microsoft 365 tenant backup.

Classic Outlook vs. New Outlook

Microsoft continues to develop the new Outlook for Windows alongside classic Outlook.

Some data-file operations historically associated with classic Outlook may not behave identically in new Outlook, and support for PST capabilities has been evolving.

If a recovery or export workflow depends on a specific feature, check the current Microsoft support page for the Outlook version you are actually using.

How to Open a PST in Classic Outlook

For comparison, a PST can normally be attached through Outlook’s data-file opening commands.

A typical process is:

Open Outlook.
Select File.
Select Open & Export.
Select Open Outlook Data File.
Browse to the PST.
Select it.

The folders then appear in Outlook.

This is the behavior people often mistakenly expect from OST files.

Do Not Rename .ost to .pst

Changing the file extension does not convert the internal data structure or relationship.

Renaming:

mailbox.ost

to:

mailbox.pst

does not create a valid PST.

At best, Outlook will reject the file. At worst, the renaming adds confusion to an already complicated recovery situation.

Do Not Use “Import From Another Program or File” for OST

That wizard is intended for supported formats such as PST and other importable data—not arbitrary OST files.

If a tutorial tells you to choose “Outlook Data File (.pst)” and then browse to an OST, the instructions are fundamentally wrong.

When Third-Party OST Conversion Tools May Be Considered

A third-party utility may be considered when:

the original mailbox is permanently unavailable;
the OST is the only remaining local copy;
server-side recovery has been exhausted;
the organization is legally authorized to access the mailbox data; and
the value of recovery justifies the privacy and technical risk.

Tools in this category attempt to read recoverable content from an OST and export it into PST or other formats.

Evaluate Recovery Software Carefully

Email files can contain highly sensitive data:

customer information;
contracts;
password-reset messages;
financial records;
HR information;
legal communications;
attachments;
health information; and
personal correspondence.

Before using software, check:

where the application was obtained;
whether processing happens locally or in the cloud;
whether the file is uploaded anywhere;
publisher reputation;
code-signing information;
privacy policy;
enterprise licensing;
data retention;
malware reputation; and
whether your organization allows the tool.

Do Not Upload Corporate OST Files to Random Online Converters

An online conversion site may require uploading the entire mailbox file to an unknown server.

For corporate, legal, healthcare, financial, or regulated data, that can create serious confidentiality and compliance problems.

Use only tools and service providers approved by the organization’s security and legal teams.

Encrypted or Protected Mailbox Content

Recovery software may not be able to reproduce all protected content accurately.

Rights-managed messages, modern authentication dependencies, encrypted attachments, damaged records, and cloud-only objects can create limitations.

No legitimate converter should guarantee perfect recovery from every OST.

OST File Corruption Does Not Always Mean the Data Is Lost

If the mailbox remains on the server, local corruption is often a cache problem rather than a data-loss event.

Before purchasing recovery software:

Check Outlook on the web.
Confirm the mailbox is active.
Check whether the data is visible online.
Review Microsoft 365 or Exchange recovery options.
Try a supported profile rebuild.

Use conversion software only when the normal authoritative source is unavailable or insufficient.

What About ScanPST?

Microsoft’s Inbox Repair Tool, commonly called ScanPST.exe, is associated with repairing PST files and certain Outlook data-file issues.

It should not be treated as a universal orphaned-OST conversion tool.

If the active OST is replaceable from the server, rebuilding the cache is generally more aligned with Microsoft’s design.

Large OST Files

Very large cached mailboxes can create performance or synchronization challenges depending on:

Outlook version;
hardware;
number of folders;
item count;
search indexing;
cached-mail duration; and
add-ins.

Organizations can reduce local cache size by adjusting how much mail is stored offline where appropriate, archiving according to policy, or addressing mailbox organization.

Do Not Delete Mail Just to Shrink the OST Without Understanding Retention

Deleting items in cached Outlook normally synchronizes those deletions to the server.

If the goal is only to reduce local storage, use supported cache settings rather than deleting business records accidentally.

Search Problems Are Not Always OST Corruption

If Outlook cannot find messages, the problem may involve:

Windows search indexing;
Outlook search scope;
server search;
profile problems;
cached range;
add-ins; or
actual file corruption.

Diagnose before rebuilding.

How Organizations Should Handle Outlook Data During Offboarding

A better offboarding process includes:

preserving required mailbox data before account deletion;
reviewing legal retention requirements;
removing user access;
transferring business ownership of appropriate information;
preserving shared mail or records;
documenting approvals; and
securely handling local devices.

The OST should be viewed as a cache, not the records-retention strategy.

Recovery Decision Tree

If the mailbox is still active:
Open it normally and export required data to PST if necessary.

If the OST is corrupted but the mailbox is online:
Use supported profile/cache rebuilding after verifying synchronization.

If the mailbox was deleted recently:
Ask the Microsoft 365/Exchange administrator about server-side recovery and retention.

If the mailbox is permanently gone but the OST remains:
Preserve the file and evaluate an authorized specialist recovery tool.

If the data has legal or regulatory significance:
Involve IT, legal, compliance, and information-security teams before altering the evidence.

How to Preserve an OST Before Recovery Work

If the file is potentially the only copy:

Close Outlook.
Do not continue experimenting on the original.
Make a forensic or ordinary working copy as appropriate.
Record the source computer and profile.
Store the original securely.
Perform conversion attempts on a copy.

For litigation or investigations, normal file copying may not meet evidence-preservation requirements. Follow the organization’s legal process.

Common OST Myths

Myth: Every OST must be converted to PST before you can read your mail

False. When the Outlook profile and mailbox are working, Outlook reads the synchronized mailbox through the profile normally.

Myth: Outlook can import an OST through the PST wizard

False.

Myth: Renaming OST to PST converts it

False.

Myth: If the OST is corrupt, the mailbox is lost

False when the server still has the data.

Myth: OST files are ideal mailbox backups

False. They are primarily synchronized cache files.

Myth: Any online converter is safe

False. Mailbox data can be highly sensitive.

Useful Microsoft Resources

Final Thoughts

The safest way to work with OST files is to remember what they are designed for: synchronized offline copies of server mailboxes.

If the original Microsoft 365, Exchange, or other supported mailbox still exists, let Outlook synchronize the account and export required content from the accessible mailbox to PST when portability is needed. Do not try to import the OST as though it were a PST.

If the mailbox is gone and the OST is truly the only remaining copy, recovery becomes a specialized task. Check server retention first, preserve the original file, confirm that you are authorized to access the data, and evaluate reputable local recovery software carefully.

Most importantly, organizations should not depend on OST files for backup or employee offboarding. Retention, backup, eDiscovery, and account-transition processes should preserve important business data before the server mailbox is deleted.