What is an OST File Used for in Outlook?

You may have spotted a large .ost file on your PC and wondered what it does. It is not junk and it is not a backup you made. Outlook created it on its own. It has a clear job.

This guide answers what an OST file is used for in plain terms first. Then, later on, it goes deeper than the usual explainer, into what the file actually holds and why that matters for recovery and investigation.

What is an OST file?

OST stands for Offline Storage Table. It is a single file that holds an offline copy of your email mailbox on your computer. Outlook makes it and keeps it up to date in the background, so you rarely notice it is there.

The key idea is that the mail does not live in the OST. It lives on the mail server. The OST is a copy that sits on your PC so Outlook stays fast and keeps working when the connection drops. Think of it as a local mirror of what is on the server.

What is an OST file used for?

An OST file is used for three main things. Each one is about making your mail faster and more reliable, not about storing the only copy.

• Offline access. You can read old mail, write replies and update your calendar with no internet. Outlook sends the queued changes once you are back online.
• Speed. Outlook reads from the local copy instead of fetching every item from the server, so the app feels quick even with a big mailbox.
• A buffer against outages. If the server is slow or down for a while, your mail is still right there to read, because it is cached on your disk.

So the OST is a working cache, built for offline use and speed. It is not meant to be moved around or treated as your backup, which is a common mix-up we clear up further down.

Which accounts make an OST file?

Outlook does not make an OST for every account. It makes one when the mail lives on a server that it needs to cache. That covers most modern setups.

• Exchange accounts
• Microsoft 365 accounts
• IMAP accounts
• Outlook.com accounts

POP accounts are the exception. POP downloads mail and stores it in a PST file, not an OST, because there is no server copy to cache. So if you only ever see a PST, you are likely on a POP account.

What is the difference between OST and PST?

People mix up these two files all the time. Both are Outlook data files, but they do opposite jobs. This is the difference that trips most users up.

The short version is simple. A PST is your file to keep. An OST is Outlook’s copy to work from. That is why a PST imports into any Outlook in minutes, while an OST will not open on its own.

Where is the OST file stored?

The OST sits in a hidden folder, which is why most people never find it. On Windows 11 and Windows 10 the default path is below. Paste it into the File Explorer address bar.

C:\Users\<YourUsername>\AppData\Local\Microsoft\Outlook\

The AppData folder is hidden by default, so turn on hidden items in the View menu if the folder looks empty. One note for newer setups: the new Outlook for Windows does not make a classic .ost file at all. It keeps its local copy in a folder named Olk instead.

What happens when an OST file goes wrong?

Because the OST depends on the server link, problems show up when that link breaks. Two cases are common. Each has its own fix.

The first is an orphaned file. If the profile is deleted, the account is removed or the server goes away, the OST loses its link and Outlook can no longer open it. You can still get the data out. Our guides on opening an orphaned OST file in Outlook and accessing an OST file without Exchange walk through it.

The second is a damaged file. A power cut, a virus or a bad sync can corrupt the OST so it will not load. An OST recovery tool repairs the file. You can then convert it to a PST. If you only want to read what is inside, you can open the OST without Outlook in a free viewer.

What is really inside an OST file?

Most articles stop at “it is an offline cache.” That is true, but it misses what makes the OST interesting once you build tools for it and use it in investigations. The next part goes under the hood. It is more technical, so it is here at the end for readers who want the depth.

Does an OST file use the same format as a PST?

An OST file uses the same internal format as a PST, the one Microsoft documents in the [MS-PST] file format spec. That spec covers both files. The main difference is that an OST also carries sync data that links it to a server mailbox, which a plain PST does not have.

Inside, the file is built in three layers. At the bottom is the node database, which stores the raw blocks of data and uses two sorted indexes, called B-trees, to find any block fast. The middle layer turns those blocks into lists, tables and properties. The top layer reads all of that as the folders, emails and attachments you recognise. When we build a reader, we walk the bottom index to find every folder and message, then pull the properties for each item. That is how a tool rebuilds your full folder tree without ever touching Outlook.

Is an OST file encrypted or password protected?

An OST file is not protected by a password you can type. The items inside are scrambled with one of the simple encoding methods the format defines, which Microsoft names permute and cyclic. A reader that knows the format simply undoes the scramble. This is why a viewer can show your mail with no password and no Exchange. It is also why “set a password to open my OST” is not a thing. The protection was never on the file, it was on the account link.

How big can an OST file get?

The format comes in two builds. The older ANSI build tops out at 2 GB and does not handle every language well. The modern Unicode build is what current Outlook makes. It scales to large mailboxes, with a default cap near 50 GB that an admin can change. This matters in practice because a file pushing its size limit is the single most common cause of corruption we see. A 49 GB OST is a corruption waiting to happen, so size management is not busywork.

What can an OST file reveal in an investigation?

An OST file can reveal a lot in an investigation, because it is a local copy that syncs on a delay and often holds things the live server no longer does. That makes it valuable far beyond simple offline access.

• Mail the server already dropped. A message deleted or aged off the server can still sit in the cached copy until the next sync prunes it. Sometimes the OST is the last place a deleted message exists.
• Deleted item traces. Items in the Deleted Items folder and the recoverable area can persist in the file. Even hard-deleted items may leave traces in unused blocks until those blocks are written over.
• Full message headers. Each email keeps its internet headers, the Received chain that shows the path a message took and the time at each hop. That is how you confirm a real sender or spot a faked address.
• Several timestamps per item. The format stores sent, delivered, created and last-modified times for an item. These can back up or break a claimed timeline.
• Proof it was a real cache. An OST carries sync markers tying it to one server mailbox, which shows it is a genuine cache and not a file someone built by hand.

Does the new Outlook use OST files?

The new Outlook for Windows breaks this pattern. It does not build a classic .ost file. It keeps its local copy in a different store under a folder named Olk, in a different layout. So the format above describes classic Outlook, which is still the source of almost every .ost file you will run into today. Microsoft covers how the older cache works in its guide to Cached Exchange Mode.

Final word

So an OST file is used to keep a fast, offline copy of your server mailbox, nothing more in normal use. The real copy stays on the server, which is why the OST is a cache and not a backup. Knowing that one fact saves a lot of confusion when the file goes orphaned or fills up.

Look closer and the same file is also a detailed record of your mail, right down to headers, timestamps and items the server has already forgotten. Now that you know what is really inside, what do you need from your OST next, a quick read or a full recovery?