Email signature generator › Hosting the logo

Where to host the logo for an email signature

A hosted signature logo is a URL that has to keep working for as long as your old messages exist. That is a longer commitment than most people think about when they upload a file somewhere.

The three that do not work, and why

Google Drive and Dropbox share links. They point at a viewer page rather than the image file. A mail client asked to render a viewer page inside an image tag gets HTML where it expected pixels and shows nothing. The link works when you test it because you are signed in.

A file on your own computer. Referenced with a file:// path it resolves only on your machine. Most clients respond by embedding a copy in every message, which is how you end up with an image001.png attachment you did not add.

Anything behind a login or a VPN. A company intranet is not reachable by the recipient's mail client, which is opening the message from somewhere else entirely.

The test that settles it in thirty seconds

Open the image URL in a private browsing window. What should happen: the image appears alone on a blank background, with no sign-in prompt, no interstitial page and no surrounding interface. If you see a page rather than an image, it is not an image URL.

Then check the address begins with https://. An image over plain http:// is treated as mixed content and blocked silently by a growing number of clients — no error, just a missing logo.

Your own website, which is usually right

If you have a site, put the logo in a folder there and reference it. You control the address, it lasts as long as the site does, and there is no third party who can change a URL scheme or close an account.

Give it a stable path that will survive a redesign — something like /assets/signature-logo.png rather than a path containing a date or a content management system's internal identifier. A rebuild that moves the file breaks every message you have ever sent.

Static hosting, when you have no site

A static host or object store serves a file at a permanent URL for very little money, and several are free at this volume. What matters is not which one but that the account belongs to you and is not going to lapse — a logo hosted on a free tier attached to an email address you no longer read will disappear silently.

Content delivery, which you do not need

Signature logos are small and cached aggressively by mail clients and by the image proxies that sit in front of Gmail and Apple Mail. A content delivery network solves a problem a signature logo does not have. Simplicity and permanence matter far more here than milliseconds.

The proxy detail worth knowing

Gmail does not fetch your logo from your server every time a message is opened. It fetches once, stores a copy, and serves that to readers. Apple Mail with Mail Privacy Protection does something similar. Two consequences: your server sees far fewer requests than there are readers, and a change to the file at the same URL may not reach people who already have the cached version.

If you change the logo, change the filename too. Same URL with new contents is the one update mail clients handle worst.

What to do about the five-year problem

Messages you send today will be read from archives long after you have reorganised your website. The hosted logo will eventually break, and every historical message loses it at once. There is no fix, only a choice: accept it, or embed the image so it travels with the message and cannot rot.

For most correspondence accepting it is fine. Where sent mail is a record that has to remain complete — legal practice, regulated advice — embedding is the more honest choice, and the paperclip is what it costs.

Frequently asked questions