What Are BIMI SVG Logo Requirements in 2026?

You’ve set up BIMI. Your DNS record is correct. But your logo still doesn’t show in Gmail. Not because of a mistake in your TXT record—but because your SVG file fails one of the many hard rules browsers and email clients now enforce.

BIMI isn’t just about adding a brand image to your emails. It’s a verification layer. Your SVG logo must pass strict format, size, color and security checks. Even a single deviation means no logo—regardless of how perfect your DNS setup is.

By 2026, BIMI is no longer optional for brands sending at scale. Gmail and others require full compliance. The logo isn’t just visual—it’s proof your brand is authentic. But proving that means meeting exact technical standards.

Key takeaways

  • Gmail and other BIMI-supporting clients will not display your logo if your SVG fails any of the format, size, color, or security rules—even if your DNS records are correct.
  • SVG files must be static, not animated, and must not include external links, scripts, or embedded fonts.
  • Logos must be exactly 140x140 pixels, use only solid fill colors, and avoid gradients or transparency in the final artwork.

Why Does Your BIMI SVG Logo Not Show in Gmail?

You’re setting BIMI up correctly, but your logo still isn’t showing in Gmail. The most likely reason is an invalid or malformed SVG file—often due to embedded scripts, unsupported features, or incorrect encoding. Gmail scans every BIMI image for malicious content, and even a single invalid attribute can block it, regardless of your DNS records being set up. The issue isn’t your TXT record—it’s the file itself.

SVGs Are Strictly Sandboxed in Gmail

Let’s be clear: Gmail treats BIMI SVGs like security-critical assets. It doesn’t just check for size or format—it actively scans for anything that could be malicious. Scripts, external links, embedded metadata, or even complex gradients that trigger SVG parsing vulnerabilities will get rejected. This is consistent with how Gmail handles email attachments and embedded content.

Even tiny issues break rendering. A single missing xmlns declaration, a typo in an attribute name, or incorrect character encoding can cause Gmail to silently ignore the logo. There’s no error message. No warning. Just a blank space where your brand should be.

Validation Isn’t Just a Good Idea—It’s Required

You can’t depend on guesswork. If your SVG has onload attributes, script tags, or links to external resources (like pointing to a remote file), Gmail will block it. These features, while valid in some contexts, are considered high-risk in BIMI.

According to the BIMI specification (RFC 8953), the image must be static and safe to render in any environment. Gmail enforces this by parsing the SVG structure and sanitizing content. If it sees anything that looks suspicious—even if it’s harmless—it strips the logo out of the thread.

Let’s say you’re generating SVGs via a tool or script. You might be including embedded styles, hidden metadata like creator="Inkscape", or non-standard tags. All of these can cause failures. Always validate your SVG against the BIMI constraints.

Want to catch issues early? Use a real-time tool like EmailListChecker’s bulk verification to spot suspicious patterns in your email list, including malformed attachments and metadata quirks. While not a direct SVG validator, it does help ensure your outbound email assets are clean and safe. You can also pair it with inbox placement testing to see how Gmail actually renders your messages in real user inboxes.

Always test your SVG in a BIMI checker before deployment. Tools like the BIMI.org validator or open-source validators can catch common format errors. Don’t assume your editor exported it correctly. Even a single misplaced character can break everything.

How to Validate Your BIMI SVG Logo Before Deployment

You must validate your BIMI SVG logo using a real validator tool, check for unsafe elements like

Keep reading