Outlook for Mac vs Windows: The Differences That Matter

If a support article, a help forum answer or a training video says to open a PST file, right-click a rule set to export it, or enable a COM add-in, and you are on a Mac, you are following instructions for a different product. Outlook for Mac and Outlook for Windows share a name, a colour and most of a calendar. Almost everything else is a separate implementation, and that is why the steps quietly fail.

This is a per-capability comparison of the two clients for mixed-OS teams and switchers, using Microsoft's own feature matrix rather than opinion. It covers where each wins, what the new Outlook unification actually changed, and which Windows-only advice you can stop trying to make work on macOS.

The short verdict#

Outlook for Windows has always been the fuller product. It carries three decades of desktop-era capability — PST files, VBA macros, custom forms, COM and VSTO add-ins, a deep rules builder, Quick Steps, Search Folders, conditional formatting and a Profile Manager. Outlook for Mac was rebuilt more than once as a mail-and-calendar client and never picked up most of those things.

New Outlook narrows the gap in a specific way. Both the new Outlook for Windows and the new Outlook for Mac are built on the same web-architected codebase, so the two now behave more alike than classic Outlook for Windows and Outlook for Mac ever did. Same experience, same web add-in model, same limits.

That helps mixed teams. It also introduces a strange new state: the closer new Outlook for Mac gets to new Outlook for Windows, the further both drift from classic Outlook for Windows, which is where the deepest features still live. If your team half-lives in COM add-ins and half-lives on macOS, unification does not fix that problem — it just moves it.

The practical answer as of August 2026: mail, calendar, categories, search and shared mailboxes work on both platforms and behave similarly. Extensibility (COM, VBA, custom forms), local-file features (PST, full offline archive) and the deep rules/Quick Steps/Search Folders builders remain Windows-only. Legacy Outlook for Mac against Exchange Online retires in October 2026, which is the one real 2026 deadline in the picture.

At-a-glance: how Outlook for Mac and Outlook for Windows compare#

This is the comparison the rest of the post unpacks. Statuses use Microsoft's own matrix wording — available, partially available, not supported, upcoming — because partial is where most of the surprises live. Verify the row you plan to depend on against Microsoft's live matrix, since the partial and upcoming rows move.

Where Outlook for Windows wins: desktop code, local files and deep rules#

The Windows advantage is not one feature; it is a stack of them, all rooted in the same fact. Classic Outlook for Windows is a Win32 application, so it can host code that runs in its own process and read files off your disk directly. Outlook for Mac has never been that kind of application, and new Outlook is deliberately not that kind of application either.

That gives Windows-only status to the categories every large organisation has grown a workflow around: COM and VSTO add-ins (Salesforce logging, DocuSign panes, Dragon dictation, ProofPoint reporting), VBA macros, custom forms, rules import and export, the full Quick Steps builder, Search Folders and conditional formatting.

Some of those are also gone from new Outlook for Windows, which is the point of the earlier verdict. If you need any of them, the answer is neither new Outlook for Mac nor new Outlook for Windows — it is classic Outlook for Windows, and it will be until Microsoft's cutover.

• COM and VSTO add-ins are the sharpest verified gap and they never had a Mac equivalent. If Salesforce logging from the reading pane is your job, Mac has not been the answer at any point in the last decade.
• VBA and custom forms are the quieter gaps because they tend to be personal and undocumented, which is exactly what makes them hard to replace when you switch.
• Mail Merge from Word to Outlook is a Windows-only integration; Word for Mac can produce documents and emails, but it does not drive Outlook for Mac as a merge target.

Data files: PST is Windows-only, OLM is Mac-only, neither reads the other#

This is the migration blocker that catches every mixed-OS team the first time they try to move an archive. Outlook for Windows uses PST for local archives and offline caches (with OST as the online mode's local cache). Outlook for Mac uses OLM as its export/archive format. Neither program can open the other's file.

Practically, you cannot hand a Mac user a PST and expect them to drop it into Outlook for Mac. You cannot hand a Windows user an OLM and expect them to drop it into Outlook for Windows. The supported route in both directions is to move the mail through the mailbox — import into a target mailbox on the platform that can read the source, and let the server carry it — or use a third-party converter.

If a PST holds the only copy of old mail, that mail belongs on a Windows machine or, safer still, back on the server before you switch platforms. Losing a PST to a format mismatch is a common way for years of mail to become unreadable in one afternoon.

Rules, Quick Steps and Search Folders — the same words, different products#

Rules split along an architectural line that holds up across both platforms. Anything the mailbox can evaluate on the server — move mail from a sender to a folder, apply a category, forward to an internal address — runs the same on Mac and Windows because it does not depend on the client. Anything that needed the client running on your PC or Mac to fire, such as playing a sound, is the part that varies.

Classic Outlook for Windows has the full builder plus client-only actions plus rules import and export. New Outlook for Windows keeps server-side and drops client-only, and does not import or export. Outlook for Mac has always had the thinnest builder of the three, and its client-only rules were never a full match for classic Windows even before new Outlook existed.

The consequence for mixed teams: a rule set built in classic Outlook for Windows does not survive the crossing to Mac. You cannot export it as a file and import it on the other side. Budget an afternoon to rebuild by hand, and take the chance to delete the ones nobody remembers writing.

• Quick Steps and Search Folders are Windows features. Neither exists on Outlook for Mac. Do not spend an hour looking for a menu that is not there.
• Conditional formatting for the message list — the classic Windows feature that colour-codes messages by sender or subject — is likewise not on Mac.
• The Exchange Online inbox rules quota is 256 KB, raisable for migrated mailboxes, verified as of August 2026. That quota is a property of the mailbox and applies whichever client you build rules from.

Profiles, delegation and shared mailboxes#

The Profile Manager is a Windows-only concept. Outlook for Windows stores per-user settings, account configurations and OST files inside a profile, and you can maintain several of them for separate contexts. Outlook for Mac has always managed accounts directly and has no equivalent to the Profile Manager. Instructions that say to create a new Outlook profile, or to run outlook.exe /profiles, have no counterpart on macOS.

Delegation splits differently. Calendar delegation works on both platforms. Assigning mail-folder delegate permissions is the harder half on new Outlook everywhere — Windows still routes some of that through classic Outlook, and Mac has historically leaned on an administrator to manage the underlying permissions.

Shared mailboxes themselves open on both platforms once permissions exist. It is the granting and changing of permissions on mail folders that sends you back either to classic Outlook for Windows or to the admin centre.

Where Outlook for Mac wins: a lighter product, and October 2026 forces the newer one#

Outlook for Mac's advantages are subtler and worth naming, because a fair comparison should not read as a one-sided ledger.

It has always been the lighter application. Fewer surfaces to configure and no COM host to break means fewer of the class of problems Windows readers spend hours on — no add-in loading failures, no PST corruption, no VBA regressions, no profile that got stuck. If those are the things that used to eat your Fridays, Mac has been a quieter product.

New Outlook for Mac is a genuine native macOS application shipped as the default going forward. It carries Mac conventions the Windows product does not — Handoff between devices, Touch ID, Universal Clipboard, native macOS notifications — and it is the officially supported client against Exchange Online once legacy Outlook for Mac retires in October 2026.

That October 2026 date is the one 2026 deadline that actually matters in this comparison. Legacy Outlook for Mac stops connecting to Exchange Online mailboxes; new Outlook for Mac is the path from that point. Outlook for Windows is not affected by this retirement.

The new Outlook unification: what actually changed, and what did not#

The single largest change to this comparison in the last two years is that Microsoft rebuilt both platforms on the same web-architected codebase. New Outlook for Windows is Outlook on the web inside a WebView2 shell with a Native Windows Integration Component. New Outlook for Mac is the same web experience inside a native macOS shell.

The upside for mixed teams is real. Feature velocity is shared, the web add-in model is identical, and the mail, calendar, search and shared-mailbox experience behaves the same way on both. When a new feature ships in Outlook on the web, both platforms get it. When a feature is architecturally not supported, both platforms lose it the same way.

That is why the Mac column in the table above tracks the new Outlook for Windows column so closely for extensibility. There is only one add-in model, so the same web add-ins that work on Windows now work on Mac. The COM add-ins that classic Outlook for Windows can still load are gone from both new clients equally.

The downside is that unification pulls the two new clients toward each other and away from classic. If your team's most-used features live in COM add-ins, VBA, custom forms, PST archives, the full rules builder or Quick Steps and Search Folders, unification does not help — those features are what makes classic Outlook for Windows classic, and Mac never had them anyway.

Pricing model — verify at the vendor#

Both Outlook for Mac and Outlook for Windows are packaged the same way: as part of Microsoft 365 (per-seat subscription) or as a perpetual Office licence, with Outlook for the web included in most Microsoft 365 plans at no extra cost. Outlook.com email accounts are free with limits and cannot be used as a substitute for a paid Microsoft 365 mailbox at work.

There is no separate Outlook-for-Mac SKU and no separate Outlook-for-Windows SKU. The client comes with the seat. Where costs differ is in the underlying mailbox — Exchange Online plan (Plan 1, Plan 2, business or enterprise Microsoft 365 bundle), archive add-ons, and any third-party add-ins you licence on top.

Prices, plan names and inclusions on Microsoft's site change often. Confirm the current SKU list, per-seat pricing and archive quotas on the Microsoft 365 comparison page before you build a budget around any specific number. Third-party add-in vendors set their own prices and have their own compatibility matrices for classic vs new Outlook and for Windows vs Mac.

Who each is genuinely for#

Because both are the default mail client on their platform for the organisations that live in Microsoft 365, this is not usually a free choice. It is more useful to know which rows in the table matter for your day, and to plan around them.

A third option, honestly#

Disclosure first: we build AI Emaily, so treat this as an interested opinion. It belongs in this comparison because a share of readers asking about Outlook for Mac vs Outlook for Windows are not really trying to pick between two Microsoft clients — they are trying to solve one specific problem: our Mac users and our Windows users end up in different products.

AI Emaily addresses that head-on. Our macOS and Windows desktop apps ship from a shared codebase, so a feature that lands on Mac lands on Windows the same day, and the shortcuts, rules and workflows behave the same on both. That is the honest cross-platform advantage in this category — neither Outlook for Mac nor Outlook for Windows can offer it, because they were rebuilt as separate products with separate roadmaps and have only recently started to converge again.

It connects Microsoft 365 and Outlook.com mailboxes alongside Gmail, iCloud and IMAP into one inbox. It triages, summarises long threads and drafts replies from a Personal Context brain you write yourself, plus per-client profiles you control, not from your past sent mail. Three levels: Manual, Copilot (nothing sends without your approval), and Autopilot for narrow cases you allow. Every action has undo and an audit trail, and we do not train on your mail. Packaging is a 7-day free trial on Pro or Autopilot (card required, $0 if cancelled before day 7) — no permanent free tier, and no free seat count.

The concession, plainly: if a COM add-in like Salesforce logging or DocuSign is the reason you need Outlook, classic Outlook for Windows is still the answer, not AI Emaily. We do not host COM or VSTO add-ins, we do not run VBA, and we do not read PST files. Where Outlook for Windows genuinely wins the desktop-code and local-file dimensions, we lose them the same way new Outlook for Mac loses them. The place we are stronger is the axis this article is about — the same product on both operating systems — and that is a specific reader, not everyone.

If the real problem is mixed-OS drift on the team, running the same client on both platforms is worth an hour of your evaluation. Start on the homepage or open the pricing page and try the 7-day trial on either OS.

The short version#

Outlook for Mac and Outlook for Windows share a mail-and-calendar core and diverge on almost everything else. Windows keeps PST, VBA, COM and VSTO add-ins, custom forms, Mail Merge, the full rules builder, Quick Steps, Search Folders, conditional formatting and the Profile Manager. Mac has never had any of them and new Outlook is not adding them.

The new Outlook unification made the two new clients behave more alike than any Outlook for Mac and Outlook for Windows before them, which helps mixed teams. It also pulls both away from classic Outlook for Windows, which is where the deepest features still live. The 2026 date that matters here is October 2026 for legacy Outlook for Mac against Exchange Online — not the misreported classic Outlook for Windows shutdown, which is not a real deadline.