Classic Outlook uses PST and OST files for data storage

Classic Outlook uses PST and OST files for data storage.

That is the short answer. Classic Outlook keeps mail in two main file types. A PST file is a local data file. An OST file is an offline copy of a mailbox that stays in sync with the server when the account uses Exchange, IMAP, or Outlook.com.

I like that this sounds simple, because the part people miss is just as simple. The file type depends on the account type. A POP account usually stores all its mail in a PST file. A server-based account usually uses an OST file for day-to-day work. The mailbox still lives on the server in that case, while Outlook keeps a local copy on the PC.

That matters when a move or repair goes sideways. If the data is in a PST file, the file itself is the container. If the data is in an OST file, the file is more like a working copy. It can be rebuilt in some cases, but that is not the same as saying every problem is easy. Outlook has a habit of making simple things look tense.

What the reader really needs to know

The main fact is this: classic Outlook does not store mail in one single way for every account. It uses PST for local storage and archives, and OST for synchronized mailbox data.

A PST file can hold mail, contacts, calendar items, tasks, notes, and other Outlook items. It is often used for backup or for older mail that sits on the computer. An OST file is tied to a mailbox that syncs with a server. It lets Outlook work even when the connection is weak or gone for a while.

That difference is the key to most migration questions. People often expect one file to act like the other. It usually does not. A PST file can be opened and moved around as a file. An OST file is more tied to the account that created it.

That is why a failed export is not always a mystery. Sometimes the export was fine, but the wrong file was chosen. Sometimes the account type was not what the person thought it was. Sometimes the mail is still on the server, and the local file was only a cache. That is a small detail with a large mood.

Why this keeps showing up in migrations

Classic Outlook is old enough to be useful and fussy at the same time. It gives clear file storage, but the rules change with account type. That is where many moves start to wobble.

If the goal is to back up mail, a PST file is the familiar target. If the goal is to restore a mailbox view for an Exchange or IMAP account, the OST file may still matter, but in a different way. The OST is not usually the final record. It is the working copy that Outlook builds from the server.

I think this is the point where people want a neat universal rule. Outlook does not really offer one. The rule is close enough for daily use, but not neat. A POP account leans on PST. A synced account leans on OST. The mailbox owner often sees only Outlook on the screen and misses the file beneath it.

That is also why a mailbox can seem gone when it is not. If the OST is damaged, Outlook may fail to show the local copy. If the server copy is still healthy, the data may return after the account is rebuilt. If the PST is damaged, the local file itself may need repair before the items can be read again. Same app. Different problem.

The one caveat worth keeping in view

There is one honest limit here. The file type tells you a lot, but not everything. Requirements can change with Outlook version, account type, and sync settings over time.

So the label on the file is useful, but it is not the whole story. A PST file can hold a lot, but not every setup uses it the same way. An OST file can be recreated in some cases, but that does not help if the real problem is deeper, like bad data in the mailbox or a broken profile. The format explains the shape of the problem. It does not promise the fix.

That is where patience saves time. Check whether the account is local or synced. Check whether the file is PST or OST. Check whether the mailbox still lives on the server. Those three facts usually tell the truth faster than hope does.

What I keep coming back to is the same plain answer. Classic Outlook uses PST and OST files for data storage. PST is the local file people can open, move, and often back up. OST is the synced copy Outlook builds for server-based accounts.

If a migration is the job, the file format is the map. Get that part right, and the rest gets less noisy. That is the kind of small truth The Migration Brief tries to keep handy: one practical fix, one file format explained, and one safer way to move your mail.