BIMI uses SVG Tiny Portable/Secure (Tiny PS), a restricted vector format. A file that looks right in a browser is not necessarily compatible with BIMI.
- Start with original vector artwork when possible.
- Use SVG Tiny PS, with a square composition and readable small-scale artwork.
- Validate the final file before certificate submission.
The format is part of the requirement
A PNG or JPEG cannot become a BIMI logo just by renaming it to .svg. An ordinary SVG export may also include features outside the allowed profile.
The BIMI Group’s guidance calls for version="1.2", baseProfile="tiny-ps", and a meaningful <title>. Scripts, animation, and external resources are not allowed. Root-level x and y attributes should be removed.
Design for a small, cropped space
Use a square canvas, centre the important artwork, and allow breathing room around it. A receiver may crop the image to a circle or a rounded shape. A long tagline that works on a website is often unreadable in an avatar.
Review the artwork at small sizes on both light and dark backgrounds. Keep enough contrast to recognise the main shape without relying on fine detail. A solid background gives more predictable results.
Keep the file lean
The BIMI Group recommends a file no larger than 32 kilobytes. Remove editing metadata and unnecessary paths while preserving the approved artwork. Avoid embedding raster images or relying on external fonts.
Changing only the profile label is not validation. Inspect the actual elements and run the final file through a BIMI-specific checker.
A practical design handoff
- Confirm the exact mark the organisation is entitled to use.
- Prepare a square version from the original vector source.
- Convert and validate the Tiny PS file.
- Have the brand owner review small-size previews.
- Give the final approved file to the certificate and implementation owners.
Keep the original artwork, approved export, and validation notes together. Agree a filename or version so nobody accidentally hosts an earlier draft.
Publish the approved asset
Use a stable public HTTPS address that returns the actual SVG, with an appropriate image/svg+xml content type. Check access without a signed-in session. A browser challenge, expired TLS certificate, or download page can prevent a receiver from retrieving the file.
If a mark certificate is involved, coordinate artwork changes with the issuer. The certificate and hosted logo must remain consistent.
Go to the source
Provider policies and specifications can change. These primary sources informed this guide, reviewed on 1 November 2026.