Image Hosting for Email Signatures, Explained

Why you cannot just attach your logo, what HTTPS hosting actually means in this context, and the three reliable ways to host signature images for free.

Email signatures are HTML, and HTML images need to live somewhere on the internet that the recipient's email client can reach. That sounds simple until you discover that "somewhere on the internet" excludes your laptop's Downloads folder, your Google Drive share link, most Dropbox URLs, and any service that requires a login to view the image. Here is the technical reality of image hosting for email signatures and the handful of approaches that actually work.

Why your logo cannot just be attached

When you paste an HTML signature into Gmail or Outlook, the email client looks at every <img src="..."> tag and tries to fetch that URL when the message is rendered — both at send time on your machine and at open time on each recipient's machine. Every recipient, every time, independently fetches the image fresh.

This means the URL has to be publicly accessible, served over HTTPS, return a 200 response with proper image headers, and stay alive for as long as you expect anyone to see your signature. That is a surprisingly high bar.

You cannot use a file path like C:\Users\you\logo.png — that only exists on your computer. You cannot use a Google Drive sharing link because Drive returns an HTML preview page, not the raw image bytes. You cannot use most Dropbox links for the same reason. You cannot use Slack uploads, Notion uploads, or any service that gates the image behind a login or a redirect.

The image needs to live at a stable URL that returns the actual image file directly when requested anonymously.

Inline base64 images: tempting, mostly broken

A common suggestion online is to inline your logo as a base64-encoded data URI: <img src="data:image/png;base64,iVBORw0KGgo..."> with the entire image bytes embedded in the HTML itself. No hosting required.

This works in some clients and fails spectacularly in others. Gmail strips data URIs from images entirely — your logo will simply disappear. Outlook for Windows handles them inconsistently across versions. Apple Mail accepts them. Most modern webmail clients support them.

The other problem is size. Inlining a 50KB logo as base64 adds about 67KB to every email you send. Multiply by the number of recipients and the number of emails you send per month and the bandwidth waste adds up. More importantly, large signatures sometimes trigger the "[Message clipped] View entire message" warning in Gmail, which is a terrible look on a professional email.

In short: do not inline images as base64 unless you are absolutely certain every recipient uses a client that supports it, which in 2026 you cannot be.

Three hosting approaches that actually work

There are essentially three reliable ways to host signature images in 2026, in order of recommended use.

The first is a dedicated image host with a CDN. ImgBB, Imgur (direct image URLs only, not gallery links), Cloudinary's free tier, and Postimages all give you a stable HTTPS URL that returns the raw image. The downside is that some of these services may eventually delete unused images or pivot their business model, breaking your signature for every existing recipient. Cloudinary is the most reliable choice for long-term hosting.

The second is your own website. If you already have a company website, upload the logo to /assets/email-signature-logo.png and reference the public URL. This is the most stable option — as long as your website exists, the image exists, and you control both. The downside is that you need a website to begin with.

The third is using SignatureCraft's built-in upload, which routes through a CDN so the image stays available without you having to set up anything. When you upload a logo in the editor, we generate a stable HTTPS URL and embed it in the exported HTML. This is the default we recommend because there is nothing for you to configure or maintain.

Why HTTPS is non-negotiable

Modern email clients, Gmail especially, refuse to load images served over plain HTTP. The browser-based webmail interface runs on HTTPS, and modern security policies forbid loading insecure resources into a secure page. The image is silently blocked and the recipient sees a broken image icon or nothing at all.

If you host an image on an old server without an SSL certificate, that image will not render in Gmail web, Outlook web, or any other browser-based client. The cost of an SSL certificate has been zero since Let's Encrypt launched in 2015, so there is no excuse to host signature assets on HTTP in 2026. Every recommended host above serves HTTPS by default.

Image dimensions, retina, and file size

Signature logos look best when they are uploaded at twice the intended display size. If you want your logo to display at 80 pixels wide, upload a 160-pixel-wide image. The high-DPI ("retina") screens on most modern laptops and phones will render the larger source crisply at the smaller display size. Uploading exactly at display size produces a noticeably soft logo on retina displays.

File size matters less than it used to but still matters. Aim for under 50KB for a logo and under 150KB for a banner. Most JPG compression tools and PNG optimisers (TinyPNG, Squoosh) will shrink files dramatically with no visible quality loss. Large signature images trigger image-blocking heuristics in some corporate email gateways, so leaner is genuinely better.

Step by step

  1. Decide where the image will live — For the easiest path, upload directly in the SignatureCraft editor — we host it on a CDN automatically. For maximum control, upload to your own website or to Cloudinary.
  2. Confirm the URL is publicly accessible — Open an incognito browser window and paste the image URL. If the image appears directly (no login, no preview page), you are good. If you see anything else, the URL will not work in email.
  3. Check that the URL starts with https:// — If it starts with http://, the image will be blocked in Gmail and most modern clients. Get a proper hosted version with HTTPS.
  4. Use the URL in your signature — In SignatureCraft, paste the URL into the Logo or Banner panel. The editor previews it instantly so you can confirm it loads correctly.
  5. Send a test to a Gmail and an Outlook address — These two clients fail in different ways. If both render the image, you can be confident the rest will too.

Tips

  • Never use temporary URLs from screen-recording tools or scratch image hosts — they expire and your signature breaks silently.
  • If you switch image hosts, your existing recipients' cached signatures keep working until they re-open old emails. New images take effect for new emails only.
  • Keep a local backup of every signature image. Hosts disappear; backups don't.