Skip to content

Why your email signature should be HTML, not an image

6 min read June 14, 2026
email signaturehtml emailoutlookgmailproductivity

An image signature is one flat picture: no clickable links, no selectable text, and a blank box the moment a client blocks images. HTML survives all three.

Why your email signature should be HTML, not an image — Hivly

You built a nice email signature, took a screenshot of it, and pasted the picture into your email settings. It looks perfect in your own inbox, so the job feels done. Then a client replies asking for the phone number they could not click, another sees a broken-image icon where your details should be, and on someone’s phone the whole thing is a pale grey smudge. The picture was the problem.

TL;DR: An image signature is a single flat picture. Its links are dead, its text cannot be read or selected, and it disappears the moment an email client blocks images. An HTML signature keeps links clickable and text visible everywhere, which is why it is the format that actually works.

An image is one flat picture with no working parts

When your signature is an image, everything in it is paint. The email address is not an email address, it is coloured pixels shaped like one. The phone number cannot be tapped. The link to your site goes nowhere, because there is no link, only a picture of underlined text. Anyone who wants to act on your details has to retype them by hand, which is exactly the friction a signature is meant to remove.

It is also invisible to anyone using a screen reader, since there is no real text to read out, only an image that may or may not carry alt text. So an image signature quietly fails the people most reliant on your contact details being machine-readable.

Blocked images leave a blank where you used to be

Plenty of email clients block remote images by default until the reader chooses to load them. With a normal HTML signature that is a minor cosmetic issue, your photo or logo simply does not show, and the text around it carries on. With an image-only signature, blocking images erases the entire thing. The reader sees an empty box or a broken-image icon, and your name, role and contact details are all gone at once.

You have no control over this setting. It lives in the recipient’s client, often switched on for privacy or to save data, and you will never know it happened. Betting your whole professional footer on the reader choosing to load images is a bet you lose silently.

Dark mode and small screens expose the seams

A signature image is baked at one size with one background. Open it on a phone and it either shrinks to unreadable or forces sideways scrolling. Open it in dark mode and a signature designed on white can sit in a glaring white rectangle against an otherwise dark email, or your dark text can vanish into a dark background.

Real HTML reflows. Text resizes for the screen, layouts adapt, and a signature built with sensible colours holds up whether the reader is in light mode or dark. The signature stops being a fixed sticker and becomes part of the email, which is what it should have been all along.

Why HTML signatures still lean on tables

Here is the twist that surprises people: a reliable HTML signature is built from HTML tables with styles written inline on each element, a technique that looks dated next to modern web layout. The reason is the email clients themselves. Outlook in particular strips out style blocks and ignores much of the CSS that ordinary web pages rely on, so the clever layout you would use on a website simply falls apart in an inbox.

Tables with inline styles are the lowest common denominator that every major client agrees to render the same way. It is not elegant, but it is the structure that survives Gmail, Outlook and Apple Mail without rearranging itself. This is why a signature you hand-code for the web often breaks in email, and why dedicated tools generate the table version for you.

Build it once, paste it in

The practical workflow is simple. Build the signature as proper HTML, with your photo or logo referenced from a public URL rather than pasted in, then copy it and paste it into your email client’s signature settings. Because it is real markup, the links stay clickable, the text stays selectable, and the layout holds across clients.

The email signature builder generates that table-based HTML for you and copies it ready to paste, so you get a signature that works in every inbox without writing a line of code.

Try the email signature toolsBuild a polished, email-safe signature with your details, layout and colour, then copy it straight into your mail client.

Frequently asked questions

Why not just use an image as my email signature?
An image is one flat picture, so its links are not clickable, its text cannot be selected or read by screen readers, and many email clients block images by default, leaving a blank box or a broken-image icon. HTML keeps links live and text visible in every case.
Why do HTML signatures use tables instead of modern CSS?
Major email clients, Outlook especially, strip out style blocks and ignore much modern CSS layout. Table-based HTML with inline styles is the one structure that renders consistently across Gmail, Outlook and Apple Mail, which is why signature tools still build it that way.
Will my logo or photo still work in an HTML signature?
Yes, but the image must be hosted at a public URL and referenced, not pasted in. Email cannot carry a local file, so the signature links to the image online. If a recipient blocks images, your text, links and layout still arrive intact.
How do I add an HTML signature to Gmail or Outlook?
Build the signature, copy it, then paste it into the signature box in your email client's settings. Because it is real HTML, the formatting, links and images carry across. Each client has its own settings screen, but the paste step is the same.

Building something bigger?

Hivly is made by CodingEagles, a software studio that ships production web apps. If you have a real project, get in touch.

See what CodingEagles does →