{{ result.summaryTitle }}
{{ result.primary }}
{{ result.summaryLine }}
{{ badge.label }}
Shown as the main identity line in the plain-text and HTML signatures.
Keep the title short enough to fit comfortably in email clients.
Appears beside the role and in the compatibility audit.
A valid work email makes the signature clickable in HTML output.
Include country code when the signature is used outside one local market.
Use a company homepage, profile page, or booking page.
Choose the visual treatment for the HTML signature; plain text stays compact.
Hex colors are safer than relying on external styles in pasted signatures.
Optional, and omitted from output when blank.
Use one concise line unless a legal postal address is required.
Omitted when blank; bare domains are normalized to https URLs.
Add both a short label and URL to include one final action link.
Keep legal text short; the audit flags signatures that get bulky.
Email signatures usually work best when kept narrow enough for replies and mobile screens.
px 
{{ 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 }}
Tags: Email, Productivity
Export to PDF Fullscreen
Customize
Advanced
:

An email signature is a compact contact block added to the end of a message. A useful one identifies the sender, gives recipients a reliable reply or contact route, and stays small enough that it does not overpower the message itself. The best signatures feel boring in the right way: the name is easy to read, the role and organization are clear, and every link has a reason to be there.

The same signature can travel through Gmail, Outlook, Apple Mail, mobile apps, forwarding chains, and ticketing systems. Each client can treat formatting a little differently, so a signature that looks polished in a browser can become crowded, oddly spaced, or partly stripped after it is pasted into a mail client. That is why plain text still matters and why HTML signatures usually favor conservative table layout, inline styling, system fonts, and a narrow width.

Identity name role and company Contact email and phone site or profile link Optional location one action link A lean signature keeps contact details useful without turning every reply into a banner.
A practical signature starts with identity, adds only the contact routes recipients need, and leaves optional material short.

Long signatures create real friction. Five links, a large disclaimer, and several profile badges can make a short reply look heavy. They also increase the chance of broken wrapping on a phone screen or inconsistent formatting in forwarded mail. A signature should help the recipient act, not make the conversation harder to read.

A good signature also has a clear privacy boundary. Work email, phone numbers, profile URLs, meeting links, and legal notices become easy to copy, forward, archive, and screenshot once they appear in outgoing mail. Use only details that belong in routine correspondence, and keep anything temporary or sensitive out of the final block.

Technical Details

Email signature HTML is not the same as normal web page HTML. Mail clients often strip style blocks, ignore modern layout rules, alter link styling, or apply their own defaults to images and spacing. The reliable pattern is small and conservative: a presentation table, inline styles, simple links, system fonts, explicit widths, and no script or external stylesheet.

This generator follows that conservative pattern. The HTML output is a single presentation table with inline font, color, spacing, and link styles. It does not embed images, tracking pixels, script, or external CSS. The plain-text output uses the same contact facts without layout styling, so there is a fallback that remains readable in clients or workflows that strip rich formatting.

Signature Generation Rules

Area Rule Used Resulting Output
Identity Full name is the required identity line. Pronouns are added only when present. The rendered signature starts with a bold name and optional pronoun text.
Role line Role or title and company are joined only when supplied. The second line can show a title, a company, both, or neither.
Email A practical user@host.tld shape becomes a mailto: link. A questionable address stays visible for review. Recipients can click valid addresses, while suspicious values are not silently turned into mail links.
Phone Visible phone text is preserved. The HTML link target keeps digits and a leading plus sign when available. The display can keep human-friendly spacing while the tel: link stays dialable.
Website, LinkedIn, and CTA Bare domains are normalized with https:// when they parse as usable web links. Links are omitted from HTML when the URL cannot be normalized, and a warning explains the omission.
Brand color Three-digit and six-digit hex values are accepted. Bad values fall back to the default blue. Links, dividers, and the brand bar use a stable hex color instead of named colors.
Maximum width The width is clamped between 260 and 600 pixels. The generated table stays narrow enough for common replies and mobile reading.
Disclaimer Optional legal text is escaped and shown in smaller muted type. A required note can be included without changing the main contact lines.

The three layout styles change presentation without changing the contact facts. Compact line keeps the table plain. Brand bar adds a colored vertical rule beside the text. Formal table adds a top border using the selected brand color. All three keep the same inline-table approach, so the choice is mainly about visual weight and how much brand presence is appropriate for the messages being sent.

The compatibility audit uses clear review boundaries rather than claiming that one HTML block will render identically everywhere. A missing name or missing contact route blocks a ready result. An invalid email, invalid URL, invalid color, wide table, high link count, or large HTML source creates a warning. The source-size warning starts above 12000 bytes, and the width warning appears above 480 pixels because wider signatures are more likely to feel cramped in replies and mobile mail.

Review Boundaries

Condition Status Effect Practical Meaning
No full name Blocking review item The signature has no reliable identity line.
No email, phone, website, LinkedIn, or CTA link Blocking review item Recipients have no contact route beyond replying to the message.
More than five contact links Warning The signature may feel cluttered and should be simplified before broad use.
Maximum width above 480 pixels Warning Replies and narrow screens may wrap the contact block awkwardly.
HTML source above 12000 bytes Warning Optional text, links, or disclaimers are making the signature heavier than a lean contact block.
URL added without a scheme Normalization note https:// is added for HTML links when the address parses correctly.

Everyday Use & Decision Guide

Start with the smallest signature that would still help a recipient. Full name plus one contact route is the minimum. For most work messages, role, company, email, phone, and website are enough. Leave pronouns, address, LinkedIn, CTA, and disclaimer blank unless each item has a real purpose in the messages where the signature will appear.

Choose the style based on the communication context. Compact line is the safest low-profile choice for support replies, internal threads, and places where the message should stay visually quiet. Brand bar gives a little more identity without adding images. Formal table works when the sender needs a polished but restrained block for proposals, account introductions, or external correspondence.

  • Use a six-digit brand color when the organization already has one. A pasted three-digit hex color is expanded automatically, but a full value is easier to audit.
  • Keep the maximum width around 420 to 480 pixels unless you have tested the signature in the exact clients your team uses.
  • Add one CTA only when it belongs in routine mail, such as Book a meeting or View support portal. A second marketing link usually creates more noise than value.
  • Use a disclaimer only when policy requires it. Long legal text increases source size and can dominate every reply.
  • Clear review messages before copying. A ready-looking preview is not enough if the audit says a URL was omitted or the contact set is missing.

The result tabs serve different handoff needs. Rendered Signature is the visual preview and the fastest copy point for HTML. HTML Source is useful when a mail client or admin console asks for source markup. Plain Text Signature gives a simple fallback for clients that do not accept rich formatting. Compatibility Audit explains what to test before rollout. Field Ledger shows exactly which fields were included, normalized, omitted, or marked for review.

Before deploying the HTML broadly, paste it into the intended mail client and send a test message to at least one Gmail account, one Outlook account, and a mobile device if those recipients matter. Read the received message, not only the compose window, because signatures can change after sending, forwarding, and reply quoting.

Step-by-Step Guide

  1. Enter the full name first, then add role, company, email, phone, and website. Use the same spelling and phone format the organization wants recipients to see.
  2. Choose Signature style. Use Compact line for the lightest output, Brand bar for a colored left rule, or Formal table for a top-border treatment.
  3. Set Brand color with a hex value. If the summary shows a color warning, correct the value before copying the HTML.
  4. Open Advanced only for optional details such as pronouns, location, LinkedIn, one CTA link, a required disclaimer, or a width override.
  5. Review the summary and any warning panel. Fix missing identity, missing contact route, invalid email, invalid URL, oversized source, high link count, or wide-layout warnings before rollout.
  6. Use Rendered Signature to copy or download the HTML, HTML Source when source markup is needed, and Plain Text Signature when the receiving mail client prefers text.
  7. Export the Compatibility Audit, Field Ledger, or JSON only when you need a record for an admin ticket, brand review, or repeatable setup note.

Interpreting Results

The summary status is the first gate. Needs details means the signature is missing a name or every usable contact route. Ready with notes means the generator can produce output, but at least one warning deserves review. Ready to paste means the required fields are present and the audit did not find a size, link, width, color, or URL issue under the current values.

The preview is helpful, but the audit table is the better rollout checklist. It shows whether the identity line exists, how many contact links are present, whether the email shape is practical, whether the layout uses inline table HTML, whether the width is within a safer range, and whether the source size is still lean.

Result Area What It Means What To Check
Rendered Signature The generated HTML displayed inside the page. Use it as a preview, then confirm inside the real mail client after sending a test.
HTML Source The copyable inline-table markup. Make sure source HTML is accepted by the destination signature editor before rollout.
Plain Text Signature The same contact details without HTML layout. Keep it readable line by line because it may be the only version some systems preserve.
Compatibility Audit A row-by-row review of identity, contact routes, links, width, source size, and disclaimer state. Resolve warning rows before copying a signature for more than one sender.
Field Ledger A normalized inventory of the entered fields and how each field is used. Look for omitted, missing, invalid, or normalized values before approving the final block.
JSON A structured snapshot of parameters, normalized values, stats, artifacts, audit rows, and field rows. Treat it as setup data because it can contain names, contact details, and generated signature content.

A clean audit is still not a rendering guarantee. It means the generated output follows conservative rules and passes the page's checks. Real mail clients, administrator policies, forwarding systems, and mobile apps can still alter spacing, underline links, hide images from other sources, or trim long signatures.

Worked Examples

Lean support reply signature

A support lead enters a full name, role, company, email, and help-center website, then chooses Compact line. Phone, address, LinkedIn, CTA, and disclaimer stay blank. The audit should show one or two usable contact links and a narrow source size, which fits short back-and-forth support messages where the answer should stay more prominent than the signature.

Client-facing brand bar

An account manager uses Brand bar, sets the brand color to the company hex value, includes email, phone, website, LinkedIn, and a Book a meeting CTA. The useful review is the link count. If the audit reaches five links, the signature is still within the page's preferred boundary, but the sender should test a real reply on a phone before making it the default.

Policy-required disclaimer

A legal or finance sender adds a short confidentiality note in the disclaimer field and keeps the style formal. The source-size row becomes the main checkpoint. If the HTML source moves beyond the lean threshold, shorten the note or remove optional links before copying the HTML into the mail client.

Text-only fallback for strict clients

A user whose mail environment strips rich formatting can still use the same name, role, company, email, phone, and website inputs, then copy Plain Text Signature. That version loses the colored divider and table treatment, but it preserves the contact order and avoids the rendering differences that affect HTML signatures.

FAQ

Does the generator add logos or image icons?

No. The generated HTML is text, links, table layout, and inline styling only. Add images manually in a mail client or signature management system if your organization requires them.

Why does the HTML use tables?

Tables remain one of the more reliable layout choices for email signatures because many mail clients handle modern web layout unevenly.

Can I paste a website without https://?

Yes, when the value can be parsed as a web address. The generated HTML normalizes usable bare domains with https:// and warns when a URL cannot be used.

Why is a long disclaimer flagged?

Long legal text makes every message heavier and can push the HTML source past the lean-signature threshold. Keep disclaimers short unless policy says otherwise.

Does Ready to paste mean it will look identical in every mail client?

No. It means the output passed the page's checks. Send test messages through the clients that matter before making the signature a default.

Is the JSON export safe to share?

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

Glossary

HTML signature
A rich-text email signature that uses markup, links, inline styles, and layout rules.
Plain-text signature
A line-based signature without HTML formatting. It is easier to preserve in strict or stripped-down mail flows.
Inline CSS
Styling placed directly on an HTML element, which is usually more dependable in email than separate style blocks.
Presentation table
A table used for layout rather than data. Email signatures often use this pattern because mail clients handle it consistently.
mailto: link
A clickable email link that opens a new message addressed to the visible email address.
tel: link
A clickable phone link built from dialable digits and an optional leading plus sign.
CTA
Call to action, a short optional link such as a booking page or support portal.
Disclaimer
Optional legal, confidentiality, or policy text appended to the signature.

References