BIMI Record Setup and Whether Your Brand Logo Is Worth It
You have seen the little brand logos next to sender names in Gmail and Apple Mail, and now someone on your team wants one too.

You have seen the little brand logos next to sender names in Gmail and Apple Mail, and now someone on your team wants one too. The catch is that a BIMI record looks like a five minute DNS job, but it only works after your domain passes a stricter authentication bar than most small senders have ever cleared. This guide walks through what BIMI actually needs, what it costs, and how to decide whether the logo is worth the effort for your domain.
What a BIMI record does and what it does not do
BIMI stands for Brand Indicators for Message Identification. A BIMI record is a single DNS TXT entry that tells receiving mailbox providers where to find your logo and, for some of them, where to find a certificate proving you own that logo. When a message passes authentication and the provider trusts the sender, it shows the logo in the inbox list instead of a grey initial.
That is the whole feature. BIMI does not sign your mail, does not change routing, and does not add a new check that rejects messages. It sits on top of SPF, DKIM and DMARC and rewards domains that have already locked those down. If those three records are still a blur, read our plain explainer on how SPF, DKIM and DMARC fit together before going further.
The DMARC policy you need before BIMI will show
This is where most attempts stall. Mailbox providers only display a BIMI logo when your DMARC policy is at enforcement. In practice that means:
- p=quarantine or p=reject on the organizational domain. A policy of p=none disqualifies you.
- pct=100 if you use quarantine. A partial rollout such as pct=25 does not count.
- sp (the subdomain policy) must not be set to none, because a spoofable subdomain undermines the whole point.
- Your real mail streams must pass DMARC alignment, either through aligned DKIM or aligned SPF, or the logo appears on some messages and not others.
Moving from p=none to p=reject on a domain that sends through a CRM, a helpdesk, a billing tool and a newsletter platform takes most small teams four to eight weeks of watching reports. The safe path is to collect aggregate reports at p=none, fix every legitimate source that fails, step up to quarantine, then reject. Our guide on reading DMARC aggregate reports without a paid tool covers that monitoring phase in detail.
Preparing the logo file
BIMI does not accept a normal SVG exported from a design tool. It requires a restricted profile called SVG Tiny Portable/Secure, usually shortened to SVG Tiny PS. The rules that trip people up:
- The root element needs baseProfile="tiny-ps" and version="1.2".
- A title element is required, and it should contain your brand name.
- No scripts, no animation, no external references, no embedded raster images.
- The image must be square, with the logo centered and a solid background color, because providers crop it into a circle.
- Keep the file small. Around 32 KB is the commonly cited ceiling, and most clean logos land under 10 KB.
The fastest route is to start from a simple vector version of your mark, export it as plain SVG, then edit the header by hand in a text editor. Strip any metadata blocks your design tool adds. Then run it through one of the free BIMI validators offered by the certificate vendors and mailbox industry groups, which report profile errors line by line.
Host the file over HTTPS on a server with a valid certificate. A static path on your main website works fine. Do not put it behind a redirect or a login.
Writing the BIMI record itself
The record lives at a selector hostname. For the default selector you create a TXT record on the name default._bimi followed by your domain. The value has three parts:
- v=BIMI1 to declare the version.
- l= followed by the full HTTPS address of your SVG file.
- a= followed by the full HTTPS address of your certificate in PEM format, or left empty if you have no certificate.
Separate the tags with semicolons and keep it on one line. A TTL of 3600 seconds is sensible while you test, and you can raise it to a day once the logo appears reliably. After publishing, query the name with dig or nslookup from two different networks to confirm the value is identical everywhere.
VMC, CMC or no certificate at all
The a= tag is where the money goes. Gmail and Apple Mail only show your logo if you attach a mark certificate. There are two kinds:
| Option | What it requires | Typical yearly cost | Who shows the logo |
|---|---|---|---|
| Verified Mark Certificate (VMC) | A registered trademark for the exact logo | Roughly 1,000 to 1,600 USD | Gmail, Apple Mail, Yahoo and others |
| Common Mark Certificate (CMC) | Proof the logo has been in public use for at least 12 months | Usually a little less than a VMC | Gmail and some others, not every provider |
| No certificate | Just the record and a valid SVG | Free | Some providers for senders with a strong reputation |
Certificate vendors also verify your organization by phone and documents, which can take one to three weeks.
Why BIMI is not a deliverability fix
A lot of marketing material claims BIMI boosts inbox placement. That claim mixes up cause and effect. The thing that helps deliverability is the DMARC enforcement you had to reach first, because it stops spoofers from burning your domain's reputation and gives providers a clear signal about which mail is really yours. The logo itself is a display feature. Gmail does not rank a message higher because it carries a BIMI record.
Where BIMI can help is recognition. In a crowded inbox a familiar logo may lift open rates by a few percent for brands people already know. For an unknown brand, a logo nobody recognizes adds very little. So the honest advice for most small senders is this: do the DMARC work now because it protects you, and treat the logo as an optional extra you buy later if your customers would actually recognize it. If placement is your real problem, start with how deliverability works and why messages land in spam instead.
A realistic rollout plan for a small team
- Week 1: publish DMARC at p=none with a reporting address and list every service that sends as your domain.
- Weeks 2 to 4: fix alignment for each sender, usually by adding a custom DKIM key in each platform.
- Week 5: move to p=quarantine with pct=100 and watch reports for two weeks.
- Week 7: move to p=reject if nothing legitimate is failing.
- Week 7 onward: prepare the SVG, decide on VMC, CMC or none, and publish the BIMI record.
Keep the logo file and certificate on a renewal calendar. An expired certificate silently removes the logo, and nobody notices for weeks.
Frequently asked questions
Do I need a trademark to use BIMI?
Only for a Verified Mark Certificate. A Common Mark Certificate accepts proof of public logo use instead, and some providers display logos with no certificate at all for well established senders. Gmail and Apple Mail still require one of the two certificates.
Why is my BIMI logo not showing in Gmail?
The usual causes are a DMARC policy below enforcement, a pct value under 100, a logo that fails the SVG Tiny PS profile, or a missing certificate. Gmail also needs time and volume, so a domain sending a few dozen messages a week may wait a while even when everything validates.
Can I use BIMI on a subdomain?
Yes. You can publish a BIMI record for a subdomain, but the organizational domain must still have DMARC at enforcement. Providers check the parent policy, so a strict subdomain under a lax parent will not qualify.
More in Email Infrastructure
Email Infrastructure
One Click Unsubscribe Headers and the Bulk Sender Rules
I send a monthly note to the people who play on the servers I run. It is not marketing.
Email Infrastructure
Why Email Forwarding Breaks SPF and What ARC Fixes
A reader wrote to me in October about invoices that reached half his list and vanished for the rest.
Email Infrastructure
Warming Up a New Sending Domain Without Hitting Spam
You moved the newsletter to a fresh domain on a Monday, sent 8,000 messages on Tuesday, and by Wednesday Gmail was deferring...