How to Add a Sender Image or Logo to Your Emails

The small logo next to your email in an inbox is not controlled by your email template. It is not an image block, a header setting, or a CSS trick. Sender images are controlled by the recipient's inbox provider and the signals it trusts for your sending domain or From address.
That is why the same campaign can show a brand logo in one inbox, a profile photo in another, initials in a third, and a generic placeholder somewhere else.
If you want your sender image to appear more consistently, work in this order:
- Authenticate the sending domain.
- Publish a brand-level logo signal with BIMI where it is supported.
- Add Apple Branded Mail if Apple Mail visibility matters.
- Set mailbox profile images for specific From addresses.
- Add Gravatar only as a secondary signal for clients that use it.
What controls the sender image
Inbox avatars come from several different systems. The mailbox provider decides which one wins.
| Inbox or client | Common sender image source | What to set up |
|---|---|---|
| Gmail | BIMI, Google profile image, or account signal | DMARC enforcement plus BIMI, or a Google Workspace profile image for the From address |
| Apple Mail | Apple Branded Mail or BIMI | Apple Business Connect Branded Mail and strong email authentication |
| Yahoo Mail | BIMI | DMARC enforcement, BIMI SVG, and provider-compatible certificate or self-asserted BIMI support |
| Fastmail | BIMI | DMARC enforcement and BIMI DNS record |
| Outlook / Hotmail | Microsoft profile sources | Microsoft account or tenant profile image where available |
| Thunderbird and some third-party clients | Gravatar or local contact image | Gravatar on the exact sender address |
| Any client with no match | Initials or generic icon | No reliable sender-controlled fallback |
The important part: your email platform can help you authenticate the domain and send aligned mail, but it cannot force every inbox to show a logo.
Start with domain authentication
Sender images are built on trust. Before you work on logos, confirm that your sending domain has SPF, DKIM, and DMARC in place.
Use these guides if the domain is not ready yet:
For BIMI and Apple Branded Mail, DMARC cannot stay in monitoring mode forever. The domain normally needs an enforcement policy:
_dmarc.example.com TXT "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@example.com"Do not jump straight from no DMARC to p=reject if you have not inventoried every system that sends as your domain. Start with reporting, fix alignment, then move to enforcement when legitimate mail is passing.
Option 1: Set up BIMI for domain-level logos
BIMI stands for Brand Indicators for Message Identification. It lets participating mailbox providers discover the logo associated with authenticated mail from your domain.
This is the most important path if you want a sender image that follows the domain instead of one mailbox account.
BIMI requirements
You need:
- SPF or DKIM passing with proper domain alignment.
- DMARC at enforcement, usually
p=quarantineorp=reject, withpct=100. - A square brand logo prepared as SVG Tiny PS.
- A stable HTTPS URL for the logo or certificate file.
- A BIMI TXT record at
default._bimi.yourdomain.com. - A Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) for mailbox providers that require one.
Google's BIMI setup guide says Gmail requires a VMC or CMC and requires DMARC enforcement. The BIMI Group implementation guide also calls out aligned SPF, DKIM, and DMARC, an SVG Tiny PS logo, and a BIMI DNS record.
BIMI DNS example
A BIMI record with a hosted certificate can look like this:
default._bimi.example.com TXT "v=BIMI1; l=; a=https://assets.example.com/bimi/certificate.pem"A self-asserted BIMI record points directly to the SVG:
default._bimi.example.com TXT "v=BIMI1; l=https://assets.example.com/bimi/logo.svg"Self-asserted BIMI has limited support. It can be useful as a first step, but it is not enough for Gmail and other clients that require a certificate.
Logo preparation
Do not upload your normal website logo and assume it is BIMI-ready. BIMI SVG is stricter than a regular SVG export.
Prepare the logo this way:
- Use a square canvas.
- Center the mark with enough padding for circular crops.
- Use a solid background if the mark depends on contrast.
- Remove scripts, animation, external links, embedded raster images, and unnecessary metadata.
- Keep the file small.
- Validate it with a BIMI SVG validator before publishing.
If the logo fails validation, the DNS record can be correct and still not produce an inbox logo.
Option 2: Use Apple Branded Mail for Apple clients
Apple Branded Mail is separate from BIMI. It is managed in Apple Business Connect and applies to Apple Mail and iCloud Mail experiences where Apple supports it.
Apple's Branded Mail guide says businesses can add a brand logo and name to business emails, but the organization and brand need Apple approval. Apple also notes that customer-visible support depends on client and language, and that messages need DKIM authentication; SPF-only authentication is not enough.
Use this path when a meaningful share of your audience reads email in Apple Mail.
Typical setup:
- Verify your organization in Apple Business Connect.
- Add or claim the brand.
- Upload the logo and brand details.
- Add the sending domain, subdomain, or specific email address.
- Complete Apple's DNS verification before the verification window expires.
- Send test messages to Apple Mail and iCloud Mail accounts.
BIMI and Apple Branded Mail are not substitutes for authentication. They sit on top of it.
Option 3: Add a Gmail profile image for the From address
If BIMI is not ready yet, a Google Workspace profile image can help in Gmail when the From address exists as a Google-managed user, group, or alias and Gmail chooses that profile signal.
This is a tactical fallback, not a universal brand logo system.
Use it for:
founder@example.comsupport@example.comhello@example.com- a sales or customer success alias
Set the profile photo in Google Workspace or the relevant Google account, then send real tests. Gmail may take time to update cached images, and behavior can vary based on the address, recipient context, and whether stronger brand signals exist.
Do not rely on this for Yahoo, Apple Mail, Outlook, or other mailbox providers.
Option 4: Add Gravatar for clients that support it
Gravatar is worth setting up because it is easy and low-risk, but it is not a replacement for BIMI.
The Gravatar support docs are direct about the limitation: many popular email services, including Gmail, Outlook, and Apple Mail, do not use Gravatar for inbox sender images.
Use Gravatar for third-party clients that look up avatars by sender address.
Steps:
- Create or sign in to a Gravatar account.
- Add the exact From address you use in campaigns.
- Verify the address.
- Upload the brand image or sender photo.
- Send test messages to clients known to support Gravatar.
If you send from multiple addresses, each address needs to be covered.
Which setup should you choose?
| Goal | Best path |
|---|---|
| Show a brand logo in major inboxes over time | BIMI with DMARC enforcement and a VMC or CMC |
| Improve Apple Mail visibility | Apple Branded Mail through Apple Business Connect |
| Make a specific Gmail sender look better quickly | Google Workspace profile image |
| Cover some third-party desktop clients | Gravatar |
| Fix deliverability | SPF, DKIM, DMARC, list quality, and sending reputation first |
For most teams, the right sequence is:
- Fix SPF, DKIM, and DMARC alignment.
- Move DMARC from monitoring to enforcement safely.
- Prepare a BIMI-compliant logo.
- Decide whether a VMC or CMC is worth the cost.
- Add Apple Branded Mail if Apple Mail is important for your audience.
- Add profile images and Gravatar for address-level coverage.
Troubleshooting missing sender images
When the logo does not appear, check the system that should have supplied it.
| Symptom | Likely cause | First check |
|---|---|---|
| Gmail does not show the logo | DMARC is not enforced, certificate is missing, or SVG is invalid | Check DMARC p, pct, BIMI record, and certificate URL |
| Apple Mail does not show the logo | Apple approval, domain verification, DKIM, or client support is missing | Check Apple Business Connect status and send a fresh DKIM-signed test |
| Yahoo or Fastmail does not show BIMI | DNS, logo hosting, or provider-specific BIMI support issue | Validate the BIMI record and hosted SVG |
| Thunderbird does not show Gravatar | The sender address is not verified in Gravatar or the client is not using it | Confirm the exact From address |
| Only initials show | No provider-recognized logo signal exists | Decide which setup path applies to that inbox |
Also check caching. Inbox providers often cache profile images, logos, and DNS results. A correct setup may take hours or days to appear everywhere.
Common mistakes
- Adding a logo to the email header and expecting inbox clients to use it.
- Publishing BIMI while DMARC is still
p=none. - Using
pct=10or another partial DMARC rollout for a BIMI domain. - Sending from a different domain than the domain with the BIMI record.
- Uploading a regular SVG, PNG, or JPG instead of a BIMI-compatible SVG Tiny PS file.
- Forgetting subdomains.
mail.example.comandexample.comcan behave differently. - Assuming Gravatar works in Gmail, Outlook, or Apple Mail.
- Testing only one inbox and treating that result as universal.
How Sequenzy should use this
In Sequenzy, sender images should be framed as part of domain readiness, not email design. The platform should guide teams through authentication first, then explain the logo paths that depend on the sender domain and target inbox.
The product should never imply that a campaign setting can force a sender avatar across all clients. A better workflow is:
- Confirm the campaign's From domain and From address.
- Show SPF, DKIM, and DMARC status for the sending domain.
- Warn when DMARC is still monitoring-only.
- Explain whether BIMI, Apple Branded Mail, Google profile image, or Gravatar is the relevant next step.
- Encourage real inbox tests across Gmail, Apple Mail, Yahoo, Outlook, and one third-party client.
Sender images can improve recognition, but they are the result of trust signals outside the message body. Treat them like deliverability infrastructure, not decoration.