The Word Engine in Outlook: What Actually Ends in October 2026 and How to Code Emails Now

October 2026 marks the end of support for Office 2021 — the suite edition that includes Outlook 2021 on the Microsoft Word engine. The engine itself is not going anywhere: classic Outlook in a Microsoft 365 subscription is supported until at least 2029. Below are the exact dates as documented by Microsoft, what the Word engine actually breaks, and the code that works in both versions of Outlook.

What ends on 13 October 2026

For nineteen years desktop Outlook on Windows rendered email with the engine of a word processor rather than a browser. That single fact explains nearly every quirk of email coding: tables instead of blocks, inline styles instead of classes, and a separate markup language called VML for buttons and backgrounds.

After that date Microsoft stops shipping security updates and fixes for Office 2021. There is no extension and no paid extended security updates. But this concerns a specific suite edition, not the email rendering engine.

A common mistake in the coverage

The phrase "Microsoft retires the Word engine in October 2026" appears across a great deal of email-coding coverage. It is a shortcut, and it misleads. The precise picture is this:

• 13 October 2026 is the end of support for Office 2021 and Office LTSC 2021 — specific editions of the suite, not the engine
• classic Outlook in a Microsoft 365 subscription and in Office LTSC 2024 is supported until at least 2029
• Microsoft has not announced a date for the full retirement of classic Outlook
• in other words, the Word engine stays with us in email for several more years

How the migration to New Outlook works

New Outlook for Windows shipped as a stable release in September 2023 and is built on WebView2, a wrapper around the Chromium engine. It understands modern CSS: rounded corners, flexbox, media queries, background images. The migration runs in stages.

The practical conclusion for a developer: it is too early to drop the workarounds. Base the decision on open statistics from your own list rather than on the Microsoft calendar.

What the Word engine breaks

The list of properties classic Outlook ignores or handles its own way has barely changed over the years.

• border-radius — not applied, the button turns into a rectangle
• background-image — not rendered, requires separate VML code
• padding and margin on div and img elements — dropped entirely
• max-width — unsupported, widths have to be set explicitly
• flexbox and grid — do not work, layout relies on tables
• position, float — ignored, columns are built with nested tables

The practical consequence: padding belongs on the table cell that wraps an element, not on the element itself. This is the first thing to check when an email looks cramped in Outlook.

A bulletproof button for both engines

The classic technique is to serve different code to different engines using conditional comments. The if mso block is visible only to Microsoft products on the Word engine; if !mso covers everything else.

Key details: arcsize sets the corner radius as a percentage of the height, so a 48-pixel button with a 6-pixel radius needs roughly 12 percent. The w:anchorlock tag stops Word from turning the button into editable text. Width and height in VML must be explicit.

New Outlook has problems of its own

Moving to Chromium fixed CSS support but introduced new behaviour. Developers report that New Outlook runs a post-processing step after the email loads: styles from the style tag disappear from the DOM and are rewritten inline, and some properties are lost.

I have also seen where my styles suddenly disappear from the DOM layout, and I find them rewritten inline.

There is no universal fix. Practical mitigations that reduce the risk:

• single-column layouts instead of multi-column
• inline content images instead of background images
• an identical corner radius on all sides
• a test send to both Outlook versions before the campaign

How to code emails right now

The rule is simple: keep the workarounds until your own list data shows classic Outlook below ten percent of opens. The share of old Outlook depends heavily on whether you sell to consumers or to businesses.

For context: Litmus data puts desktop Outlook well behind Apple Mail and Gmail in overall opens, yet that share is concentrated in the corporate segment.

How Mailvex handles this

Mailvex compiles your email straight into compatible HTML: buttons ship with a VML fallback, padding is applied to table cells, styles are inlined, and the total weight is kept in check. You never have to remember arcsize or anchorlock.

You also get separate spacing settings for mobile screens, dark mode support and tag profiles for popular email service providers.

Frequently asked questions

Can I remove VML from my templates already?

No. Classic Outlook is supported until at least 2029, and corporate subscribers upgrade the slowest of all. Base the decision on open statistics from your own list.

What happens on 13 October 2026?

Office 2021 and Office LTSC 2021 stop receiving security updates. The applications keep working and emails keep opening. This is not a shutdown of the Word engine.

When will classic Outlook disappear entirely?

Microsoft has not announced a date. What is known is that from April 2026 New Outlook became the default with the option to switch back, and full retirement has been postponed indefinitely.