Skip to content
Email Delivery Platform
Talk to engineering

/ Free Tools — SVG to BIMI Converter

Make your logo pass instead of fail.

Paste a normal SVG and watch it become BIMI-compliant SVG Tiny P/S: scripts, animation, and external references stripped, the viewBox squared and centered, absolute pixel size set, the required title added. Before-and-after preview, downloadable result, nothing uploaded.

Request infrastructure review Why logos fail

Parsed and rewritten in your browser — nothing uploaded. The result still needs enforced DMARC and a BIMI record to display.

/ What this does

BIMI requires the SVG Tiny P/S profile, a restricted form of SVG that a logo from a design tool almost never matches — it carries scripts, animation, external references, or a non-square canvas that a validator rejects, so the logo silently fails to appear. This converter rewrites the file into the compliant shape in your browser: it strips every forbidden element and attribute, squares and centers the viewBox so nothing is cropped, sets an absolute pixel size of at least 96, declares the tiny-ps profile, and adds the required title. It shows a before-and-after preview inside a real avatar shape and hands you the fixed file to download, with each change listed so you know exactly what was done.

This fixes the one thing it fixes — a compliant logo file — which is the piece most senders get stuck on and the easiest to misdiagnose as a DNS or certificate fault. It's honest about the rest: display still needs enforced DMARC, HTTPS hosting, a BIMI record, and a certificate for Gmail and Apple. Run the output through the validator to confirm, then the generator to build the record. Nothing about your logo leaves the page.

  • Strips the forbidden

    Scripts, animation, external references, raster images, and interactivity removed — the things that make Tiny P/S validators fail.

  • Squares + centers

    A non-square canvas becomes a square from 0 0 with the artwork centered, so the avatar crop is clean.

  • Before & after

    See the original and the converted logo side by side in a real avatar shape, with every fix listed.

  • In the browser

    Parsed, rewritten, and offered for download locally. No logo is uploaded or stored.

/ Why logos fail

Why does a perfectly good SVG fail BIMI?

The SVG format is huge and permissive — it can run scripts, animate, pull in external files, and embed photos. That power is exactly the problem for email. Mailbox providers can't safely render arbitrary SVG next to a message, so BIMI mandates SVG Tiny P/S, a locked-down subset that removes everything with a security or consistency risk. A logo exported from a design tool is valid SVG and still fails, because it carries the very features the profile bans.

The usual culprits are predictable. A designer's export includes editor metadata and sometimes a stray script or animated flourish. The canvas is whatever shape the artwork happened to be, rarely a perfect square from the origin. Dimensions are set as percentages so the logo scales to its container, when Gmail wants absolute pixels of at least 96. And the required title element is simply absent, because nothing outside BIMI needs it. Each of these is a hard fail on its own.

What makes this maddening is the failure mode: the logo just doesn't appear, with no error to the sender. It's easy to blame DNS or the certificate and spend hours there when the real fault is a viewBox that isn't square. Converting the file to a clean Tiny P/S profile eliminates that entire category of problem in one step, so when you then troubleshoot display, you're looking at the parts that are actually left.

/ After conversion

The file is compliant — now what makes it appear?

A compliant logo is necessary and not sufficient, so here's the honest rest of the checklist. The file has to be hosted over HTTPS with the correct image/svg+xml content type — some CDNs serve it as plain XML or application/octet-stream instead, which fails silently. Your domain needs DMARC at enforcement, quarantine or reject, because BIMI does nothing at p=none. You publish a BIMI record pointing to the logo. And for Gmail and Apple Mail specifically, you need a Verified Mark Certificate or Common Mark Certificate; Yahoo and a few others will show a self-asserted logo without one.

The sequence is worth respecting because each step depends on the one before. Convert the logo here, confirm it with the validator, publish it over HTTPS, get DMARC to enforcement, add the BIMI record with the generator, and layer the certificate on last. Skipping ahead is how people end up debugging a certificate when the logo was never valid to begin with. The steady-state work — keeping DMARC enforced across every sender so the logo keeps showing — is the operation behind a verified inbox presence, which is what we run.

/ Converter FAQ

Why won't my normal SVG work for BIMI?
BIMI requires the SVG Tiny Portable/Secure profile — a deliberately restricted subset of SVG built so mailbox providers can render logos safely and identically. A logo exported from Illustrator, Figma, or a design tool almost always includes things Tiny P/S forbids: scripts, animation, external references, embedded raster images, interactivity, or a non-square viewBox. Any one of those makes a validator reject the file, and the logo silently won't display. This converter takes the ordinary SVG and rewrites it into the compliant shape — removing what's disallowed, squaring the canvas, fixing the root attributes, and adding the required title — so it passes instead of failing.
What exactly does the converter change?
It runs the fixes a validator checks for, in order. It removes every forbidden element — script, animate and its siblings, foreignObject, external image, use, and a — and strips event-handler attributes and external href references. It squares the viewBox to start at 0 0, centering your artwork inside the square canvas BIMI requires so nothing is cropped. It sets width and height to absolute pixels at least 96 wide, as Gmail demands. It declares version 1.2 and the tiny-ps base profile on the root. And it inserts a title element, which the profile requires, plus a desc element that Gmail recommends for accessibility. Each change is listed so you can see precisely what was done.
Will squaring the viewBox distort my logo?
No — it centers rather than stretches. If your logo's canvas is wider than it is tall, the converter computes a square the size of the longer side and translates the artwork to the middle of it, so the proportions are untouched and the logo sits centered with even margins. That's exactly how a mailbox provider wants it, because they crop the square into a circle for Gmail or a rounded square for Apple Mail, and a centered logo survives that crop cleanly. The before-and-after preview shows you the result inside a real avatar shape so you can confirm nothing important lands at the edge.
Is the converted file guaranteed to display?
The file will pass the SVG Tiny P/S structural rules, which is the gate most logos fail — but BIMI display depends on more than the SVG. Your domain still needs DMARC at enforcement, the logo hosted over HTTPS with the right content type, a BIMI record pointing to it, and for Gmail and Apple a VMC or CMC certificate. So think of this as fixing the one piece it fixes: a compliant logo file. Run the output through the BIMI validator to confirm, then use the generator to build the record. The converter removes the formatting problem that's easy to misdiagnose as a DNS or certificate issue.
Does my logo get uploaded?
No. The SVG is parsed, rewritten, previewed, and offered for download entirely in your browser — the same Tiny P/S rules applied locally with no server involved. Nothing about your logo is sent or stored, which you can confirm in the network tab where converting makes no request. The download writes the fixed file straight to your device from the page.
What if my logo has raster images or gradients?
Gradients and standard vector shapes are fine — Tiny P/S supports them. Embedded raster images are not: BIMI logos must be pure vector, so a PNG or JPEG pasted inside the SVG has to go, and the converter removes it and flags that the artwork needs a true vector version. If your logo is fundamentally a raster image wrapped in SVG, no converter can make it compliant — it needs to be redrawn as vector art. The tool tells you plainly when that's the case rather than producing a file that looks converted but renders empty.

A compliant logo is step one. Keeping it lit is the operation.

The converter fixes the file; a logo only keeps showing while DMARC stays enforced across every sender and the record and certificate stay valid. That standing work is what we operate. Convert the logo, then let's light it up for good.

Book infrastructure review

Related capabilities