How to Add a Sender Image or Logo to Your Emails
The small logo beside a sender is not controlled by the HTML email. It is a mailbox-provider display decision based on sender identity, authentication, reputation, account profile data, or BIMI support.
The main paths
| Path | Who controls it | What it can do |
|---|---|---|
| Provider profile image | Mailbox account or workspace admin | May display for recipients using that provider |
| Gravatar or avatar service | Sender address and provider integration | Coverage varies by mailbox |
| BIMI | Sending domain and participating mailbox provider | Publishes a brand logo for authenticated mail |
| Apple branded display | Apple Mail and provider criteria | Depends on BIMI and Apple’s support rules |
Do not promise a logo in every inbox. Each provider can apply its own eligibility and reputation checks.
BIMI prerequisites
The BIMI Group implementation guide requires aligned SPF, DKIM, and DMARC, with DMARC at enforcement for supported implementations. Google’s BIMI setup guide says Gmail requires third-party certification through a Verified Mark Certificate or Common Mark Certificate.
Typical preparation:
- Authenticate every sending stream.
- Move DMARC from monitoring to an enforcement policy after reviewing reports.
- Create a compliant SVG Tiny PS logo.
- Host the logo and, where required, the certificate chain over HTTPS.
- Publish the BIMI TXT record.
- Test with supported mailbox providers.
Example BIMI record
The exact record depends on your certificate and logo host:
Type: TXT
Name: default._bimi
Value: v=BIMI1; l=https://brand.example.com/logo.svg; a=https://brand.example.com/certificate.pemThe a value is optional in the BIMI record syntax but required by providers that require a VMC or CMC. Replace all example URLs with assets you control.
Logo requirements
For Gmail, the logo must be SVG and meet the provider’s requirements; Google recommends a square, centered image, absolute dimensions, a solid background, and a file size of 32 KB or less. Follow the current Google requirements and validate the SVG with a BIMI-aware tool.
Avoid external links, scripts, animation, and unsupported SVG features. Keep an original raster logo for other channels; do not assume that a normal website SVG is valid BIMI artwork.
DNS and message checks
Query the record:
dig +short TXT default._bimi.example.com
dig +short TXT _dmarc.example.comThen inspect a real message for aligned SPF, DKIM, and DMARC. A correct BIMI record cannot compensate for a failed authentication result or a From domain that does not align.
What does not work
- Adding a logo image to the email header.
- Putting a base64 avatar in the HTML.
- Changing the display name to include the word “image.”
- Publishing BIMI while DMARC remains p=none.
- Assuming the logo will appear immediately after DNS propagation.
- Treating a missing logo as proof that authentication failed.
A sender image is a trust and recognition layer on top of authentication. Fix delivery and identity first, then treat logo display as a provider-specific enhancement.
QA checklist
- Logo ownership and certificate requirements are documented.
- SVG is valid, hosted over HTTPS, and reachable.
- BIMI, DMARC, SPF, and DKIM records resolve publicly.
- From domain and authenticated domains align.
- Display is tested at supported providers without assuming universal coverage.
- Brand team knows the logo may not appear for every recipient.
Profile image, BIMI, and message logo are different things
These paths are often mixed together in implementation tickets:
| Request | Actual owner | Implementation question |
|---|---|---|
| “Put our logo in the email” | Email template | Is the image useful when images are blocked and does it have alt text? |
| “Show our logo beside the sender in Gmail” | Gmail and sender identity | Is the sending account or domain eligible for Gmail’s display treatment? |
| “Make the brand appear in supported inboxes” | Domain and mailbox provider | Is authentication aligned and is BIMI supported for this stream? |
| “Make it appear in Apple Mail” | Apple and participating providers | Which Apple-specific eligibility requirements apply now? |
An image inside the message can improve recognition, but it does not change the sender avatar. Treat the two as separate deliverables in the brief.
Validate the asset before publishing DNS
Use a dedicated brand asset rather than exporting a website logo and hoping it passes. Record the source file, owner, revision, certificate status, and expiry date. The SVG should be a simple, square, centered mark with no scripts, external references, animation, or unsupported filters. Keep its contrast high enough to survive circular or masked provider UI.
The hosting path also matters. Confirm that the logo URL resolves over HTTPS without authentication, redirects, or bot protection that blocks mailbox-provider fetchers. Check the certificate URL separately when your implementation requires one, and create a renewal owner before the certificate is close to expiry.
Troubleshoot in layers
When the logo does not appear, check the layers in this order:
- The sending message has a stable From domain.
- SPF and DKIM pass and align with that domain.
- DMARC passes with the intended enforcement policy.
- The BIMI TXT record is published at the correct selector and is visible from public DNS resolvers.
- The SVG and certificate URLs return the expected content.
- The recipient provider supports the path and has had time to refresh its cache.
- The domain and message reputation meet the provider’s display criteria.
This order prevents teams from repeatedly editing the logo when the real problem is alignment or provider support. A DNS checker can confirm publication, but a received-message header confirms what actually happened for a specific send.
Ownership and measurement
Deliverability should own authentication and certificate renewal. Brand should own the artwork and its visual review. Engineering should own hosting, DNS-as-code where available, and monitoring. Marketing should document which From domains and streams are covered.
Do not use “logo displayed” as a universal KPI; most providers do not expose a reliable cross-inbox metric. Track authentication pass rates, BIMI/DNS health, complaint rate, and brand-recognition feedback from representative mailbox tests. The logo is valuable when it reinforces a trustworthy identity, not when it becomes a substitute for one.