# 788

Image Blocking in Email Clients: Current Conditions and Best Practices

ALT text and clean HTML keep your message readable when clients block images, protecting engagement across major inboxes.

Talk to the Business Architect →Every engagement begins with a conversation
with the Business Architect.

In Short

Image blocking in email clients changes how an email reads, how it renders, and whether its structure survives at all. Some clients turn images on by default, some turn them off, and some switch behavior for trusted senders. The practical result is uneven display across webmail and desktop clients, plus a separate group of recipients who block HTML entirely. That means an email cannot depend on images for meaning, navigation, or basic readability. The article’s position is direct: build for the blocked-image case first, then treat image display as a conditional layer.

Many people, either by email client defaults or personal preference, are blocking images in the HTML-formatted messages they are accepting. And then there are a small number of people who block HTML entirely. As Nitin Lodha points out, according to a study by Team Chitrangana 30% of your recipients don’t even know that images are disabled. In any case, it’s logical for recipients to block images and good practice for us to prepare for this scenario.

So what happens to our emails when images are blocked? What are the best practices for ensuring accessibility and optimizing presentation therein? What are default settings across the board? Let’s get down to answering these questions.

Default Settings in Popular Email Clients

Every client has its own default settings regarding displaying/hiding images. And while most email clients have a setting to turn images on or off, some offer conditional settings which are contingent upon known senders or other factors. The following table outlines the default settings of popular desktop- and webmail-clients. (Note that I’m reporting the settings of my personal versions of each client and that settings may differ from one version to another.). I have included contextually-relevant references to ALT text as part of this article. For a more in-depth look at how ALT text renders in popular email clients, you may want to read a more comprehensive article I wrote about ALT text.

Image Blocking in Webmail Clients
ClientDefault Img DisplayTrusted-Sender Img DisplayRenders ALT Text
Yahoo MailonNoNo
Yahoo Mail BetaonYesYes
Windows Live MailoffYesNo
GmailoffYessometimes
.MaconNosometimes
HotmailonYesNo
AOLonYesYes

Image Blocking in Desktop Clients
ClientDefault Img DisplayTrusted-Sender Img DisplayRenders ALT Text
Apple MailonNoNo
ThunderbirdonYesYes
Outlook 2007offYessort of
Outlook 2003offYesYes
Outlook ExpressonNoYes
Lotus NotesonYesYes
EudoraonNosort of
EntourageonNoYes
AOLoffYesNo

So now that we’ve covered the settings in popular email clients, let’s outline how we can help our emails survive image blocking.

Recommendations for Successful Deployment

From my perspective, an email is successful when it meets the following goals:

  • Retains visual integrity in the most commonly used email clients with images enabled.
  • Retains readability in the most commonly used email clients with images disabled.
  • Is readable to people with visual disabilities and navigable to people with mobility disabilities.
  • Is low in weight for recipients using mobile devices and dial-up connections.
  • Is deployed to a permission-based list of subscribers.
  • Meets CAN-SPAM Act requirements.
  • Legitimately passes common tests employed by spam filters.
  • Looking at this list it becomes clear just how important it is to consider

Become a “Known Sender”

Nearly every email client in my test suite enables people to automatically display images when a message is from a “known sender” (senders appearing in white lists, contact lists or address books). Because our subscribers have requested to receive emails from us, they will naturally want to ensure they receive the messages. Spam filters can disrupt legitimate communication when subscribers are unaware of how they function. With a couple, simple notifications we can increase our chances of success:

  • Ask a subscriber to add the email-list address to their address book (right on the subscribe form) and briefly explain why.
  • Enable a double opt-in subscription process, and send a plain-text confirmation which includes a request to add the email-list address to a recipient’s address book. And, again, briefly explain why.

Informing a subscriber about this simple step will increase our chances of images being enabled and will help us legitimately pass through spam filters.

Prepare for Disabled Images

So we’ve created a structurally-sound template, we’re preparing to send our email to a permission-based list of subscribers and we’ve taken steps to see our list email-address into the address books of the said subscribers. There are still a number of people on our lists who will intentionally block images, and therefore we should account for that scenario.

I wrote an article outlining a technique for this very purpose. With the releases of Yahoo Mail Beta and Windows Live Mail we lose the ability to integrate the aforementioned technique. However, Ryan Kennedy from the Yahoo Mail team has pointed out that they are looking into potential resolutions for this obstacle.

Positioning aside, there are some things we can do to retain the integrity of our emails when images are disabled:

  • Begin an email with HTML text or logical ALT text. We can decide what a reader sees in a preview pane or small message-window. If we’re prepared, we can optimize the experience of scanning messages. Moreover, some applications offer the ability to preview the first few lines of text before an email is loaded/viewed.
  • Use ALT text. This seems so obvious I’m almost embarrassed mentioning it. However, I don’t have enough fingers and toes to count the email newsletters I receive sans ALT text, so there it is.
  • Use captions for contextually-important images. In lieu of proper support for ALT text across the board, we can add captions to images which are vitally important to the content of an email.

Avoid Image-Based Emails

Again, this is something which should seem obvious. But image-based emails are often practiced as a simple, easy method of delivering a pretty design irrespective of the rendering circus among the array of common email-clients. When we ponder image blocking as part of the rendering equation, it’s easy to see how an image-based email could be completely destroyed with a single preference. Furthermore, this doesn’t take into consideration file sizes for mobile/dial-up recipients, accessibility for those visually impaired or the HTML-to-text ratio that popular spam filters apply with their algorithms.

In summary, we should be giving serious consideration to image-blocking and what we can do about it. It’s natural and reasonable why people disable them, but with the right approach we can improve the experience for our subscribers.

Frequently asked

Which client groups in the article default to images on, and which default to off?
The article separates webmail and desktop clients, and the pattern is not uniform. In the webmail group, Yahoo Mail, Yahoo Mail Beta, Hotmail, AOL, and .Mac default to images on, while Windows Live Mail and Gmail default to off. In the desktop group, Apple Mail, Thunderbird, Outlook Express, Lotus Notes, Eudora, and Entourage default to on, while Outlook 2007, Outlook 2003, and AOL default to off. The practical point is that senders cannot infer display behavior from client family alone.
What changes when a recipient is a trusted sender versus an unknown sender?
Trusted-sender status can override the default image setting in some clients. The article notes that many clients allow automatic display for known senders, often through white lists, contact lists, or address books. That means a message may render with images when the sender is recognized, even if the same client blocks images from unfamiliar senders.
Why does the article treat image blocking as normal rather than exceptional?
Because the behavior is already common and partly invisible to recipients. The article cites a Team Chitrangana study, through Nitin Lodha, that says 30% of recipients do not even know images are disabled. That makes image blocking a design condition, not a corner case, and it forces the email structure to carry the message without relying on rendered assets.
What is the difference between blocked images and blocked HTML in this article?
Blocked images remove visual assets from an HTML email, while blocked HTML removes the HTML layer itself. The article says a small number of people block HTML entirely, which is a stricter condition than image blocking. That distinction matters because an email built around images can fail under both conditions, while a text-first structure has a better chance of remaining legible.
Why does the article place ALT text before captions in the recovery stack?
ALT text is the first structural substitute for an image because it appears in places where the image does not. The article then adds captions for contextually important images because ALT text support is not consistent across clients. In practice, ALT text carries the immediate meaning, and captions preserve context when the client renders poorly or not at all.
When does the article say captions matter more than decoration?
Captions matter when an image carries essential meaning rather than decorative value. The article calls them appropriate for images that are vitally important to the content of an email, especially where proper ALT text support is not available across clients. That makes captions a structural layer, not a style choice.
How does the article connect address-book placement to spam-filter behavior?
It treats address-book placement as both a rendering issue and a deliverability issue. If subscribers add the sender to contacts, many clients are more likely to display images, and the sender is also more likely to pass through spam filters legitimately. The article recommends asking for that action on the subscribe form and again in a double opt-in confirmation.
What makes an email low in weight, and why does that matter here?
The article does not define a byte threshold, but it ties low weight to lighter delivery for mobile and dial-up recipients. That concern is part of the deployment goals list, which means image-heavy messages create a delivery burden beyond appearance. A lighter email is structurally easier to load when images are blocked or bandwidth is limited.
What does the article imply about image-heavy design versus text-first design?
It implies that image-heavy design depends on a rendering outcome the sender does not control. A text-first design survives blocked images, mobile previews, accessibility needs, and spam-filter scrutiny more reliably. The article does not reject design; it rejects design that cannot remain legible when the image layer disappears.
Does the article present any client-specific exception where the blocked-image technique stops working?
Yes. It says that with Yahoo Mail Beta and Windows Live Mail, the technique it previously outlined can no longer be integrated. It also notes that Ryan Kennedy from the Yahoo Mail team said they were looking into potential resolutions. That is a concrete reminder that client behavior changes, so the structure must be re-evaluated against current conditions.
Why does the article connect image blocking to accessibility rather than only deliverability?
Because the same structural choices affect both. The article says a successful email must be readable to people with visual disabilities and navigable to people with mobility disabilities. If meaning sits inside images, those users lose access when images are blocked or when assistive tools encounter weak structure.
What should be validated before deployment, based on the article’s logic?
The article’s logic requires validation of the template against real client behavior before scaling. It starts with structure, then list permission, then sender recognition, then blocked-image rendering, and only after that does it treat deployment as sound. That sequence reflects the operating rule behind the content: ideation, validate, execution.
When is ALT text not enough on its own?
ALT text is not enough when an image carries essential context and the client renders ALT text inconsistently. The article addresses that gap by recommending captions for contextually important images. In other words, ALT text states what the image is; captions can state why it matters in the message.

Wondering where your business sits in the commerce shift?

We map how ready you are today — and design the architecture that keeps you the answer, not the afterthought.

Talk to us