What are the BIMI requirements for SVG files and Yahoo brand recognition?

Key findings

• SVG format: BIMI requires logos to be in SVG format, specifically adhering to the SVG Tiny 1.2 profile. This is a common point of failure for logos not displaying.
• Common SVG errors: Problems frequently include SVGs containing rasterized images (like embedded PNGs), base64 encoded data, or disallowed references (e.g., xhref). These elements make the SVG non-compliant with BIMI standards.
• Brand recognition: Yahoo requires brand recognition for BIMI logo display. This is typically achieved through a consistent volume or period of regular commercial email sends.
• DMARC policy: A robust DMARC policy, ideally set to quarantine or reject, is a foundational requirement for BIMI implementation. Proper DMARC alignment helps with BIMI display.

Key considerations

• SVG validation: Utilize reliable BIMI check tools, but be aware that some may provide conflicting results. It's essential to understand the underlying technical reasons for SVG failures.
• Logo design: Ensure your logo is an exact square, centered within the SVG, and designed to avoid rasterization or disallowed elements. This often means creating it as a pure vector graphic.
• Yahoo's volume requirement: Focus on consistent sending of commercial emails from your primary marketing domains. Personal or low-volume domains may not qualify for BIMI display on Yahoo.
• Gmail's support: While this thread mentions Gmail's pilot program, Gmail (Google Mail) now supports BIMI. Ensure you meet their specific requirements for SVG and VMC if pursuing BIMI for Gmail.

Key opinions

• Conflicting validation tools: Marketers often report that while some BIMI check tools (like MXToolbox or Agari) may indicate a record and SVG are fine, others (like Mailkit) highlight issues, particularly with the SVG's internal structure.
• SVG file integrity: A common belief among marketers is that SVG files must be pure vector graphics without embedded raster images or base64 data to meet the strict BIMI Tiny 1.2 specification.
• Brand recognition for display: Many marketers recognize that beyond technical compliance, mailbox providers like Yahoo require a certain level of brand recognition or consistent sending volume for the BIMI logo to appear.
• Gmail's BIMI journey: Marketers previously noted that Gmail's BIMI support was initially limited to a pilot program, and it was not universally available. This highlighted the need to differentiate between providers' BIMI adoption phases.

Key considerations

• SVG re-creation: If an SVG file is flagged for containing rasterized images, base64 data, or disallowed references, marketers should consider re-creating the logo as a native SVG using vector-based software, ensuring it strictly adheres to the Tiny 1.2 profile.
• Commercial sending: For Yahoo Mail, prioritize sending commercial emails from the domain associated with the BIMI record to build the necessary brand recognition for logo display. Personal domains or one-off emails may not qualify.
• DNS record accuracy: Regularly check the BIMI DNS record for proper configuration and ensure it points to the correct SVG file location.
• Ongoing monitoring: Stay updated on BIMI specifications and mailbox provider policies as they evolve, as requirements can change over time.

Key opinions

• Strict SVG compliance: Experts confirm that the SVG file must be a true SVG Tiny 1.2, free from rasterized images, base64 data, or disallowed references like xhref. If these elements are present, Yahoo (and other providers) will not accept the SVG.
• Yahoo's brand recognition: Yahoo requires brand recognition, which is tied to consistent commercial email volume or a period of regular sends. This is separate from technical BIMI record validation.
• Gmail's limited support (historically): While now fully supported, experts noted that previously Gmail's BIMI implementation was in a pilot phase, meaning universal display could not be expected, unlike Yahoo's earlier adoption.
• Redoing the logo file: If a logo file doesn't meet the stringent BIMI standard, experts advise that it needs to be completely redone to ensure compliance rather than attempting minor fixes.
• DMARC policy importance: A DMARC policy of p=quarantine or p=reject is a prerequisite for BIMI to function, ensuring strong email authentication.

Key considerations

• Specialized SVG creation: Work with designers or use specialized tools to create SVGs specifically for BIMI, ensuring they meet the Tiny 1.2 profile and avoid common pitfalls like embedded bitmaps.
• Consistent commercial sending: Maintain a consistent and reputable sending pattern for commercial emails from your domain to build the necessary brand recognition with Yahoo.
• Validate with multiple tools: Use a combination of BIMI validation tools for comprehensive checks, as some may catch issues others miss, especially regarding SVG content.
• Stay informed: Keep abreast of updates from the BIMI Group and major mailbox providers, as BIMI specifications and ISP support continue to evolve.

Key findings

• Specific SVG profile: The SVG logo must strictly follow the restrictions defined by the SVG Tiny Portable/Secure profile, as authored by the BIMI Working Group. This is fundamental for BIMI compatibility.
• No rasterized images: Documentation explicitly prohibits embedded bitmap formats (like JPEG or PNG) within the SVG. Logos must be developed using vector rules.
• File size limit: There is a maximum file size for BIMI SVGs, commonly cited as 32KB, to ensure efficient loading and display by email clients.
• Square aspect ratio: The logo image itself must be an exact square with equal height and width, and it should be centered within the SVG canvas.
• DMARC prerequisite: Official BIMI guidelines confirm that a DMARC policy set to quarantine or reject is a mandatory requirement for BIMI to display.

Key considerations

• Validation tools: Utilize official BIMI validation tools and generators, often found on the BIMI Group website, to ensure SVG compliance before deployment.
• SVG creation best practices: Create SVGs using vector editing software, exporting specifically for the BIMI Tiny 1.2 profile to avoid embedding non-vector elements or disallowed references.
• Hosting requirements: The SVG logo must be hosted on a publicly accessible web server using HTTPS, ensuring it can be securely retrieved by mailbox providers.
• VMC requirement for some providers: While not universally required for all BIMI displays, some providers (like Google) mandate a Verified Mark Certificate (VMC) for logo display.