Latest / Misar.Blog Podcast / What Is BIMI and How to Set It Up (2026 Guide)
Transcript
- What Is BIMI and How to Set It Up (2026 Guide) What Is BIMI and How to Set It Up (2026 Guide) BIMI showing brand logos in email. Photo by Carlos Muza on Unsplash Quick Answer: BIMI (Brand Indicators for Message Identification) displays your brand logo next to your emails in Gmail, Apple Mail, and other supported clients. To set it up: (1) authenticate with SPF, DKIM, and DMARC (p=quarantine or p=reject), (2) create an SVG logo, (3) publish a BIMI DNS record, and (4) optionally verify with a VMC (Verified Mark Certificate). Below, the complete setup guide. On This Page What Is BIMI? How BIMI Actually Works Under the Hood Why BIMI Matters BIMI Requirements Step 1: Authenticate Your Email Step 2: Create Your Logo Step 3: Publish the BIMI Record Step 4: Add a VMC (Optional) Step 5: Verify and Test Real-World Scenarios Common Mistakes When Setting Up BIMI Frequently Asked Questions What Is BIMI? BIMI (Brand Indicators for Message Identification) is an email standard that displays your brand logo next to your emails in supported email clients. How it works: You publish a BIMI DNS record pointing to your logo. Email clients (Gmail, Apple Mail) fetch the logo. Your logo appears next to your emails in the inbox. BIMI was built as a deliberate extension of the existing authentication stack rather than a standalone system. It doesn't introduce a new way to verify who sent an email — it reuses DMARC, which in turn relies on SPF and DKIM, and simply adds a visual reward layered on top of an already-strict authentication posture. This design choice is important to understand: BIMI is not a branding feature you can bolt on independently of your authentication setup. It's structurally impossible to qualify for BIMI without already having strong, enforced authentication in place, which is exactly the point — the logo is meant to function as a visible signal that a message passed a strict verification chain, not just a cosmetic flourish. How BIMI Actually Works Under the Hood When a BIMI-supporting mail client receives a message, it runs through a sequence before deciding whether to render your logo: Authentication check. The receiving client first verifies the message passes DMARC, which itself requires the message to pass SPF or DKIM (or both) and be in domain alignment — meaning the domain in your visible From address matches (or is a subdomain of) the domain that SPF or DKIM actually authenticated. Policy check. The client checks your DMARC policy tag. BIMI generally requires your DMARC policy to be enforced ( p=quarantine or p=reject, not p=none ), and typically expects the policy to apply to essentially all of your mail (a pct=100 posture, meaning the enforcement policy covers the full volume of mail from the domain, not just a sampled percentage) — the logic being that a logo signal tied to a domain that only partially enforces its own authentication policy isn't a reliable trust signal. BIMI record lookup. If authentication passes, the client performs a DNS TXT lookup at default._bimi.yourdomain.com (or a selector-specific record, if you're using BIMI selectors) to find your logo URL and, if present, your VMC/authority evidence location. Logo fetch and validation. The client fetches the SVG from the URL in your record, over HTTPS, and validates that it conforms to the BIMI image spec (a restricted SVG profile — more on this below). If a VMC is present and required by that client (as Gmail requires), the client also validates the certificate chain against the trademark or mark evidence it asserts. Render. If every check passes, the client renders your logo next to the sender name in the inbox list and often in the open-message header area too. Why this sequencing matters for troubleshooting: if your logo isn't showing up, the fault is almost always in step 1 or step 2 — a DMARC alignment failure or an insufficiently strict policy — long before it's actually about the SVG file itself. Most "my BIMI logo won't show" cases trace back to authentication, not artwork. Why BIMI Matters Benefit Impact Brand recognition Your logo builds trust in the inbox Deliverability BIMI signals legitimacy to ISPs Anti-phishing Verified logos reduce spoofing Engagement Recognizable emails get opened more Competitive edge Most senders don't use BIMI yet The Anti-Phishing Angle, Explained The anti-phishing value of BIMI is worth unpacking, because it isn't really about the logo image itself — a phisher could, in principle, still paste your logo into the body of a fake email. The protection comes from what it takes to earn the BIMI display in the first place: strict DMARC enforcement at the domain level. Once your domain enforces DMARC at p=reject (or even p=quarantine ), messages that spoof your domain in the From address without passing your actual SPF/DKIM authentication get rejected or quarantined before they ever reach an inbox — meaning the BIMI logo essentially only appears on messages the receiving system has already confirmed came from your real infrastructure. The logo becomes a visible reward for enforcement you'd ideally want in place anyway, purely from a security standpoint, regardless of whether you care about the branding benefit. The Trust and Recognition Effect Recipients scan inbox lists quickly, relying heavily on visual pattern-matching — sender name, subject line, and (where available) an avatar or logo. A verified brand logo gives your emails a recognizable visual anchor in a crowded inbox in a way plain sender names and generic default avatars can't. Because the vast majority of senders still haven't implemented BIMI, adopting it early is one of the few remaining ways to visually differentiate your emails in the inbox list without changing your actual content. BIMI Requirements The Prerequisites Requirement Details SPF Must pass DKIM Must pass DMARC Must be p=quarantine or p=reject Logo SVG format, square, hosted on HTTPS DNS Ability to add TXT records Supported Clients (2026) Client Support Gmail Yes (with VMC) Apple Mail Yes (no VMC required) Yahoo Yes Fastmail Yes Outlook Partial Domain Alignment: The Requirement Underneath the Requirement The DMARC prerequisite above is doing more work than it might first appear. "DMARC must be p=quarantine or p=reject" implicitly requires that your SPF and/or DKIM authentication be in domain alignment with your visible From address — meaning the domain that's actually cryptographically verified (via DKIM) or authorized (via SPF) needs to match, or be a parent domain of, the domain shown to the recipient. A message can technically pass SPF and DKIM in isolation while still failing DMARC, if those checks were validating a different domain than the one in the visible From header (for example, when a third-party sending platform signs with its own domain rather than yours). This is one of the most common reasons a domain that "has SPF and DKIM set up" still can't get BIMI working: the authentication is passing, but not for the domain BIMI cares about. Why the DMARC Policy Threshold Matters Requiring p=quarantine or p=reject (rather than the monitoring-only p=none ) exists because BIMI's entire trust model depends on the sending domain actually rejecting or quarantining unauthenticated mail claiming to be from it. A domain publishing p=none is only monitoring spoofing attempts via DMARC aggregate reports, not blocking them — so a logo tied to that domain wouldn't reliably mean "we blocked impersonators," undermining the whole point. Step 1: Authenticate Your Email BIMI requires full email authentication first. The Authentication Checklist [ ] SPF record added and passing [ ] DKIM record added and signing enabled [ ] DMARC policy at p=quarantine or p=reject [ ] All records verified (MXToolbox, Mail-Tester) Note: Gmail requires a VMC (Verified Mark Certificate) for BIMI, which requires DMARC at p=quarantine or p=reject. The Recommended Rollout Path to Enforcement Jumping straight from p=none to p=reject is risky if you haven't fully mapped every legitimate sending source using your domain (marketing platform, transactional email service, CRM, support desk, billing system, and so on) — anything sending as your domain that isn't properly authenticated will get rejected outright once enforcement is active. The safer, widely-used path is a gradual DMARC rollout: start at p=none while monitoring aggregate (RUA) reports to inventory every legitimate sending source, fix authentication gaps for each one, move to p=quarantine at a low percentage and increase it as confidence grows, and only then move to p=reject at full coverage. This rollout should be treated as its own project completed before you start the BIMI-specific work, not rushed just to unlock a logo. For the full mechanics of setting up each record, see How to Set Up SPF, DKIM, and DMARC (Step-by-Step 2026) Mail app icon with unread badge on a smartphone screen. Photo by Brett Jordan on Unsplash Step 2: Create Your Logo Logo Requirements Requirement Details Format SVG (Scalable Vector Graphics) Size Square (e.g., 512x512) File size Under 32KB Colors Solid colors (no gradients) Background Solid color or transparent Hosting HTTPS URL (publicly accessible) Why BIMI Uses a Restricted SVG Profile BIMI doesn't accept just any SVG file — it requires a deliberately restricted, security-hardened profile of SVG (commonly referred to as the "Portable/Secure" or "P/S" profile, based on the older SVG Tiny 1.2 specification). This restriction exists because a general-purpose SVG file can embed scripts, external resource references, and other dynamic behavior — exactly the kind of thing you don't want a mail client automatically fetching and rendering across millions of inboxes. The BIMI logo profile strips out scripting, animation, external references, and most dynamic features, permitting only static, self-contained vector shapes and solid colors. This is precisely why most general-purpose design tool exports (a plain SVG straight out of a design app) usually fail BIMI validation on the first attempt — they include metadata, editor-specific namespaces, or unsupported elements that need to be stripped or converted using a dedicated BIMI-compliant SVG conversion tool before publishing. Creating the SVG Create your logo as a square SVG. Ensure solid colors (no gradients, no transparency effects). Keep the file under 32KB. Host it at a public HTTPS URL (e.g., ). Practical Logo Design Notes Because BIMI logos render small — often at avatar size in a crowded inbox list — overly detailed logos with fine text or intricate linework tend to become illegible at that scale. Simpler marks (an icon, a monogram, a simplified version of your full logo) generally read better than a full wordmark. If your primary brand logo already includes a distinct icon or symbol separate from the wordmark, that icon is usually a better BIMI candidate than the combined lockup. It's also worth testing your logo against both a light and dark inbox background, since you don't control what background color it renders against across different clients and themes — a logo that relies on a transparent background disappearing into a dark-mode inbox, for instance, is a common oversight. SVG Example Step 3: Publish the BIMI Record The BIMI DNS Record BIMI uses a TXT record at default._bimi.yourdomain.com: How to Add It Log in to your DNS provider. Add a TXT record: Host/Name: default._bimi Value: v=BIMI1; l= TTL: Default Save and wait for propagation (5 minutes to 48 hours). With VMC (for Gmail) Understanding the BIMI Selector The default portion of default._bimi.yourdomain.com is called the BIMI selector, and it works conceptually the same way DKIM selectors do — it lets you publish more than one BIMI record under the same domain if you ever need to (for example, different logos or certificates for different sending streams), by specifying a different selector name in a header your sending platform adds to the message. For the vast majority of senders using a single logo for the whole domain, the default selector is all you'll ever need, and most sending platforms won't require you to think about this further. Subdomain and Organizational Domain Considerations If you send from a subdomain (for example, mail.yourdomain.com or news.yourdomain.com rather than the bare root domain), your BIMI record generally needs to be published under that exact sending subdomain — default._bimi.mail.yourdomain.com — matching where your DMARC policy and DKIM signing actually apply. Publishing the record only at the organizational root domain while sending from a subdomain is a common setup mistake, since BIMI evaluation is tied to the aligned domain the message actually authenticated against, not just your brand's primary domain in general. Step 4: Add a VMC (Optional) What Is a VMC? A VMC (Verified Mark Certificate) is a digital certificate that verifies your logo is a registered trademark. Gmail requires it for BIMI. VMC Providers Provider Cost DigiCert ~$100-200/year Entrust ~$100-200/year GlobalSign ~$100-200/year How to Get a VMC Register your logo as a trademark (required). Choose a VMC provider. Submit your trademark registration and logo. Receive your VMC (.pem file). Host the VMC at an HTTPS URL. Add the a= tag to your BIMI record. Why the Trademark Requirement Exists The trademark requirement behind a VMC isn't bureaucratic friction for its own sake — it's the mechanism that prevents brand impersonation through BIMI itself. Without some external verification tying a logo to a legally registered mark, nothing would stop a bad actor from simply publishing a BIMI record pointing at a well-known brand's logo and benefiting from the same trust signal. A VMC provider (a Certificate Authority accredited for this purpose) checks your trademark registration against your claimed logo and domain before issuing the certificate, adding a layer of accountability that a plain DNS TXT record alone can't provide. This is also why the process can't be shortcut — if you don't already have a registered trademark for your logo, that registration itself needs to happen first, and trademark registration processes can take significant time (often many months, depending on jurisdiction and any office actions or oppositions along the way), so it's worth starting that process well before you expect to launch BIMI on Gmail specifically. Do You Need a VMC? Client VMC required? Gmail Yes Apple Mail No Yahoo No Fastmail No Is a VMC Worth It If You Don't Need Gmail Support? Given that Apple Mail, Yahoo, and Fastmail display BIMI logos without a VMC, some senders reasonably choose to launch BIMI without one initially, capturing the branding benefit across every non-Gmail client while deferring the VMC cost and trademark process. Whether that trade-off makes sense depends heavily on how much of your subscriber base reads mail in Gmail specifically — for many consumer-facing senders, Gmail represents a large enough share of the inbox that skipping VMC leaves a meaningful portion of your list without the visual benefit, while for others it may be a reasonable way to test BIMI's impact before committing to the VMC cost and trademark process. Step 5: Verify and Test Verification Tools Tool What it checks BIMI Group validator BIMI record validity MXToolbox DNS record presence Gmail test Logo display in Gmail Apple Mail test Logo display in Apple Mail The Test Process Send a test email to Gmail and Apple Mail. Check that your logo appears next to the email. If no logo, check: BIMI record syntax Logo URL accessibility DMARC policy (p=quarantine or p=reject) VMC (for Gmail) Caching and Propagation Delays Even with a fully correct setup, don't expect your logo to appear instantly on the very first test send. Mail clients typically cache BIMI logo and validation results for a period rather than re-fetching and re-validating on every single message, both to reduce load on their systems and on your logo's hosting. This means a first test send might not show the logo even with a perfectly correct configuration, while a retry sent some time later does. Combined with ordinary DNS propagation delay for your BIMI TXT record itself, it's worth allowing at least a day or two of patience before concluding your setup is broken, and re-testing from a clean send (a genuinely new message, not a resend of the same one) rather than assuming the first failed check is final. A Practical Troubleshooting Order When your logo isn't appearing, work through causes roughly in this order, since each step depends on the one before it: confirm DMARC is actually enforcing ( p=quarantine / p=reject, not p=none ) and that your message is passing in alignment (not just passing SPF/DKIM for an unrelated domain); confirm the BIMI TXT record resolves correctly and has valid syntax; confirm the logo URL is reachable over HTTPS and returns a valid, spec-compliant SVG; and only then, if targeting Gmail, confirm your VMC is valid, unexpired, and correctly referenced in the a= tag. Skipping straight to re-validating the SVG when the real issue is a DMARC alignment failure is one of the most common time-wasters in BIMI troubleshooting. Real-World Scenarios Scenario 1: A company with SPF/DKIM but stuck at DMARC p=none. A mid-size company has had SPF and DKIM correctly configured for years but never moved DMARC past the initial monitoring policy, out of caution about breaking third-party sending tools. BIMI simply won't activate under p=none regardless of how correct the logo and DNS record are — the fix is completing a proper DMARC rollout to enforcement first, using aggregate reports to confirm every legitimate sender is accounted for before flipping to p=quarantine or p=reject. Scenario 2: A logo that passes everywhere except Gmail. A brand publishes a correct BIMI record with a valid, spec-compliant SVG and sees their logo appear reliably in Apple Mail and Yahoo within days — but nothing shows in Gmail. The missing piece is the VMC; without a trademark-backed certificate referenced in the a= tag, Gmail simply won't display the logo no matter how correct everything else is. Scenario 3: A subdomain sender publishing the record in the wrong place. A company sends its marketing email from news.brand.com but publishes its BIMI record only at default.bimi.brand.com. Because authentication and alignment are evaluated against the actual sending subdomain, the record needs to live at default.bimi.news.brand.com to be found and validated correctly. Common Mistakes When Setting Up BIMI Attempting BIMI before DMARC is at enforcement. No amount of logo or DNS correctness matters if your DMARC policy is still p=none. Exporting an SVG straight from a design tool without conversion. General-purpose SVG exports almost always fail the restricted BIMI profile and need dedicated conversion/validation. Publishing the BIMI record at the wrong domain level. Especially common when sending from a subdomain but only publishing the record at the root domain. Assuming the logo will appear immediately after publishing. Caching and propagation delays mean it's normal to wait before the logo shows up, even with a correct setup. Skipping the VMC and being surprised Gmail doesn't show the logo. Non-VMC setups work in several major clients but not Gmail — plan for this explicitly rather than assuming universal support. Using an overly detailed logo that becomes illegible at small inbox sizes. Simpler marks generally perform better visually than full detailed lockups. Forgetting to test against both light and dark inbox themes. A logo that disappears against a dark background is a common, easily-avoidable oversight. Frequently Asked Questions What is BIMI in email? BIMI (Brand Indicators for Message Identification) is a standard that displays your brand logo next to your emails in supported clients like Gmail and Apple Mail. How do I set up BIMI? Authenticate with SPF, DKIM, and DMARC (p=quarantine or p=reject), create an SVG logo, publish a BIMI TXT record at default._bimi.yourdomain.com, and add a VMC for Gmail. Does BIMI improve email deliverability? BIMI signals legitimacy to ISPs and can improve engagement (recognizable emails get opened more), which indirectly helps deliverability. Is BIMI free? The BIMI DNS record is free. A VMC (required for Gmail) costs ~$100-200/year and requires a registered trademark. Why is my BIMI logo not showing in Gmail? Gmail requires a VMC (Verified Mark Certificate). Check your DMARC policy (must be p=quarantine or p=reject), BIMI record syntax, and logo URL. Does BIMI work in Outlook? Outlook has partial BIMI support. Gmail, Apple Mail, Yahoo, and Fastmail have the best support. Can I use a PNG or JPEG logo for BIMI? No — BIMI requires a specific restricted SVG profile, not raster image formats like PNG or JPEG. A raster logo needs to be recreated or converted as a compliant vector file. Why does BIMI require DMARC enforcement instead of just SPF and DKIM? Because BIMI's trust model relies on the sending domain actually rejecting or quarantining unauthenticated mail impersonating it. SPF and DKIM alone don't guarantee that unauthenticated mail is blocked — DMARC at enforcement is what makes that guarantee, and BIMI is built specifically on top of that guarantee. Do I need a separate BIMI record for each subdomain I send from? Generally yes, if authentication and DMARC alignment are evaluated at that subdomain level. The BIMI record needs to be published at the domain that actually sent and authenticated the message, which for subdomain-based sending means publishing under that subdomain rather than only the root domain. How long does it take for a BIMI logo to start appearing after setup? Beyond normal DNS propagation, mail clients cache logo and validation results, so it can take longer than a single test send to see the logo appear even with a fully correct setup. Allow at least a day or two, and retest with a fresh message rather than assuming an early failed check is final. Can small businesses realistically get a VMC without a big legal budget? It's possible, but it requires an actual registered trademark for the logo, which involves its own separate cost and timeline through a trademark office (and potentially legal help), on top of the VMC provider's own fee. Businesses without an existing registered trademark should treat trademark registration as a prerequisite project, not a quick add-on step. Does BIMI replace the need for SPF, DKIM, and DMARC? No — it's the opposite. BIMI is entirely dependent on SPF, DKIM, and DMARC already being correctly configured and enforced. You cannot get BIMI working without full authentication in place first. Will BIMI logos look different across light mode and dark mode inboxes? They can, depending on how your logo is designed. A logo with a transparent background or colors that only work against a light background may become illegible or disappear in dark mode. Testing your logo against both themes before publishing is worth the extra step. Is BIMI a ranking or spam-filtering factor on its own? Not directly — BIMI itself is a display feature, not a spam-filtering signal. Its deliverability benefit comes indirectly, through the strict DMARC enforcement it requires you to already have in place, and through the engagement lift that a recognizable, verified logo can produce. Tags: Related Reads How to Set Up SPF, DKIM, and DMARC (Step-by-Step 2026) What Is Email Warm-Up and Do You Really Need It? How to Set Up a Custom Tracking Domain for Email Links (CNAME Guide 2026) How to Get Off an Email Blacklist (Step-by-Step 2026)