Naimh is a seasoned marketer of 12 years, including in SaaS and tech. She’s an expert at simplifying complex technology concepts, bridging the gap between IT and marketing. Naimh specializes in turning tech speak into actionable insights, helping marketers get the most out of their tools and technology.
Embedded vs hosted images in email signatures
TL;DR
Embedded images are stored directly inside the email itself.
Hosted images are stored on a web server and loaded by reference, which keeps the email smaller and more mobile-friendly.
The right choice depends on which email clients your recipients use. If most read email in Outlook desktop or Gmail, embedding usually works. If many are on Microsoft 365, Outlook Web App, or mobile, hosted images are the safer default.
For organizations managing email signatures at scale, hosted images are almost always the lower-maintenance option, since they can be updated centrally without touching every employee's signature.
Adding images to an email signature sounds simple until you hit the two ways to actually do it: embedding or hosting. Get the choice wrong, and you end up with logos that show up as attachments, banners nobody can update without a company-wide resend, or a signature heavy enough to slow delivery.
The decision isn't complicated once you know what each method actually does.
Embedded images are stored within the email itself. Hosted images are stored on a web server and loaded by reference, which keeps the email lighter and easier to view on mobile.
For IT admins managing email signatures centrally across an organization, this decision affects two things directly: how much control you keep over branding after emails are sent, and how much work it takes when an image needs to change.
If you're using Microsoft 365 or Google Workspace, Exclaimer's email signature solution removes the guesswork. It gives you centralized control over how images are managed and displayed across your organization's email signatures, so this decision doesn't have to be made once and lived with forever.
Should I embed or host images in my email signature?
To add images like a company logo or social media icons to an email signature, you have two options: embed the image directly into the signature template, or host it externally and link to it.
The choice comes down to email client compatibility, post-send brand control, deliverability, and operational overhead at scale. Here's how the two methods compare, followed by a closer look at each.
Embedded | Hosted | |
|---|---|---|
How the image is stored | Encoded directly in the email | Stored on a server, linked by URL |
Email payload size | Larger. Base64 encoding adds roughly 33% to image file size | Minimal |
Displays offline | Yes | No |
Updatable after send | No | Yes |
Reliable in Microsoft 365 and Exchange | Inconsistent. Often shows as an attachment instead of inline | Yes |
Reliable in Outlook 2016/2019 desktop and Gmail | Yes | Yes |
Brand control post-send | None | Full. Update the file on the server |
Analytics and tracking | No | Yes, via platforms like Exclaimer |
Embedding images
An embedded image is encoded directly into the email, either as a base64 string or as an attachment referenced by a Content-ID.
Pros:
Displays offline: once downloaded, the image stays visible even if the recipient is offline
No external calls: better for privacy-conscious environments or secure email setups
Works well for internal-only email: reliable in controlled environments like Outlook desktop or within the same organization
Cons:
Increases email size: heavier emails can slow load times and add to the factors spam filters weigh
Inconsistent rendering: some clients don't handle embedded images cleanly, and behavior can vary by device and app version. Gmail's mobile app is one client where this has been reported
Hard to update: once an email is sent, the image is locked in. If branding changes, there's no way to update it retroactively
Hosting images (web-linked images)
A hosted image lives on a server and gets pulled into the email by URL rather than stored inside it.
Pros:
Lightweight emails: keeps message size down, which helps with delivery speed and spam filtering
Brand control: update or swap the image anytime, without asking anyone to resave their signature
Tracking: signature management platforms like Exclaimer can report on image loads and clicks
Cons:
Blocked by default in some clients: recipients may need to click to display images manually
Needs connectivity: the image won't load if the recipient is offline or behind a strict firewall
Depends on the host: if the hosting server goes down or gets blacklisted, the branding disappears or breaks
"Whether you use embedded or hosted really depends on what you're applying the signature through, whether that's mobile devices primarily, or Outlook, or Gmail. You might be restricted to what you can actually use before you even get to choose. Both options have their pros and cons, their own quirks. But at the end of the day, it's your choice. Some third-party tools will let you use either, or both."
When to use each method
Use embedded images when:
Most recipients use Outlook desktop (2016 or later) or Gmail
Offline viewing matters
You're operating in a privacy-conscious or secure email environment
The image won't need updating after emails go out
Communications are internal-only, within a controlled environment
Use hosted images when:
- Recipients mostly view email on mobile
Recipients use Microsoft 365, Outlook Web App, or Exchange
Branding or promotional banners need updating after emails have already been sent
You're managing email signatures at scale
You need analytics or tracking on signature images
Post-send brand control matters more than guaranteed offline display
How do I find out which email clients my recipients use?
Everything above assumes you know your organization's client mix. If you don't, ask your Microsoft 365 or Google Workspace admin: both platforms report this in their usage data.
For external recipients, check your email service provider's open and click analytics, which often break down by client, or look at the message headers on a handful of recent replies. If there's no clean way to check either, default to hosted images. It's the safer choice when you don't know your audience's exact mix.
Which email clients support embedded images in email signatures?
Compatibility information last verified: August 2026
Email client | Supported |
|---|---|
Microsoft 365 (Office 365) | Inconsistent |
Google Workspace (G Suite) | Yes |
Exchange 2019 | Inconsistent |
Exchange 2016 or earlier | Inconsistent |
Outlook 2019 desktop | Yes |
Outlook 2016 or earlier desktop | Yes |
OWA (Outlook Web App) | Inconsistent |
Gmail | Yes |
Outlook.com | Inconsistent |
Where this table says "inconsistent," it's not a clean no. Microsoft's own support forum notes that Outlook on the web doesn't fully support embedded or locally stored images in signatures, and can convert or strip them during composition or reply. This can happen even when the image displayed fine in the signature editor itself. On Exchange Server 2016 specifically, this has historically depended on whether the server has the latest cumulative updates installed.
Key takeaway
Microsoft 365 and Outlook Web App don't reliably display embedded images, even when the signature editor shows them correctly. That unpredictability is why hosted images are the safer default for those environments.
Do hosted images in email signatures get blocked by email clients?
Compatibility information last verified: August 2026
Email client | Supported |
|---|---|
Microsoft 365 (Office 365) | Yes |
Google Workspace (G Suite) | Yes |
Exchange 2019 | Yes |
Exchange 2016 or earlier | Yes |
Outlook 2019 desktop | Yes |
Outlook 2016 or earlier desktop | Yes |
OWA (Outlook Web App)* | No |
Gmail | Yes |
Outlook.com** | No |
* To add a linked image in OWA, open the image in a browser and copy it directly into the signature editor.
** In Outlook.com, add a hosted image by pasting the HTML source into the signature editor.
Do embedded or hosted images affect email deliverability and security?
Image choice touches two things IT and security teams care about directly: whether the email gets delivered, and whether it draws attention from security scanning.
Payload size and spam filtering
Base64 encoding itself isn't a red flag. It's a standard way to carry an image inside HTML, and deliverability researchers note it's "common and usually harmless when the MIME structure is correct." The historical concern was base64-encoded plain text, occasionally used to hide spam content from older, simpler scanners. That's a different pattern from an embedded image, and modern filters decode content before scoring it either way. Size is what actually matters: every embedded image adds to the total message weight, and base64 adds roughly a third on top of the original file size.
Heavier messages are a contributing factor spam filters weigh alongside sender reputation, not an automatic flag on their own. Hosted images avoid the size question entirely, since the email itself only carries a URL.
What actually causes deliverability problems
The bigger risk in either direction comes from a sloppy rollout rather than the embed-versus-host choice itself: a weak-reputation image host, an oversized file, or a signature appended after DomainKeys Identified Mail (DKIM) signing, since changing the message body after it's been signed can break the signature receiving providers rely on to trust it.
Tip
If a security team is already flagging signature images as unexpected attachments, switching to hosted images usually resolves it, since it removes the attachment pattern entirely.
How to embed images in email signatures
If you want an image to display automatically, without the recipient needing to click "download images," embedding is the way to do it. However, embedded images can increase email size enough to appear as an attachment in some clients.
Step 1: Add the image to your email signature
Insert the image into your signature as you normally would, sized correctly before you add it.
Step 2: Set up the Content-ID reference
Embedding attaches the image to the email and references it with a Content-ID, added through HTML in the signature's source:
<img src="cid:myimagecid" />
Step 3: Save and test
Save the signature and send yourself a test email. If it's set up correctly, the image displays automatically, since it's already referenced in the message itself rather than pulled from elsewhere.
Tip
Some iOS Mail versions have stripped or resized embedded images in the past, so test on iOS specifically before rolling a signature out organization-wide.
How to host images in email signatures
To keep images from showing up as attachments, host them on a web server or an image hosting platform and reference them by URL instead.
Step 1: Upload your image
Upload the image to a web server or hosting platform. You'll get a direct URL to the file once it's uploaded.
Step 2: Link the image in your email signature
Reference the hosted URL with an HTML image tag:
<img src="https://cdn.exclaimer.com/Static2/exclaimer-logo_178x36.png" />
This links the image into the signature without attaching it, which keeps the email file size down.
Step 3: Add alt text (optional but recommended)
Alt text means recipients still understand what the image is even if it doesn't load:
<img src="https://cdn.exclaimer.com/Static2/exclaimer-logo_178x36.png" alt="Exclaimer logo"/>
Tip
Hosted images may prompt recipients to click "download images" before they display. That's a security feature, not a bug, and it's worth setting expectations for internally if this is new for your organization.
What are common problems with embedded and hosted signature images, and how do you fix them?
Problem | Solution |
Images appearing as attachments on iOS | Use hosted images instead of embedded, or reduce image file size to under 50KB |
Blocked images showing red X or placeholder | Add alt text to all images; consider using embedded images for recipients with strict security settings |
Caching issues after logo updates | Rename the hosted image file or add a version query string (e.g., logo.png?v=2) to force browsers to fetch the new version |
Images not displaying in Outlook Web App | Copy the image directly from a browser window into the OWA signature editor rather than linking |
Embedded images stripped in Gmail | Switch to hosted images for Gmail recipients, as Gmail often converts embedded images to attachments |
The bottom line: which should you use?
The answer depends on how your recipients, and your own team, actually receive email.
Use embedded images if most recipients read email in Outlook desktop (2016 or later) or Gmail, and you won't need to update the image after emails go out.
Use hosted images if recipients are mostly on Microsoft 365, Outlook Web App, or mobile, or if your team needs to update branding centrally after emails have already been sent.
This is usually where the maintenance math settles the decision. In Exclaimer's 2025 State of Business Email research of 4,009 IT leaders across the UK, US, Germany, and Australia, 35% named email signature management one of their two most time-consuming tasks, and 80% said they still handle it manually.
Every embedded image that needs replacing adds to that pile. For organizations managing email signatures at scale, hosted images are the lower-maintenance choice almost every time, since they remove that recurring source of manual work. Managed centrally through a platform like Exclaimer, image hosting, updates, and tracking happen automatically, without anyone needing to touch an individual signature when a banner changes.
Start a free trial and see how easy it is to automate and scale email signatures across teams and devices.
