Browser app · Nothing to install

Free Online OST Viewer

Read a disconnected Outlook cache without the account that made it. No Exchange, no profile, no install.

Built by OnlinePCApps, Outlook formats since 2013

Stays on your disk No sign-in No Exchange needed Any operating system
0
Bytes off device
<1s
To the folder tree
Caches opened daily
$0
Price, permanently
Why the file will not open

When Outlook Says It Is Not an Outlook File

That error message is where most people start. Here are the three routes that lead to it.

The Account Behind It Is Gone

Exchange was decommissioned, the tenant was closed or the mailbox was deleted. Outlook now answers with an error saying the file is not an Outlook data file.

Reads the store on its own terms, because it needs no account to point at.

A Leaver's Laptop Came Back

A deprovisioned account left a cached mailbox behind on a returned laptop, and somebody has to establish what was in there before the disk gets wiped.

Opens the cache read only, so nothing about the disk changes during review.

It Is Not a Windows Machine

Every tool for this job is a Windows executable, and the file has landed on a Mac, a Linux box or a locked-down laptop.

Runs in the browser, so the operating system stops being part of the problem.
How it works

Read an OST File in 3 Steps

instant OST

Locate the Offline File

OST files sit under AppData Local Microsoft Outlook. Drag the one you want onto the panel and it opens where it lies.

instant

Open the Folder Tree

The cached hierarchy appears as it stood at the final sync. Mail, contacts and calendar all list together.

instant

Lift Out What Matters

Save an attachment, write an item out as EML or print it. No profile is created and nothing is registered on the machine.

The last synced tree Folders exactly as they stood at the final sync
Drafts never sent Queued mail that reached the disk but not the server
Attachments Pulled out per item with nothing behind a paywall
Open an OST File Free, and nothing to register Look at the Desktop Build When a cache runs to 50 GB
The online app

An OST Reader That Is Not a Windows App

Search for a way into a cached mailbox and every answer is an installer for Windows. That is the gap this fills.

On Your Phone

A small cache opens fine. Anything into the gigabytes will exhaust a handset first.

On a Tablet

No tablet has ever shipped anything that reads a cached Outlook mailbox.

On a Locked-Down Laptop

Where policy forbids installing software, the browser is still there and still enough.

On Someone Else's PC

Nothing written to their disk and no profile registered. Shut the tab and it is finished.

The OnlinePCApps OST Viewer is a free browser-resident reader for Outlook offline data files. It rebuilds the cached folder tree from a .ost that no longer has an account behind it, shows mail beside the address book, the diary, tasks and notes, and asks for no Exchange connection, no Outlook profile and no upload. When a cache outgrows the memory a single tab can spare, the desktop build carries it.

Where the file came from

What Makes Outlook Write an OST at All

Four account types produce one, and only one of them is the Exchange setup everybody assumes.

Cached Exchange Mode

The classic source. Outlook holds a MAPI profile against the server and mirrors the mailbox locally so it keeps working when the network does not.

Microsoft 365

Exchange Online caches in exactly the same way, and Outlook.com accounts do too. The file is still an OST long after the tenant has gone.

IMAP Accounts

Outlook 2013 onward writes an OST rather than a PST for IMAP too, which surprises people who expected a PST.

Shared and Delegate Mailboxes

Anything a profile has permission to open gets cached beside the primary account.

Against the field

This OST Viewer vs a Windows Download

Every OST tool on the first page of results is an executable you have to install. That is a fair approach, and it is not free of cost either.

What differs This page This page Runs in your browser A typical desktop OST tool Installs a binary on your machine
Operating system Windows, macOS, Linux Windows only, without exception
Installation None at all A download and an installer
Admin rights Not needed Usually needed to install
Exchange connection Seconds Download, install, then scan
Outlook profile Nothing Nothing, but you installed their binary
What reaches a server Never created Never created either
Time to first folder Windows, macOS, Linux No
Removing it afterwards Close the tab Uninstall and clear the leftovers

That covers how the category behaves rather than singling anyone out. Several of those tools are good at what they do.

Privacy

Your OST File Never Reaches Us

An abandoned cache is rarely your own correspondence. It usually belongs to somebody who has left, and reading it is already a decision that deserves care.

So nothing here collects one. No endpoint accepts a mailbox, no component runs on our side, and no record exists that you opened anything at all. Open the browser network view and drop a file in if you would sooner confirm that than accept it.

$ Browser network view, 12 GB cache loading
external requests ....... 0
the cached store ....... 0 requests
0
Bytes leaving
0
Logins needed
0
Caches retained
0
Trackers running
Inside an OST

What an OST File Holds and Why

An OST was built to be a cache rather than an archive, and almost everything awkward about one follows from that single design choice.

PartHeaderWhat it holds
Purposeoffline cacheAn OST mirrors a server mailbox so Outlook keeps working with the network down. It was never meant to be a portable archive.
Profile bindingentry ID and accountThe file records which profile and which account created it. That binding is why Outlook refuses a file it did not make.
Underlying layoutsame node databaseStructurally an OST is built the same way a PST is: a B-tree of nodes beneath a property store. It is not a separate format at all.
Sync stateper-item change keysEvery item carries the change key it had at the last sync, which is how Outlook knew what still needed sending.
Cached rangesync slider settingOutlook only caches as far back as the profile told it to. Anything older than that window was never written to disk.
Unsent itemslocal-only nodesDrafts and queued mail that never reached the server exist only here. When the account goes, they go with it unless the file is read.
Deleted itemsretained nodesItems removed from the folder view often survive in the store until the file is compacted, which is why triage tools look here.
Encryptioncompressible or highThe same optional obfuscation Outlook applies to a PST. It scrambles the bytes on disk and stops no reader that understands it.
Item classesIPM.Note and the restIPM.Contact, IPM.Appointment and the rest sit alongside IPM.Note, because this is a mailbox rather than a mail file.
Size ceiling50 GB by defaultUnicode files have a configurable ceiling in the registry. Long-serving cached mailboxes reach it more often than people expect.
Alternatives

Other Ways to Open an OST File

Four other routes exist. Each works in the right circumstances, and each asks for something the person holding an orphaned cache usually does not have.

Reconnect the Original Profile

Outlook will open an OST only when the profile and account that created it still exist.
Recreate the account with the same address and Outlook may adopt the existing cache.
Once the mailbox is deleted on the server side this route closes for good, and recreating an account can trigger a resync that overwrites the cache.

Export From a Live Mailbox

If the mailbox still exists open it in Outlook and export to PST rather than touching the OST.
This is the supported path and Microsoft documents it properly.
It only works while the account is alive, which is precisely not the situation most people are in.

Convert It to PST First

A converter will write the store out as PST, MBOX or EML for another client to import.
The result then opens in Outlook, Thunderbird or anything else.
A conversion is a rewrite. For anything that might be evidence, reading the original is the safer move.

Restore From Backup

Exchange or Microsoft 365 backups may hold the mailbox itself rather than the cache.
An admin can usually restore to a recovery mailbox and export cleanly from there.
It needs a backup that was actually taken, an admin with time, and a retention window that has not already closed.

Check the Header Before Anything

Look under AppData Local then Microsoft Outlook, which is where the file lives, and its first bytes declare whether it is ANSI or Unicode. That single field explains a surprising number of failures.

Knowing the variant tells you why Outlook baulked. It still will not get the mail out.

Look for the Archive Beside It

Look under Documents then Outlook Files, which often holds a separate PST containing everything AutoArchive moved off the server. The cache and the archive together are usually the whole picture.

The two files overlap unpredictably, so neither one on its own can be assumed complete.
Desktop edition

When an OST File Grows Past the Browser

One tab holds only so much. The desktop build takes the caches that sit above that line.

What the Desktop Build Adds

Resolving the tree means holding the store in memory. For a cache of a few gigabytes that is fine. A mailbox that has been cached for a decade and sits near its 50 GB ceiling is a different proposition, and a phone reaches its limit far sooner than a laptop.

Working through the file in chunks straight off the disk is the desktop approach, and it takes size out of the conversation.

Online viewerheld in memory
Desktop toolread from disk
Never connects

Nothing leaves the machine once it is installed, which is what isolated networks and evidence rooms require.

Past the memory ceiling

A long-serving cached mailbox at the 50 GB mark streams from disk rather than sitting in RAM.

Every store at once

Point it at a folder of recovered caches and move between them instead of opening one file at a time.

Made for oversized caches

A whole shelf of recovered caches, queued past what one tab could hold.

Search across the cache

Locate an item anywhere in the tree by sender, date or body rather than folder by folder.

Export in bulk

Write a whole store out to PST, MBOX, EML or PDF in a single pass.

See the Desktop Build Free trial · Windows 10 and later $39 flat · no renewal · 30 days to change your mind
Questions people ask

Questions About Orphaned OST Files

The OnlinePCApps OST Viewer runs inside the browser and reads Outlook offline data files. Given an OST whose account has gone, it rebuilds the cached hierarchy and surfaces everything held in it. No Exchange connection is opened, no profile is created, and nothing at all is transmitted.
OST stands for Offline Storage Table. Outlook writes one to keep a local mirror of a server mailbox so that mail, contacts and the calendar stay usable when the connection drops. It is a cache by design rather than an archive, which is what makes an abandoned one awkward.
Because the file records the profile and account that created it, and Outlook checks that binding before it will mount anything. Point it at a file from a different profile and it answers that the file is not an Outlook data file. That refusal is deliberate, not a fault.
It means the mailbox the cache mirrored no longer exists or is no longer reachable: a decommissioned server, a closed tenant, a deleted account. The local file survives intact while the only thing that could authorise opening it has gone.
Yes, and the free part covers everything. Reading, opening attachments, writing an item out and printing are all included. No scan limit, no watermark, and no upgrade prompt appearing precisely when you try to keep hold of something.
No. The store is worked through by your own browser, on the disk where you found it. There is no endpoint here that could take delivery of a mailbox. Prefer to see it? Leave the browser network view open while the file loads.
Neither. At no stage does anything here speak to a mail server. Whatever the cache captured is already on disk, and that is all this reads.
No. There is no profile to configure and no Office installation involved. That matters because the usual advice for this problem starts with owning Outlook, which is not much help to somebody who does not.
Yes. The awkwardness is that this whole category ships as Windows executables, so a cache landing on a Mac leaves people stuck. Chrome, Firefox, Safari and Edge all run this equally well, which is what puts macOS, Linux and ChromeOS back in play. Android and iOS work too, though a large cache will finish a handset first.
Yes. Drafts and queued mail that reached the disk but never the server exist only inside the cache. When the account disappears those items exist nowhere else, so reading the file is the only way to recover them.
Yes. Caching covers the mailbox rather than the inbox, so the address book, the diary, outstanding tasks, notes and journal entries are all in there with the mail, and all of them appear.
What Outlook keeps is a hash, not the password, and the check happens in Outlook rather than in the file. So a password on a cached mailbox restricts one program and nothing else, which is worth knowing before anyone relies on it.
That turns on where the damage sits. Because everything hangs off a tree, one bad node can take a whole branch out of reach while the rest resolves perfectly. You are shown what resolves and told where it stops. No repair is attempted and no gap is filled in with guesswork.
It does not. Everything happens in a read-only pass with no write path at all, leaving the bytes untouched. When the machine came back from somebody who has left, that distinction separates looking from meddling.
Nothing is tiered and nothing is artificially capped. What binds you is how much memory the machine has, since resolving a tree means holding the store. Caches of a few gigabytes present no difficulty. One that has crept up towards its 50 GB limit wants the desktop build.
It fits early review, whether that is a legal hold, an internal audit, a compliance check or formal discovery. The file opens read only and is not transmitted, so the copy you are holding remains the sole one. Forensic triage tends to turn on full folder paths and per-item properties, and both are visible.
Outlook 2013 changed this. Before it, IMAP accounts got a PST. Since then they get an OST instead, which catches out anyone who goes looking for a PST that was never created.
Different tool for that. The OST Converter writes a cache out to PST, MBOX, EML, EMLX, MSG, HTML, PDF or CSV, and sends address book and diary entries to VCF and ICS respectively.
They sit inside your user profile at AppData Local Microsoft Outlook. If you would rather not guess, Outlook prints the exact path under Account Settings on the Data Files tab.
Nothing in the file can run on its own. Every item renders inside a sandbox, scripting switched off and outside image fetches refused, so a mailbox belonging to someone else stays silent while you go through it.
Who wrote it

Who Built This OST Reader

OnlinePCApps Formats Group

Outlook offline formats since 2013

Prepared and checked by
13
Years at this
110
Browser tools live
3
Microsoft specs used
0
Test caches held

Desktop migration software was the first thing this company built, back in 2013. Pulling a cached mailbox apart by hand came with that territory long before a browser could manage the same trick. The same logic now runs as JavaScript on this page: resolve the nodes, read the properties, rebuild the cached hierarchy and draw each item, with nothing leaving the machine at any point.

Documents we build against

MS-PST · Store layout MS-OXOSFLD · Special folders MS-OXCFXICS · Sync state FileReader API TextDecoder

What it is tested on

Real caches taken from Exchange, Microsoft 365 and IMAP profiles, never generated ones Files whose originating account no longer exists anywhere Add-in properties numbered inside one mailbox rather than globally Caches holding contacts, appointments, tasks and notes as well as mail Stores left half written when a machine was shut down mid sync Rerun on every browser release before the app goes out
Spotted a cache we misread? Send it across and we will look.

That OST File Outlook Will Not Open

Hand it over and the hierarchy comes back. No Exchange, no profile, and the disk is untouched.

Open an OST File Free, no account Look at the Desktop Build For caches past one tab
Open OST File · Free