HomeText & GeneratorsEmail Signature Generator

professional signatures. copy & paste.

create a professional HTML email signature in seconds. pick a template, fill in your details, copy the code. works with Gmail, Outlook, and Apple Mail.

Template

Your Details

Accent Color

Live Preview

Your Name

How to Add to Your Email

GmailSettings → See all settings → General → Signature → Paste
OutlookFile → Options → Mail → Signatures → New → Paste
Apple MailMail → Settings → Signatures → + → Paste
View HTML Source
<table cellpadding="0" cellspacing="0" border="0" style="font-family:Arial,Helvetica,sans-serif;color:#333333;max-width:500px;">
  <tr>
    <td style="padding-right:18px;border-right:3px solid #2563eb;vertical-align:top;">
      <table cellpadding="0" cellspacing="0" border="0">
        <tr><td style="font-size:18px;font-weight:700;color:#2563eb;white-space:nowrap;">Your Name</td></tr>
        
        
      </table>
    </td>
    <td style="padding-left:18px;vertical-align:top;">
      <table cellpadding="0" cellspacing="0" border="0">
        
        
        
      </table>
    </td>
  </tr>
</table>

What this tool does

Build an HTML email signature with your name, title, company, contact info, and an optional photo or logo. Output is the HTML you paste into your email client's signature settings.

Email signatures are not normal HTML

Designing for email is a separate craft from designing for the web because email clients render HTML through engines that are 10-15 years behind browsers. The most common rendering engine — Outlook on Windows desktop — uses a Word-based renderer that does not support modern CSS, flexbox, grid, or many other layout primitives. To look correct everywhere, email signatures have to be built with techniques that feel archaic by 2026 web standards.

Specifically:

  • Tables for layout. Yes, in 2026. Outlook does not reliably support divs for any layout beyond stacking, so signatures use nested tables exactly the way websites did in 2003.
  • Inline styles only. Most email clients strip style tags from the head. Every CSS property has to be inline on each element.
  • Fixed pixel widths. Responsive design with vw or percentage widths is unreliable. Pick a fixed width (typically 400-500px) and live with it.
  • Images hosted externally. Embedding images via data URIs works in some clients and breaks in others. Hosting a logo on a public CDN URL is the reliable choice.

Information density

The right amount of information is less than most people think. The typical pattern that reads well across clients:

  • Line 1: Name (bold) and title.
  • Line 2: Company (linked to website).
  • Line 3: Phone or single contact-by-preference link.

Three lines of useful information is usually enough. Anything beyond that competes with the message itself for the recipient's attention.

What to skip

  • Lengthy disclaimers— “This email may contain confidential information” etc. Lawyers often request these; they are not enforceable in most jurisdictions and add visual weight to every message you send.
  • Quotes from famous people — distract from the message and date quickly.
  • Six different social media icons — pick one or two that actually matter for your work. The rest look like a recruiter signature.
  • Animated images — break in many clients, render as broken-image icons in others.

Test before deploying widely

After generating, send the signature to yourself across every email client you regularly use (Gmail web, Apple Mail, Outlook, Spark, mobile apps). The same HTML will render slightly differently in each. Adjust until it works in all of them, then save.

Browser-only

The signature HTML is generated locally and copied to clipboard or downloaded as text. Your contact information — which is going to be in every email you send anyway — never goes through Persimmon's servers.

What this tool does

Build an HTML email signature with your name, title, company, contact info, and an optional photo or logo. Output is the HTML you paste into your email client's signature settings.

Email signatures are not normal HTML

Designing for email is a separate craft from designing for the web because email clients render HTML through engines that are 10-15 years behind browsers. The most common rendering engine — Outlook on Windows desktop — uses a Word-based renderer that does not support modern CSS, flexbox, grid, or many other layout primitives. To look correct everywhere, email signatures have to be built with techniques that feel archaic by 2026 web standards.

Specifically:

  • Tables for layout. Yes, in 2026. Outlook does not reliably support divs for any layout beyond stacking, so signatures use nested tables exactly the way websites did in 2003.
  • Inline styles only. Most email clients strip style tags from the head. Every CSS property has to be inline on each element.
  • Fixed pixel widths. Responsive design with vw or percentage widths is unreliable. Pick a fixed width (typically 400-500px) and live with it.
  • Images hosted externally. Embedding images via data URIs works in some clients and breaks in others. Hosting a logo on a public CDN URL is the reliable choice.

Information density

The right amount of information is less than most people think. The typical pattern that reads well across clients:

  • Line 1: Name (bold) and title.
  • Line 2: Company (linked to website).
  • Line 3: Phone or single contact-by-preference link.

Three lines of useful information is usually enough. Anything beyond that competes with the message itself for the recipient's attention.

What to skip

  • Lengthy disclaimers— “This email may contain confidential information” etc. Lawyers often request these; they are not enforceable in most jurisdictions and add visual weight to every message you send.
  • Quotes from famous people — distract from the message and date quickly.
  • Six different social media icons — pick one or two that actually matter for your work. The rest look like a recruiter signature.
  • Animated images — break in many clients, render as broken-image icons in others.

Test before deploying widely

After generating, send the signature to yourself across every email client you regularly use (Gmail web, Apple Mail, Outlook, Spark, mobile apps). The same HTML will render slightly differently in each. Adjust until it works in all of them, then save.

Browser-only

The signature HTML is generated locally and copied to clipboard or downloaded as text. Your contact information — which is going to be in every email you send anyway — never goes through Persimmon's servers.

more free tools

PDF utilities, image tools, developer helpers — all free, no signup.

Something wrong?