Skip to main content

Email Signature Generator

Generate professional HTML email signatures with contact details and social links.

Reviewed by · Last reviewed

Your Details

Social Links

Live Preview

Fill in your details to see the signature preview.

How to Use the Email Signature Generator

  1. Enter your name, role, and company in the form. These become the headline of your signature.
  2. Add contact fields: business email, phone (in E.164 format, like +1 415 555 0142, for tap-to-call compatibility), and optionally a website URL.
  3. Add social links: LinkedIn, Twitter/X, and GitHub handles or full URLs. The generator turns them into clickable links.
  4. Preview the signature in the live render panel. The HTML is also shown in a code panel so you can inspect exactly what will be pasted.
  5. Click Copy HTML and paste the result into your email client's signature settings (Gmail, Outlook, Apple Mail, Thunderbird, Spark).

What This Tool Does and Why the Output Is HTML Tables

The signature is rendered as an HTML fragment using the old-school email-safe pattern: <table> elements with inline style attributes. This is not because tables are semantically correct; it is because email clients have dramatically varying CSS support. Outlook desktop, still in wide use in corporate environments, uses Microsoft Word\'s rendering engine for HTML email, which ignores most flexbox, grid, and external stylesheets. Tables with inline styles survive that environment because they mirror the 1999-era HTML that Word rendering was designed for.

All links (mailto, tel, http, social profiles) are constructed according to RFC 6068 for mailto: URIs and RFC 3966 for tel: URIs. Email addresses are validated against the RFC 5322 address-spec pattern, although modern email permits characters that RFC 5322 formally forbids (most notably plus signs, which Gmail uses for plus-addressing). Output sanitization happens in the browser: the generator uses textContent escaping rather than innerHTML insertion, which prevents a malicious input from being interpreted as script. You can copy the HTML with confidence that it will not carry an injection payload from the tool itself.

Scenarios That Benefit From a Clean Signature

  • Onboarding a new hire who needs a company-standard signature on their first day without waiting for IT to configure their template.
  • Updating your title after a promotion so that every client email going out carries the right role (a surprisingly common cause of awkward correspondence).
  • Adding a regulatory disclaimer or a pronouns line to match a new company policy without waiting for an email-platform admin.
  • Differentiating signatures for different inboxes: one for customer support with the helpdesk URL, one for sales with the booking-link URL.
  • Cleaning up the mess of a signature that was pasted from Word and has accumulated broken image tags, stray styles, and stale phone numbers.
  • Preparing signatures for a team of 20 where every person needs the same layout with different personal details.

Pitfalls of HTML Email Signatures

The biggest surprise is that image-based logos in signatures often render as red X boxes for recipients because images require either a public URL (which means the image can be tracked) or a Content-ID attachment (which most email clients flag as spammy). If your brand requires a logo, host it on your public website and use an <img> tag with a fixed width; accept that recipients on privacy-conscious clients like Apple Mail\'s Mail Privacy Protection will see the image only after explicit download. A pure-text signature with a Unicode bullet (U+2022) for separators is more reliable.

Outlook desktop renders differently from Outlook web. A signature that looks perfect in Gmail and Outlook.com can be broken in classic Outlook because of the Word-based renderer. Test by sending yourself a message viewed in every client you care about. Dark mode is another problem: Gmail and Outlook auto-invert some colors but not others, so a dark-gray-on-white signature can end up dark-gray-on-dark-gray. Use named CSS colors (rather than hex shades close to black) and test in dark mode. Finally, mobile email clients often strip trailing whitespace and collapse lines; design the signature to degrade gracefully if a line is lost.

Email Signature Conventions by Region and Role

The classic business signature descended from 1980s internal-memo formats and has been codified by style guides at large organizations. Most companies require at minimum: full name, title, company name, and a direct phone number. Many EU companies require their VAT number, company registration, and physical address by law (under the German Telemediengesetz, for example). In Japan, formal email signatures include the department name in parentheses before the title. Some law firms include a confidentiality notice; some tech companies forbid legal boilerplate as clutter. The right signature depends on your jurisdiction, industry, and company policy. Keep it under 6 lines of text plus at most one small image for best cross-client rendering.

Alternatives and Where Each Wins

For enterprise deployments, paid services like Exclaimer, CodeTwo, and WiseStamp manage signatures centrally on your Microsoft 365 or Google Workspace tenant; a policy updates every employee\'s signature without their involvement. HubSpot\'s free signature generator has polished templates and integrates with CRM tracking. Gmail\'s built-in signature editor is sufficient if you do not need HTML-level control. A browser-local HTML generator like this tool wins when you want full control over the markup, when your company has no central signature management, or when you need to create multiple variants for different inboxes quickly. The output is plain HTML that you can paste anywhere; there is no dependency on a service that could go away. For privacy, the local-only generation means your contact details are not logged by a signature vendor.

Frequently Asked Questions

Why does the generator use HTML tables instead of modern CSS?

Outlook desktop uses Microsoft Word's rendering engine for HTML email, which supports only a subset of CSS and ignores flexbox, grid, and external stylesheets. Tables with inline styles are the lowest-common-denominator layout that renders consistently across Outlook desktop, Outlook web, Gmail, Apple Mail, and Thunderbird. Tables for layout are an anti-pattern on the modern web, but email is a special environment where pragmatism wins.

Does Gmail respect the HTML signature I paste in?

Mostly. Gmail strips some attributes for security: classes, IDs, and style attributes referencing external files are dropped, but inline styles are preserved. Complex gradients may simplify. The table layout from our generator survives Gmail's sanitization. Paste directly into the signature rich-text editor in Gmail settings; do not paste into plain-text mode or HTML will appear as raw markup.

How do I add a profile photo to the signature?

The generator ships with text-only signatures. To add an image, edit the HTML and insert an <code>&lt;img&gt;</code> tag with a <code>src</code> pointing to a publicly hosted image. Keep it under 20KB and 200px wide, and include <code>alt</code> text. Many privacy-focused clients (Apple Mail with MPP, ProtonMail) do not load external images, so the signature must remain legible without the photo.

Is my information uploaded when I generate the signature?

No. The HTML is assembled from your inputs using JavaScript string interpolation inside your browser. No fetch call carries your name, email, or phone number. Watch the Network tab in DevTools and confirm that clicking Copy HTML produces no request. This matters because signatures often contain direct-dial and personal mobile numbers you do not want leaking to analytics.

How do I format phone numbers so they work on mobile?

Use E.164 format with country code and no punctuation: <code>+14155550142</code>. The <code>tel:</code> URI links follow RFC 3966, and iOS and Android tap-to-call work most reliably with E.164. Display text can be formatted for humans (<code>+1 (415) 555-0142</code>), but the href should remain E.164. The generator produces both forms correctly.

Why does my signature look different in dark mode?

Gmail and Outlook auto-invert some colors in dark mode. Pure black (#000000) gets inverted to near-white. Mid-tone grays may end up dark-gray-on-dark-gray. Avoid near-black colors (like #111111), which clients leave unchanged. Use named colors like <code>color: black</code> or a solid #333333 on #FFFFFF for consistent inversion.

Should I include a legal disclaimer or confidentiality notice?

Only if required. Law firms, financial services, and some healthcare organizations mandate them. Most tech and consumer companies consider them clutter. A confidentiality notice has limited legal weight anyway; courts have ruled that email boilerplate does not create an enforceable NDA. If required, keep it under three lines.

How do I add my pronouns to the signature?

Add them in parentheses after your name: <em>Jane Doe (she/her)</em>. Common in technology, academia, and progressive corporate environments. Include only if you want to; if your workplace has not normalized it, you are not obligated. The name field accepts the parenthetical to keep the signature compact.

How can I test the signature renders correctly across clients?

Litmus and Email on Acid offer paid cross-client previews across 90+ email clients. For free testing, send to personal accounts covering Gmail web, Gmail mobile, Outlook desktop, and Apple Mail iOS. Review in both light and dark mode. If a render looks broken, simplify the HTML (remove borders, background colors) until it works.

Can I create different signatures for different inboxes?

Yes. Generate one, save to a text file, then generate another. Gmail lets you save multiple signatures and assign per account. Outlook lets you pick a signature per compose. The generator is one-at-a-time. For team deployments where everyone needs a matching signature, enterprise tools like Exclaimer handle that server-side.

Is the generated HTML compliant with HTML5?

Yes, with a caveat: email HTML is a permissive subset with quirks. The tables, inline styles, and link structures are valid HTML5. Some attributes (like <code>cellpadding</code>) are HTML 4 legacy features email clients still honor. The generator uses them for Outlook compatibility; a strict HTML5 validator will flag them. Acceptable for email, not for modern web pages.

More Productivity