The reference minimal sales signature: brand wordmark, vertical divider, name, title, nothing else. It reads instantly and never breaks across clients, the baseline every AE template should start from.
email signature image hosting
Email signature image hosting
Your signature logo looks perfect to you and is a grey broken box to everyone you email. Email signature image hosting is the single biggest reason signatures fail in the wild. This explains why every common shortcut breaks for the recipient, what a real image URL needs, and how to get one without thinking about it.
Last updated
TL;DR
An email signature image must load from a stable, public, HTTPS URL — not a local file, an email attachment, a Google Drive or Dropbox share link, a social-media hotlink, or a data URI. Each of those works on your screen and breaks on the recipient's. Host it on a real CDN, or use an editor that hosts it for you on export.
Why email signature image hosting matters
A signature image is not part of the email. It is a reference to a file somewhere else, fetched by the recipient's mail client when they open the message. If their client cannot reach that file, they see a broken box where your logo should be.
The trap is asymmetry. The image loads for you because it sits on your file system, inside your signed-in account, or in your browser cache. The person you emailed has none of those. Testing by emailing yourself hides the exact failure everyone else sees.
What not to use, and exactly why each breaks
- A local file path. Points at your hard drive. Nobody else has that drive: instant broken image.
- An email attachment or embedded CID. Bloats every message, often shows as a separate attachment, and renders inconsistently across clients. Gmail also counts it toward the signature character limit.
- A Google Drive or Dropbox share link. Returns a viewer page, not the raw image, and access is account- or rate-limited. Commonly a broken box for the recipient even when it opens for you.
- A hotlink to someone else's site. They can move, delete, or block the file at any time, and many hosts deny hotlinking. Your signature breaks with no warning.
- A data URI. Embeds the whole image as text in the signature. It inflates the code, trips the Gmail character limit, and is stripped by some clients.
What a hosted signature image actually needs
A signature image URL has to be: public (no login), permanent (it will not expire or move), served over HTTPS, the right small size for signature scale, and delivered with the correct image content type. Per Google's Gmail Help, an embedded image also counts toward the 10,000-character limit, which is another reason to reference a hosted URL rather than embed the bytes. Microsoft's Outlook documentation shows Outlook is the strictest common client for blocked or broken images, so getting this right matters most there.
How to host a signature image
The manual route is to upload the image to a real object store or CDN that returns a direct, permanent, public link, then reference that URL in the signature. That works, but it is the step most people skip or get wrong, which is why so many signatures break weeks later.
The done-for-you route is the reason this product exists. Open the editor, add your logo or headshot, and the export embeds a hosted URL automatically: no separate hosting step, no expiring link. Decide whether you even need the image first with the anatomy of an email signature, and see the HTML email signature code guide for how the hosted image fits the exported markup.
You may not need an image at all
Before solving hosting, question the requirement. Many of the strongest signatures use no image — a text wordmark in one accent color carries the brand and can never render as a broken box. These real examples hold a clear identity with type alone:
Fixing an image that is not showing
If your signature image is a broken box for recipients, check, in order:
- Open the image URL in a private window. If it does not load there, it will not load for anyone: it is not truly public.
- Confirm it is the raw image, not a viewer page. Drive and Dropbox links usually fail this.
- Check HTTPS. Many clients block mixed or insecure image requests.
- Re-host instead of hotlinking. If the URL is someone else's domain, host your own copy.
- Add alt text. Per the W3C Web Accessibility Initiative, an informative logo needs descriptive alt so a blocked image still communicates the company name.
Then re-test by emailing someone on a different provider, or use the Gmail, Outlook, or Apple Mail guide to reinstall it cleanly.
Key takeaways
- A signature image is fetched by the recipient; it must be public, permanent, and HTTPS.
- Local files, attachments, Drive/Dropbox links, hotlinks, and data URIs all break for someone.
- Testing by emailing yourself hides the exact failure recipients see.
- Often the best fix is no image — a text wordmark cannot break.
- When you do need one, an editor that hosts it on export removes the step people get wrong.
Skip the hosting step
The editor hosts your logo or headshot on export and embeds a permanent URL, so the most common signature failure cannot happen.
Build with the image hostedQuestions about email signature image hosting
Where should I host my email signature image?
On a stable, public, HTTPS URL: a real object store or CDN, not your computer, your email account, or a file-sharing link. The simplest path is an editor that hosts the image for you on export so the URL is permanent and recipient-safe.
Why is my email signature image not showing?
The recipient cannot reach the image. It references a local file, an attachment, a private Drive or Dropbox link, or a host that blocks hotlinking. It loads for you because of your machine, account, or cache; they have none of that.
Can I use a Google Drive or Dropbox link for my signature image?
No. Those share links return a web page or a viewer, not the raw image, and access can be restricted or rate-limited. They frequently render as a broken image in the recipient client even when they open fine for you.
Why does my signature image work for me but not for others?
That asymmetry is the whole problem. The image loads from your file system, your signed-in account, or your browser cache. The recipient has none of those, so an unhosted image is a broken box on their screen.
Can I just attach the image to my email instead?
Attaching or embedding it as a CID reference bloats every message, often shows as a separate attachment, and is unreliable across clients. Gmail also counts an embedded image toward its 10,000-character signature limit. A hosted URL avoids all of it.
What size and format should a signature image be?
Small and predictable: a logo or headshot a couple hundred pixels on the long edge, well under about 50 KB, as PNG or JPEG. Oversized images slow the inbox, wrap on mobile, and add nothing visible at signature scale.
Do I need an image in my email signature at all?
Often no. Many of the strongest signatures use a text wordmark and one accent color and never risk a broken image. Add a hosted image only if a logo or headshot earns its place for your role.
Is it safe to hotlink an image from another website?
No. The owner can move, delete, or block the file at any time, and many hosts deny hotlinking outright. Your signature breaks the moment they do, with no warning. Host your own copy instead.
Why is my signature image blurry or huge in Outlook?
Outlook applies its own sizing rules and ignores some CSS. Export the image at display size with width and height set, rather than scaling a large file down with styling, so it renders crisp and correctly sized there.
How do I get a permanent URL for my signature image?
Upload it to a service that returns a direct, public, permanent link, or use an editor that does this on export. The export embeds a hosted URL automatically — the part that otherwise breaks weeks later when a temporary link expires.