Why Apple Branded Email logos don't show in native Mail apps
Updated on 21 Oct 2026: We clarified Apple's logo display checks, sender-icon settings, and Branded Mail requirements under the current DMARC standard.
Apple Branded Mail logos fail to appear when one part of Apple's display chain is ineligible or incomplete. The common causes are hidden sender icons, an unsupported client, an unsupported iPhone default language, an unapproved brand or sender identity, a domain mismatch, or a message that does not meet Apple's DKIM and DMARC requirements.
A sender logo beside the From name is different from a logo embedded in an email signature or HTML body. For an image missing inside the message, check its image URL, HTTPS certificate, and remote-content loading. Those checks address the message content rather than Apple Business sender branding.
A logo that appears in iCloud Mail on the web but not in Mail on an iPhone is a useful comparison, but it does not identify whether the image came from Branded Mail or BIMI. The iPhone still needs an eligible language setting and a fresh authenticated message. A missing logo on iPad or Mac does not prove the Branded Mail setup failed because Apple currently lists iPhone and iCloud Mail on the web as its Branded Mail display paths.
Debug the issue in a strict order: confirm that the client and language are supported and sender icons are visible, confirm the exact From domain, confirm DKIM and DMARC on a newly delivered message, then check the approval status and elapsed time. Testing a fresh message with Suped's email tester provides message-level evidence instead of relying on one inbox display.
Fast answer
If Apple Business says the sender is approved and iCloud.com shows the logo, check the iPhone's default language and Show Contact Photos setting, the exact sender coverage, and whether the delivered message has a valid DKIM pass and DMARC pass. Do not use iPad or Mac results as proof that Apple Branded Mail has failed.
What has to happen before the logo appears
Apple Branded Mail is Apple's branded sender path in Apple Business, formerly Apple Business Connect. It is separate from BIMI. Apple's BIMI support page says Apple Mail supports BIMI in iOS 16, iPadOS 16, macOS Ventura 13 or later, and iCloud.com. Those BIMI client versions do not define Apple Branded Mail availability. Apple currently documents Branded Mail for iPhone with an eligible default language and for iCloud Mail on the web.
Separate the problem into layers to avoid guessing. An approved logo can still fail at the client or language layer. An eligible iPhone can still hide the logo when the message comes from an uncovered sender identity. A covered domain can still fail when the message lacks DKIM or does not pass DMARC.
If the logo upload is still unapproved, check Apple's brand logo requirements: a square image with dimensions between 1024 x 1024 and 4864 x 4864 pixels, in HEIF, JPEG, PNG, or SVG format. A logo already approved for the correct brand does not need a new upload solely because one client is missing it.
Apple Branded Mail logo checks: brand verification, domain matching, DMARC, and client eligibility.
|
|
|
|---|---|---|
Brand | Approved | Eligible |
Sender | From match | Covered |
Authentication | DKIM and DMARC pass | Message checks pass |
Client | iPhone language and sender icons | Eligible display settings |
Timing | Approval status and elapsed time | Ready to retest |
Use this table to isolate which layer is failing.
Why iCloud web can show the logo when iPhone Mail does not
iCloud Mail in a browser and Mail on iPhone are different display paths. An image in the browser alone does not establish that Branded Mail supplied it, because iCloud Mail also supports BIMI. It also does not prove that the iPhone is eligible or that the same sender passes authentication on every sending stream.
iCloud Mail on the web
- Provides a webmail comparison for the same sender, but a visible logo does not identify its source.
- Provides a useful control when testing the same fresh message sent to an eligible iPhone.
- Does not prove iPhone language eligibility, sender coverage, or a DKIM pass on another message.
Mail on iPhone
- Requires one of Apple's supported default languages for Branded Mail.
- Should be tested with a new message sent after the brand and sender identity are approved.
- Can show a contact photo instead of the branded logo, so test with an address that is not saved in Contacts.
Check Branded Mail review separately from the publication of brand information. Apple lists up to seven business days for Branded Mail review and up to five working days for brand names and logos to appear in its services. If review is overdue, or an approved logo remains missing after the appearance window, collect the message headers, iPhone language, sender-icon setting, screenshot, and timestamp before requesting support.
Check Apple Mail client support
A verified sender cannot force a Branded Mail logo into an unsupported client. Start by recording the exact client, device, OS version, mailbox account type, and whether the test was done in the inbox list or an opened message. For Apple Branded Mail, use iCloud Mail on the web and an eligible iPhone as the primary controls.
Illustration of Apple Business Connect Branded Mail setup with domain verification and a logo preview.
- Install the latest iOS version supported by the test iPhone, then send a new message after Apple approves the setup.
- Use iCloud Mail on the web as the second Branded Mail control for the same sender.
- Do not use iPad or Mac as Branded Mail controls because Apple does not list them for this display path.
- Test in a mailbox where the sender is not saved in Contacts, so a local contact photo does not affect the comparison.
Check whether Mail is hiding sender icons
The inbox can hide sender photos and logos even when brand verification and authentication pass. Check whether icons are missing for every sender or only for your brand.
- In Mail on iPhone, open an inbox, tap More (...), and select Show Contact Photos.
- Compare the icon in the inbox list with the sender area inside a newly opened message. Record which view is missing the logo.
- Test in a mailbox where the sender is not saved in Contacts, so a local contact photo does not affect the comparison.
- If icons appear for other senders, continue with your brand's sender coverage and message authentication checks.
Keep the sender-icon setting in the test record so two iPhones are compared under the same display conditions.
Check the iPhone's default language
Apple currently says customers can see Branded Mail on iPhone when the device's default language is English, Portuguese, French, Italian, German, Spanish, or Simplified Chinese. An iPhone outside that language list is not an eligible control, even when its iOS version is current and iCloud Mail on the web shows the logo.
- On iPhone, record the iOS version, default language, mailbox account, and whether the sender is saved in Contacts.
- Send a fresh message to an iCloud mailbox, then open it on iCloud.com to compare Apple's web display path.
- On iPad or Mac, treat a logo as possible BIMI or contact data rather than proof of Branded Mail support.
- After changing the iPhone language for a diagnostic test, send another message instead of judging an old message.
Check the exact From address and domain
Next, check whether the visible From address is covered by the domain, subdomain, or specific email address registered in Apple Business. Verifying a parent domain covers that domain and its subdomains. Register a subdomain separately only when it needs different branding, or register a specific address when branding should apply only to that sender.
Address coverage does not fix authentication
Adding every From address to Apple Business does not fix missing DKIM or a DMARC failure. It helps only when the sender is outside the current brand coverage or needs sender-specific branding.
Examples of sender identities to test separatelytext
news@example.com billing@example.com alerts@mail.example.com receipts@shop.example.com
Apple requires a commercial email domain with an MX, A, or AAAA record. Consumer domains are not eligible, and each brand can have no more than 100 combined domains, subdomains, and email addresses. If the display name is wrong rather than the logo being absent, that is a separate sender identity problem. The page on sender name issues covers that symptom.
If a domain is pending verification, complete Apple's DNS ownership check within 14 calendar days or restart the process. Allow for the verification TXT record's DNS propagation before checking again.
- Copy the exact visible From address from the delivered message, not the campaign setup screen.
- Check whether its parent domain, subdomain, or specific address is approved for the intended brand.
- Test transactional, marketing, support, and account mail separately because each stream can sign differently.
- Record the result in iCloud Mail on the web and on an eligible iPhone for that exact sender.
Check DKIM and DMARC after Apple verification
Apple Business verification is not a substitute for message authentication. Apple requires every Branded Mail message to have DKIM authentication, and SPF-only authentication is not supported. The applicable DMARC policy must be quarantine or reject. For a registered subdomain, check its own DMARC record first; if it inherits a parent-domain policy, check sp when present, otherwise the inherited p policy. An explicit sp tag is not always necessary.
RFC 9989 marks pct as historic, so pct is no longer a general DMARC enforcement control. Apple's Branded Mail documentation still explicitly asks for pct=100. The example below retains that tag for compatibility with Apple's published verification checks.
A message can pass DMARC through SPF and still be ineligible for Apple Branded Mail when DKIM is absent or fails. Check the receiving provider's Authentication-Results header for the exact message that missed the logo, including dkim=pass and dmarc=pass. Suped's domain health checker validates the published authentication records. Suped's DMARC monitoring shows which sending sources pass over time, and the DKIM checker can confirm that the selector and public key resolve before another Apple Mail test.
DMARC example for Apple's published Branded Mail checksdns
_dmarc.example.com. 3600 IN TXT ( "v=DMARC1; p=quarantine; pct=100; " "rua=mailto:dmarc@example.com" )
For DMARC, a passing SPF or DKIM identity must match the visible From domain under the record's relaxed or strict matching rules. A DKIM pass for an unrelated signing domain does not, by itself, make DMARC pass. The sample below shows matching identities; the receiving provider's results are the evidence to check.
Illustrative authentication results for a direct messagetext
From: Example News <news@example.com> Authentication-Results: receiving.example; dkim=pass header.d=example.com header.s=selector1; spf=pass smtp.mailfrom=bounce.example.com; dmarc=pass header.from=example.com
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
A valid DNS record does not prove that every sending service complies. One service can use a stale DKIM selector, sign with an unexpected domain, or omit the signature. Check the delivered message together with aggregate DMARC reports. DNS shows the intended policy, while the reports show how real sources authenticated.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
Suped's DMARC reporting and email authentication platform helps identify the affected sending source and review its authentication results. After correcting that source, test a fresh message in the receiving mailbox to confirm DKIM and DMARC pass before escalating the logo issue to Apple.
A practical test plan that removes guesswork
Send one fresh message per sender identity, record the two eligible client results, and keep the headers. A small test matrix shows whether the problem follows the sender, authentication result, iPhone language, sender-icon setting, account, or approval timing.
When to wait and when to escalate
Check review status and brand publication separately after confirming message authentication.
Review
Up to 7 business days
Wait for Apple to review the Branded Mail setup.
Appearance
Up to 5 working days
Allow brand names and logos to appear in Apple services.
Support
Overdue review or publication
Request support when review is overdue or approved branding remains absent after display checks.
- Send a new message after the brand and sender identity show as approved.
- Save the Authentication-Results header and confirm both DKIM and DMARC pass.
- Check iCloud Mail on the web and an iPhone using a supported default language and visible sender icons as separate rows.
- Change only one variable at a time, such as the sender, mailbox, iPhone language, or sending source.
- If review is overdue or approved branding remains absent after the appearance window, request support with the headers, screenshot, timestamp, and device details.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
If the email tester shows missing DKIM or a DMARC domain mismatch, fix that before retesting Apple Mail. If authentication passes and the logo remains absent on an eligible iPhone after approval and the appearance window, request Apple Business support with the saved evidence, including the iCloud web comparison.
How Apple Branded Mail differs from BIMI
Apple Branded Mail and BIMI both place logos near email senders, but they use different setup and display paths. Apple Branded Mail is configured in Apple Business. BIMI (Brand Indicators for Message Identification) is a DNS-based standard that mailbox providers can use to discover a logo and its evidence document. Apple Mail supports BIMI, but Apple Business does not create a BIMI record and BIMI does not fix a Branded Mail configuration problem.
Apple Branded Mail
- Managed in Apple Business with organization, brand, logo, and sender verification.
- Displayed on iPhone with a supported default language and in iCloud Mail on the web.
- Requires DKIM and DMARC enforcement; Apple's published checks also request pct=100.
BIMI
- Published in DNS and tied to DMARC enforcement plus an accepted logo evidence document.
- Displayed by supporting mailbox providers and qualifying Apple Mail versions.
- Can fail because of DNS, authentication, evidence-document, or mailbox-provider requirements.
For BIMI, the receiving mailbox provider must validate the message and logo evidence and add the required headers before Apple Mail can display the logo. A correct BIMI DNS record alone does not establish support for that mailbox.
Example BIMI record for contextdns
default._bimi.example.com. 3600 IN TXT ( "v=BIMI1; l=https://assets.example.com/logo.svg; " "a=https://assets.example.com/vmc.pem" )
If the issue is Apple Branded Mail, do not assume a BIMI change will fix it. Keep BIMI healthy for qualifying clients, but debug Apple Business and the two documented Branded Mail display paths separately. A logo on iPad or Mac can come from BIMI or contact data, so it does not validate the Apple Business configuration.
The fixes that address each failure
No single DNS change forces Apple Mail to show a logo. The fix depends on the failed layer, and the order below avoids changing brand settings that are already correct.
Best practical workflow
- Confirm the organization, brand, logo, domain, and any sender-specific entries are approved.
- Confirm the delivered message has a valid DKIM signature and passes DMARC under an enforced policy.
- Retest with a fresh message in iCloud Mail on the web and on an eligible iPhone with sender icons enabled.
- If review is overdue or approved branding remains absent after the appearance window, request support with the saved evidence.
If authentication is clean and the eligible Apple display paths disagree, further SPF or DKIM changes will not make the logo publish faster. Keep DNS stable and request Apple Business support with the exact failing message. Changing several variables at once makes the result harder to diagnose.
