BIMI SVG Tiny PS Requirements and Export Checks

Overview

SVG Tiny PS is a restricted profile derived from SVG Tiny 1.2. The restriction matters because a mailbox provider may fetch and render a logo controlled by an external domain. General-purpose SVG can include scripts, external references, animation and complex features that are unnecessary for a static brand mark and increase security or interoperability risk.

The logo should use a square coordinate system through viewBox, for example 0 0 100 100. The artwork can have visual padding inside that square, but the canvas itself should not be a wide banner or tall rectangle. Include a short title element for identification and accessibility.

Why it happens

Design applications optimize for broad web compatibility, not BIMI's portable and secure subset. An export may silently embed a raster preview, preserve editor metadata, add x and y attributes, link to a local font, convert a gradient into an unsupported construct, or omit the tiny-ps profile. The file can look correct in a browser while failing a BIMI validator or a provider's renderer.

How to fix it

Export a clean vector-only SVG, then inspect the source rather than relying on appearance. Confirm the root namespace, version, baseProfile and square viewBox; add one meaningful title; convert text to vector paths when font availability could change the logo; remove scripts, event handlers, animation, external URLs, linked raster images and unnecessary editor metadata; and simplify filters or gradients that the Tiny profile cannot represent reliably.

Serve the file publicly over HTTPS without login, cookies or expiring signed URLs. Use the BIMI Inspector to check fetch status, content type, viewBox, title, profile and structural findings. A clean structural result does not certify visual quality, trademark rights, evidence-document trust or provider display eligibility.

Examples

A minimal root commonly resembles: <svg xmlns="http://www.w3.org/2000/svg" version="1.2" baseProfile="tiny-ps" viewBox="0 0 100 100"><title>Example Company</title>...</svg>. The ellipsis represents self-contained vector paths and shapes, not scripts or externally loaded assets.

Common mistakes

Frequent export problems include width and height without a usable viewBox, a non-square viewBox, missing or incorrect baseProfile, no title, embedded PNG or JPEG data, linked fonts or images, script and event attributes, animation, unsupported gradients or filters, an XML parser error, an HTTPS redirect loop, an HTML response at the SVG URL, and the wrong MIME type.

Checklist

• The root element declares the SVG namespace, version 1.2 and baseProfile tiny-ps.
• The viewBox exists and uses a square canvas.
• A meaningful title element is present.
• Artwork is self-contained vector content with no script or external resource references.
• Text, gradients, filters and editor-specific output are simplified for portable rendering.
• The public HTTPS URL returns the SVG itself with a suitable content type and no authentication.

Forbidden and high-risk features

Scripts, event-handler attributes and external resource references are incompatible with the secure profile. Linked or embedded raster images, external fonts, animation, interactivity, complex filters and unsupported gradient output are also common rejection or rendering risks. When a feature is not essential to a static logo, remove it rather than depending on provider-specific tolerance.

Why the square canvas matters

Mailbox interfaces render brand indicators in compact square or circular placements. A square viewBox gives the provider a predictable coordinate system. Keep important artwork away from the edges because a provider may apply a circular mask or additional padding.