A logo added to your email template won’t automatically appear beside your messages in an inbox. A bimi certificate can help eligible mail providers verify a brand logo, but only after the sending domain meets authentication and publishing requirements.
A BIMI certificate is a third-party credential that associates a brand’s logo with its email domain. A Verified Mark Certificate (VMC) generally requires a registered trademark; a Common Mark Certificate (CMC) can serve some brands without one. To use either with BIMI in Gmail, publish an eligible logo and certificate, enforce DMARC, and add a BIMI DNS record.
What a bimi certificate does—and what it doesn’t
BIMI, or Brand Indicators for Message Identification, gives participating mailbox providers a way to display a sender’s logo alongside messages. The certificate helps a provider check that the logo is associated with a verified organization or mark. It is not a certificate for encrypting email, a substitute for SPF or DKIM, or a promise that every recipient will see an avatar.
The distinction matters operationally. A BIMI record can point to an image, but a mailbox provider decides whether to fetch and display it based on its own support and evaluation. Google’s current Workspace guidance requires a VMC or CMC for BIMI display in Gmail and specifies additional setup requirements, including DMARC enforcement and a hosted certificate file.
BIMI also doesn’t make a message trustworthy by itself. SPF and DKIM help authenticate mail; DMARC checks whether those authentication results align with the visible From domain and applies the domain owner’s policy. The logo is a visual indicator layered on top of that foundation, not a replacement for it.
VMC or CMC: which certificate fits your brand?
A VMC is the route for a logo that is registered as a trademark with an intellectual-property office recognized by certificate issuers. Google recommends working with a legal team or lawyer on trademark eligibility; its Workspace guidance says trademark registration can take 6 to 12 months. If a brand already has a qualifying registration, a VMC is the direct option to investigate.
A CMC is an alternative for some brands whose logo is not registered as a trademark. Eligibility depends on the issuing authority’s criteria and the evidence the applicant can supply. Resend’s January 2025 article on BIMI changes described a CMC route based on demonstrating 12 months of public logo use, including visibility on the Internet Archive. Treat that as an issuer-specific requirement to confirm, not a universal guarantee of eligibility.
The certificate choice also affects what recipients may see. Google says Gmail displays a verified checkmark for senders using a VMC; a CMC can support the logo without that checkmark. So the decision is not simply “certificate or no certificate.” It is whether the trademark path, evidence requirements, cost, and intended display outcome fit the business.
Before applying, assemble your legal brand name, domain ownership details, exact logo artwork, and evidence of trademark or prior use as relevant. Ask the certificate authority which domains and logo variations the credential will cover. Don’t assume a certificate for one brand mark automatically covers a refreshed logo or another sending domain.
Prepare authentication before applying
Certificate work is wasted effort if the sending domain is not ready for BIMI. Google’s setup guidance requires a DMARC record with p=quarantine or p=reject and pct=100; p=none does not qualify for Gmail’s stated BIMI requirements. SPF or DKIM must be configured first so DMARC can evaluate authenticated mail.
A simplified DMARC record might look like this:
_dmarc.example.com TXT "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@example.com"
This is an example, not a universal production value. The reporting address, subdomain policy, and rollout plan depend on your mail flows. Before enforcing quarantine or rejection, inventory every system that sends using your domain—including product notifications, billing tools, support desks, and marketing platforms—and correct SPF, DKIM, and alignment for each one.
A practical rollout is to monitor DMARC reports while the policy is p=none, identify legitimate mail that fails authentication, and fix those sources. Move to enforcement only when the domain’s mail is accounted for. BIMI’s pct=100 requirement means a partial enforcement percentage is not enough for the Gmail setup described by Google.
For implementation background, our email deliverability and sending guides cover the broader sending and authentication concerns that BIMI depends on. Treat domain authentication as ongoing configuration: a new SaaS integration or a changed sending domain can affect alignment after the logo is already in place.
Prepare the logo and certificate files
The logo used for BIMI is not simply any PNG or JPEG. Google’s documented Gmail requirements call for a BIMI-compatible SVG, with absolute pixel dimensions and a minimum height and width of 96 pixels. Google recommends a square-centered mark, a solid background, an SVG file no larger than 32 KB, and an accessibility description.
The certificate workflow also affects the published file format. Google says Gmail and other supporting clients use PEM files for certificate-backed BIMI. When a VMC or CMC is issued, the certificate authority supplies an entity certificate file; Google’s instructions describe combining that with the required intermediate and root certificates in the order provided by the authority.
A useful preflight checklist is:
- Confirm the logo is the approved mark for the brand and domain.
- Validate the SVG against BIMI requirements and Gmail’s additional image constraints.
- Obtain the certificate authority’s PEM and any required chain files.
- Host the resulting file at a stable, publicly reachable HTTPS URL.
- Keep the published logo and credential synchronized if the artwork or certificate changes.
Google requires the public server hosting BIMI files to use HTTPS. A broken URL, invalid certificate chain, or SVG that fails parsing can prevent a provider from retrieving or accepting the brand asset. Test the exact public file—not just a local copy—before publishing the DNS assertion.
Publish the BIMI DNS record
BIMI is published as a TXT record under the _bimi label. For the default selector, the hostname is typically default._bimi.example.com. A certificate-backed record has this general shape:
default._bimi.example.com TXT "v=BIMI1; l=https://assets.example.com/brand.svg; a=https://assets.example.com/bimi.pem"
Here, l= points to the logo and a= points to the certificate file. Use the actual URLs supplied by your setup, and follow your certificate authority’s instructions for the PEM bundle. If your DNS provider adds the domain name automatically, check that the final record owner is not accidentally duplicated—for example, default._bimi.example.com.example.com.
After the record is published, inspect the authoritative DNS response and confirm the TXT value is intact. Long records can be mishandled by dashboards that split strings, add quotation marks, or alter semicolons. Check that the image and PEM links resolve publicly over HTTPS and that access does not require a login or special headers.
Google notes that it can take up to 48 hours for the logo to appear after the record is added. That is a stated processing window, not a display guarantee. The receiving provider still applies its own criteria, and different inboxes can behave differently for messages sent from the same domain.
Where certified BIMI can—and cannot—show up
A certificate should be selected with recipient coverage in mind. Google’s documentation directly describes VMC and CMC support in Gmail, including the difference in checkmark treatment. Other mailbox providers set their own rules for displaying a BIMI logo; adoption of the standard does not mean every client uses every certificate type in the same way.
The BIMI Group’s implementation guidance says mailbox providers have their own display criteria and characterizes certificates as highly recommended, while noting that self-asserted records have limited support. That is a reason to check the provider mix that matters to your audience before paying for a credential. A sender with mostly Gmail recipients has a different decision from one whose customers use a mix of providers.
Resend’s January 2025 overview also distinguished Apple’s Branded Mail pathway from BIMI and described differences among Apple Mail, Gmail, Yahoo, Fastmail, and Outlook at that time. Those platform details can change, so don’t treat a past client-support table as a current compatibility contract. Verify the latest requirements with the mailbox provider and certificate authority that matter to your use case.
For a practical audit, sample your real recipient domains rather than relying on a single test inbox. Check whether the provider supports the BIMI implementation you plan to use, whether your domain meets its criteria, and whether the logo appears in the particular app or web client your users rely on. Also distinguish a displayed logo from a verification checkmark: Gmail associates that checkmark with VMC use.
Troubleshoot a logo that doesn’t appear
Start with the parts you control: DMARC, DNS, and files. A successful BIMI validator cannot force a mailbox provider to display the logo, but it can help identify mistakes in the record or asset that would prevent retrieval.
Work through this sequence:
- Query the TXT record at
default._bimi.yourdomain.comand confirm the selector and syntax. - Check DMARC for the organizational domain and confirm the required enforcement policy and
pct=100for Gmail eligibility. - Confirm SPF or DKIM authenticates the message and aligns with its visible From domain.
- Open the logo and PEM URLs from outside your network; confirm HTTPS returns the intended files.
- Check the SVG dimensions and file format, then verify the certificate chain matches the issuing authority’s instructions.
- Test with the same mailbox provider and interface where you expect the logo to show.
If the logo appears for one provider but not another, investigate provider-specific support and criteria before changing a valid DNS record. If it disappears everywhere after a logo update, compare the new asset, certificate, and published URLs with the previous working configuration. Keep a copy of the former record so a mistaken DNS edit can be reversed quickly.
Authentication issues can affect more than BIMI. A sender that moves from monitoring-only DMARC to enforcement without discovering an overlooked billing or support system can reject legitimate mail. Our guide to cold email deliverability best practices discusses adjacent authentication and sender-reputation considerations, though BIMI itself is mainly a brand-display layer.
Decide whether the certificate is worth pursuing
Start with the outcome you need. If the goal is a Gmail logo and you have a qualifying trademark, evaluate a VMC. If the mark is not trademarked, ask issuing authorities whether a CMC is available for your brand and what evidence they require. If neither path is practical, prioritize DMARC and other authentication work first; a logo asset alone does not provide the certified setup Gmail describes.
Then compare the expected audience benefit with the work involved. A team with multiple sending systems may need to fix authentication across several vendors before it can safely enforce DMARC. A team with one well-managed domain and a registered mark may have a simpler implementation, but still needs accurate files, DNS access, and maintenance ownership.
Assign ongoing responsibility as well as setup tasks. Someone should own the BIMI record, certificate renewal or replacement, logo changes, and DMARC monitoring. Put the BIMI DNS record and public asset URLs in the same configuration inventory as SPF and DKIM records; otherwise a domain migration or asset cleanup can silently break the display path.
The strongest conclusion is straightforward: BIMI is a downstream benefit of correctly authenticated mail, not a shortcut around it. Get SPF, DKIM, and enforced DMARC right, then choose the certificate route based on the brand’s eligibility and the mailbox providers your recipients actually use.
FAQ
Do I need a certificate to use BIMI?
It depends on the mailbox provider. Google’s current Workspace instructions require a VMC or CMC for Gmail’s BIMI setup. The BIMI Group says certificates are highly recommended and that self-asserted records have limited support, so a logo-only DNS record should not be assumed to display broadly.
What is the difference between a CMC and a VMC?
A VMC is associated with an eligible registered trademark, while a CMC can be an option for some marks without trademark registration. Gmail can display a logo with either certificate, but Google associates the verified checkmark with VMC. Issuer eligibility and application evidence vary, so confirm them before choosing.
Can I use BIMI if DMARC is set to p=none?
Not for the Gmail requirements Google publishes. The DMARC policy must use p=quarantine or p=reject, with pct=100; p=none is a monitoring policy and does not meet that requirement. First identify and fix legitimate senders that fail authentication, then move to enforcement deliberately.
How long does it take for a BIMI logo to appear?
Google says a logo can take up to 48 hours to appear after you add the DNS record. That timing applies to processing, not universal inbox display. A receiving provider may not support your certificate route or may apply additional criteria, so test with the mailbox services your audience uses.
Start free with 1,000 emails a month → https://app.volanea.com/signup