Can BIMI logos be animated and how do Google profile images interact with BIMI?
Updated on 23 Jun 2026: We updated this guide for Gmail's current BIMI certificate rules, DMARC's newer pct handling, and the sender-volume limits that affect BIMI display testing.
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 is usually a Google Account or Google Workspace profile image, often uploaded as an animated GIF. That image is not BIMI. It is a Google identity image tied to the sender address or account, and it only affects Google-controlled surfaces. When Gmail accepts BIMI for the sending domain, the BIMI logo usually takes the message sender-logo slot ahead of the Google profile image.
The practical answer is simple: keep BIMI static for authentication-backed brand display, then use a Google profile image as a Gmail-only enhancement if the brand wants animation. Do not replace working BIMI with a profile image. BIMI has the durable authentication job. The profile image has the optional visual job.
The direct answer
BIMI has two separate constraints that matter here. First, the BIMI record points mailbox providers to a BIMI asset and, for Gmail, usually to 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 VMC. A Google profile image does not create that checkmark.
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 intentionally narrows the allowed SVG behavior because the image appears inside security-sensitive mail UI, across many clients, with different rendering engines.
- BIMI logo: A static SVG Tiny PS logo, usually delivered to Gmail inside a VMC or CMC-backed PEM file.
- Google profile image: A Google Account or Workspace avatar that can be static or animated in some Gmail views.
- Interaction: When Gmail accepts BIMI, it usually uses the BIMI logo in the message sender slot while the profile image still matters in contact and account surfaces.
- Gmail checkmark: A VMC-backed BIMI setup can create the Gmail verified checkmark. An animated profile image cannot.
- Best choice: Use BIMI as the primary brand logo system and treat animated profile images as Gmail-only decoration.
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 failure mode is simple: the mailbox provider rejects the asset, ignores the BIMI record, or displays no logo.
BIMI
- Scope: Mailbox-provider standard for brand logo display.
- Format: Static SVG Tiny PS, often embedded in a PEM file.
- Trust signal: Depends on DMARC enforcement and, in Gmail, VMC or CMC handling.
- Gmail checkmark: VMC-backed BIMI can show it in supported Gmail views.
Google profile image
- Scope: Google-only identity image tied to the sender account.
- Format: Static image or animated GIF, depending on upload path and client behavior.
- Trust signal: No DMARC certificate requirement and no cross-provider guarantee.
- 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 restriction is also why BIMI image format work feels pickier than ordinary logo export work. The logo needs a square composition, absolute dimensions, a small file size, and no behavior. Resaving a PNG as an SVG does not make it a compliant BIMI logo if the file still contains embedded bitmap artwork.
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 is the important part when a VMC or CMC-backed PEM file is used. The static SVG is inside that certificate file. Trying to hide animation inside the SVG defeats the purpose of the verified image workflow.
BIMI logo rules: static SVG, no scripts, no animation, and verified logo.
|
|
|
|---|---|---|
Animation | Not allowed | GIF can animate |
Bitmap embeds | Not allowed | Normal image upload |
Authentication | DMARC required | Account based |
Reach | Supporting inboxes |  Google 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 perfectly static BIMI record.
Google Account profile photo settings with GIF 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 also has more than one place to show sender imagery. When BIMI is accepted in Gmail, expect BIMI to win the message sender logo placement. The Google profile image can still appear on hover cards, account pages, directory-style views, and cases where Gmail does not show BIMI. The exact display changes by app, account state, contact state, and Gmail UI.
|
|
|
|---|---|---|
Message sender | BIMI when valid | BIMI can replace profile avatar |
Hover card | Profile | Account avatar |
Address book | Profile | Contact image |
No BIMI | Profile | Fallback avatar |
Where each logo source tends to matter inside Gmail.
If employee profile photos disappear after BIMI is enabled, the domain scoping is usually too broad for the desired behavior. Keep corporate user mail on the organizational domain and put marketing mail on a dedicated subdomain or From domain when the marketing stream needs BIMI but employee mail should keep Google profile photos.
This is why a sender with correct BIMI can still benefit from a Google profile image. BIMI covers the authenticated logo path. The profile image covers Gmail identity surfaces where BIMI is not shown. A useful mental model is to treat them as parallel systems with different jobs, not competing versions of the same logo.
If the brand is asking because they saw a moving sender logo, the safest explanation is that they saw an animated Google profile image. The ANIBIMI example is a useful illustration of that distinction: the animation is a profile-image workaround, not an animated BIMI standard.
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. For a large sender, this is a controlled Gmail UI test, not a BIMI migration.
- Keep BIMI: Do not edit the working BIMI SVG or certificate file to add movement.
- Match sender: Set the profile image on the exact Google identity that matches the visible From address.
- Test Gmail: Send real messages to Gmail and Workspace recipients, then check message view and contact surfaces.
- Monitor DMARC: Keep authentication stable so the static BIMI logo remains available when Gmail chooses it.
DMARC policy shape for BIMI readinessdns
_dmarc.example.com TXT "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"
The DMARC policy is not optional for BIMI. Gmail requires p=quarantine or p=reject for the BIMI domain. Google's BIMI setup docs still describe full enforcement with pct=100, while RFC 9989 removed pct from the DMARC tag registry. Treat the durable requirement as enforced DMARC on the BIMI domain, and do not rely on monitoring-only DMARC or testing mode when you want BIMI display.
BIMI readiness by DMARC policy
A simple way to judge whether the domain is ready for Gmail BIMI display.
Not ready
p=none
Monitoring only, useful for discovery but not enough for BIMI.
In progress
testing mode
Discovery or staged enforcement, useful for cleanup but not enough for BIMI display.
Ready
quarantine or reject
Enforcement applies to the BIMI domain.
For implementation checks, start with the authentication base. A DMARC checker will catch the policy mistakes that make BIMI fail before anyone gets into logo rendering debates.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
After the DMARC record passes, send test mail from the real production path. Do not test with a different mailbox, a different From domain, or a personal Gmail alias. The profile image behavior depends on the exact sender identity, and BIMI depends on the exact authenticated domain.
There is no universal sending-volume threshold for BIMI itself, but low-volume senders should test display with real Gmail and Workspace recipients after the technical checks pass. If Gmail has little history for the domain, sender reputation and account context can delay visible display even when DNS is correct.
Where Suped fits
Suped's product keeps the authentication side measurable while the brand team experiments with Gmail-only profile imagery. Suped brings DMARC, SPF, DKIM, blocklist (blacklist) monitoring, hosted DMARC, hosted SPF, SPF flattening, hosted MTA-STS, alerts, and issue fix steps into one place.
For teams working toward BIMI readiness, Suped turns DMARC monitoring into a practical workflow: identify unauthenticated sources, move policy safely, keep SPF and DKIM healthy, then confirm that BIMI prerequisites stay in place after every sender change.
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.
A practical split
- Suped: Monitor authentication, source health, policy staging, and BIMI readiness.
- Google profile: Test Gmail-only animated avatar behavior for the exact sender address.
- BIMI: Keep the verified brand logo static and standards-compliant.
Decision path
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.
DMARC readiness flow for static BIMI, VMC or CMC, and Google profile image testing.
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 as is
Use this path when BIMI already works in Gmail and other target inboxes.
- Risk: Changing the SVG can break a working logo.
- Result: Stable authenticated brand display.
Add profile image
Use this path when the brand specifically wants Gmail-only avatar coverage.
- Risk: Animation behavior changes without DNS or BIMI notice.
- Result: Extra Gmail visibility in surfaces BIMI does not cover.
Views from the trenches
Best practices
Keep BIMI static and let a Google profile image handle any Gmail-only animation tests.
Test with real Gmail inboxes because profile images and BIMI appear in different views.
Scope BIMI by subdomain when employee photos and marketing logos need different behavior.
Common pitfalls
Treating an animated Google avatar as proof that animated BIMI exists causes bad fixes.
Using p=none for DMARC blocks Gmail BIMI display even when the SVG itself validates.
Changing a working BIMI SVG for movement breaks the standard and can remove the logo.
Expert tips
Set the profile image for the exact From address if Gmail profile display matters.
Use the static BIMI logo as the durable path, then treat animation as a Gmail test.
Watch provider-specific volume and reputation before calling valid BIMI broken.
Expert from Email Geeks says BIMI logos are static, and animated examples in Gmail usually come from a Google Account profile image rather than BIMI.
2022-06-06 - Email Geeks
Marketer from Email Geeks says large senders can test a Google profile image, but they should keep an existing VMC-backed BIMI setup in place.
2022-06-06 - Email Geeks
Keep the roles separate
BIMI is the standards-based logo path, and it is static. Google profile images are account-based Gmail visuals, and they can create the appearance of an animated sender logo in some Google views. When both exist, Gmail can prefer BIMI in the message sender slot while still using the profile image in account and contact surfaces.
For a brand that already has BIMI with a VMC or CMC, leave BIMI alone. Add a Google profile image only if the team accepts that it is a Gmail-specific visual layer. If the animation stops appearing, the static BIMI logo is still the correct authenticated fallback.
