Suped

Can BIMI logos be animated and how do Google profile images interact with BIMI?

Published 18 Jul 2025
Updated 24 Oct 2026
14 min read
Summarize with
Static BIMI logo and Google profile avatar illustrating Gmail sender-image differences.
Updated on 24 Oct 2026: We clarified Gmail logo selection, Google profile-image testing, and the authentication requirements for static BIMI logos.
No, BIMI logos cannot be animated. Even though SVG as a general file format can contain animation, BIMI uses SVG Tiny Portable/Secure, a restricted SVG profile for logo safety and compatibility. The BIMI SVG must not include animations, scripts, external references, bitmap embeds, or interactive elements.
The moving sender logo people notice in Gmail usually comes from a Google Account or Google Workspace profile image, sometimes uploaded as an animated GIF. That image is not BIMI. Animated playback has appeared in some Gmail views, but Google does not document or guarantee it. When Gmail displays BIMI for the sending domain, its static logo can replace the Google profile image in the message sender slot.
Keep BIMI static for brand display backed by email authentication, then test a Google profile image separately if the brand wants animation. Do not replace working BIMI with a profile image. BIMI depends on email authentication; it does not authenticate messages itself.

BIMI logo requirements and Gmail checkmarks

BIMI has two separate constraints that matter here. First, the BIMI record points mailbox providers to a BIMI asset and, for Gmail, must identify a PEM file containing a verified logo certificate. Second, the logo asset must meet BIMI SVG requirements. Google states on its Google BIMI setup page that BIMI SVG files should not contain animations or interactive elements. Gmail can also show a verified checkmark for senders verified with a Verified Mark Certificate (VMC). A Common Mark Certificate (CMC) supports eligible logos without a registered trademark, but does not create that checkmark. A Google profile image does not create it either.
That rule catches the common misunderstanding. SVG support in a browser does not equal SVG support in BIMI. A browser can run many SVG capabilities. BIMI narrows the allowed SVG behavior because the image appears inside security-sensitive mail UI, across many clients, with different rendering engines.
  1. BIMI logo: A static SVG Tiny PS logo, delivered to Gmail inside a VMC or CMC-backed PEM file.
  2. Google profile image: A Google Account or Workspace avatar. Animated GIF playback has appeared in some Gmail views but is not guaranteed.
  3. Interaction: Gmail can use the BIMI logo in the message sender slot while the profile image remains available in contact and account surfaces. Display depends on the Gmail view and recipient context.
  4. Gmail checkmark: A VMC-backed BIMI setup can create the Gmail verified checkmark. A CMC or profile image cannot.
  5. Best choice: Use BIMI as the primary brand logo system and treat profile-image animation as an unguaranteed Gmail-only effect.
Do not animate the BIMI asset
If a brand already has BIMI working with a VMC or CMC, leave the BIMI logo static. Adding SVG animation to the BIMI file is a standards problem, not a creative improvement. The mailbox provider can reject the asset, ignore the BIMI record, or display no logo.
BIMI
  1. Scope: Mailbox-provider standard for brand logo display.
  2. Format: Static SVG Tiny PS, often embedded in a PEM file.
  3. Trust signal: Depends on DMARC enforcement and, in Gmail, VMC or CMC handling.
  4. Gmail checkmark: VMC-backed BIMI can show it in supported Gmail views.
Google profile image
  1. Scope: Google-only identity image tied to the sender account.
  2. Format: A normal profile image upload. GIF animation depends on Gmail's current client behavior.
  3. Trust signal: No email authentication or mark certificate requirement for the image itself, and no cross-provider guarantee.
  4. Display priority: Gmail can place it behind BIMI in the message sender slot.

Why SVG animation still fails

A normal SVG file can contain animated elements, timing logic, external resources, raster image embeds, and script hooks. BIMI strips that down. The accepted BIMI file profile is designed for a static, predictable logo that a mailbox provider can fetch, validate, cache, and render without executing behavior.
The BIMI image format requires a stricter export than an ordinary web logo. Gmail requires an image at least 96 pixels high and wide, with width and height specified in absolute pixels. Google recommends centering the logo in a square, using a solid background, keeping the SVG at 32 KB or smaller, and including a desc element for accessibility. Resaving a PNG as an SVG does not make it compliant if the file still contains embedded bitmap artwork.
Check the SVG root element for baseProfile="tiny-ps" and version="1.2". Include a nonempty <title> naming the organization, and remove x= and y= attributes from the root <svg> element. A square SVG export alone does not establish SVG Tiny PS compliance.
BIMI record with a certificate filedns
default._bimi.example.com TXT "v=BIMI1; l=; a=https://bimi.example.com/vmc.pem"
For Gmail, the a= tag points to the VMC or CMC-backed PEM file. The static SVG is embedded in that certificate file. Trying to hide animation inside the SVG defeats the verified image workflow and makes the asset noncompliant. If the logo artwork changes, have the certificate reissued for the new logo; replacing a separately hosted SVG does not update the logo embedded in the certificate.
BIMI SVG Tiny PS logo requirements: static artwork without scripts or animation.
BIMI SVG Tiny PS logo requirements: static artwork without scripts or animation.

Item

BIMI

Google profile

Animation
Not allowed
GIF playback not guaranteed
Bitmap embeds
Not allowed
Normal image upload
Authentication
DMARC required
Account based
Reach
Supporting inboxes
google.com logoGoogle only
Best use
Primary logo
Extra avatar
BIMI logo asset rules compared with a Google profile image.

How Google profile images fit in

A Google profile image comes from Google Account or Google Workspace identity data. If the exact sending address has a Google identity with a profile photo, Gmail has an image it can use in places that rely on that identity system. That is why a sender can look animated in Gmail while still having a static BIMI record.
Google Account profile picture editor with a circular avatar preview for Gmail.
Google Account profile picture editor with a circular avatar preview for Gmail.
There are two important practical limits. First, the profile image is not an email authentication mechanism. It does not prove the sender controls the brand, and it does not replace DMARC, DKIM, SPF, VMC, CMC, or BIMI. Second, it is not portable. Yahoo Mail, Apple Mail, Outlook, and other mailbox clients do not use a sender's Google profile image as a general BIMI substitute.
Gmail has more than one place to show sender imagery. An accepted BIMI logo can replace the Google profile image in the message sender slot. The Google profile image can still appear on hover cards, account pages, directory views, and cases where Gmail does not show BIMI. Google does not publish a universal priority order covering every Gmail view, so compare the same message on the clients your recipients use.

Gmail surface

Primary source

What to expect

Message sender
BIMI when accepted
BIMI can replace profile avatar
Hover card
Profile or contact
Account or saved contact image
Address book
Profile or contact
Saved contact data can win
No BIMI
Profile or fallback
Display remains recipient dependent
Where each logo source tends to matter inside Gmail.
If employee profile photos disappear after BIMI is enabled, review where the BIMI record is published. For marketing-only BIMI, publish the logo record on the marketing From subdomain and leave the employee From domain without a BIMI logo record. A subdomain without its own record can inherit the organizational domain's BIMI record, so moving mail to a subdomain alone does not exclude it. Where exclusion is needed, an explicit v=BIMI1; l=; a=; record at the relevant BIMI selector declines BIMI participation. Disabling BIMI does not guarantee that Gmail will show an employee photo, and it does not require weakening DMARC.
A Google profile image can supplement BIMI in Google identity surfaces where BIMI is not shown. Neither image configuration guarantees which avatar every recipient sees.
A moving sender avatar is consistent with a Google profile image, but appearance alone does not identify its source. Al Iverson's historical ANIBIMI example demonstrates a Google profile-image workaround, not an animated BIMI standard. Its 2022 playback results are not a guarantee of current Gmail behavior.

How to tell which logo Gmail is showing

A logo beside a message does not prove that BIMI supplied it. Check the same production message before changing the SVG or Google profile image.
  1. Inspect the checkmark: Gmail's verified sender checkmark indicates VMC-backed BIMI. An absent checkmark does not rule out BIMI, because CMC-backed logos do not receive it.
  2. Check message authentication: On Gmail web, open the message's More menu and choose "Show original". A DMARC pass supports BIMI eligibility but does not prove that Gmail selected the BIMI image.
  3. Compare contact context: Send the same message to a Gmail account without a saved sender contact. Compare that result with an account that has a contact photo, then check web and mobile views.
  4. Check the image location: An animated GIF in the message body or signature is separate from the sender avatar. Gmail Promotions annotations also control promotional previews rather than permitting animation in the BIMI SVG.

What to do if the brand wants animation

If a sender already has BIMI working with a VMC or CMC, keep that setup untouched. Then test a Google profile image separately for the exact From address the campaign uses. This is a Gmail display test and does not require a BIMI migration.
  1. Keep BIMI: Do not edit the working BIMI SVG or certificate file to add movement.
  2. Match sender: Set the profile image on the exact Google identity that matches the visible From address.
  3. Test Gmail: Send real messages to external Gmail and Workspace recipients, then check message and contact surfaces.
  4. Monitor DMARC: Keep authentication stable so the static BIMI logo remains eligible when Gmail chooses it.
DMARC policy shape for Gmail BIMI readinessdns
_dmarc.example.com TXT "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@example.com"
The DMARC policy is not optional for BIMI. Gmail requires p=quarantine or p=reject and its current BIMI documentation still requires pct=100. RFC 9989 made pct historic and introduced t=y for testing. Test mode requests one policy level lower for failing messages: reject becomes quarantine, and quarantine becomes none. Retain pct=100 to meet Google's published requirement, and keep testing off by omitting t or setting t=n when preparing BIMI.
BIMI readiness by DMARC policy
DMARC policy eligibility for Gmail BIMI. Passing these policy checks does not guarantee logo display.
Not ready
p=none
Monitoring only, useful for discovery but not enough for BIMI.
Testing
t=y
Requests one policy level lower for failures: reject becomes quarantine; quarantine becomes none. Turn testing off for BIMI readiness.
Policy eligible
p=quarantine or p=reject; pct=100; t omitted or t=n
Enforcement is enabled and Google's published pct requirement is met. Message authentication and other BIMI checks still apply.
For implementation checks, start with the authentication base. Suped's DMARC checker identifies DNS policy mistakes. A valid record alone does not prove that an individual message passes DMARC.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
After checking the DMARC record, send test mail through the real production path. Do not test with a different mailbox, a different From domain, or a personal Gmail alias. Each message must pass DMARC through SPF or DKIM using a domain that matches the visible From domain under DMARC's domain-matching rules. Profile-image behavior depends on the exact sender identity.
BIMI has no published universal minimum sending volume. Correct DNS, authentication, certificate, and SVG data still do not guarantee display because Gmail controls final eligibility and UI placement. Test with real external recipients and avoid treating one inbox result as a universal outcome. After publishing the BIMI record, Google advises allowing up to 48 hours for the logo to appear; that window is not a display guarantee.

Monitor BIMI authentication requirements with Suped

Suped's DMARC reporting and email authentication platform helps teams check the authentication requirements behind BIMI while testing Gmail profile imagery separately.
For teams working toward BIMI readiness, Suped turns DMARC monitoring into a practical workflow: identify legitimate sending sources, investigate messages that fail DMARC, then move policy to enforcement after those sources pass. Continue monitoring after sender changes to catch authentication failures that affect BIMI eligibility.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
The hosted controls matter when DNS ownership slows everything down. With Hosted DMARC, a team can stage policy changes without turning every adjustment into a DNS ticket. That is useful when moving toward BIMI enforcement, especially across many brands or client domains.
Check authentication separately from avatar display
  1. Suped: Review DMARC reports, investigate source authentication failures, and manage the policy needed for BIMI.
  2. Google profile: Test Gmail-only avatar behavior for the exact sender address.
  3. BIMI: Keep the verified brand logo static and standards-compliant.

Choose between BIMI and a Google profile image

The decision comes down to the sender's current state. A brand with no BIMI should not start with animation. Start with DMARC enforcement, a compliant SVG, and a certificate path that matches the target mailbox providers. A brand with working BIMI can add a Google profile image, but that should be treated as a separate Gmail enhancement.
BIMI setup and Gmail profile-image testing flow with DMARC and VMC or CMC requirements.
BIMI setup and Gmail profile-image testing flow with DMARC and VMC or CMC requirements.
There is also a placement question. If the team needs to understand where BIMI appears, separate that question from whether a Google avatar animates. BIMI coverage is about mailbox provider support and policy requirements. Profile animation is about Google account UI.
Keep working BIMI
Use this path when BIMI already works in Gmail and other target inboxes.
  1. Risk: Changing the SVG can break a working logo.
  2. Result: Stable authenticated brand display.
Add profile image
Use this path when the brand specifically wants Gmail-only avatar coverage.
  1. Risk: Animation behavior can change without DNS or BIMI notice.
  2. Result: Extra Gmail visibility in surfaces BIMI does not cover.

How to set and test the Google profile image

Use the Google Account tied to the exact visible From address. A photo applied only through an administrator directory does not prove that external Gmail recipients can see it, and an alias or group address does not automatically inherit another account's profile image. A Google Account can use an existing non-Gmail email address; a paid Google Workspace mailbox is not required. Choose "Use your existing email" when creating the account and verify ownership. This does not move your email hosting or change the production sending service.
  1. Open the matching account: Sign in to the Google Account or Workspace user that matches the campaign's visible From address.
  2. Upload the image: Under Personal info, choose the profile picture and upload the file. Design it for Google's circular crop.
  3. Check visibility: If Google offers an audience control, set the profile picture to Anyone for testing with external recipients.
  4. Allow propagation: Google says profile changes can take a few days to update across its products.
  5. Test both paths: Send through the production mail stream to external Gmail and Workspace accounts, then compare message, hover-card, contact, and account views. Include a test recipient with no saved sender contact, and compare Gmail web with the mobile app.
Animation remains an experiment
Google's profile-photo instructions describe image uploads but do not promise animated GIF playback in Gmail. Use a first frame that works as a static avatar, because Gmail can freeze the image, replace it with BIMI, or show a recipient-controlled contact photo.

Frequently asked questions

No. BIMI requires a static SVG Tiny PS profile. Animation, scripts, interactivity, external references, and bitmap embeds make the logo unsuitable for BIMI use.

You were probably seeing a Google profile image tied to the sender's Google Account or Workspace identity. GIF animation has appeared in some Gmail views, but Google does not guarantee playback.

No. It is a Google-only profile image. It does not replace DMARC enforcement, a compliant BIMI SVG, a VMC or CMC required by Gmail, or a BIMI TXT record. When BIMI is accepted in Gmail, it can replace the profile image in the message sender slot; the result still depends on the recipient and Gmail view.

Yes, if the brand wants Gmail-specific avatar coverage and accepts that it is separate from BIMI. Keep the BIMI logo static, and make sure the profile image's first frame works when Gmail does not animate it.

BIMI does not publish a universal minimum send volume. Correct authentication and certificate data still do not guarantee display because Gmail controls sender eligibility and UI placement.

Check DMARC enforcement with testing off and pct=100 for Google's published compatibility requirement, then confirm the production message passes DMARC. Verify the BIMI TXT record for the visible From domain, a valid VMC or CMC covering that domain, the embedded SVG format, and publicly accessible HTTPS certificate hosting. Allow for caching and test a supported Gmail view.
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