Smartphone inbox showing a brand logo avatar, the result of meeting BIMI setup requirements

BIMI Setup Requirements: What You Need Before Your Logo Appears

The core BIMI setup requirements are email authentication with a DMARC policy at enforcement, a logo saved in the SVG Tiny PS format, and, for Gmail, a mark certificate (either a Verified Mark Certificate or a Common Mark Certificate). Once those are ready, you host the logo and certificate files over HTTPS and publish a BIMI TXT record in DNS that tells mailbox providers where to find them. Google’s own BIMI setup guide for Gmail spells out the specifics: DMARC must be set to quarantine or reject at 100 percent, and a policy of p=none won’t qualify.

The order matters. SPF or DKIM has to be working before DMARC can do its job, and DMARC enforcement is the gate that every later step depends on. Even when every piece is correct, a logo isn’t guaranteed to show. Yahoo, for example, says it also weighs sending volume, reputation and engagement before displaying a brand logo.

This guide walks through each requirement in the order you’ll actually tackle them. It covers getting DMARC to enforcement, preparing a compliant SVG file, choosing between a VMC and a CMC, and publishing your DNS record. It also explains why providers handle BIMI differently and where to start if your domain isn’t ready yet.

The short answer: what BIMI needs before any logo shows

Before your logo can appear next to your emails, you need three things: email authentication with DMARC at enforcement, a mark certificate for your logo, and a BIMI record in DNS that points to your logo and certificate. Google’s own Gmail BIMI setup requirements list the essentials as:

  • A mark certificate: a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) issued by a third-party certificate authority.
  • DMARC on your domain: set to an enforcement policy, not just monitoring.
  • A public web server that supports BIMI: somewhere to host your logo file and certificate over HTTPS.

The BIMI Group’s implementation guide puts the work in a clear order:

  1. Authenticate and align SPF, DKIM and DMARC, with DMARC at enforcement.
  2. Get a VMC or CMC for your logo.
  3. Publish a BIMI record in DNS.

One important point to understand from the start: meeting every technical requirement makes you eligible for logo display, but it doesn’t guarantee it. Each mailbox provider decides on its own whether to show your logo, and their rules aren’t identical.

The sections below follow the same order as the checklist because each step depends on the one before it. A certificate won’t help if DMARC isn’t enforced, and a BIMI record has nothing to point to until your logo file and certificate are ready. Working through the steps in sequence saves you from redoing work later.

BIMI DMARC enforcement: the gate everything else depends on

BIMI only works when your domain’s DMARC policy is at enforcement. That means you tell mailbox providers to quarantine or reject mail that fails authentication. A policy of p=none only asks for reports and takes no action, so it doesn’t qualify, no matter how polished your logo or certificate is.

What counts as enforcement

Google’s BIMI setup instructions for Workspace admins require p=quarantine or p=reject and state that p=none isn’t supported. Google also requires pct=100, so the policy applies to all of your outgoing mail rather than a sample of it.

The BIMI Group implementation guide takes the same position: none policies and pct values below 100 are not accepted. It adds that enforcement must cover your organizational domain and its subdomains. Your sp tag needs to be quarantine or reject too. A strict p= value paired with a leftover sp=none can still leave you short.

DMARC tag Qualifies for BIMI Does not qualify
p (organizational domain) quarantine or reject none
sp (subdomains) quarantine or reject none
pct 100 Anything below 100

Authentication comes before DMARC

DMARC can’t do its job until SPF or DKIM is in place, and Google lists them as a step to complete before DMARC. Simply passing isn’t enough, though. BIMI Group notes that SPF, DKIM and DMARC must be aligned. In practice, the domain that SPF or DKIM authenticates needs to match the domain your readers see in the From line.

Tighten the policy carefully

Jumping straight to reject can block your own legitimate mail. Before you change the policy, follow these steps:

  1. Review your DMARC aggregate reports to see every source sending as your domain.
  2. Authenticate each legitimate sender, such as your email platform, CRM, help desk and billing system.
  3. Move from none to quarantine, then to reject, once the reports show clean results.

If you’re starting from scratch, our guide to step-by-step SPF, DKIM and DMARC setup for high-volume senders walks through each record in order.

IT administrator reviewing email authentication settings while working toward BIMI DMARC enforcement

Preparing your logo as an SVG Tiny PS file

Your logo can’t be just any image file. BIMI expects a specific, locked-down version of SVG called SVG Tiny Portable/Secure (often shortened to SVG Tiny PS). Small formatting mistakes in this file are a common reason a logo gets rejected, so it’s worth checking each rule before you move on to certificates and DNS.

According to Google’s BIMI setup guidance for Gmail, your logo file needs to meet these requirements:

  • Correct profile and version: the root element must declare baseProfile=”tiny-ps” and version=”1.2″.
  • Minimum size: at least 96 x 96 pixels, set in absolute pixel values rather than percentages.
  • Nothing active or outside the file: no scripts, animations, interactive elements or external references such as linked images or fonts.
  • No position attributes on the root element: remove any x= or y= attributes from the root svg tag.
  • A title that names your organization: including a title element with your company name is recommended.

Why a standard export usually isn’t enough

Design tools save SVGs for websites and print, not for BIMI. A typical export uses the wrong profile, includes extra metadata or editor-specific code, and may set its size in percentages. That means you should plan to convert or clean up the file instead of uploading it as-is. Open the file in a text editor and compare it line by line against the rules above. Common fixes include changing the root attributes, removing embedded or linked assets, and setting fixed pixel dimensions.

Keep the design simple and square, with a solid background. Mail apps often crop logos into a circle or rounded shape, so detail near the edges may be cut off. Once the file passes these checks, keep that exact version. The mark certificate you apply for next is tied to the logo you submit, so any later change to the artwork can mean starting that step again.

VMC certificate or CMC: which mark certificate you need

To show your logo in Gmail, you need a third-party mark certificate. There are two options: a Verified Mark Certificate (VMC) or a Common Mark Certificate (CMC). Which one you can get depends mostly on whether your logo is a registered trademark.

Google recommends a VMC. To get one, your logo must be trademarked with an intellectual property office that VMC issuers recognize. If you haven’t registered your logo yet, Google’s BIMI setup guidance says trademark registration can take 6 to 12 months, so plan for that delay.

If your logo isn’t trademarked, a CMC is the alternative. DigiCert explains that a CMC is available once you prove at least one year of prior use of the logo. Government entities are a special case: they don’t need an active trademark to qualify.

Certificate Who qualifies Gmail checkmark
VMC Logos trademarked with a recognized intellectual property office, or government entities Yes
CMC Logos without a trademark that have at least one year of proven prior use No

The checkmark is the main visible difference. Only senders with a VMC get Gmail’s checkmark, and web mail apps other than Gmail don’t support that checkmark at all. A CMC still lets your logo appear in Gmail, just without the checkmark.

Once you buy a certificate and pass the certificate authority’s validation, the authority gives you a PEM-encoded certificate chain. That file is what your BIMI record points to, so keep it ready for the DNS step.

A practical tip: if you’ll need a trademark, bring in legal counsel early. The trademark is usually the slowest part of BIMI setup, and starting it first lets the rest of your work run alongside it.

Designer's desk with a vector logo and an embossed seal, representing VMC certificate trademark checks

Hosting the files and publishing the BIMI DNS record

Once your logo file and certificate are ready, you need to put them somewhere mailbox providers can fetch them, then publish a DNS record that tells providers where to look. Google’s BIMI setup guidance for Workspace says the server hosting your BIMI files must use HTTPS and recommends TLS 1.2 or later.

Follow the steps in order

Google lays out the sequence like this:

  1. Create your logo as an SVG Tiny PS file.
  2. Get your VMC or CMC and its files from the certificate authority.
  3. Upload the PEM certificate file to your HTTPS server.
  4. Add the BIMI TXT record to your DNS.

Publishing the DNS record last means it never points to files that aren’t live yet.

What the BIMI record says

The record is a single line of text with a few parts:

Part What it means Example
Version Identifies the record as BIMI v=BIMI1
Logo location (l=) The HTTPS address of your SVG logo l=https://example.com/logo.svg
Certificate location (a=) The HTTPS address of your PEM certificate file a=https://example.com/cert.pem

The BIMI Group’s implementation guide notes that the a= tag is reserved for the location of your VMC or CMC. It isn’t a place for other files or notes.

Make sure the files are publicly reachable

Mailbox providers fetch your logo and certificate automatically, with no person clicking through. Anything that gets in the way can stop the check, including:

  • A login wall or password-protected folder
  • Bot protection or challenge pages from a security service or CDN
  • Redirects to non-HTTPS addresses
  • Firewall rules that block unfamiliar visitors

A quick test is to open both URLs in a private browser window. If you see a challenge, a login prompt or an error, an automated fetch will likely run into the same problem. Fix that before you troubleshoot anything else.

Why your logo still might not appear: provider rules differ

Meeting the BIMI standard doesn’t mean every inbox will show your logo. Each mailbox provider sets its own display rules, and at Yahoo your sending reputation matters as much as your DNS records.

Yahoo’s BIMI guidance for senders says it displays a logo when all of these are true:

  • You have a valid BIMI record that points to an SVG logo.
  • Your DMARC policy is set to quarantine or reject.
  • The message is bulk mail.
  • Yahoo sees enough reputation and engagement for your domain.

Yahoo doesn’t currently require a VMC. If your BIMI record includes one, though, Yahoo uses it to help decide eligibility. Yahoo also honors BIMI on subdomains, but it prefers BIMI and DMARC to be set up at the organizational domain level.

Gmail works differently. Google’s BIMI setup instructions require a VMC or CMC. A BIMI record without a certificate might qualify for a logo at Yahoo, but it won’t produce one in Gmail.

Requirement Yahoo Mail Gmail
Mark certificate Not currently required, but used to inform eligibility VMC or CMC required
DMARC policy Quarantine or reject Quarantine or reject
Reputation and engagement Must be strong enough Not listed as a display condition
Subdomain setup Honored, but organizational level preferred Not addressed

If your logo shows in one inbox but not another, compare your setup against each provider’s rules. Our plain-English checklist of Gmail and Yahoo bulk sender requirements is a good place to start.

If everything looks correct and Yahoo still doesn’t show your logo, the cause is often weak reputation or a gap in authentication that’s hard to see from the outside. An email deliverability audit can show you which one is holding you back, so you know what to fix first.

Where to start if you’re not BIMI-ready yet

Start with authentication and DMARC enforcement. A logo file, a certificate and a BIMI record do nothing until your domain passes that gate, so it makes sense to put your first effort there. Here’s a practical order that avoids wasted time and money:

  1. Get SPF and DKIM working, then move DMARC to enforcement. Review your DMARC reports, confirm every legitimate sender is authenticating, and then step your policy up to quarantine or reject.
  2. Check your trademark or prior-use position at the same time. Don’t wait for DMARC to finish before looking at this. Google notes that the trademark registration process can take 6 to 12 months, so if you’re aiming for a VMC, starting early keeps it from becoming the bottleneck. If you don’t have a registered mark, find out whether your logo use history could support a CMC instead.
  3. Prepare the SVG Tiny PS logo. Get it converted and validated so it’s ready the moment you need it.
  4. Order the certificate last. Buy a VMC or CMC only after your DMARC policy and logo file both meet the requirements. DigiCert’s steps for getting a Verified Mark Certificate place DMARC and the logo file ahead of purchase and validation, which tells you the certificate isn’t the place to begin.
  5. Host the files and publish your BIMI record. This final step goes quickly once everything above is in place.

If the DNS side feels like the hardest part, our done-for-you DNS authentication setup covers SPF, DKIM and DMARC configuration so you can move toward enforcement without breaking legitimate mail along the way.

Not sure where your domain stands today? You can book a free consult, and we’ll walk through your SPF, DKIM, DMARC and BIMI readiness with you. We can help you meet the requirements, but each mailbox provider makes the final call on showing your logo.

Keep researching on Digital Bulldogs

Frequently asked questions

Can I set up BIMI while my DMARC policy is p=none?

No. A monitoring-only policy won’t qualify. The BIMI Group implementation guide states that “none” policies and pct values below 100 are not accepted. Your DMARC record needs p=quarantine or p=reject, applied to all of your mail.

You can still keep p=none while you review reports and fix authentication gaps. Just plan to move to enforcement before you publish your BIMI record.

Do I need a VMC certificate for my logo to show in Yahoo Mail?

Not at the moment. Yahoo’s sender guidance says a VMC is not currently required, though Yahoo does use it to help decide eligibility. Yahoo still expects a valid BIMI record that points to an SVG logo, DMARC at quarantine or reject, bulk sending, and enough reputation and engagement. Meeting the technical requirements doesn’t guarantee your logo will appear.

What’s the difference between a VMC and a CMC?

The difference is what you have to prove about your logo. DigiCert explains that a VMC requires a logo that is legally trademarked with the right regional office. Government entities are an exception and don’t need an active trademark. A CMC is available once you show at least one year of prior use of the logo. With either certificate, the certificate authority gives you a PEM-encoded certificate chain to reference in your BIMI record.

How long does it take to get a trademark for a VMC?

Plan for months, not weeks. Google’s BIMI setup guide notes that registering a trademark through a recognized intellectual property office can take 6 to 12 months. If your logo isn’t trademarked yet, Google points to a CMC as the route for non-trademarked logos. Only a VMC earns the verified checkmark in Gmail, though.

Do my subdomains need DMARC enforcement for BIMI?

Generally, yes. The BIMI Group guide linked above calls for enforcement on your organizational domain and its subdomains. That means both the p and sp tags should be set to quarantine or reject. If your sp tag is missing, check what policy your subdomains actually inherit.

Yahoo’s guidance, also linked above, says it honors BIMI on subdomains but prefers setup at the organizational level. Configuring the parent domain first keeps things simpler.

Sources

  1. Set up BIMI · Google Workspace Admin Help
  2. Implementation Guide · BIMI Group
  3. BIMI · Yahoo Sender Hub
  4. What Steps are Required to get a Verified Mark Certificate (VMC)? · DigiCert

This article is general information, not legal advice. Laws and deadlines vary by state and change over time; check the linked sources or speak with a licensed attorney about your situation.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *