Inboxlogy Free Tools
BIMI Generator
Build your BIMI DNS record to display your brand logo next to your emails — with a checklist of the DMARC, SVG and VMC prerequisites Gmail and Apple require.
How it works
Confirm the prerequisites
BIMI needs DMARC enforced at quarantine or reject on the From domain, a trademark-backed certificate, and a logo in the restricted SVG profile. The checklist flags whatever is missing before you publish.
Host the logo and certificate
Upload your SVG and your certificate PEM file to HTTPS URLs that stay stable. Both are fetched by mailbox providers, so no redirects, no authentication, and no expiring links.
Publish the TXT record
Copy the generated value into a TXT record on the host default._bimi. Confirm it resolves, then send a test message to a Gmail account and check whether the avatar renders.
Why BIMI needs a VMC, not just an SVG
A BIMI record is a TXT record at default._bimi.yourdomain.com holding v=BIMI1, an l= tag with the HTTPS URL of your logo, and an a= tag with the HTTPS URL of your certificate. The logo must follow SVG Tiny Portable/Secure: baseProfile set to tiny-ps, a title element, a square viewBox, and no scripts, animation, raster images or external references. Keep the file small; Gmail will not fetch an oversized asset.
Mailbox providers will not display an arbitrary image next to a sender name, so the a= tag is what makes BIMI work. Gmail requires a Verified Mark Certificate from an approved authority such as DigiCert or Entrust, which binds the exact logo to a registered trademark. Apple Mail also requires one. DMARC must be at p=quarantine or p=reject, with no weaker subdomain policy.
Common mistakes
Publishing BIMI with p=none
BIMI is ignored unless DMARC is enforced at quarantine or reject on the From domain. A valid record, a valid certificate and a perfect SVG still produce no logo while the policy stays at none.
Using a standard SVG export
Exports from design tools include scripts, gradients, embedded fonts or external references that break the Tiny Portable/Secure profile. The record resolves, the file loads, and the logo simply never renders with no error anywhere.
Unstable logo and certificate URLs
Providers refetch both files. A redirect, an expired certificate, a CDN rule requiring a referrer, or a moved path quietly disables the logo. Serve both from stable HTTPS paths and track the certificate expiry date.
Expecting BIMI on cold outreach domains
BIMI requires a registered trademark and an enforced DMARC policy on the From domain, which fits your primary brand domain and rarely fits the throwaway sending domains used for outbound.
Frequently asked questions
Do I need a VMC to use BIMI?
For Gmail and Apple Mail, yes. Both require a Verified Mark Certificate from an approved authority binding your logo to a registered trademark, referenced in the a= tag of your BIMI record. Without it the record is valid but no logo displays. Certificates renew annually.
What DMARC policy does BIMI require?
p=quarantine or p=reject on the domain in your From header, and a subdomain policy that is no weaker. p=none disqualifies you entirely. Get DMARC enforced and verified first, since every BIMI implementation that fails to display a logo usually fails on policy rather than on the record or the image.
Why is my BIMI logo not showing in Gmail?
Work through four things in order: DMARC must be enforced at quarantine or reject, the certificate URL must load a current PEM chain over HTTPS, the SVG must validate against the Tiny Portable/Secure profile, and the TXT record must sit on default._bimi. Gmail also caches results, so allow time after a fix.
Will BIMI improve my open rates?
There is no reliable way to promise that. BIMI adds a verified logo to the sender slot, which is a visible trust signal recipients can recognize, but it changes no filtering decision and delivers no placement benefit by itself. Treat it as brand presentation on top of authentication you already enforce.
Does BIMI work for cold email from a new domain?
Generally no. BIMI needs a registered trademark tied to the sending domain plus enforced DMARC, which fits established brand domains rather than the new secondary domains used for outbound sequences. For cold email, the useful work is correct SPF, DKIM and DMARC alignment; BIMI belongs on your main brand domain.