When Outlook Creates an OST File
Microsoft Outlook creates an Offline Storage Table (OST) file the moment a mailbox is configured to work in an offline or cached mode. This applies to Microsoft Exchange Server accounts, Microsoft 365 mailboxes, and, since Outlook 2016, IMAP accounts as well. 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, which is the default for new Exchange and Microsoft 365 profiles since Outlook 2010, 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 prompts Outlook to rebuild the OST file from scratch, since the previous file is deleted along with the mode change.
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
Before Outlook 2016, IMAP accounts stored their local data in a PST file. Starting with Outlook 2016, Microsoft changed this behavior so that IMAP accounts also generate an OST file. This shift aligned IMAP account handling with Exchange-style caching and synchronization, giving IMAP users the same offline access benefits that Exchange and Microsoft 365 users already had.
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\
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: The Mail applet in Control Panel, or the account settings repair option within Outlook, removes the damaged OST file and recreates it during the repair process.
- Changing the Exchange or Microsoft 365 mailbox's Autodiscover configuration: such as after a mailbox move between servers or databases, which can force Outlook to re-establish the connection and rebuild local cache data.
In each of these cases, the previous OST file is not reused. Outlook treats the rebuilt file as a new synchronization target tied to the current server-side mailbox state.
OST Files and Server Disconnection
An OST file remains tied to the mailbox it was synchronized from through a set of internal identifiers, including the mailbox GUID. If that mailbox is deleted from the Exchange or Microsoft 365 environment, or if the Outlook profile referencing it is removed, the OST file becomes orphaned. Outlook can no longer open it directly, since there is no active mailbox connection for it to reconcile against.
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 itself may still contain complete mailbox data on disk, but 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 file loses its connection to the source mailbox, whether the mailbox was deleted, the account deprovisioned, or the machine decommissioned before the file was backed up, Outlook has no way to open it directly. The data itself isn't gone, it's still there in the file's internal structure, but Outlook's synchronization engine requires an active, matching mailbox connection to render it, and a disconnected file no longer has one.
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 the standard way to make that data usable again instead, since a PST file doesn't depend on any live server connection and can be opened directly in Outlook on any profile. 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.
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.
See the step-by-step guide 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 B machines, and identify when a local file has become disconnected from its source mailbox.
