Does Outlook 365 Support PST Files? (w/Examples) + FAQs

Yes, Outlook 365 supports PST (Personal Storage Table) files, but with important limits, platform differences, and shifting rules under the New Outlook for Windows rollout. The classic desktop version of Outlook included in Microsoft 365 Apps still reads, writes, imports, and exports .pst files on Windows. The newer cloud-first Outlook client, the web app (OWA), Outlook for Mac, and mobile apps handle PSTs very differently, and some do not handle them at all.

The file format itself is governed by Microsoft’s open MS-PST specification, and its use inside a business is shaped by federal rules like the Federal Rules of Civil Procedure Rule 26, the SEC’s 17a-4 recordkeeping rule, and the HIPAA Security Rule. A PST that sits on a local laptop can fall outside retention, legal hold, and audit controls, which is why Microsoft’s own guidance pushes admins toward online archives. Ignoring these rules can trigger spoliation sanctions, regulator fines, and broken eDiscovery searches.

According to a Microsoft-sponsored Osterman Research study, more than 75% of enterprises still have active PST files somewhere in their environment, even after a decade of cloud migration. That single statistic explains why this question keeps coming up.

Here is what you will learn in this guide:

• 📬 How classic Outlook, New Outlook, OWA, Mac, and mobile each treat PST files
• ⚙️ How to import, export, open, and close PSTs step by step, with menu paths
• 🏢 How admins bulk-migrate PSTs to Exchange Online with the Network Upload method
• ⚖️ How U.S. laws like FRCP, SEC 17a-4, and HIPAA turn PSTs into legal risk
• 🛠️ How to fix corrupt PSTs with scanpst.exe and avoid the top mistakes users make

What a PST File Actually Is

A Personal Storage Table, or PST, is a local database file that Outlook uses to store mail, contacts, calendar items, tasks, and notes on a user’s computer. Microsoft created the format in the 1990s for the original Exchange client, and the current version is called Unicode PST. The file extension is .pst, and each file acts as a self-contained mailbox on disk.

A PST is different from an OST file. An OST (Offline Storage Table) is a synced cached copy of a server mailbox, while a PST is a standalone archive that lives only where you save it. You can move a PST to a USB drive, email it, or copy it to another computer and open it in Outlook, which you cannot do with an OST.

Microsoft documents the binary layout in the public MS-PST Outlook Personal Folders File Format spec. This openness is why third-party tools like Stellar Repair for Outlook and Kernel for Outlook PST Repair can read and rebuild damaged files. The format is open, but the risks of holding business email in a local file are not small.

ANSI vs. Unicode PST

The old ANSI PST format, used in Outlook 97–2002, caps out at 2 GB and is prone to corruption as it fills. The modern Unicode PST, introduced in Outlook 2003, supports much larger sizes and better international character handling. Outlook 365 creates Unicode PSTs by default.

The consequence of using an ANSI PST today is that you can silently corrupt the file the moment it crosses 2 GB. A common misconception is that “all PSTs are the same,” but opening a 2002-era archive in Outlook 365 without converting it is a fast route to data loss. A real example: Marcus, a paralegal, opened a 2001 PST in Outlook 365 and lost two folders because new messages pushed the file past the ANSI ceiling.

Default Location on Windows

On Windows, Outlook 365 stores new PSTs under C:\Users\<user>\Documents\Outlook Files\ by default. That default path matters because it sits inside the user profile, which means roaming profiles, OneDrive Known Folder Move, and backup tools can all interact with it in surprising ways.

The consequence of letting OneDrive sync a live PST is file locking errors and sync conflicts, because Outlook holds the file open while running. Microsoft explicitly warns against this in the article on PSTs in OneDrive. Admins should move PSTs outside synced folders to avoid corruption.

Does Outlook 365 Support PST Files on Every Platform?

Outlook 365 is not one program. It is a family of clients that share a name and a subscription but behave differently with PSTs. Knowing which client you are running is the single most important step before trying to open or import a PST.

Microsoft now ships two Windows versions side by side: the classic Outlook desktop app (built on the old Win32 codebase) and the New Outlook for Windows, which is rebuilt on the web platform. On Mac, Outlook is a Cocoa app with its own data store. On the web and mobile, there is no local file system to host a PST at all.

Classic Outlook for Windows

Classic Outlook, the version installed with Microsoft 365 Apps for Enterprise, fully supports PSTs. You can open, create, import, export, and close them through File > Open & Export, and through File > Account Settings > Data Files. This is the only Outlook client with complete PST functionality in 2026.

The consequence of relying on classic Outlook long-term is that Microsoft has announced a phased transition to New Outlook, and classic support will eventually wind down. Example: Priya, an IT manager at a 200-seat firm, is standardizing on classic Outlook through 2026 to keep PST workflows for her legal team intact. A common misconception is that “classic Outlook is gone,” but Microsoft’s New Outlook transition roadmap keeps it available for business customers into 2029.

New Outlook for Windows

The New Outlook for Windows has added limited PST support in 2025 and 2026, but it is not feature-complete. You can import from a PST and, in some builds, export to a PST, but classic features like opening a PST as a live folder in the navigation pane are missing or gated behind preview flags.

The consequence of assuming full parity is broken archiving workflows. Example: David, a solo accountant, switched to New Outlook and could no longer drag mail into his 2019 tax archive PST because it would not mount. Microsoft tracks feature gaps on the New Outlook feature comparison page.

Outlook for Mac

Outlook for Mac can import PSTs through File > Import, but it cannot export to PST. Mac Outlook uses its own SQLite-based data store and exports to the .olm format instead. That asymmetry catches many users off guard.

The consequence is one-way migration: mail flows from Windows to Mac, but not back without a third-party converter. A real example: Elena, a designer moving from a Windows laptop to a MacBook, imported her 12 GB PST successfully but had to buy a conversion tool to move her Mac mailbox back to a Windows PST when she changed jobs.

Outlook on the Web (OWA) and Mobile

OWA, the browser-based Outlook at outlook.office.com, does not support PST files at all. There is no local file system in a browser tab. The same is true for Outlook mobile on iOS and Android.

The consequence is that users who only use the web or phone cannot open an archive someone emailed them. The workaround is to import the PST through classic Outlook first, then let Exchange Online sync the mail to the cloud mailbox. Microsoft documents this path in the import PST files article.

Platform Support Matrix

How to Import a PST Into Outlook 365

Importing a PST is the most common PST task. It moves the contents of an old archive into your current mailbox so that Exchange Online, search, and retention policies can act on the data. The process takes a few minutes for a small file and several hours for a file over 10 GB.

The governing rule for end users is the Import and Export Wizard built into classic Outlook. Skipping it and just dragging a .pst into Outlook does not work the way users expect, because drag-and-drop opens the file as a secondary data file rather than merging the data.

Step-by-Step Import in Classic Outlook

1. Open classic Outlook and click File in the top left.
2. Select Open & Export, then click Import/Export.
3. Choose Import from another program or file and click Next.
4. Pick Outlook Data File (.pst) and click Next.
5. Browse to the .pst, choose how to handle duplicates, and click Next.
6. Select the destination folder (usually the top-level mailbox) and click Finish.

The consequence of picking “Replace duplicates with items imported” is that newer cloud items can be overwritten by older local copies. Example: Jamal, a sales rep, replaced duplicates and lost three weeks of follow-up notes that only existed in the cloud mailbox. The safer default is “Do not import duplicates.”

Bulk Import for Admins

Admins handling dozens or hundreds of PSTs should not use the wizard. Microsoft offers the Import Service in the Microsoft Purview portal, with two options: Network Upload and Drive Shipping.

Network Upload uses AzCopy to push PSTs to a staging Azure location, then a CSV mapping file assigns each PST to a target mailbox. Drive Shipping lets the admin mail physical hard drives to a Microsoft data center when upload bandwidth is the bottleneck. Both methods preserve message metadata like original received dates, which the end-user wizard does not always do reliably.

How to Export a Mailbox to a PST

Export is the mirror image of import. It pulls mail out of the live mailbox and writes it to a standalone .pst. This is useful for personal backups, departing-employee archives, and legal holds that need a portable copy.

Only classic Outlook can reliably export to PST. The export to a .pst file article on Microsoft Support walks through the dialog.

Step-by-Step Export

1. Click File, then Open & Export, then Import/Export.
2. Choose Export to a file and click Next.
3. Pick Outlook Data File (.pst) and click Next.
4. Select the folders or the whole mailbox, check Include subfolders.
5. Browse to a save location and optionally set a password.

The consequence of setting a password and losing it is total data loss, because Microsoft does not offer a password recovery service for PSTs. Example: Sara, a freelance consultant, password-protected a client archive in 2021, forgot the password, and had to pay for a commercial PST password removal tool to recover it.

Admin Export via eDiscovery

For compliance exports, admins use eDiscovery (Standard) or (Premium) in Microsoft Purview. A case search can export results as a PST directly, which preserves chain-of-custody logging. This matters when the export may become evidence under FRCP Rule 34 production demands.

Size Limits and Performance Rules

PSTs have hard size limits that Outlook 365 enforces. The default maximum for Unicode PSTs in Outlook 365 is 50 GB, raised from the older 20 GB default via the registry values documented in Microsoft KB article on PST size.

The consequence of hitting the size limit is a silent failure: Outlook stops writing new items to the file and may throw error 0x80040116. Example: Hiroshi, a developer with 12 years of mail in one PST, hit the wall during a big attachment import and lost the partial write. A common misconception is that Outlook auto-expands the limit, but it does not.

Why Performance Degrades at Scale

Outlook performs best with PSTs under 10 GB. Above that, search indexing, folder switching, and send/receive all slow down. Microsoft’s own performance guidance recommends splitting large archives.

Storing a PST on a network share or NAS is unsupported per KB 297019. The consequence is corruption when network latency spikes. A common misconception is that a fast gigabit LAN is safe, but Outlook holds the file open with exclusive locks that do not tolerate packet loss.

Three Realistic Scenarios

Every PST decision has a consequence. The three most common situations below show how the rules play out.

Scenario 1: Migrating From an Old Laptop

Scenario 2: Departing Employee Archive

Scenario 3: Legal Hold Production

Named Examples That Make the Rules Real

Example 1: Priya the IT Manager

Priya runs IT at a 200-person law firm. She keeps every user on classic Outlook because her litigators need to open old case PSTs dating back to 2008. When a partner asked to switch to New Outlook, Priya showed the feature comparison page and the partner agreed to wait.

The consequence for Priya is control: she can guarantee access to legacy evidence. The lesson is that platform choice is a legal decision, not just a UX decision.

Example 2: David the Solo Accountant

David runs a tax practice out of his home. He exports a client mailbox to PST at the end of every tax year, then stores it on a Bitlocker-encrypted external drive. This keeps him aligned with IRS Publication 583 recordkeeping expectations.

The consequence of skipping the yearly export would be a bloated live mailbox and slower search during the next filing season. David’s approach also satisfies his professional liability insurer’s data-retention clause.

Example 3: Elena the Designer Switching to Mac

Elena moved from a Dell to a MacBook. She imported her 12 GB PST into Outlook for Mac with File > Import, and all her mail came through. When she later switched jobs and needed a Windows-friendly copy, she used a third-party .olm-to-.pst converter.

The consequence of not planning the round trip was an extra weekend of work and a $49 software purchase. The lesson is that Mac PST support is one-way.

U.S. Legal Rules That Govern PSTs

PSTs are not just a tech topic. They are governed by federal rules whenever the mail inside them relates to business, health data, financial records, or litigation.

FRCP Rule 26 and Rule 37

The Federal Rules of Civil Procedure Rule 26 requires parties to disclose electronically stored information. PSTs are squarely ESI. Rule 37(e) adds spoliation sanctions when ESI is lost due to failure to preserve.

The consequence of letting a custodian’s PST get wiped after a hold notice is an adverse-inference instruction at trial, which can decide the case. A common misconception is that a hold only applies to server mail. Local PSTs are in scope too.

SEC Rule 17a-4

SEC Rule 17a-4 requires broker-dealers to preserve electronic communications in non-rewritable, non-erasable form for three to six years. A PST on a user’s laptop does not meet this standard.

The consequence is FINRA fines, which regularly exceed $1 million for recordkeeping failures, per the FINRA disciplinary actions database. A common misconception is that any backup satisfies 17a-4. The rule requires WORM-compliant storage.

HIPAA Security Rule

The HIPAA Security Rule requires covered entities to apply administrative, physical, and technical safeguards to electronic protected health information (ePHI). An unencrypted PST containing patient mail violates the rule.

The consequence is civil monetary penalties up to $2.1 million per year per violation category under the HHS OCR enforcement guidance. A common misconception is that password-protecting a PST equals encryption. PST passwords do not encrypt the file; they only gate the Outlook UI.

State Privacy Laws

State laws like the California Consumer Privacy Act (CCPA) and the New York SHIELD Act add breach-notification duties when a PST with personal data is lost or stolen. A lost USB drive with a PST of customer mail is a reportable breach in most states.

The consequence of non-notification is a separate enforcement action on top of the breach itself. The lesson is that PSTs on portable media are a compliance trap.

Repairing Corrupt PSTs with scanpst.exe

Outlook ships with the Inbox Repair tool, better known as scanpst.exe, for fixing corrupt PSTs. It lives in the Office installation folder, typically C:\Program Files\Microsoft Office\root\Office16\.

The tool performs eight passes over the file, repairs header damage, rebuilds indexes, and creates a .bak before writing changes. The consequence of running it without a backup is permanent loss if a pass fails mid-write.

When scanpst Fails

scanpst cannot fix every problem. For files over 2 GB with deep structural damage, third-party tools like Stellar Repair for Outlook or Kernel for Outlook PST Repair often succeed where scanpst gives up.

Example: Marcus the paralegal ran scanpst on a 9 GB corrupted archive. It froze at pass four. A commercial tool rebuilt the file in two hours and recovered 99.6% of items. The lesson is to try Microsoft’s free tool first, then escalate.

Mistakes to Avoid

The following mistakes trigger real, documented losses. Avoid all of them.

• Storing a PST on a network share: unsupported per Microsoft, causes corruption under network latency.
• Letting OneDrive sync a live PST: file locks and sync conflicts corrupt the file.
• Skipping a backup before running scanpst: a failed repair can destroy the file.
• Forgetting a PST password: Microsoft cannot recover it; commercial removal is the only path.
• Assuming OWA opens PSTs: the web client has no file system access.
• Ignoring the 50 GB limit: Outlook stops writing silently when the cap is hit.
• Deleting a PST after import without verification: cloud upload can fail mid-way, stranding items.
• Mixing ANSI and Unicode PSTs without converting: 2 GB ANSI cap causes data loss.
• Storing unencrypted PSTs with PHI or PII: HIPAA and state law violation.
• Failing to preserve PSTs under litigation hold: FRCP Rule 37(e) spoliation sanctions.

Do’s and Don’ts

Do’s

• Do store PSTs on local drives or secure encrypted volumes; Microsoft’s supported storage guidance requires local storage to prevent corruption.
• Do back up PSTs with file-level backup tools like Veeam or Macrium; Outlook must be closed first so the file is not locked.
• Do migrate PSTs to Exchange Online with Purview’s Network Upload; bulk migration preserves metadata and removes local risk.
• Do encrypt the drive holding any PST with Bitlocker or FileVault; PST passwords are not encryption.
• Do split archives by year or project under 10 GB; performance and search indexing stay responsive.

Don’ts

• Don’t store PSTs on SharePoint, OneDrive, Dropbox, or any sync service; live files corrupt during sync.
• Don’t open the same PST on two computers at once; exclusive locks will fail and damage the file.
• Don’t assume a PST password encrypts the file; the bytes on disk are plain and readable by forensic tools.
• Don’t rely on PSTs for regulated recordkeeping; SEC 17a-4 requires WORM storage, which PSTs are not.
• Don’t let departing employees walk out with PST backups of company mail; this creates data-loss and trade-secret risk.

Pros and Cons of Using PSTs in Outlook 365

Pros

• Portability: a single .pst moves mail between computers, which cloud mailboxes cannot do offline.
• Offline access: PSTs work without network connectivity, useful for travel or outages.
• Cheap archive: no per-user license cost for cold mail, unlike expanded Exchange Online storage.
• Forensic friendliness: the open MS-PST spec lets eDiscovery tools parse them directly.
• Control: the user or admin holds the file; no dependency on vendor uptime to access it.

Cons

• Corruption risk: local files fail far more often than server mailboxes, per Microsoft support telemetry.
• No retention enforcement: PSTs sit outside Exchange retention and Purview policies.
• Compliance risk: HIPAA, SEC 17a-4, and FRCP obligations are hard to meet with local files.
• Size ceiling: 50 GB cap forces splitting and creates sprawl.
• Platform fragmentation: Mac, web, and mobile Outlook cannot open them fully.

Key Entities to Know

• Microsoft 365 Apps for Enterprise: the subscription that delivers classic Outlook on Windows, which is the only PST-complete client.
• Exchange Online: the cloud mailbox service where imported PST data ends up, governed by Exchange Online limits.
• Microsoft Purview: the compliance suite that runs eDiscovery, retention, and the PST Import Service.
• AzCopy: the command-line tool used for Network Upload PST migration.
• scanpst.exe: Microsoft’s free Inbox Repair tool bundled with Office.
• FINRA and SEC: regulators that enforce 17a-4 recordkeeping against broker-dealers.
• HHS OCR: the Office for Civil Rights that enforces the HIPAA Security Rule.
• FRCP Rule 26 / Rule 34 / Rule 37: the federal civil procedure rules that define ESI duties.

Process Details: The Import/Export Wizard Options

Every dialog in the Import/Export Wizard has a consequence. Understanding each checkbox prevents data loss.

• “Include subfolders” sweeps child folders. Unchecking it exports only the selected folder, a common cause of incomplete exports.
• “Filter” applies a date or sender filter. A misconfigured filter can silently skip responsive documents under a hold.
• “Replace duplicates with items imported” overwrites newer cloud items with older local copies, which can erase recent work.
• “Allow duplicate items to be created” is the safest option for one-way archival imports.
• “Do not export duplicate items” shrinks the output file but can skip items you expected to see.
• Password field: adds UI-level gating only; the file itself is not encrypted, a common and dangerous misconception.
• Compressible Encryption vs. High Encryption: only affects internal obfuscation, not actual AES encryption.

Court Rulings That Shaped PST Practice

Two published rulings illustrate how courts treat PSTs.

In Zubulake v. UBS Warburg, 229 F.R.D. 422 (S.D.N.Y. 2004), Judge Shira Scheindlin imposed adverse-inference sanctions after key email, including local archives, was lost despite a litigation hold. The case reshaped U.S. eDiscovery and is the foundation of modern FRCP Rule 37(e).

In Pension Committee v. Banc of America Securities, 685 F. Supp. 2d 456 (S.D.N.Y. 2010), the court found gross negligence where custodians failed to preserve personal archives, reinforcing that local PSTs are within a hold’s scope. The consequence is that ignoring PSTs during a hold is not a defense.

A common misconception is that only IT has a duty to preserve. Both rulings put duty on custodians and counsel as well.

State Nuances for PST Handling

While federal rules set the floor, states add their own layers. California’s CCPA and CPRA require deletion on consumer request, which is hard to honor if the data sits in a PST outside the enterprise index. New York’s SHIELD Act triggers breach notification for lost unencrypted PSTs.

Texas, Illinois, and Massachusetts all have their own encryption and breach rules that apply to PSTs holding personal data. Illinois’ Biometric Information Privacy Act has generated the largest per-record penalties in the country. The consequence of a lost PST with BIPA-covered data in Illinois can run into the tens of millions of dollars.

A real example: Priya’s firm treats any PST leaving the office network as a reportable event under the strictest state law applicable to each client, a belt-and-suspenders approach. The lesson is that one uniform policy across states is safer than trying to map each state’s quirks.

FAQs

Does Outlook 365 on the web (OWA) support PST files?

No. OWA runs in a browser sandbox with no file system access, so it cannot open, import, or export .pst files. You must use classic Outlook for Windows instead.

Can I open a PST file in New Outlook for Windows?

No, not fully in 2026. New Outlook supports PST import in recent builds but does not mount PSTs as live folders the way classic Outlook does. Classic Outlook remains the complete option.

Does Outlook for Mac support PST files?

Yes, but only for import. Outlook for Mac cannot export to .pst; it exports to the .olm format instead, which requires a third-party converter to round-trip back to Windows.

Is there a size limit for PST files in Outlook 365?

Yes. The default Unicode PST cap is 50 GB in Outlook 365, configurable via registry keys documented by Microsoft. Hitting the limit causes silent write failures and error 0x80040116.

Can I store a PST file on OneDrive or SharePoint?

No. Microsoft explicitly warns against syncing live PSTs through OneDrive or SharePoint because file locks and sync conflicts cause corruption. Store PSTs on local or Bitlocker-encrypted drives.

Does password-protecting a PST encrypt the file?

No. PST passwords only gate the Outlook UI and do not encrypt the bytes on disk. Forensic tools can read contents directly. Use Bitlocker or FileVault for real encryption.

Can admins bulk-import PST files into Exchange Online?

Yes. The Microsoft Purview Import Service offers Network Upload via AzCopy and Drive Shipping for physical drives, with CSV mapping to destination mailboxes and metadata preservation.

Are PST files acceptable for SEC 17a-4 recordkeeping?

No. SEC 17a-4 requires non-rewritable, non-erasable WORM storage for broker-dealer communications, which PSTs do not provide. Firms face FINRA fines for PST-based recordkeeping.

Can I recover a lost PST password?

No, not from Microsoft. Microsoft does not offer password recovery for PSTs. Third-party password removal tools can strip the password, but only the file owner should use them.

Does scanpst.exe fix every corrupt PST?

No. scanpst handles most header and index corruption but often fails on files over 2 GB with deep structural damage. Commercial repair tools like Stellar or Kernel can succeed where scanpst cannot.

Do PST files fall under litigation holds?

Yes. Under FRCP Rule 26 and Rule 37(e), PSTs are electronically stored information subject to preservation duties. Failure to preserve can trigger spoliation sanctions and adverse-inference rulings.

Can I import a PST directly into Outlook mobile?

No. Outlook mobile on iOS and Android has no file system access for PSTs. Import through classic Outlook for Windows first, then Exchange Online sync makes the mail available on mobile.