SVG Tiny PS: Why BIMI Files Fail Validation and How to Stay Compliant

A logo that looks right on your website can still fail BIMI validation. The file format is usually the cause. BIMI doesn’t accept a standard SVG file.

BIMI must use SVG Tiny Portable/Secure (PS), a restricted profile built for secure use. A BIMI SVG fails validation when it's missing a required element or contains a prohibited one. A design team can hand over a BIMI SVG that renders correctly in a browser but doesn't meet this profile. The result is a stalled rollout, repeated handoffs between marketing and IT, and a brand logo that never reaches the inbox.

This guide explains what the profile requires, what it prohibits, why exports fail, and how to keep your BIMI SVG compliant after launch.

A compliant logo is one part of a BIMI rollout that also depends on DMARC enforcement, certificates, and DNS changes across teams. Explore BIMI Management to see how Sendmarc supports logo readiness alongside the rest of your rollout.

What an SVG Tiny PS Logo Must Include

SVG Tiny PS uses SVG Tiny 1.2 as its base and restricts it further. Both profiles declare version="1.2", so the baseProfile attribute is what identifies an SVG Tiny PS file. The profile is defined in an Active Internet-Draft, and the BIMI Group publishes the BIMI requirements.

The BIMI Group lists three required elements for a BIMI SVG:

A <desc> element isn’t required. The BIMI Group recommends it to support accessibility.

The BIMI Group also gives design guidance for consistent display:

What SVG Tiny PS Prohibits

A valid BIMI SVG can’t include:

The draft removes these features to reduce the security concerns interactive content introduces. They limit a BIMI SVG to the elements needed to render static vector graphics. The draft also expects files to be self-contained, because the email client may not have an active network connection.

Why Design Tool Exports Fail SVG Tiny PS Validation

Design tools export SVG for browsers, not for BIMI. The BIMI Group recommends exporting from Adobe Illustrator as SVG Tiny 1.2, the closest available profile, and then editing the file.

The BIMI Group has released SVG conversion tools to help with these edits. Validate the BIMI SVG after every conversion. A file that opens correctly in a browser can still fail validation.

Why a Compliant BIMI SVG Might Still Not Display

SVG Tiny PS compliance is necessary, but it isn’t enough on its own. The BIMI Group implementation guide requires a DMARC policy at enforcement, either p=quarantine or p=reject.

Certificates add another condition. Self-asserted BIMI records, published without a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC), have limited support across mailbox providers. Each provider also sets its own criteria for displaying a logo.

How to Keep Your BIMI SVG Compliant After Launch

Logo validation isn't a one-time task. A brand refresh or a hosting change can replace a compliant file with one that fails.

Logo updates also affect your certificate. The BIMI Group states that a VMC or CMC is tied to both your domain and your logo file. A new logo needs revalidation by the certificate authority. Your BIMI record then needs updated l= and a= values that point to the new files.

In large organizations, these steps cross teams. Marketing owns the logo, and IT owns DNS. Without a shared process, one team’s change can break another team’s configuration.

Build these checks into change control:

How Sendmarc Helps

BIMI depends on two things staying in place: DMARC enforcement and a compliant logo. Both require ongoing work across security, IT, and marketing teams that already have full workloads.

Sendmarc reduces that internal effort with:

Your brand logo only reaches the inbox when your domain stays at enforcement. Explore DMARC Management to see how Sendmarc helps enterprises reach p=reject and keep their domains protected as their environments change.