You have probably noticed it in your own inbox: some brands show a small logo next to their name in the message list, while everyone else gets a generic gray circle with an initial. That logo is not a Gmail perk you buy. It is BIMI, and it is one of the clearest visual signals a recipient gets that a message is from a real, verified sender before they even open it.
BIMI stands for Brand Indicators for Message Identification. It is a standard that lets you publish your logo so that supporting inboxes (Gmail, Apple Mail, Yahoo, Fastmail, and others) can display it next to your authenticated messages. The catch, and the reason so many teams try BIMI and give up, is that BIMI is not really a logo feature. It is a reward for getting the boring parts of email right first. This guide walks through exactly what BIMI needs, how to set it up, and why your list hygiene matters more than your artwork.
What BIMI Actually Requires
BIMI is the last brick in a wall, not the foundation. Before an inbox will show your logo, it checks that you have already done everything a trustworthy sender does. Here is the full dependency chain, in order.
1. SPF and DKIM must pass
SPF (Sender Policy Framework) tells receivers which servers are allowed to send on behalf of your domain. DKIM (DomainKeys Identified Mail) cryptographically signs your messages so receivers can confirm they were not tampered with in transit. BIMI does not display for a message unless at least one of these aligns with your sending domain. In practice you want both configured correctly.
2. DMARC must be enforced
This is the gate most senders trip over. DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receivers what to do when SPF or DKIM fails. BIMI requires your DMARC policy to be set to quarantine or reject, not the passive p=none. A record that enforces looks like this:
v=DMARC1; p=reject; rua=mailto:[email protected]You cannot go straight to p=reject without breaking legitimate mail if your authentication is not already clean. Most teams roll out DMARC in stages: start at p=none to collect reports, fix every source that fails alignment, move to p=quarantine, and only then to p=reject.
3. A properly formatted logo (SVG Tiny PS)
BIMI does not accept any SVG. It requires the SVG Tiny Portable/Secure profile, which is a stripped-down version of SVG with no scripts, no external references, and a square aspect ratio. Your logo needs to be centered, readable at small sizes, and hosted over HTTPS.
4. A VMC for the major mailboxes
Gmail and Apple Mail require a Verified Mark Certificate (VMC) before they will display your logo. A VMC is issued by a certificate authority after you prove you own the trademark on the logo. This step costs money and takes time, which is why some senders start with mailboxes that display BIMI without a VMC and add the certificate later.
Step by Step: Publishing Your BIMI Record
Once the authentication groundwork is in place, the BIMI record itself is simple. It is a single DNS TXT record.
Step 1. Confirm DMARC is at quarantine or reject. Check it by querying the _dmarc.yourdomain.com TXT record. If it still says p=none, stop here and fix that first. Nothing below will work until it is enforced.
Step 2. Prepare your logo as an SVG Tiny PS file. Keep it square, keep the file small, and strip out any editor metadata. Host it at a stable HTTPS URL, for example https://yourdomain.com/bimi/logo.svg.
Step 3. If you are targeting Gmail or Apple Mail, obtain a VMC from an authorized certificate authority. Host the resulting PEM file at an HTTPS URL as well.
Step 4. Publish the BIMI TXT record at default._bimi.yourdomain.com:
v=BIMI1; l=https://yourdomain.com/bimi/logo.svg; a=https://yourdomain.com/bimi/vmc.pemThe l= tag points to your logo and the a= tag points to your VMC. If you do not have a VMC yet, you can omit the a= tag, but expect Gmail to withhold your logo until it is added.
Step 5. Send a test message to a supporting inbox and check whether the logo renders. Reporting can lag, so give it time and confirm your DMARC reports show alignment holding steady.
Why Sender Reputation Is the Real Gate
Here is the part most BIMI tutorials leave out. Passing SPF, DKIM, and DMARC gets you eligible to display a logo. It does not guarantee it, and it does nothing to protect the reputation that keeps you eligible over time. Mailbox providers still weigh your sending behavior: spam complaints, spam trap hits, and bounce rates all feed into whether your mail lands in the inbox at all. BIMI only shows on messages that reach the inbox, so a damaged reputation quietly erases the logo you worked to earn.
Bounces are the fastest way to erode that reputation. Every time you send to an invalid, dead, or trap address, providers register it as a signal that you do not maintain your list. Enough of those signals and your DMARC-authenticated, VMC-backed mail starts landing in spam, where no logo displays. This is why authentication and list hygiene are two halves of the same job, not separate projects.
Cleaning your list before you send is the highest-leverage thing you can do here. A validation service like Scrubby is built to catch the addresses that quietly wreck sender reputation, including the risky catch-all and accept-all mailboxes that most cheaper verifiers mark as “unknown” and pass through. Running your list through Scrubby before a campaign strips out the bounces and spam traps that would otherwise chip away at the exact reputation BIMI depends on.
BIMI and Cold Outreach
If your sending includes cold or prospecting email, the reputation stakes are even higher, because you are mailing addresses you did not collect through opt-in. Unverified prospect lists are dense with role accounts, typo domains, and long-dead mailboxes, and each bounce there hits the same reputation score that governs your BIMI display.
Two habits keep this under control. First, validate every prospect list before the first send, so you never learn an address is dead by bouncing on it. Second, favor sending channels that lift reply rates without hammering deliverability. A calendar-invite outreach tool like Kali reaches prospects through a channel that behaves differently from a cold inbox blast, which helps you protect the domain reputation that BIMI, and every future campaign, rides on.
Common Reasons BIMI Does Not Show
If you have published everything and still see a gray circle, work through these in order:
- DMARC is still
p=none. This is the number one cause. Enforcement is mandatory. - SPF or DKIM does not align with the exact domain in your visible From address. Subdomain and alignment mismatches are common.
- The logo is not valid SVG Tiny PS. A normal exported SVG will fail. It must match the profile and be square.
- No VMC for a mailbox that requires one. Gmail and Apple Mail will not display without it.
- Reputation is too low. Even with everything correct, providers can suppress the logo for a domain with a poor sending history. Clean the list, warm the domain, and let the reputation recover.
The Short Version
BIMI is worth doing. A verified logo lifts open rates, signals legitimacy, and makes phishing impersonation harder. But it is a capstone, not a starting point. Get SPF and DKIM aligned, enforce DMARC, format the logo correctly, and get your VMC. Then keep the whole thing standing by protecting your sender reputation, which means validating your list with a tool like Scrubby before every send and choosing outreach methods that do not burn your domain. Do the boring work first, and the logo takes care of itself.
Abhinav
Content Writer