Outlook Desktop Line-Height and mso-line-height-rule Explained

Why does Outlook desktop mess up your email line height?

You send a clean, well-formatted email. It looks perfect in Gmail, Apple Mail, and even in Outlook on the web. Then you open it in Outlook desktop—version 2013 through 2021—and suddenly the text is cramped, the spacing is all wrong, and the lines don’t align. What happened?

Outlook desktop uses Microsoft Word’s rendering engine behind the scenes. That engine ignores standard CSS line-height and applies its own rules, which are inconsistent, unpredictable, and often break your layout. This isn’t a bug—it’s a design compromise that affects every email sent through these versions.

The result? Spacing collapses, content stacks unpredictably, and your carefully crafted newsletter or transactional message becomes hard to read. This issue is especially noticeable in multi-column layouts, nested tables, or text with mixed styles.

Key takeaways

• Outlook desktop (2013–2021) uses Word’s rendering engine, which overrides standard CSS line-height.
• Word applies its own spacing rules, often causing cramped or inconsistent vertical spacing in emails.
• Using mso-line-height-rule is required to force consistent line-height behavior in Outlook desktop.

What is mso-line-height-rule and how does it fix the Outlook bug?

Outlook desktop versions use a broken line-height algorithm that causes inconsistent vertical spacing in email designs, making content look misaligned or cramped. The mso-line-height-rule property is a proprietary CSS hack from Microsoft that forces Outlook to use fixed line height instead of its unreliable internal spacing logic. When used correctly, it restores consistent line spacing across all Outlook desktop clients, fixing one of the most frustrating rendering issues in email development.

The root cause: Outlook’s line-height algorithm

Outlook for Windows (especially versions before 2013) doesn’t respect standard CSS line-height values. Instead, it applies a heuristic based on font size and margin calculations that often produce unpredictable results—lines too close or too far apart depending on the context.

For example, a line height of 1.5 might render as 1.2 in one email and 2.0 in another. This unpredictability breaks the visual rhythm of your email design, especially in long blocks of text.

How mso-line-height-rule fixes it

The mso-line-height-rule property overrides Outlook’s default behavior. When set to exactly, Outlook stops using its internal spacing algorithm and instead honors the pixel values you define in your CSS.

Here's how it works in practice: div { line-height: 20px; mso-line-height-rule: exactly; } This tells Outlook: “Use exactly 20px between lines, no exceptions.” It doesn’t affect other email clients, which continue to follow standard CSS rules.

It’s important to use mso-line-height-rule: exactly; on the same elements where you’ve set a fixed line-height in pixels. Use it sparingly—overuse can lead to unintended spacing in older clients or mobile devices.

For developers, this property has been a critical tool since the early 2000s. It’s not a “fix” for the underlying issue—it’s a workaround, but a necessary one. According to the W3C HTML4 specification, line height should be consistent across platforms, but Outlook’s deviations remain a documented issue.

If you're validating email list quality or testing deliverability across mail clients, it's also worth ensuring your templates are tested in real Outlook environments. MailTester’s inbox placement tool lets you preview how your email renders in actual Outlook clients, helping catch spacing issues before send.

How to use mso-line-height-rule without breaking other clients

You can safely use mso-line-height-rule: exactly by applying it as an inline style only inside table cells or divs where spacing is inconsistent, and always pair it with a standard line-height setting. This ensures Outlook desktop renders spacing correctly while other clients follow modern CSS. Avoid using it at the document level—it will break alignment in non-IE environments.

Target only problematic elements

Don’t apply mso-line-height-rule globally. It’s meant for specific content blocks where line spacing looks off in Outlook desktop—like lists, paragraphs with tight spacing, or table cells with multiple lines. Apply it only inside the elements that need it, using inline styles so it doesn’t cascade unpredictably.

Pair it with standard line-height

Always set a standard line-height value (like 1.4 or 24px) alongside mso-line-height-rule: exactly. This gives modern clients and other email readers a fallback. Without it, your email may look cramped in Gmail, Apple Mail, or web clients, since they ignore the mso rule completely.

For example, when using a table cell with multiple lines, wrap the content in a div with inline styles like:

style="line-height: 1.4; mso-line-height-rule: exactly;"

This pattern is widely used and supported across email clients. It respects Outlook’s quirks while keeping the experience consistent elsewhere.

For more complex layouts, test your email across real inboxes using tools like MailTester’s inbox placement checker, which simulates how your email renders in Gmail, Outlook, Apple Mail, and others—without the guesswork.

According to the W3C CSS2.1 specification, line-height is a fundamental layout property, and its behavior varies across rendering engines—especially in legacy clients. This is why a workaround like mso-line-height-rule exists: it fills a gap that standard CSS cannot.

Even with this fix, email clients still treat styles inconsistently. That’s why verifying your list beforehand improves delivery and rendering outcomes. Use MailTester’s bulk verification to clean up invalid, malformed, or role-based addresses before sending—so your layout issues aren’t worsened by bounce-prone or misrouted emails.

Let’s be clear: mso-line-height-rule: exactly is a tactical fix, not a universal solution. Use it sparingly, only where needed, and always with a fallback. That’s how you maintain cross-client consistency without introducing new problems.

Real-world example: Fixing a broken email layout in Outlook

You can fix inconsistent line spacing in Outlook by applying line-height: 1.5 alongside mso-line-height-rule: exactly directly in a table cell’s inline style. This combination forces Outlook to render spacing consistently across versions 2013 through 2021, even when the default rendering engine ignores standard CSS. Always test with a real Outlook client, not just a preview tool, to confirm results.

Step-by-step: Apply the fix in practice

1. Start with a basic email table structure. Use a <td> to contain body text, like a paragraph or short content block.
2. Add inline styles: style="line-height: 1.5; mso-line-height-rule: exactly;" directly to the <td> element. This tells Outlook to use fixed spacing, not its default aggressive line-breaking behavior.
3. Send the email to a real, live Outlook client (Windows) — not just a preview pane or browser-based tester. Outlook’s rendering engine behaves differently in a live environment, especially with HTML email.
4. Test across multiple versions: 2013, 2016, 2019, and 2021. These versions share the same rendering engine (Word HTML), but subtle differences exist in how they handle non-standard CSS. The mso-line-height-rule rule is critical here; without it, spacing collapses or expands unpredictably.
5. If spacing still shifts, check for conflicting global styles or styles applied to parent containers. Only inline styles take effect reliably in Outlook — external and internal CSS often get stripped.

Why this works: The technical reality

Outlook on Windows renders email using the Word HTML engine, which ignores standard CSS line-height unless you explicitly enforce it with mso-line-height-rule: exactly. This rule is a Microsoft-specific directive that overrides Word’s defaults. According to Microsoft’s documentation on email rendering, non-standard line-height rules should be applied via MSO-specific properties to ensure stability.

The fix is not just cosmetic. Poor spacing affects readability, conversion, and perceived professionalism. A poorly spaced email can lead to higher unsubscribe rates, especially when content feels cramped or disjointed.

For teams sending bulk emails, verifying deliverability is just as important as layout. Use real inbox tests to ensure your fix doesn't trigger spam filters. MailTester’s Inbox Placement Test can check how your styled email lands across major providers, including Outlook, using real mailboxes.

Common mso-line-height-rule values and their effects

You can control line spacing in Outlook desktop with the mso-line-height-rule CSS property. Use exactly for precise pixel-perfect spacing, atleast when you need flexibility for dynamic text, or normal only if you’re okay with inconsistent results — it relies on Outlook’s default behavior and often produces unpredictable spacing.

Understanding the most reliable values

The exactly value ensures that line-height is applied strictly in pixels, regardless of content changes. This is the most predictable option for consistent layout, especially in HTML emails where visual alignment is essential. You can achieve precise control over vertical spacing in Outlook desktop clients, which often render line-height differently than web browsers.

When to use atleast or avoid normal

Use atleast when your content might grow (e.g., user-generated text or multi-language emails). It sets a minimum line height but allows more space if needed, preventing text from appearing cramped. However, it's not suitable for fixed layouts. Avoid normal in any situation where spacing consistency matters — it’s unreliable across Outlook versions and can lead to inconsistent rendering, especially in older clients like Outlook 2010 or 2013.

Per Microsoft’s documentation on HTML rendering in Outlook, the mso-line-height-rule property is designed specifically to address rendering inconsistencies across the Outlook desktop suite — a known challenge due to its use of Word’s rendering engine [Microsoft Docs].

For testing how your email will render in real inboxes, especially Outlook desktop, run an inbox placement test to catch layout bugs before sending. MailTester's inbox tester simulates real rendering across major clients.

Why you still need to test on real clients even with correct CSS

Even if your CSS follows the rules and uses mso-line-height-rule correctly, Outlook desktop can still render your email differently than expected. Behavior varies between machines due to individual user settings, outdated updates, or disabled HTML rendering—and no amount of theory accounts for all real-world edge cases.

Outlook isn’t a single client

Outlook 365, Outlook 2021, and even the same version on different machines behave inconsistently. Some users disable HTML rendering entirely, while others run outdated builds where mso-line-height-rule doesn’t apply. What looks perfect in one test environment may collapse or gap unexpectedly on another.

Even with correct CSS, features like line-height can break when styles are stripped, ignored, or overridden by a user’s settings. According to Microsoft’s own documentation, some rendering rules are conditional based on configuration, and there’s no central enforcement across all installations.

Testing on real machines is the only reliable method

Automated tools and renderers simulate behavior—but they can’t replicate real user settings, third-party add-ons, or corrupted local caches. You might pass every test in a virtual environment and still see broken layouts in real inboxes.

Let’s be honest: email deliverability and rendering are inherently fragile. The best way to catch these inconsistencies is to test on actual machines in real environments. That includes using devices with known issues, disabled features, or older versions of Outlook.

For example, you can validate your HTML and CSS rigorously, but until you see how it renders on a real Outlook 365 installation behind a corporate firewall with restricted rendering, you won’t know for sure if it will work. This is why tools like MailTester’s inbox placement tester help verify how your email lands in real inboxes across different clients and filters.

https://mailtester.com/inbox-tester

Ultimately, you can build a technically perfect email, but if it breaks in reality, it fails. The only way to be confident is to test where it matters: on actual users’ machines and with their real configurations.

How to test if your email renders properly in Outlook Desktop

You can’t trust a web client or a generic preview tool to show how your email actually looks in Outlook Desktop. The best approach is to test your email in a real Outlook Desktop installation on Windows, using a test email address, and validate the rendering across multiple screen sizes and zoom levels. Use a dedicated email testing tool that simulates Outlook’s rendering engine, or send a live version to yourself via a real Outlook client to catch layout bugs, line-height issues, and mso-line-height-rule quirks before your campaign goes live.

Test in a real Outlook Desktop environment

• Use a real Outlook Desktop client on Windows — not the web version or mobile app — since rendering behavior differs significantly.
• Send your email to a test account set up in Outlook Desktop (e.g., outlook.com or an Office 365 account with the desktop client installed).
• Check the final layout at 100%, 125%, and 150% zoom levels to catch scaling issues that affect line spacing and alignment.
• Resize your window to simulate different screen sizes and observe how content reflows, especially around tables and inline styles.

Use proven tools to simulate & validate rendering

• Use a dedicated email testing tool that renders your email in real Outlook versions (2013, 2016, 2019, 2021, and 365) using actual rendering engines. Tools like Campaign Monitor’s email testing suite or MailTester’s inbox placement tester run through multiple client environments and highlight visual discrepancies.
• Check the final output for line-height inconsistencies — particularly when mso-line-height-rule is applied — which can cause cramped or spaced-out text in Outlook.
• Verify that your email’s layout remains intact when users view it with accessibility or high-contrast settings, which can override CSS behavior.
• For list hygiene, ensure your mailing list is clean. Use MailTester’s bulk verification to filter out invalid, disposable, or catch-all addresses that can lead to unexpected render issues or sender reputation damage.

Outlook Desktop’s rendering engine is notoriously inconsistent with CSS. The only reliable way to ensure visual correctness is testing in a real client, not in simulated previews.

What happens if you ignore the mso-line-height-rule issue?

If you ignore the mso-line-height-rule issue, your email’s layout will break in Outlook desktop clients—text may appear jammed together or unnaturally spaced, making it hard to read. This visual inconsistency reduces engagement, which hurts your sender reputation over time and increases the risk of inbox placement failures. Fixing it early prevents downstream deliverability problems.

Outlook ignores standard line-height in HTML emails

Outlook desktop (2013–2023) uses a proprietary rendering engine that ignores standard CSS line-height declarations. Instead, it relies on the mso-line-height-rule attribute to control spacing between lines. Without it, text can appear crammed or too loose, especially in long paragraphs.

For example, a line-height of 1.4 in your CSS might render as 2.0 or 0.6 in Outlook. This discrepancy isn’t a bug—it’s intentional. Microsoft’s documentation confirms that this behavior is part of the legacy Word-based email renderer.

Why poor layout hurts deliverability

When users can’t read your email due to tight or inconsistent spacing, they’re more likely to skip it. Low engagement—measured as read rates, click-throughs, and time spent—signals to ISPs that your content is irrelevant or unengaging.

While no one source publishes a direct algorithmic threshold, industry-standard practices from return-path and Litmus consistently show that low engagement correlates with degraded inbox placement over time. Even a 5% drop in open rate over three months can trigger increased spam filtering.

You don’t need a perfect layout to deliver emails, but consistent, readable formatting reduces bounce risk, boosts trust in your brand, and supports long-term deliverability. If your emails look broken, recipients may mark them as spam or unsubscribe without a second thought.

Use tools like our inbox placement tester to see how your email renders across Outlook, Gmail, and Apple Mail. Real-time feedback shows visual flaws before you send. You can also verify your entire list with our bulk verification tool to catch invalid, catch-all, or role accounts that could inflate your bounce rate.

How MailTester helps prevent deliverability issues from formatting bugs

You can't fix render bugs in Outlook by changing your markup alone, but MailTester helps prevent deliverability issues caused by them—by catching invalid or risky email addresses before they land in inboxes. It reduces bounces, prevents sender reputation strain, and gives you a real-world preview of how your email will behave across inboxes, including Outlook’s HTML quirks. The inbox-placement test simulates delivery in live environments, highlighting layout problems that might otherwise go undetected.

Keep your list clean, reduce the risk of reputation damage

Even a perfect HTML template can fail if it hits a dormant or invalid address. MailTester scans your list for real delivery risks: non-existent domains, role accounts, disposable email providers, and catch-all setups that often trigger rejections. By filtering these out early, you avoid the cumulative effect of hard bounces—something that hurtful to your sender reputation. According to Return Path, consistent sending to valid addresses is one of the top three factors in inbox placement, and a clean list is the first step.

See how your emails render in real conditions

While Outlook's line-height and mso-line-height-rule quirks are part of the rendering challenge, MailTester doesn’t render your email—it tests whether it reaches the inbox at all. The inbox-placement test delivers your message to major providers like Gmail, Outlook, and Yahoo, so you can see how layout issues, including spacing inconsistencies, impact visibility. It’s not a rendering simulator, but it tells you whether your email makes it past filtering and lands readable.

When results flag potential layout problems, the in-app AI assistant helps you interpret what they mean. It doesn’t write code, but it can point to common fixes—like reviewing tables or spacing values that break in Outlook—based on known patterns in industry deliverability data. Let's say your email has inconsistent spacing in Outlook: the AI might suggest checking for inline styles or the use of line-height in a single table cell. It doesn’t replace testing—but it helps you act faster.

Use the bulk verification tool on your next campaign to catch invalid addresses before they hurt deliverability. Or integrate the verification API into your signup flow to verify addresses in real time. Either way, you’re reducing the risk of technical issues becoming reputation-killer bounces—before they happen.

Common myths about Outlook CSS fixes

You don’t need to rely on hacks like
tags or assume web previews reflect desktop behavior—Outlook desktop is its own beast. It ignores most modern CSS, especially margin and padding, and treats line-height differently than other clients. Relying on myths leads to wasted time and inconsistent results. Stick to proven methods: tables, inline styles, and real-world testing.

Reality-check on common myths

• Using <br> tags is a reliable fix. No. These create unpredictable spacing, break responsive layouts, and don’t scale across devices. Outlook’s parsing of line breaks is inconsistent, especially when combined with word wrap or table-based rendering.
• All modern clients support the same CSS. False. Outlook desktop (especially versions 2010–2023) ignores line-height, margin, padding, and many pseudo-selectors. For example, while web clients follow CSS standards, Outlook uses Word’s engine, which has a long history of quirks. This is why Microsoft's own documentation on compatibility with email standards acknowledges limitations.
• Testing in web preview is enough. Never. Web-based previews (even in tools like Litmus or Email on Acid) don’t replicate Outlook’s table and line-height rendering. You’ll miss issues like collapsed or uneven spacing that only appear in the actual desktop client.
• Fix one CSS property and you’re done. No. Outlook’s behavior is not isolated to line-height. It also affects width, display, and table-cell layout. You must test the full output across real mail clients, not just simulated ones.
• Outlook ignores all CSS. Not quite. It supports some inline styles and basic table structures. But relying on it to render modern CSS is a mistake. The safest path is to design for the lowest common denominator—HTML tables, inline styles, and mso-line-height-rule.

Better approaches than myths

Let’s be clear: if you’re building emails for mass deliverability and inbox placement, you’re dealing with real-world constraints. The most reliable fix for Outlook’s line-height quirks isn’t a hack—it’s structure. Use a single <td> with mso-line-height-rule: exactly, combined with precise line-height values in pixels. This ensures consistent vertical spacing even in Outlook’s Word engine.

Testing tools that simulate real Outlook clients are better than guessing. Tools like MailTester’s inbox placement tester help you verify how your email renders in real environments, including Outlook desktop. They don’t just tell you if an email lands in spam—they show you where formatting breaks.

For validating your email list before sending, use MailTester’s bulk verification to remove invalid or risky addresses early. A well-verified list improves sender reputation, which in turn affects inbox placement—even in the most finicky clients.

The bottom line: Fix Outlook line spacing to improve deliverability and trust

Outlook’s inconsistent line spacing can break layout integrity, reduce readability, and signal poor email hygiene to recipients and inbox filters.

Well-formatted emails with proper line-height—especially using mso-line-height-rule—ensure your message appears professional and consistent across clients. Even small fixes like this contribute to higher engagement and improved long-term inbox placement.

Correcting Outlook’s rendering quirks isn’t just about aesthetics. It’s a technical detail that supports deliverability, sender reputation, and user trust.

Sources

• Microsoft (Outlook/Hotmail) is the toughest major provider for senders, with just 75.6% inbox placement and a 14.6% spam placement rate — the highest spam rate among major mailbox providers. — Validity 2025 Email Deliverability Benchmark Report (2025)
• Gmail requires bulk senders to keep user-reported spam rates below 0.3%, warning that rates above 0.1% already hurt inbox delivery — just 3 complaints per 1,000 emails crosses the line. — Google Email Sender Guidelines FAQ (2024)

Keep reading

• Inbox placement by mailbox provider: Gmail, Outlook, Yahoo and spam filters (complete guide)
• How Do SpamAssassin BAYES Rules Affect Email Deliverability in 2026
• How to Define Email Inbox Placement Metrics in Vendor SLAs
• Ensure Intercom Messages Pass Spam Filters with Email Verification
• Postmaster Tools V2 Migration Error Codes Explained

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Does mso-line-height-rule work in Outlook on Mac?

No. Outlook on Mac uses the same rendering engine as Apple Mail and does not support mso-line-height-rule. Use standard CSS and test separately.

Can I use mso-line-height-rule with tableless layouts?

Yes, but only if you use inline styles. It may not apply if the style is in a linked or embedded stylesheet in Outlook.

Is mso-line-height-rule still needed in 2026?

Yes—Outlook Desktop on Windows continues to use Word’s engine in 2026, and the bug remains unresolved.

Why does my email look fine in webmail but broken in Outlook?

Webmail clients (Gmail, Yahoo) use their own rendering engines. Outlook Desktop relies on Word, which ignores standard line-height rules. Test in both.

Can I use other CSS properties to fix line height in Outlook?

Yes, but poorly. Use padding, margin, or line-height with mso-line-height-rule. Avoid relying on margin-top or padding for spacing in text blocks.

What’s the difference between 'exactly' and 'atleast' in mso-line-height-rule?

'exactly' forces precise spacing. 'atleast' preserves minimum spacing but allows more if needed. Use 'exactly' for consistent design.

Should I always use mso-line-height-rule in all email templates?

Only where line height is critical. Overusing it can cause issues in non-Outlook clients when not paired with standard CSS.

How do I test my email in multiple Outlook versions?

Use a cloud-based tester with real inbox snapshots, or set up test accounts in different Outlook versions on Windows.

Does using mso-line-height-rule affect spam filtering?

No. It only affects rendering. However, proper formatting supports deliverability by maintaining engagement.

Is there a way to avoid Outlook-specific CSS entirely?

No. Outlook Desktop’s unique rendering engine requires targeted fixes. Avoiding these CSS rules makes your emails less reliable.

Can MailTester detect rendering issues like Outlook line-height bugs?

No, MailTester does not render emails. But it helps ensure your list is valid and your sends are not blocked by deliverability issues.

What’s the fastest way to test an email for Outlook rendering issues?

Use a dedicated inbox placement tester with real Outlook client snapshots, not just browser-based previews.