Force Thunderbird to Show Plain Text

Why You Might Want to Force Thunderbird to Show Emails in Plain Text

You open an email from an unknown sender, and suddenly your inbox starts acting weird—slow, jumpy, or even sending data back to a remote server you never authorized. It's not just paranoia. HTML emails often come with hidden tracking pixels, embedded scripts, and links that can expose you to surveillance or phishing. If you're handling sensitive content or just want to avoid digital ghosts, seeing emails in plain text is a smarter default.

Thunderbird renders HTML by default, which means every email is processed as code. That introduces unnecessary risk. Switching to plain text mode isn’t about nostalgia—it’s a deliberate security choice. It strips away rendering vulnerabilities, reduces distractions, and keeps your inbox clean of hidden trackers. This guide explains how to force Thunderbird to show emails in plain text, and why doing so matters more than you think.

Key takeaways

HTML emails can include tracking pixels and malicious scripts, even without interaction.
Forcing Thunderbird to display emails in plain text eliminates rendering risks and improves security.
Plain text mode is especially useful for handling sensitive data, reducing inbox spam noise, and minimizing phishing exposure.

How to Force Thunderbird to Display Emails in Plain Text

You can force Thunderbird to display incoming emails in plain text by changing your account’s default message format. This prevents HTML rendering, reducing phishing risk and ensuring consistent formatting across devices. The setting applies globally to one account at a time. After the change, restart Thunderbird for it to take effect.

Set Plain Text as Default Message Format

Open Thunderbird and click on the menu bar at the top of the window.
Click Tools, then select Account Settings from the dropdown menu.
In the left panel, choose the email account you want to modify—this setting applies per account, not globally.
Click on the Composition & Addressing tab in the settings pane.
Under Default message format, select Plain Text from the dropdown menu. This disables HTML rendering for all incoming mail from this account.
Close the settings window. Restart Thunderbird to ensure the change is properly applied.

After restarting, Thunderbird will display all incoming messages in plain text format by default. This is particularly useful for security-conscious users or when testing email deliverability—ensuring content renders consistently.

The 6 steps described in “Set Plain Text as Default Message Format”, in order.

Setting Thunderbird to plain text also aligns with industry standards for email transparency. According to the RFC 8314, plain text is the baseline format for email, designed for universal compatibility and readability. While many modern clients default to HTML, forcing plain text reduces reliance on potentially broken or malicious code in messages.

When to Use This Setting

Use this setting when you’re reviewing inbound emails that might contain malicious scripts or embedded content. It helps avoid exposure to common attack vectors like hidden iframes or JavaScript in emails. It also improves readability when you’re debugging or testing delivery—just as you would with an inbox placement test.

If you're validating email lists before sending, consider using MailTester’s bulk verification tool to ensure recipients’ inboxes accept your plain-text messages without issues. This step helps avoid bounce rates and deliverability pitfalls common with outdated or incorrect email formats.

What Happens When You Set Thunderbird to Plain Text Only

When you set Thunderbird to send and display emails in plain text only, every new message you compose will be sent as unformatted text—no HTML, no styles, no embedded images. Existing messages in your inbox stay as they are unless you manually re-save them. HTML content is stripped during rendering, leaving only raw text. This setting applies per account, so you can use plain text for one email address and keep HTML enabled for another.

How Messaging Changes After the Setting Is Applied

Once you enable plain text mode, every new email you write—regardless of formatting attempts—will be sent as plain text. You can't accidentally send rich formatting, which helps avoid issues with spam filters that flag HTML-heavy messages. This is especially useful if you're sending to mailing lists or systems that reject non-plain-text content outright.

Existing messages already in your inbox won’t change format automatically. If you opened a message with embedded images or styled text, it will still display that way until you re-save or re-download it. You can still view HTML emails in your inbox, but composing new ones will default to plain text.

What Happens to Media and Styling

HTML content—including styling, colors, bullet points, and embedded images—is completely removed during rendering. Even if the original email had images hosted on a remote server, they won't appear. The message will show only the raw text, with line breaks preserved. This reduces email size and simplifies the rendering experience across devices and email clients.

Some users switch to plain text to improve deliverability. While plain text doesn’t guarantee inbox placement, it reduces the chance of being flagged by spam filters that associate HTML with phishing or promotional abuse. According to RFC 5322, the standard for email format, plain text remains the most universally supported format for email transmission.

For teams managing large contact lists, checking email validity before sending can avoid unnecessary plain text send problems. You can verify your list’s quality first with tools like MailTester’s bulk verification to ensure every address is active and deliverable. That way, you’re not just sending plain text—you’re sending it to addresses that actually receive it.

When You Should Avoid Using Plain Text Mode

You should avoid forcing Thunderbird to display emails in plain text when your message or receipt depends on visual formatting, interactive elements, or structured layout. HTML emails aren’t just decorative—they’re functional. Rendering them as plain text breaks links, hides images, and strips away critical context. If you’re sending marketing content or receiving time-sensitive, formatted data like invoices or calendar invites, you’re likely losing key information. Always check formatting in a preview before assuming plain text is sufficient.

When HTML Format Is Required for Functionality

Don’t use plain text when sending newsletters or campaigns that use responsive layouts, embedded images, or branded styling—these elements rely on HTML structure to be effective.
Avoid plain text when receiving event invitations with calendar attachments; these require HTML parsing to sync with your calendar app (as defined in RFC 5546).
Never render invoices, reports, or financial statements in plain text—multi-column tables and dollar amounts often misalign or become unreadable.
Don’t disable HTML if you’re using interactive forms embedded in email (e.g., surveys, registration links), as submission buttons may not function.

When You Need to Maintain Sendership Integrity

Some email providers mark plain text-only messages as suspicious or low reputation, especially if they follow a pattern associated with spam or phishing attempts.
Using plain text for marketing emails reduces inbox placement rates—platforms like Gmail and Outlook prioritize rich content from known senders.
When your audience expects branded experiences, forcing plain text signals poor sender hygiene, even if technically valid.
Use tools like MailTester’s bulk verification to check your list for invalid or risky addresses before sending any email—ensuring you’re not accidentally sending to outdated or poorly configured inboxes.

Security Implications of HTML Rendering in Thunderbird

You should disable HTML rendering in Thunderbird because it exposes you to tracking pixels, remote script execution, and IP leaks—risks that disappear when you view emails in plain text. Even unsolicited messages can trigger these threats, making plain text the safer default choice for mail clients.

Tracking and Data Leakage

HTML emails often include hidden tracking pixels—tiny, invisible images hosted on remote servers. When you open such an email, your client downloads the image, secretly notifying the sender you’ve read it. This is a standard tactic in marketing and phishing, commonly documented by privacy researchers at EFF.

Images in HTML emails load from external domains, which can log your IP address, device type, and browser details. This information helps build a profile of your online behavior—data that is entirely avoidable by rendering emails in plain text, where no remote requests are made.

Malicious Scripts and Exploits

Older versions of Thunderbird have known vulnerabilities that can be triggered by malicious HTML or JavaScript in emails. While newer versions patch these, users with outdated software remain at risk. A crafted email can exploit these flaws to execute code, install malware, or redirect your browser.

Even if your Thunderbird is up to date, disabling HTML rendering eliminates the attack surface for these embedded threats. You’re not just blocking spam—you’re avoiding a vector that hackers actively monitor and refine, as noted in reports from Cisco Talos.

When you force Thunderbird to display emails in plain text, all these risks vanish. No image loading. No script execution. No tracking data sent. This isn’t paranoia—it’s a proven defense against common email-based attack methods. For teams managing high-volume email lists, ensuring your team's email clients don’t render HTML can significantly reduce exposure to data leaks and targeted campaigns. If you’re sending to many addresses, verify your list first—tools like MailTester’s bulk verification can detect invalid or risky addresses before they hit your inbox, reducing the number of untrusted messages you even need to parse.

Alternative Security Practices for Email Clients

You can’t force Thunderbird to display all emails in plain text by default, but you can reduce risk by treating it as a security-conscious tool: use a dedicated client for sensitive work, block images automatically, verify senders before engaging, and keep Thunderbird updated. These steps limit exposure to malicious content even if emails arrive in HTML.

Key Security Practices to Implement

Run high-risk or public-facing communications through a separate, isolated email client—like a virtual machine or dedicated email app—for better compartmentalization of threats.
Enable automatic image blocking in Thunderbird: go to Preferences > Privacy & Security, and check "Load remote content in messages" — set it to never. This prevents tracking pixels and malware delivery via images.
Verify sender authenticity before opening any attachment or clicking any link. Check the full email address, look for mismatches in the display name, and avoid unexpected messages, even from known contacts—account compromises are common.
Keep Thunderbird updated. Vulnerabilities in the HTML rendering engine can be exploited through crafted emails. Regular updates patch known flaws—check Mozilla’s official site for release notes and security advisories.

Additional Precautions

Use a read-only or sandboxed environment when reviewing suspicious messages—consider tools like Proton Mail’s shield mode or dedicated email analysis platforms.
Check that your client is set to display messages in plain text by default when possible. Thunderbird doesn’t enforce this, but you can use extensions like Plain Text Emails (available in Thunderbird Add-ons) to override HTML rendering.
Before sending to large lists, run a bulk email verification to detect disposable addresses, invalid formats, and likely-bounce domains—this reduces both spam complaints and the risk of triggering security filters.

Security isn’t about one perfect setting—it’s layered. Even the most secure client can be compromised by user behavior. Stay proactive: verify before you open, update on schedule, and treat email like a potential threat vector, not just a communication channel.

Can You Switch Back to HTML After Choosing Plain Text?

Yes, you can switch back to HTML at any time through the same Account Settings menu where you disabled it. No data is lost, and existing messages remain unaffected—only new outgoing emails will use HTML formatting unless changed again. This setting is fully reversible, with no side effects or configuration issues.

Changing the format is safe and immediate

You don't need to delete or reconfigure your account. Just go to Account Settings, navigate to the composition section, and toggle HTML back on. The change takes effect immediately for future messages. There’s no risk to your stored emails, even if you’ve already sent or received several plain-text messages.

Existing messages stay untouched

Switching back to HTML doesn’t convert past emails. If you previously saved messages in plain text, they remain in that format. Thunderbird preserves the original format of each message as stored. This behavior is consistent with how email clients handle composition preferences—HTML settings apply only to new messages, not archived content.

It's worth noting that some email providers or clients may still display HTML messages as plain text in certain contexts, especially if they’re rendering them in a limited environment. This is not a Thunderbird limitation—it’s a result of how the receiving client interprets MIME types. The MIME standard defines how content types are handled, and Thunderbird follows it precisely.

For users managing large mail queues or mailing lists, verifying that addresses are valid before sending can reduce delivery issues. If you're sending bulk mail, making sure each address is deliverable helps prevent bounces and maintains sender reputation. MailTester’s bulk verification tool helps identify invalid, disposable, or catch-all emails, ensuring your messages reach real inboxes—whether sent in HTML or plain text.

The ability to switch formats freely gives you full control over your email workflow. You can use plain text for quick or sensitive messages, and HTML when you need rich formatting. The key is consistency: pick the right format early, and stick with it until the next intentional change.

Thunderbird’s Built-in Options for Managing Email Format

You can force Thunderbird to display emails in plain text by setting your default composition format to plain text per account. This overrides HTML rendering even if the sender used HTML, and requires no third-party tools. While Thunderbird defaults to auto-detecting format, you can manually control how messages appear using built-in settings—just go to Account Settings and change the default format.

Understanding Thunderbird’s Composition Modes

Thunderbird lets you choose between plain text, HTML, or auto-detect for composing messages. The auto-detect option uses the sender’s preferences but can still render HTML, even if you'd prefer plain text. This behavior often leads to unexpected formatting, especially with promotional or marketing emails that rely heavily on rich content.

HTML messages can include embedded scripts, images, and styling—all of which pose privacy and security risks. If you're focused on clarity, privacy, or compatibility, plain text is often safer and more predictable. Thunderbird’s built-in support for plain text composition means you don’t need plugins to strip formatting; the control is native.

Overriding Default Behavior Per Account

Even when auto-detect is enabled, you can override HTML rendering by setting your default format to plain text. This setting applies per email account and is preserved across sessions. To do this, open Account Settings, go to Composition & Addressing, and select “Plain text” from the “Default format” dropdown.

This change affects how you send messages—but not how you receive them. For incoming messages, Thunderbird still displays HTML by default unless you disable it entirely. However, you can also configure viewing preferences: go to Preferences > Display > Message Body and uncheck “Show HTML content in messages.” This forces Thunderbird to display HTML emails as plain text.

For a more secure workflow, consider validating email addresses before sending, especially when dealing with large audiences. Tools like bulk email list verification help ensure deliverability and reduce the risk of spam triggers that might force unwanted HTML rendering in some clients.

These settings are part of Thunderbird’s long-standing commitment to privacy and user control. As outlined in the MIME standard (RFC 2046), email clients should respect sender formatting while allowing users to override it—something Thunderbird supports transparently. A solid grasp of these options helps maintain consistency, improve security, and avoid unnecessary rendering issues.

Does Setting Plain Text Affect Email Deliverability?

Setting Thunderbird to display emails in plain text has no effect on how those emails are delivered. Deliverability is governed by server-side factors: sender reputation, email authentication (SPF, DKIM, DMARC), list hygiene, and content quality — not by how you view messages in your client. Your display preference is purely local.

What Actually Controls Deliverability?

When an email is sent, its journey begins long before it hits your inbox. The receiving mail server evaluates it based on technical signals: whether your domain is authenticated, if your IP has a clean history, and if your content avoids known spam patterns. These checks happen independently of any client settings, including Thunderbird’s display preferences. The SPF, DKIM, and DMARC records are verified by the receiving server using DNS — not your email client.

For example, a mail server may reject an email not because it’s in HTML format, but because the sender’s IP is listed on a blocklist or the authentication headers don’t align. This process is standardized — RFC 5321 and RFC 5322 define the core rules for email transmission and message structure. You can review the official specification for SMTP behavior at tools.ietf.org/html/rfc5321.

Plain Text and Inbox Placement — A Misunderstood Link

If you're sending emails through Thunderbird (say, from a personal or small business account), sending in plain text may improve inbox placement with some providers. That’s because plain text messages are less likely to trigger spam filters — they don’t carry embedded images, tracking pixels, or complex HTML that could be flagged as suspicious.

But again, this isn’t because Thunderbird is forcing deliverability. It’s about content risk. A plain-text-only message sent from a new or untrusted domain will still be filtered if the sending infrastructure is problematic. High-volume senders who rely on tools like inbox placement testing use such tools to simulate how real email clients and filters react — not to change Thunderbird’s display mode.

Ultimately, your client-side setting only changes what you see. It doesn’t alter how the message is routed, authenticated, or evaluated for delivery. If you’re trying to improve deliverability, focus on the factors that actually matter: clean lists, correct sender authentication, sending only to engaged recipients, and avoiding spammy patterns in your content. Use a tool like email validation to check addresses before you send — that’s where real gains happen.

How to Verify That Your Email List Is Free of Invalid or Risky Addresses

You can clean your email list by using MailTester’s bulk verification to flag invalid, catch-all, or disposable addresses, then remove those with high bounce risks or role-based patterns that harm sender reputation. This step directly reduces delivery failures and improves inbox placement over time.

Scan Your List for Problematic Addresses

Upload your list to MailTester’s bulk verification tool — it checks each email in real time using SMTP, MX, and domain validation. This catches syntax errors, nonexistent domains, and inactive accounts before you send.
Review the results for invalid, catch-all, or disposable addresses — these are red flags. Catch-all domains accept any email, which increases spam risk and bounces. Disposable domains are used for short-term signups and rarely engage, hurting deliverability.
Exclude addresses marked as ‘risky’ — these include role-based emails like info@, sales@, or support@, which often have low engagement and higher spam complaints. They’re common targets for filters. According to Spamhaus, such addresses can trigger filters even if technically valid.

Automate List Hygiene with Your Email Platform

Connect MailTester to Mailchimp, SendGrid, Klaviyo, or HubSpot — via our integrations, cleanup happens automatically before each campaign, reducing manual effort.
Monitor bounce rates and delivery logs — if you see spikes in hard bounces or delivery failures, it may point to malformed addresses or overuse of role-based mailboxes. Tools like RFC 5322 define valid address formats — if your list includes malformed entries, they’ll fail during SMTP validation.
Re-check your list after cleaning — after removing risky or invalid addresses, re-verify the remaining list. A well-maintained list improves sender reputation over time, increasing the chance your messages land in inboxes, not spam folders.

Using MailTester’s real-time verification API or checking individual addresses with the email checker lets you validate addresses on the fly, which helps when building lists from forms or imports.

The 3 steps described in “Scan Your List for Problematic Addresses”, in order.

Final Thoughts: Prioritizing Security Over Convenience

For users handling sensitive information or opening messages from unfamiliar senders, forcing Thunderbird to display emails in plain text removes a significant attack surface. Embedded scripts, pixel trackers, and malicious links can’t execute in plain text mode.

Even with updated software, no client is fully immune to zero-day exploits or social engineering via HTML content. Plain text ensures content is seen exactly as intended—no hidden elements, no rendered images, no dynamic behavior.

Visual appeal from HTML is outweighed by control and clarity. When combined with a clean, verified email list using a tool like MailTester, this approach strengthens both client-side and sender-side defenses.

Sources

Benchmark testing of 15 major email service providers found about 10.5% of legitimate emails land in the spam folder and a further 6.4% go undelivered. — EmailTooltester deliverability benchmark (via WarmForge) (2026)
Only about one quarter of email senders report spam complaint rates below 0.1% — the best-practice band — leaving three quarters exposed to some degree of deliverability degradation. — Validity 2025 Email Deliverability Benchmark Report (2025)

Keep reading

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

Frequently asked questions

Does forcing Thunderbird to display emails in plain text affect receiving emails?

No—this setting only affects how emails are displayed and composed. Received HTML emails are still downloaded in full, but rendered as plain text in the preview.

Can I set plain text mode for only specific email accounts?

Yes—Thunderbird applies the default message format per account, so you can use plain text for personal mail and HTML for work accounts.

Why does Thunderbird show HTML emails by default?

HTML rendering improves user experience by preserving formatting, images, and links. It is the standard for modern email clients.

What happens to images in HTML emails when plain text is enabled?

Images are not displayed. They are ignored during rendering, and no remote loading occurs, enhancing privacy.

Is plain text email safer than HTML email?

Yes—plain text eliminates risks from embedded scripts, trackers, and malicious content while still preserving core message content.

Can I switch back to HTML later?

Yes—simply revisit the Account Settings and change the default message format. No data is lost or corrupted.

How does plain text impact deliverability?

It does not impact deliverability. Delivery depends on technical setup, sender reputation, and content quality, not client-side rendering.

Does MailTester support verifying plain text-only email lists?

Yes—MailTester validates email addresses regardless of intended message format. It checks for validity, catch-all status, and risk factors.

Can I use MailTester with Thunderbird?

MailTester integrates with platforms like Mailchimp and SendGrid. Use it to clean your list before sending via Thunderbird or any client.

Are disposable email addresses safe to receive?

No—disposable addresses are often used for spam or fake signups. Remove them before sending emails to reduce bounce rates and improve reputation.

What is the best way to check if an email list is clean?

Run a bulk verification using MailTester. It checks for invalid, catch-all, risky, or disposable addresses with 98.9% accuracy.

Do I need to re-verify my list after changing Thunderbird settings?

No—client-side settings don’t affect the list. Verify your list separately using MailTester to maintain sender reputation and deliverability.