Yes, it absolutely does. BIMI (Brand Indicators for Message Identification) has very strict requirements for the logo file, and this includes specifying the correct XML namespace. While it might seem like a minor technical detail, getting it right is crucial for your BIMI record to validate and for your logo to appear in your recipients' inboxes.
The core of the issue is that BIMI doesn't just use any standard SVG (Scalable Vector Graphics) file. It requires a specific, more secure version.
The SVG portable/secure profile
BIMI mandates the use of an SVG profile known as SVG Portable/Secure (SVG P/S). This is a stripped-down, security-focused subset of the full SVG specification. The whole point is to eliminate potential security risks that can come with standard SVGs, like embedded scripts or external links.
Because BIMI logos are rendered inside email clients, this restricted format ensures that the image file can’t execute malicious code or cause other problems. It is a critical part of the security model that underpins BIMI.
The required XML namespace
Within the SVG P/S specification is the requirement for the correct XML namespace. When you open your SVG file in a text editor, the very first element, <svg>, must include the following namespace attribute:
xmlns="http://www.w3.org/2000/svg"
This line tells the application rendering the file (in this case, the email client) what set of rules, or schema, the XML markup is following. As some sources note, this is generally the only external reference allowed in a BIMI-compliant SVG. While a web browser might render an SVG without this namespace, the strict validation process for BIMI will fail it immediately.
Other critical SVG requirements
The namespace is just one piece of the puzzle. Getting your SVG ready for BIMI involves meeting several other strict criteria. This is often the most difficult part of setting up BIMI for many brands.
Your SVG file must adhere to the following rules:
- No external links: Apart from the required XML namespaces, your SVG cannot link out to any other files or resources.
- No scripts or animation: All interactive elements, like scripts and animations, must be removed to prevent security vulnerabilities.
- Include a <title> element: The file must contain a <title> element that reflects your company name. This is important for accessibility and validation.
- File size: The final SVG file must be 32 kilobytes or smaller.
- Vector format: The image must be a true vector graphic. It cannot contain embedded raster images like PNGs or JPEGs, which you can check by looking at the XML code for base64 text strings.
Simply using a "Save as SVG" option in a graphics editor is rarely enough to create a compliant file. You will often need to open the SVG in a text editor to manually clean it up, removing unnecessary code and ensuring every requirement is met. The BIMI group provides tools and schemas to help validate your image, which is a highly recommended step before publishing your BIMI record.
In short, the XML namespace is a non-negotiable requirement for your BIMI logo. It’s a key part of the SVG P/S format that ensures your logo is secure, compliant, and ready to be displayed by major email providers.
Does BIMI require the SVG to be publicly accessible via HTTPS?
What are the specific requirements for an SVG image to be BIMI compliant?
Does BIMI specify the location of the SVG file?
Does BIMI work with non-SVG image formats?
Does BIMI support animated SVG files?
Does BIMI validate the content of the SVG image?
