Suped

Are gradients allowed in BIMI SVG logos?

Published 15 Nov 2025
Updated 17 Oct 2026
11 min read
Summarize with
BIMI SVG logo file with a simple linear gradient swatch.
Updated on 17 Oct 2026: We clarified BIMI gradient requirements and how to update certified logo artwork.
Yes, gradients are allowed in BIMI SVG logos when they stay inside the SVG Tiny Portable/Secure (Tiny-PS) profile. Simple linear and radial gradients are acceptable. Filter-based effects, embedded raster images, external references, animation, scripting, and other markup outside the profile are not.
The problem is usually not the idea of a gradient. The problem is how the design tool exports it. A clean gradient in a design file can become an embedded bitmap, a filtered object, or a pile of editor markup that fails Tiny-PS validation. That explains the conflicting advice: many gradient exports fail, but gradients themselves are not banned.
  1. Allowed: Simple SVG linear and radial gradients that validate as Tiny-PS.
  2. Rejected: Rasterized gradients, filter effects, external references, scripts, animation, and out-of-profile markup.
  3. Risk: A validator error can come from SVG content, DNS, file hosting, redirects, certificate checks, or a failed fetch.
  4. Preference: Keep the logo simple enough to work as a flat mark, then add a restrained gradient only when it helps recognition.

What the BIMI SVG profile allows

Infographic showing simple linear and radial gradients as the safe BIMI SVG choices.
Infographic showing simple linear and radial gradients as the safe BIMI SVG choices.
BIMI uses a restricted SVG profile, not the full browser SVG feature set. The BIMI Group guidance says SVG Tiny-PS supports simple gradient definitions, specifically linear and radial gradients, while excluding filters, embedded images, scripting, and animations. That distinction matters because a visual effect that looks like a gradient in a design file can become something else after export.

Item

Status

What to check

Linear gradient
Allowed
Simple stops and no filter dependency.
Radial gradient
Allowed
Simple radius, center, and color stops.
Embedded bitmap
Rejected
No PNG or JPEG data inside the SVG.
Filter effect
Rejected
No blur, shadow, lighting, or blend effect.
Animation
Rejected
The logo must be static.
Gradient and effect handling for BIMI SVG logos.
The mailbox provider never sees the design file. It sees the hosted SVG. Treat a browser preview as a smoke test because browsers accept SVG patterns that Tiny-PS validation rejects. Review the final XML, URL, file size, MIME type, and DNS record together.
The practical rule
A gradient is fine when it is part of the vector structure. A gradient is a problem when it has been turned into a picture, a complex effect, or editor-specific markup that the restricted profile cannot render safely.
  1. Keep: A small number of color stops and a clear shape.
  2. Remove: Filters, embedded images, external dependencies, scripts, and animation.
  3. Check: The final exported SVG, not the original design file.

Technical checks beyond gradients

A valid gradient can still sit inside an invalid BIMI SVG. Review the document structure and canvas as well as file size and hosting. These checks cover both Tiny-PS compliance and mailbox provider requirements.

Check

Target

Reason

Root attributes
version=1.2 and baseProfile=tiny-ps
Declares the profile the validator should enforce.
Metadata
A title, with a description recommended
The title is required and the description supports accessibility.
Canvas
Square viewBox with a centered mark
Providers can display the logo in circular or rounded frames.
Gmail dimensions
Explicit width and height of at least 96 pixels
A square viewBox alone does not meet Gmail's dimension requirements.
File size
32 KB (32,768 bytes) or smaller, uncompressed
A compatibility recommendation; validators and mailbox providers apply their own retrieval limits.
Dependencies
Fully self-contained SVG
External images, fonts, stylesheets, and data files are not allowed.
Hosting
Stable HTTPS and image/svg+xml
Mailbox providers need to retrieve and identify the file.
Technical checks for a BIMI-ready SVG.
For Gmail's BIMI requirements, specify absolute pixel dimensions, such as width="96" height="96". Percentage dimensions are not accepted. The 32 KB recommendation applies to the uncompressed SVG, even if the server compresses its HTTP response.
Remove x and y attributes from the root svg element if the editor adds them. Use a solid background when transparency would make the logo unpredictable across provider themes or cropped frames. SVG compliance does not guarantee display because each mailbox provider also applies its own certificate, reputation, and presentation criteria.

Why gradient SVG exports fail BIMI validation

The export step is where most gradient BIMI problems start. A design file can contain a reasonable gradient, but the exported SVG can contain unsupported objects. Check the raw SVG before blaming BIMI because the visual preview alone does not show whether the file is Tiny-PS friendly.
BIMI-safe intent
  1. Shape: The brand mark still reads as a simple silhouette.
  2. Color: The gradient has a few stops and clear contrast.
  3. Markup: The gradient is defined in SVG and applied to a path or shape.
Risky export
  1. Bitmap: The gradient becomes embedded image data.
  2. Effect: The file relies on blur, shadow, masking, or blending.
  3. Weight: The SVG exceeds the recommended 32 KB size or carries unnecessary editor data.
Simple linear gradient patternxml
<svg version="1.2" baseProfile="tiny-ps" xmlns="http://www.w3.org/2000/svg" width="96" height="96" viewBox="0 0 96 96"> <title>Example, Inc.</title> <desc>Logo for Example, Inc.</desc> <defs> <linearGradient id="g" x1="0" y1="0" x2="1" y2="1"> <stop offset="0" stop-color="#f25533"/> <stop offset="1" stop-color="#29292f"/> </linearGradient> </defs> <rect width="96" height="96" fill="#ffffff"/> <circle cx="48" cy="48" r="42" fill="url(#g)"/> </svg>
That example uses Tiny-PS root attributes, explicit pixel dimensions, a square viewBox, and a solid background. The fill="url(#g)" reference points to a gradient in the same document, so it is not an external dependency. Real brand artwork still needs validation after export.
Before touching gradients, make sure the logo works at inbox size. The BIMI SVG dimensions page covers sizing and creation details, but the short version is simple: a small inbox logo punishes fine detail. A gradient will not rescue a weak flat mark.
  1. Simplify: Start with the cleanest approved mark and remove small internal details.
  2. Flatten: Convert decorative effects into ordinary vector shapes where possible. Convert lettering to paths (outlines) so it does not depend on installed fonts.
  3. Reduce: Use fewer gradient stops and keep the color change readable.
  4. Export: Export SVG Tiny 1.2-compatible artwork, remove unsupported elements, then set version=1.2 and baseProfile=tiny-ps in the final XML. Changing those attributes alone does not convert an ordinary SVG into Tiny-PS.
  5. Optimize: Remove unnecessary editor metadata while keeping the title and description. Aim for an uncompressed file of 32 KB or smaller.
  6. Validate: Validate the hosted SVG and BIMI record, then keep a flat-color fallback ready.
Steps to prepare a gradient logo, export SVG, inspect XML, validate, and publish for BIMI.
Steps to prepare a gradient logo, export SVG, inspect XML, validate, and publish for BIMI.
Self-asserted BIMI TXT record pointing at the SVGdns
default._bimi.example.com TXT "v=BIMI1; l=https://assets.example.com/bimi.svg; a=;"
Gmail requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC). The empty a= in the preceding DNS example makes it self-asserted, which does not meet Gmail's certificate requirement. Neither certificate permits SVG effects outside Tiny-PS.
Changing gradient colors or stops changes the certified artwork. The BIMI Group's logo update guidance requires a new certificate for a changed logo. Replacing the hosted SVG alone does not update the artwork bound to an existing certificate.
  1. Finalize the gradient and Tiny-PS cleanup before submitting the SVG for certification.
  2. For an existing deployment, keep the approved logo and certificate live while the revised artwork is validated and a new certificate is issued.
  3. Host the approved SVG and corresponding certificate PEM file over HTTPS. Update l= and a= when their URLs change.
  4. Test new messages in supported inboxes after DNS and logo caches refresh.

DMARC requirements for BIMI

BIMI does not start with the logo file. It starts with email authentication. The organizational domain and applicable sending subdomains need DMARC at enforcement, meaning p=quarantine or p=reject, applied to 100 percent of mail. Do not spend hours tuning a gradient before confirming the domain meets the DMARC for BIMI requirements.
Suped's DMARC monitoring groups aggregate reports by sending source so you can identify legitimate services with SPF or DKIM domain-matching failures before enforcing DMARC.
For a quick readiness check before working on the SVG, start with the domain health checker. Move into monitoring when real mail sources appear in DMARC reports.
?

What's your domain score?

Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.

DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
DMARC record that can support BIMIdns
_dmarc.example.com TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"
The pct tag is historic under RFC 9989 and is omitted here. BIMI still requires full DMARC enforcement. Keep policy test mode (t=y) disabled for BIMI.

How to validate before publishing

Validate in layers. Check the SVG file and its response headers, then the BIMI DNS record, followed by DMARC. The DMARC checker handles the DMARC record layer, while the SVG and certificate guide covers the BIMI logo and certificate checks.
Do not diagnose gradients from fetch errors
An error mentioning curl or libcurl can point to URL fetching, redirects, TLS, local networking, or a validator-side retrieval problem. It does not prove the gradient is invalid. Separate fetch failures from SVG syntax failures before changing artwork.
  1. Fetch: Confirm the HTTPS URL returns the SVG directly with the image/svg+xml content type.
  2. Inspect: Search the SVG for embedded data, external references, filters, scripts, and animation tags.
  3. Size: Aim for 32 KB or smaller before compression and remove unnecessary editor metadata. Check the receiving system's actual fetch limit.
  4. Render: Preview the centered logo at inbox size and with circular or rounded cropping.
  5. Authenticate: Confirm each sending source passes DMARC through SPF or DKIM domain matching, then verify full policy enforcement.

Symptom

Likely cause

Next check

Fetch error
URL or network
HTTPS, redirects, access rules, and any response-size limit named in the error.
Wrong file type
Hosting header
Content-Type: image/svg+xml.
SVG profile error
Unsupported markup
Root attributes and forbidden elements.
Logo too busy
Design density
Small-size and cropped previews.
BIMI not shown
Eligibility gap
DMARC, certificate, reputation, and provider criteria.
Common validation symptoms and where to look first.
Gradient readiness bands
How to judge whether a gradient logo is ready for BIMI validation.
Ready
Ship
Simple vector gradient, file at 32 KB or smaller, readable mark, clean validation.
Review
Fix
Gradient works visually, but the export needs cleanup or file-size reduction.
Rebuild
Redo
Raster data, filter effects, or unreadable small-size rendering.

Views from the trenches

Best practices
Keep gradients simple enough that a plain icon still reads clearly at mobile inbox size.
Start with the trademark shape first, then add color depth only where it helps recognition.
Validate the exported SVG, not the source artwork, because exporters change the file.
Common pitfalls
Do not let the export create embedded bitmap data when a gradient is hard to flatten.
Avoid tiny details, because the inbox logo has less visual space than the design canvas.
Treat fetch errors separately from SVG syntax errors so the fix stays focused and fast.
Expert tips
Keep one approved flat-color fallback so the team can ship if a gradient fails late.
Ask designers for fewer stops and no filters before the final Tiny-PS export pass.
Review the public SVG URL with a fresh browser session before checking BIMI again.

Marketer view

Marketer from Email Geeks says gradients can work in BIMI, but the implementation must stay inside the Tiny-PS subset rather than general SVG.
2025-07-22 - Email Geeks

Marketer view

Marketer from Email Geeks says the practical limit is not all gradients, but which gradients the exported SVG actually contains.
2025-07-22 - Email Geeks

When to use a flat-color fallback

Design the mark so it works without the gradient, then keep the gradient simple enough to survive export and validation. If cleanup cannot bring the file within the recommended 32 KB size, or the gradient makes the mark unclear at inbox size, use the approved flat version. For a certified logo, complete the certificate change process before switching artwork.

Frequently asked questions

No. Simple linear and radial SVG gradients are allowed when the final SVG complies with Tiny-PS. Complex visual effects and rasterized gradients are the usual problem.

Yes, but inspect the exported SVG. Source artwork can look correct while the export contains embedded images, filters, external dependencies, or editor markup that fails validation.

They fail when the gradient is exported as a bitmap, depends on unsupported effects, or is mixed with markup outside Tiny-PS. A file above the recommended 32 KB size also risks retrieval failures, depending on the receiving system's limits.

No. A VMC or CMC verifies rights to the logo, but the SVG still needs to meet the BIMI SVG requirements. Changing a certified gradient logo requires a new certificate for the revised artwork.

Use a gradient when the centered logo reads clearly at inbox size, survives circular or rounded cropping, and validates cleanly. A flat mark is often easier to maintain.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing