Getting your logo to display in email inboxes with BIMI (Brand Indicators for Message Identification) is a fantastic way to boost brand recognition and trust. However, it's not as simple as just uploading your standard PNG logo. Mailbox providers have very specific requirements for the logo file to ensure it's secure, scalable, and renders correctly everywhere. The entire system hinges on a specially crafted SVG (Scalable Vector Graphics) file.
Let's walk through the exact requirements for creating a BIMI-compliant SVG image. Getting these details right is the most common hurdle people face when setting up BIMI.
The most fundamental requirement is the file format. Your logo can't be a JPG, PNG, or GIF; it must be an SVG. More specifically, it needs to adhere to a strict profile known as SVG Portable/Secure (SVG P/S). This is a specialized version of SVG Tiny 1.2, designed to prevent security risks.
The 'secure' part of the name is key. This profile heavily restricts what can be included in the file to eliminate potential vulnerabilities. This means the SVG file cannot contain certain elements that could be exploited.
Additionally, the final file size of your SVG must be 32 kilobytes or smaller.
Beyond the technical format, there are visual guidelines to ensure your logo looks great in the various email clients that support BIMI. Since clients may crop the logo into different shapes (like a circle or a rounded square), these rules ensure it remains clear and recognizable.
The key design requirements are:
Because an SVG is just an XML file, you can open it in a text editor to verify the specific attributes. Certain attributes and elements must be present for it to be compliant.
When you open your SVG, the root <svg> element should have a baseProfile="tiny-ps" attribute. You'll also need to see version="1.2".
Inside the <svg> tags, there must be a <title> element that contains your organization's name. This should match the name on your Verified Mark Certificate (VMC) if you have one. Lastly, an x="0" and y="0" attribute should generally be avoided on the main <svg> element to ensure proper rendering.
While these requirements might seem daunting, they are essential for creating a standardized, secure, and interoperable system. Getting your SVG right is a critical step towards a successful BIMI implementation.
What DNS record type is used for BIMI?
What image format is required for BIMI logos?
Is a VMC (Verified Mark Certificate) required for BIMI to display a logo?
What is the recommended size for a BIMI SVG image?
Does BIMI require the SVG to be publicly accessible via HTTPS?
Does BIMI authenticate the logo itself?