BIMI SVG Validator

⚙ DNS & authentication

Check whether a logo meets the SVG Tiny Portable/Secure profile that BIMI requires.

No sign-up required Runs on our own infrastructure Also available via API

Structural checks run in your browser. This validates the SVG Tiny P/S profile constraints; it does not verify a VMC/CMC certificate.

The logo is the single most common reason a BIMI setup fails. Everything else — the DNS record, DMARC, even the certificate — is straightforward once you know the rules. The SVG is where good intentions go to die, because the file your designer hands you almost never conforms to the profile BIMI demands. Export a logo from Illustrator or Figma and it’ll look perfect and still be rejected. This validator checks the structural rules so you can fix the file before it costs you a support ticket with your CA.

Why BIMI insists on a special SVG profile

BIMI doesn’t accept ordinary SVG. It requires SVG Tiny Portable/Secure (SVG Tiny P/S) — a deliberately restricted subset built on the SVG Tiny 1.2 profile. The reason is security: an SVG is executable-ish, capable of running scripts and pulling in external resources, and mailbox providers won’t render something like that next to your name in the inbox. The Portable/Secure profile strips out everything dangerous or ambiguous, leaving a file that renders identically everywhere and can’t phone home. The profile is documented by the BIMI Group.

What a conforming file needs

  • The right root attributes. The <svg> element must declare version="1.2" and baseProfile="tiny-ps". This is the signature the profile is defined by, and it’s the first thing missing from a normal export.
  • A <title> element as a direct child of the root, naming the brand. It’s required, not optional.
  • A square viewBox. The viewBox must be 1:1 — providers render the logo in a circle or square, and a non-square aspect ratio is rejected outright.
  • No scripts, no interactivity. No <script>, no <a> hyperlinks, no animation elements, no event handlers.
  • No external or raster content. No <image> elements, no references to external files, no embedded fonts. Text must be converted to paths.

The failures we see most

Almost every rejection comes down to the same short list:

  1. Missing baseProfile="tiny-ps" or version="1.2". Design tools don’t add these — you usually have to hand-edit the root tag.
  2. No <title>. Easy to forget, and it’s a hard requirement.
  3. A non-square viewBox — a logo that’s wider than it is tall. Pad it to a square canvas centred on the mark.
  4. Live text instead of outlines. Fonts don’t travel, so text left as <text> can render wrong or be disallowed. Convert every glyph to a path.
  5. Leftover editor cruft — namespaces, metadata, or elements the profile doesn’t permit. A clean, minimal file is the goal.
  6. No solid background. BIMI expects a filled background rather than transparency; a transparent logo can render awkwardly.

Where this fits in the BIMI flow

This tool checks the structural rules of the SVG itself — it doesn’t touch DNS. Once your file passes here, host it over HTTPS, then build the DNS record with the BIMI Record Generator and confirm the whole thing end to end with the BIMI Checker. Remember that a valid SVG is necessary but not sufficient: you still need DMARC at enforcement and, for Gmail and Apple Mail, a VMC. The full walkthrough is in our guide to adding a BIMI logo to your email.

Frequently asked questions

Why does my logo fail even though it opens fine in a browser?
Browsers render almost any SVG; BIMI requires the strict SVG Tiny P/S profile. A file that looks fine can still lack baseProfile="tiny-ps", a <title>, or a square viewBox. Rendering and conformance aren’t the same.
How do I convert a normal SVG to SVG Tiny P/S?
Square the canvas, outline all text, remove scripts/external refs/raster images, add a <title> and a solid background, then set version="1.2" and baseProfile="tiny-ps" on the root tag. Validate before publishing.
Does the viewBox really have to be square?
Yes — providers show the logo in a round or square slot, so a 1:1 viewBox is required. Pad a wide logo to a square canvas centred on the mark; don’t stretch it.
Does passing this validator mean my BIMI logo will show?
It clears the biggest hurdle — a structurally valid file. But you still need DMARC at enforcement and, for Gmail/Apple, a VMC. Confirm the full setup with the BIMI Checker.