When Outlook Creates an OST File

Microsoft Outlook creates an Offline Storage Table (OST) file to keep a local, synchronized copy of mailbox data for several account types, including Microsoft Exchange Server accounts, Microsoft 365 mailboxes, Outlook.com accounts, and IMAP accounts. For Exchange and Microsoft 365 accounts, this local file is maintained through Cached Exchange Mode; IMAP accounts can also generate an OST file in current versions of classic Outlook, but through a separate mechanism — Cached Exchange Mode itself is an Exchange/Microsoft 365 feature and does not apply to IMAP. In each case, the OST file acts as a local mirror of the mailbox stored on the server, letting Outlook display folders, emails, calendar items, and contacts even when the connection to the mail server is temporarily unavailable.

Understanding the exact conditions that trigger OST creation helps administrators diagnose profile issues, plan mailbox migrations, and recover data when the original mailbox becomes inaccessible. Tools such as the EdbMails OST to PST Converter are frequently used at this stage, since orphaned or disconnected OST files cannot be opened directly in Outlook once their parent mailbox is deleted or moved.

OST Creation During Initial Profile Setup

An OST file is generated automatically the first time a user adds an Exchange or Microsoft 365 account to an Outlook profile. During this process, Outlook uses Autodiscover to locate the mailbox server settings, authenticates the user, and then downloads a synchronized copy of the mailbox structure to the local machine.

This first synchronization can take anywhere from a few minutes to several hours, depending on mailbox size and network bandwidth. Outlook does not wait for the full download to finish before becoming usable. It creates the OST file immediately and populates it progressively, which is why newly configured profiles sometimes show incomplete folder contents for a short period after setup.

Cached Exchange Mode as the Primary Trigger

Cached Exchange Mode is the setting responsible for most OST file creation. When this mode is enabled — currently the default when an Exchange or Microsoft 365 account is added to classic Outlook — the client maintains a local copy of the mailbox rather than querying the server for every action.

Disabling Cached Exchange Mode switches the profile to Online Mode, where Outlook reads and writes directly to the server and no OST file is used for that account. Re-enabling Cached Exchange Mode later typically prompts Outlook to build a new local cache and resynchronize from the server; whether the previous OST file is removed as part of that mode change can depend on the Outlook version and configuration.

Administrators managing bandwidth-sensitive environments sometimes toggle this setting through Group Policy, and each toggle back to cached mode results in a fresh synchronization cycle.

OST Files for IMAP Accounts

In current versions of classic Outlook, IMAP accounts can generate an OST file to store synchronized mailbox data locally, giving IMAP users offline access similar to what Exchange and Microsoft 365 users get through Cached Exchange Mode. This is a separate mechanism from Cached Exchange Mode itself, which applies only to Exchange and Microsoft 365 accounts.

The underlying synchronization logic differs from Exchange, since IMAP does not support the same set of folder and item types, but the file format and local storage behavior are otherwise consistent with Exchange-based OST files.

Where Outlook Stores the OST File

By default, Outlook places the OST file in the following path on Windows:

C:\Users\\AppData\Local\Microsoft\Outlook\

The file name typically matches the primary SMTP address of the mailbox, followed by the .ost extension. When a user connects to more than one Exchange or Microsoft 365 account within a single Outlook profile, each account receives its own separate OST file in the same folder. Shared mailboxes added in Outlook, as well as delegated mailboxes opened through Cached Exchange Mode, may also generate their own OST files depending on client version and configuration.

Events That Cause Outlook to Recreate an OST File

Several scenarios beyond initial setup cause Outlook to generate a new OST file:

• Adding the same account to a new device or profile: Each Outlook profile maintains its own OST file, so moving to a new computer or creating a new profile on the same machine triggers a fresh download.
• Deleting or renaming the existing OST file while Outlook is closed: Outlook detects the missing file on the next launch and rebuilds it from the server copy.
• Repairing a corrupted Outlook profile: Recreating a profile, or deliberately deleting or renaming the OST as part of a repair, can lead Outlook to build a new local cache. The Mail applet in Control Panel and Outlook's own account-repair options don't always follow the same path, so treat this as a common outcome rather than a guaranteed one.
• Changing the Exchange or Microsoft 365 mailbox's Autodiscover configuration: such as after a mailbox move between servers or databases — this doesn't automatically force a new OST, but in some cases it can lead Outlook to re-establish the connection and rebuild local cache data.

When Outlook creates a replacement cache, it treats that file as a synchronization target tied to the current account and profile. The old file may remain on disk in some scenarios, but it is not a portable mailbox file and should be preserved separately before profile removal if it may contain unique local data.

OST Files and Server Disconnection

An OST file is associated with the account and profile it was synchronized from, and isn't designed as a standalone portable file. If the mailbox is deleted from the Exchange or Microsoft 365 environment, the OST file can become orphaned and Outlook can no longer open it directly, since there is no active mailbox connection for it to reconcile against. Removing the Outlook profile itself is a different situation — Microsoft documents that removing a profile can remove its offline cached data along with it, so the OST isn't guaranteed to survive as a recoverable orphaned file in that case. Preserve a copy of the OST before removing a profile if you might need the local data later.

This scenario comes up often during offboarding, server migrations, or account deletions performed before a local backup of the data was taken. The OST file may still contain a substantial portion of mailbox data on disk, depending on cache settings and how recently it synchronized — it typically won't include Online Archive or other server-only content that was never cached locally. Outlook's synchronization engine requires an active, matching Exchange or Microsoft 365 connection to render that data.

When a Disconnected OST File Needs a Different Kind of Fix

Once an OST loses its usable connection to the source mailbox, Outlook cannot normally attach it as a standalone file. The amount recoverable depends on what was cached, whether it had synchronized, and the condition of the file; do not assume every expected item is present.

This is the one trigger condition on this page that Outlook itself can't resolve by rebuilding the file, there's no server-side mailbox left to rebuild from. Converting the file to PST is one standard way to make that data usable again, since a PST file doesn't depend on any live server connection and can be opened directly in Outlook on any profile — though migrating the recovered data directly into a Microsoft 365 or Exchange mailbox is also possible and skips the PST step entirely. EdbMails OST to PST Converter Tool is built specifically for this scenario: it reads the OST file's internal structure directly, independent of the original Exchange or Microsoft 365 connection, and exports emails, calendar items, contacts, and folder hierarchies into a standard PST file or migrates them directly to a live mailbox.

This applies whether the original mailbox has already been deleted, the user account has been deprovisioned, or the OST file was recovered from a decommissioned machine with no corresponding server access, situations where Outlook itself would otherwise report the file as completely inaccessible.

EdbMails can scan and preview the preserved OST without the original Outlook profile. Outlook with a configured profile is required for PST export; direct migration to Exchange or Microsoft 365 does not require Outlook.

  See the guide on how to convert OST to PST to recovering a disconnected OST file.

Conclusion

OST file creation in Outlook is governed by a consistent set of rules rather than random behavior. The file is generated whenever a mailbox is configured for cached or offline access, rebuilt whenever the local cache is invalidated by profile changes or repairs, and treated as a mailbox-specific artifact tied to a particular Exchange, Microsoft 365, or IMAP connection. Recognizing these triggers makes it easier to anticipate resynchronization delays, plan for storage requirements on client machines, and identify when a local file has become disconnected from its source mailbox.

---

Additional resources:

• Outlook Cached Exchange Mode
• Rebuild OST File in Outlook
• Recover Orphaned OST File
• Recover Outlook mailbox from OST file
• Recover password-protected OST file
• Recover archived mailbox from OST
• Export shared mailbox from OST