Skip to Content
SendlySendly
Guides

Sender logo

Configure a sender logo through the UI, API or MCP, and check inbox provider requirements

Most inboxes show a grey initial next to a message from a sender they have no picture for. A mailbox that supports BIMI (Brand Indicators for Message Identification) shows your logo instead, and a recognisable face in a list of messages is one of the few things that changes whether yours gets opened.

Every sending identity in Sendly has a logo already. Until you upload one, it is your domain's initial on a coloured square. A provider may display it once its BIMI requirements are met.

What it takes

Start with these three prerequisites; some providers also require certification (see below):

  1. The file. Your upload, or the default initial. Sendly hosts it at a URL that belongs to the identity and never changes.
  2. A TXT record in your DNS, naming that URL. You publish it once.
  3. An enforced DMARC policy: p=quarantine or p=reject, applied to all of your mail (no pct below 100). A mailbox will not put a logo on mail from a domain whose owner has not said what to do with forgeries.

Settings → Domains → Sender logo → Set up shows the file, gives you the record to copy, and reads the other two back from public DNS, in words that say what to change.

The logo is served only once the identity verifies, and not at all while the project is disabled. An upload alone proves only that someone typed the domain into a form; serving a logo before the domain proves it is yours would let anyone put a brand's face on mail that is not theirs.

The record

One TXT record per identity
Name:  default._bimi.news.example.com
Value: v=BIMI1; l=https://app.sendly.now/bimi/<identity id>.svg;

The panel shows the exact name and value for each identity. Each identity gets its own record, at its own host, so mail.example.com and news.example.com can carry different logos. If you publish a record at the root (default._bimi.example.com) instead, every host under it that has no record of its own falls back to that one.

Replacing or removing the logo later changes what the URL serves. It does not change the record, so there is nothing to republish.

Upload an SVG from the panel, or over the API. Sendly rebuilds it into SVG Tiny PS, the restricted profile mailboxes require, and that rebuilt file is what the URL serves. The rebuild drops what design tools add for their own use and keeps the shapes.

The file has to:

  • be square: the mailboxes crop it to a circle, so keep the mark inside the middle;
  • draw with shapes. <text> renders only in fonts the reader happens to have, so it is refused: convert text to outlines before exporting;
  • reference nothing outside itself: no embedded images, no links, no external fonts;
  • come to 32 KB or less after the rebuild.

A file that does not fit is refused with the reason, and the logo you had stays in place.

Upload a logo
curl -X PUT https://api.sendly.now/api/v1/domains/$DOMAIN_ID/logo \
  -H "Authorization: Bearer $SENDLY_API_KEY" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile svg logo.svg '{svg: $svg}')"

The answer carries the file as served, the record to publish (bimi_record), and a fresh DNS reading (readiness). GET the same path to read them again, and DELETE it to go back to the default. Uploading and removing need the domains:write scope; reading needs domains:read.

Through MCP

Use get_domain_logo with the sending domain's ID to read its logo, BIMI record and live DNS checks (domains:read). Use upload_domain_logo with domainId and square vector svg source to replace it (domains:write). The upload uses the same validation as the UI and API. It affects the domain and its mailboxes; it does not change DNS or obtain a certificate.

A PNG logo can be used inside a rich email through document.brand.logoUrl. An inbox sender logo needs a suitable vector SVG instead; wrapping a PNG in an SVG does not qualify.

Which inboxes show it

Providers decide whether to display a sender logo. Published BIMI and enforced DMARC are prerequisites, not a guarantee that every recipient sees it. Yahoo and AOL also consider sender reputation and engagement; see their BIMI requirements.

Gmail additionally requires a Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) issued by a certificate authority, with its associated files published as required by Google's setup guide. Apple Mail does too: its mail provider must have verified a BIMI Evidence Document (for example a VMC) before Apple Mail shows the logo, per Apple's BIMI requirements. Sendly does not issue or validate these certificates. Its DNS ready badge reports only the logo's availability and DNS checks. Other inbox providers have their own display requirements.

Mailboxes cache what they fetch. A new upload can take a day or more to appear in an inbox that has already shown your old one.

Check what is still missing

GET /api/v1/domains/{id}/logo/readiness (domains:read) answers, step by step and inbox by inbox, what is in place and what is not:

Stepmet when
dmarc_enforcedDMARC is p=quarantine or p=reject at pct=100, on the sending host and its registered domain
bimi_recorda default._bimi TXT record exists and its l= is an https URL
logo_filethe file at l= is SVG Tiny PS (Sendly checks the file it serves, and fetches a file you host)
mark_certificatethe record's a= URL answers with a PEM file; the certificate chain itself is not validated
gmail_profile_photonever: a Google account photo on the exact From address is set by the sender and cannot be seen
apple_branded_mailnever: it is registered with Apple (Apple Business), not published in DNS, and cannot be seen

Each step carries a plain-English reason when it is not met, the inboxes it unlocks, and evidence (what was read). A step is unknown when a lookup failed or it is self-attested with the provider: it is never a pass and never a failure, so check again in a minute. providers has one checklist per inbox (Gmail, Yahoo, Apple Mail, Fastmail) saying which steps that inbox required, treats as optional, or offers as an alternative route.

The reading comes from public DNS and from the hosts your record names, and ends after 5 seconds whatever they are doing (a step it had not finished is unknown), so it is held for a minute: checked_at says when it was taken. ready means every required step is met, which is still not a promise: providers decide whether to display a logo.

The name beside it

The logo sits next to the sender name, which you set per identity as well, with defaultFromName. See the sender name recipients see. The default monogram is titled with that name too, or with the project name when the identity has none.

On this page