Email Signature Generator

Full name:

Shown as the main identity line in the plain-text and HTML signatures.

Role or title:

Keep the title short enough to fit comfortably in email clients.

Company:

Appears beside the role and in the compatibility audit.

Email address:

A valid work email makes the signature clickable in HTML output.

Phone:

Include country code when the signature is used outside one local market.

Website:

Use a company homepage, profile page, or booking page.

Signature style:

Choose the visual treatment for the HTML signature; plain text stays compact.

Brand color:

Hex colors are safer than relying on external styles in pasted signatures.

{{ result.blockingErrors.length ? 'Review signature inputs' : 'Compatibility notes' }}

{{ item }}
{{ item }}

Pronouns:

Optional, and omitted from output when blank.

Location or address:

Use one concise line unless a legal postal address is required.

LinkedIn URL:

Omitted when blank; bare domains are normalized to https URLs.

CTA link:

Add both a short label and URL to include one final action link.

Disclaimer:

Keep legal text short; the audit flags signatures that get bulky.

Maximum width:

Email signatures usually work best when kept narrow enough for replies and mobile screens.

{{ result.html }}

{{ result.plainText }}

Check	Status	Detail	Recommendation	Copy
{{ row.check }}	{{ row.status }}	{{ row.detail }}	{{ row.recommendation }}

Field	Value	Output use	Status	Copy
{{ row.field }}	{{ row.value }}	{{ row.use }}	{{ row.status }}

{{ jsonOutput }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Email signatures sit at the end of a message, but they carry more weight than their size suggests. They identify the sender, give recipients a dependable way to reply or call, and often act as the last contact record preserved in a forwarded thread. A useful signature feels like part of the correspondence, not a miniature advertisement pasted under every note.

Most signature problems come from trying to make the block do too much. A name, role, organization, and one or two contact routes are usually easier to scan than a stack of badges, profile links, booking links, banners, and legal copy. Extra material can still be appropriate, especially for regulated teams or client-facing sales flows, but each line should earn its place in ordinary mail.

Identity text should make the sender recognizable without forcing recipients to parse initials or internal titles.
Contact links should point to destinations a recipient is actually expected to use.
Widths and line breaks matter because signatures appear in replies, quoted threads, mobile clients, and narrow reading panes.
Legal disclaimers should stay short unless policy requires longer wording.

HTML signatures and plain-text signatures solve different needs. HTML can add weight, color, spacing, and clickable links, while plain text survives strict mail systems, support desks, command-line mail, and tools that strip rich formatting. Teams that care about consistency often prepare both versions so the same contact facts remain readable even when the visual treatment changes.

Email signature diagram with identity, contact, optional details, and a narrow reply-width bar.

Email clients treat pasted signatures unevenly. Some preserve spacing and colors, some simplify the markup, and some change link styling in dark mode or reply chains. That is why conservative signatures still lean on table layout, inline styles, system fonts, explicit links, and narrow widths instead of modern page-layout tricks.

The safest signature is modest and testable. It should answer who sent the message, how to reach them, and which link matters most, while leaving room for the actual message to remain the focus.

How to Use This Tool:

Fill the identity and contact facts before choosing a visual treatment. The status summary will ask for details until the signature has a name and at least one contact route.

Enter Full name. Add Email address, Phone, Website, LinkedIn URL, or a complete CTA link so the summary can move past Needs details.
Use Role or title and Company for the professional line. Keep both short enough to fit beside replies and quoted text.
Choose Signature style. Compact line is the leanest, Brand bar adds a colored divider, and Formal table uses a top rule.
Set Brand color as a three- or six-digit hex value such as #2563eb. If the value is not a valid hex color, the result uses the default blue and reports a warning.
Open Advanced only for details that should travel with routine mail: pronouns, location, LinkedIn URL, one CTA link, a disclaimer, or a Maximum width from 260px to 600px.
Check Rendered Signature first, then inspect HTML Source and Plain Text Signature. Use the plain-text version when a mail flow strips rich formatting.
Review Compatibility Audit and Field Ledger. Fix warnings about invalid URLs, missing CTA URLs, wide signatures, large HTML, or high link count before copying the final output.
After copying, send a test message to the mail clients your recipients actually use. The browser preview is a first check; the pasted signature is the version that matters.

Interpreting Results:

Start with the summary badges. Ready to paste means the required identity and contact checks passed without current warnings. Ready with notes means the signature can be generated, but at least one detail deserves review. Needs details means a required name or contact route is missing.

The preview and audits reduce obvious mistakes, but they cannot prove every mail client will keep the same spacing, colors, or link behavior. Paste the HTML into the target signature settings and send test messages through Gmail, Outlook, Apple Mail, mobile mail, and any support desk or CRM mailer that will use the signature.

How to interpret email signature result tabs
Result tab	Trust for	Verify before rollout
`Rendered Signature`	Current browser preview of identity, color, spacing, optional lines, and contact order.	Actual pasted appearance in the mail clients and reply formats your team uses.
`HTML Source`	The rich signature markup with inline styling and clickable links when values validate.	Whether the destination client keeps links, spacing, width, and colors after saving.
`Plain Text Signature`	The same sender and contact facts without formatting.	Line breaks, legal wording, and whether the plain version is short enough for strict workflows.
`Compatibility Audit`	Identity, contact count, email shape, link count, width, HTML size, and disclaimer status.	Brand policy, legal approval, and real rendering in client signatures.
`Field Ledger`	Which values were included, normalized, omitted, missing, or marked invalid.	Whether each phone number, profile link, location, and CTA belongs in routine mail.

Warnings about more than five contact links, a width above 480px, or HTML above 12,000 bytes point to signatures that may feel heavy in replies. Remove optional links or shorten disclaimers before treating the signature as final.

Technical Details:

Email signature markup has to survive copying into mail-client settings, repeated quoting, mobile reading widths, and corporate mail gateways. Broad compatibility favors old-fashioned choices: presentation tables, inline styling, system fonts, simple colors, and direct contact links. Modern web layouts can look better in a browser preview but become less reliable after paste, forward, or reply operations.

Contact links are URI-based. An anchor can point to a web address, a mailto: email target, or a tel: phone target. The signature should therefore keep visible contact text readable even when a clickable target cannot be built with confidence.

Transformation Core:

Email signature transformation rules
Signature fact	Rule	Output consequence
Identity	`Full name` is required for a ready status. Pronouns appear only when entered.	The first line is the main identity line, with optional pronoun text kept near the name.
Professional line	`Role or title` and `Company` are joined only when supplied.	The line can contain a role, an organization, both, or no professional line.
Email address	A practical `user@host.tld` shape becomes a `mailto:` link. A questionable address remains visible for review.	Recipients can click a valid-looking address, while suspicious text is not silently turned into a mail link.
Phone	The displayed phone text is preserved. The click target keeps dialable digits and an optional leading plus sign.	Human-friendly spacing can remain visible while capable devices receive a compact `tel:` target.
Web, LinkedIn, and CTA URLs	HTTP and HTTPS URLs are accepted. Bare domains are normalized to `https://` when they parse cleanly.	Usable URLs become links; invalid URLs are left out of clickable HTML and reported for correction.
CTA link	A CTA needs both a short label and a valid URL.	The action link is omitted when the label is present but the URL is missing or invalid.
Brand color	Three- and six-digit hex colors are normalized. Other values fall back to `#2563eb`.	Links, dividers, and brand-bar styling use a predictable color value.
Width	`Maximum width` is rounded and clamped from `260px` to `600px`.	The generated table avoids extreme widths, with audit guidance favoring `420px` to `480px` for safer replies.

Audit Rules:

Email signature audit rule boundaries
Audit check	Pass or included condition	Review or missing condition
Identity line	A full name is present.	No name is entered.
Contact channel	At least one usable email, phone, website, LinkedIn URL, or complete CTA link is present.	No usable contact route is available.
Email format	The email field is blank or has a practical address shape.	The email text does not match the expected address shape.
Link count	`5` or fewer contact links.	More than `5` contact links.
Signature width	`480px` or narrower.	Wider than `480px`.
HTML size	`12,000` bytes or less.	More than `12,000` bytes.
Disclaimer	Marked `Included` when text is present.	Marked `Omitted` when blank; this is normal unless policy requires legal text.

Compatibility Boundaries:

The generated HTML avoids images, scripts, embedded style blocks, and external stylesheets. That reduces common paste and remote-loading problems, but it does not control how every mail client applies dark mode, wraps long text, sanitizes links, or rewrites saved signature markup. A real sent-message test remains the final compatibility check.

Privacy Notes:

The signature content can include personal and organizational contact data. Treat copied HTML, plain text, JSON, CSV, and DOCX exports as contact records, not as harmless formatting samples.

Use only phone numbers, profile links, addresses, and booking links that belong in routine outgoing mail.
Do not include temporary tokens, private calendar links, internal profile URLs, or sensitive legal notes unless policy explicitly requires them.
Review generated artifacts before sharing them, especially JSON and table exports that can include normalized values and audit notes.

Worked Examples:

Lean support reply

Full name is Sam Lee, Role or title is Customer Success Lead, Company is Acme Support, email is sam@example.com, phone is +1 555 0100, style is Compact line, and width is 420px. Rendered Signature should stay short, while Compatibility Audit should show Identity line, Contact channel, Link count, and Signature width as pass-level checks.

Brand bar with normalized links

A client-facing signature uses Brand bar, color #2563eb, website example.com, a LinkedIn profile, and a CTA label Book a meeting with a valid HTTPS URL. Field Ledger should mark the bare website as Normalized, and Compatibility Audit should keep Link count at Pass when the total is five or fewer.

Wide signature under review

A formal signature with a short disclaimer and Maximum width set to 600px can still generate output, but Compatibility Audit marks Signature width as Review because the value is above 480px. Reducing the width to 420px or 480px is safer for mobile replies and narrow reading panes.

Invalid details before copying

If the email is sam.example.com, the brand color is blue, and a CTA label is entered without a valid URL, the generated result needs review. Email format becomes Review, Brand color falls back to the default blue, and CTA link is marked missing until the URL is fixed.

FAQ:

Does the generated signature include a logo?

No. The HTML output uses text, links, table layout, inline styling, and optional divider treatment only. Add image assets separately if your organization requires a logo.

Why does the HTML use a table?

Presentation tables are still more dependable in many mail-client signature fields than modern layout CSS. The table is for layout, not for tabular data.

Can I enter a website without https://?

Yes, when the value can be parsed as a valid web address. A bare domain is normalized to HTTPS, and the result reports a note so you can check the final link.

Why did my CTA link disappear?

The CTA needs both a label and a valid URL. If the label is present but the URL is missing or invalid, the CTA is omitted and the review notes tell you to correct it.

Why is my phone link different from the displayed number?

The visible phone text keeps the spacing you entered. The clickable tel: target keeps dialable digits and a leading plus sign when one is present.

Does Ready to paste guarantee the same look in Outlook and Gmail?

No. It means the current fields passed the page checks. Paste the HTML into each target mail client and send test messages before rolling it out.

Is the JSON export safe to share?

Treat it as contact data. It can include entered values, normalized links, generated HTML, plain text, audit rows, field rows, and warning counts.

Glossary:

HTML signature: A rich email signature that uses markup, links, inline styling, and table layout.
Plain-text signature: A line-based signature without HTML formatting, useful when rich mail is stripped or unavailable.
Inline styling: Styling placed directly on each HTML element so critical appearance details travel with the copied markup.
Presentation table: A table used for email layout because many mail clients handle it more consistently than modern page layout.
mailto: link: A clickable email link that opens a new addressed message in a capable mail program.
tel: link: A clickable phone link built from dialable digits and an optional leading plus sign.
CTA: A call to action, such as a short booking link or support portal link.
Disclaimer: Optional legal, confidentiality, or policy text appended to the signature.