Which Email Clients Support BIMI in 2026: Full Comparison
A comprehensive comparison of email clients that support BIMI in 2026, including which require a VMC, which accept self-asserted logos, and what this means for your sender strategy.
The Supported Clients: Which Email Clients Support BIMI in 2026
BIMI (Brand Indicators for Message Identification) adoption varies significantly across email clients. Before investing in a Verified Mark Certificate (VMC) or configuring a self-asserted BIMI record, you need to understand exactly where your logo will render — and where it will not. This article provides a definitive, structured comparison of email client support as of 2026.
How BIMI Support Is Categorised
Email clients fall into three distinct groups based on their BIMI implementation requirements:
- Group 1 — VMC Required: The client renders your logo only when a valid, CA-issued Verified Mark Certificate (VMC) is present in your BIMI record.
- Group 2 — Self-Asserted Accepted: The client renders your logo based on a valid BIMI DNS record alone, without requiring a VMC.
- Group 3 — No Support: The client does not implement BIMI and will not render brand logos via this mechanism.
Understanding which group each client belongs to determines your certificate investment requirements and your realistic reach.
Group 1: VMC Required
These clients enforce certificate validation before rendering a logo. A BIMI record without a valid a= authority evidence tag pointing to a VMC will be ignored.
Gmail (Google Workspace & Personal)
| Property | Detail |
|---|---|
| Support status | Active — VMC required |
| Introduced | July 2021 |
| Platforms | Web (mail.google.com), Android, iOS Gmail app |
| DMARC requirement | p=quarantine or p=reject |
| VMC issuers accepted | DigiCert, Entrust |
| Logo format | Tiny SVG P/S profile |
| Display location | Avatar/sender icon in inbox list and message view |
Key considerations:
- Gmail is the single largest email client by active users globally, consistently holding between 27–30% of the email client market share.
- Gmail renders the logo in both the inbox list view and the open message view, maximising brand visibility.
- Without a VMC, Gmail will silently ignore your BIMI record. No fallback partial rendering occurs.
- Google Workspace accounts follow the same rules as personal Gmail accounts.
Apple Mail
| Property | Detail |
|---|---|
| Support status | Active — VMC required (BIMI + MLS) |
| Introduced | iOS 16 / macOS Ventura (2022), expanded since |
| Platforms | Apple Mail on iOS, iPadOS, macOS |
| DMARC requirement | p=quarantine or p=reject |
| VMC issuers accepted | DigiCert, Entrust |
| Logo format | Tiny SVG P/S profile |
| Display location | Sender avatar in inbox list and message thread |
Key considerations:
- Apple Mail commands approximately 10–14% of global email client market share, with significantly higher share among premium consumer demographics in North America and Western Europe.
- Apple’s implementation aligns with the BIMI specification but Apple also operates its own Mail Privacy Protection (MPP) layer, which does not interfere with BIMI logo rendering.
- Apple Mail on iCloud.com (webmail) does not currently support BIMI rendering. Support is limited to the native Mail application.
- The combination of Gmail and Apple Mail means a VMC unlocks logo rendering for approximately 40–44% of the global email client market.
Group 2: Self-Asserted / No VMC Required
These clients render BIMI logos based on a valid, correctly formatted BIMI DNS record. A VMC is not required, though having one does not break rendering.
Yahoo Mail
| Property | Detail |
|---|---|
| Support status | Active — self-asserted accepted |
| Introduced | 2020 (earliest major BIMI adopter) |
| Platforms | Web (mail.yahoo.com), iOS app, Android app |
| DMARC requirement | p=quarantine or p=reject |
| VMC requirement | Not required |
| Logo format | Tiny SVG P/S profile |
| Display location | Sender avatar in inbox list |
Key considerations:
- Yahoo was the first major provider to implement BIMI at scale, making it the longest-running production deployment.
- Yahoo Mail holds approximately 3–4% of global email client market share, though its share is higher among older demographics in the United States.
- Because Yahoo accepts self-asserted records, senders can achieve logo rendering on Yahoo with only a valid BIMI DNS record and a correctly formatted SVG — no certificate purchase required.
AOL Mail
| Property | Detail |
|---|---|
| Support status | Active — self-asserted accepted |
| Platforms | Web (mail.aol.com) |
| DMARC requirement | p=quarantine or p=reject |
| VMC requirement | Not required |
| Logo format | Tiny SVG P/S profile |
| Infrastructure | Shares backend infrastructure with Yahoo (Verizon Media / Yahoo Inc.) |
Key considerations:
- AOL Mail operates on the same underlying mail infrastructure as Yahoo Mail. BIMI configuration that works for Yahoo will function identically for AOL.
- AOL’s market share is minimal (under 1% globally) but relevant for senders targeting legacy US consumer audiences.
Fastmail
| Property | Detail |
|---|---|
| Support status | Active — self-asserted accepted |
| Platforms | Web (fastmail.com), iOS app, Android app |
| DMARC requirement | p=quarantine or p=reject |
| VMC requirement | Not required |
| Logo format | Tiny SVG P/S profile |
Key considerations:
- Fastmail is a privacy-focused independent email provider with a smaller but technically sophisticated user base.
- Its self-asserted BIMI support makes it straightforward to implement without additional certificate overhead.
- Market share is under 1% globally but disproportionately represented among developers, privacy-conscious users, and small business professionals.
La Poste (laposte.net)
| Property | Detail |
|---|---|
| Support status | Active — self-asserted accepted |
| Platforms | Web |
| Geographic relevance | France |
| VMC requirement | Not required |
Key considerations:
- Relevant primarily for senders with significant French consumer audiences.
- Demonstrates that BIMI adoption is not limited to US-centric providers.
Group 3: No BIMI Support
These clients do not implement the BIMI specification. Logo rendering via BIMI is not possible regardless of DNS record configuration or certificate status.
Microsoft Outlook / Exchange Online
| Property | Detail |
|---|---|
| Support status | Not supported |
| Platforms | Outlook desktop (Windows, macOS), Outlook Web Access (OWA), Outlook mobile (iOS, Android), Exchange Online |
| Microsoft 365 | Not supported |
| Announced support | None confirmed as of 2026 |
Key considerations:
- Outlook and Exchange Online represent the most significant gap in BIMI coverage. Microsoft’s combined email client and server ecosystem accounts for approximately 30–35% of global email client market share, making it the largest single block of unsupported users.
- Microsoft has not published a public roadmap for BIMI support. The absence of support is a deliberate product decision, not a pending implementation.
- Microsoft operates its own sender reputation and brand indicator system (BIMI is not part of it). Outlook displays sender profile images sourced from Microsoft account data, LinkedIn profiles, and Gravatar — not from BIMI records.
- Senders should not assume that a BIMI record will have any effect on how their emails appear in any Microsoft mail client.
Other Clients With No BIMI Support
Receiver display is only one part of a BIMI deployment. See BIMI: how it works for the full implementation path.