# Does Transactional email support embedded image?

**URL:** <https://community.brevo.com/t/does-transactional-email-support-embedded-image/6665>\
**Category:** Transactional\
**Created:** [Septembre 26, 2025, 1:51 UTC](https://community.brevo.com/t/does-transactional-email-support-embedded-image/6665 "2025-09-26T01:51:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmqu](https://avatars.discourse-cdn.com/v4/letter/j/43a26b/32.png) [@jmqu](https://community.brevo.com/u/jmqu)\
**Post date:** [Septembre 26, 2025, 1:51 UTC](https://community.brevo.com/t/does-transactional-email-support-embedded-image/6665/1 "2025-09-26T01:51:47Z")

</div>

Hi there,

I have found that campaigns support embedded image with an advanced setting. For transactional, I have tested that with default configuration, it seems the image with CID referencing SRC doesn’t work. I found the Content ID header is missing for the attachments. Is there any way to enable the embedded image with CID referencing? Anyone encountered same issue?

---

<div class="post-metadata">

**Author:** ![adam](https://dub1.discourse-cdn.com/flex013/user_avatar/community.brevo.com/adam/32/1337_2.png) [@adam](https://community.brevo.com/u/adam)\
**Post date:** [Octobre 4, 2025, 2:53 UTC](https://community.brevo.com/t/does-transactional-email-support-embedded-image/6665/2 "2025-10-04T14:53:15Z")

</div>

Hi there 🙂

Right now, unfortunately, embedding images (CID header) is not supported for transactional emails either via API or SMTP. This is mostly due to deliverability issues as «&nbsp;heavy&nbsp;» emails tend to be filtered out by recipient ISPs, so it is not recommended, I’m afraid.

I would recommend hosting your images externally (e.g. on your CDN or Brevo’s content library) and referencing them directly in your HTML:

```auto
<img src="https://cdn.example.com/logo.png">

```

Feel free to come back to me with any questions!

---

<div class="post-metadata">

**Author:** ![jmqu](https://avatars.discourse-cdn.com/v4/letter/j/43a26b/32.png) [@jmqu](https://community.brevo.com/u/jmqu)\
**Post date:** [Octobre 9, 2025, 10:17 UTC](https://community.brevo.com/t/does-transactional-email-support-embedded-image/6665/3 "2025-10-09T10:17:19Z")

</div>

Hi Adam

Thanks for the reply.

The risk that you mention definitely exists. That said, as a platform, Brevo should still make it possible to provide this flexibility so that customer have the right to take the risk after a proper evaluation. In addition, it could still be a heavy email if customer just embed it with base64 encode. The only difference is it cannot be downloaded as an attachment.

In our case, we need to deliver a confidential info in the image. So we cannot just make it public.

I hope Brevo team could consider my suggestion and add it into your roadmap. Thanks.