viewhack

PST and OST viewer: open an Outlook .pst or .ost without Outlook

Open the .pst from an old job or an Outlook export, or the .ost Outlook left on a dead Windows PC, on a Mac, a Chromebook or Linux. See the folder tree with how many items each folder holds, list any folder's e-mails by date, sender, subject and size, and read a message's headers and text.

The file is read on your device, a few kilobytes at a time, so a 20 GB .pst opens in seconds. It is never uploaded and never written to.

What works today (slice 1 of 3): the folder tree, each folder's item list, and each item's headers, plain-text body and stored properties. HTML and RTF bodies, recipient addresses, attachments and search come next; calendar, contact and task views and saving as .eml after that. An .ost opens the same way as a .pst.

What it shows

What it cannot do yet

Getting at a .pst

From Outlook on Windows
File › Open & Export › Import/Export › “Export to a file” › Outlook Data File (.pst). Pick the mailbox or one folder and tick “Include subfolders”. Archives Outlook made itself are already .pst files, usually named archive.pst.
Where old files are
Outlook 2010 and later keep them in Documents\Outlook Files. Older versions used C:\Users\you\AppData\Local\Microsoft\Outlook, a hidden folder. On a dead PC's disk, look in both.
From a former job
IT departments often hand over a mailbox as a .pst when someone leaves, or when a Microsoft 365 account is closed. It is the whole mailbox in one file, often several gigabytes.
On a Mac
Outlook for Mac cannot read a .pst from Windows directly (it imports it into an account), and Apple Mail cannot read one at all. This page reads it as it is.

Useful to know about .pst files

What is inside
A .pst is a small database, not a folder of e-mails. It holds two B-trees of 512-byte pages: one maps each item's node ID to its data, the other maps each block ID to where the block sits in the file. Each folder, message and table is built from blocks of up to 8 KB. That is why this page can open a message by reading a few pages and blocks instead of the whole file.
Why the bytes look scrambled
Outlook stores data blocks with “compressible encoding” by default: each byte is swapped through a fixed 256-byte table. Older files may use “high encoding”, a table-based scramble keyed on each block's ID. Neither needs a password; Microsoft publishes both tables in its [MS-PST] specification, and this page decodes them.
.pst and .ost
An .ost is the cache Outlook keeps of an Exchange, Microsoft 365 or Outlook.com mailbox (the server holds the real mailbox); a .pst is a standalone file. Inside they are the same database, except that the header says “SO” instead of “SM”. Since Outlook 2013, Outlook writes a new .ost in a different layout (version 36): 4 KB pages instead of 512 bytes, larger blocks, and blocks that can be compressed with deflate. Microsoft's [MS-PST] specification does not describe that layout. This page reads it as the libpff project's public notes describe it, and decompresses the blocks with your browser's own decompressor. Outlook itself will not open an .ost as a file: it only uses one through the account that created it. This page opens it as a file.
Unicode and ANSI
Outlook 2003 introduced the Unicode .pst (version 23 in the file's header), with 64-bit offsets; Outlook caps it at 20 GB by default in Outlook 2003 and 2007 and at 50 GB from Outlook 2010. The ANSI format before it stopped at 2 GB. The page shows which one your file is.
Size in the list
The size is Outlook's own figure for the item with its attachments, as it would appear in Outlook's Size column, not the space the item takes in the file.

Made with AI tools. · Privacy