BIMI SVG Tiny-PS compliance Validator

How BIMI Validation & Auto-Fixing Works

The validation and sanitization workflow operates on a client-side parsing pipeline to maximize speed and data safety. Stage 1: XML Parsing and Namespace Audit. When an SVG is uploaded or pasted, the engine initializes a Cheerio parsing instance inside strict XML mode. This mode is critical because standard HTML parsers force lowercase transformations on attributes, which corrupts case-sensitive SVG properties (like viewBox). The engine scans the root element to ensure the baseProfile matches tiny-ps and the version attribute is exactly 1.2. Stage 2: CSS Stylesheet Class Mapping. Standard vector graphics editors often export styling rules inside style elements using classes. Because SVG Tiny-PS forbids stylesheet tags, this engine runs a custom CSS rule extractor. It parses styling declarations, queries matching elements in the DOM tree, and writes the properties directly to individual elements as presentation attributes (like fill and stroke). Visual class values and style blocks are then deleted. Stage 3: Security and Banned Tag Sweep. The engine performs a search for forbidden tags including script, style, iframe, object, embed, foreignObject, text, and animate. It filters all properties to reject external HTTP links or base64 raster streams, ensuring that all visual assets are self-contained vectors. Stage 4: Geometry and Accessibility Standardisation. If the auto-fixer is triggered, missing width and height attributes are inferred from the viewBox coordinates. A default title tag is prepended as the first child of the root element to meet accessibility criteria. The final document is then formatted as valid XML for immediate download.

Severity Levels Breakdown

The validator dashboard displays the test results categorized into two severity groups to help guide modifications: Critical Failures represent errors that will cause recipient email servers to immediately reject your logo. These include files that exceed the 32 KB size threshold, mismatch root baseProfile or version declarations, contain dynamic javascript blocks, or reference external CSS styling definitions. These failures must be resolved before proceeding. Deliverability Warnings cover items that do not break XML parsing but introduce render issues. For example, transparent backgrounds will render fine on white interfaces but can make dark logos invisible when the user switches to Dark Mode. The validator warns against transparency, suggesting a solid color background container. It also flags non-square viewBox layouts and misplaced accessibility tags. The XML Source tab details the raw markup of the SVG. Clicking on any validation error automatically targets the offending node in the code view, scrolling the container to highlight the exact line number.