Hosted HTTPS Images vs. Base64 Embedded Photos in Email Signatures

Deliverability · Published 2026-11-17 · 4 min read · Email Signature Editorial

Uploading a local image is great for instant previewing, but sending signatures with base64 data URIs triggers spam filters and broken image boxes.

Why Gmail and Outlook block base64 data URLs

Embedding a photo as a data:image/png;base64 string bloats your signature HTML by tens of kilobytes and is widely blocked by Gmail, Outlook, and corporate email gateways for security and anti-spam reasons.

That is why Email Signature flags uploaded local files as preview-only and recommends replacing them with a hosted https:// image URL before exporting.

Best practices for hosting your signature photo

For fast loading and sharp retina rendering without bloating the message:

  • Export your headshot or logo at 2x display dimensions (e.g., 144x144px for a 72px slot).
  • Use compressed JPEG, PNG, or WebP under 40 KB.
  • Host the file on your company website, CDN, or public HTTPS asset path with no login wall.
  • Always include descriptive alt text so recipients see your name even when images are blocked.