{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Style{{ resultsReady ? styleLabel : '—' }} Links{{ resultsReady ? computation.values.link_count : '—' }} Checks{{ resultsReady ? `${passCount}/${computation.values.audit_labels.length}` : '—' }}

{{ primaryCopyAnnouncement }}

Professional identity and signature presentation
Required and limited to 100 characters.
Shown with the organization when provided.
Optional, but useful for external correspondence.
Required; use the address recipients should contact.
Include a country code for an international audience.
Use a homepage, profile, portfolio, or booking page.
The style changes layout, not the information included.
Use a six-digit value such as #2563eb.
Accepted range: 260–600 px.
px
Leave blank to omit this line.
Leave blank unless location context is useful or required.
Leave blank to omit the profile link.
Both fields must be present or both left blank.
Optional; keep legal text concise and verify organizational requirements.

{{ artifactExportStatus }}

{{ computation.values.html_signature }}

{{ artifactExportStatus }}

{{ computation.values.plain_text }}

{{ artifactExportStatus }}

{{ chartExportStatus }}

The chart renderer is unavailable. The same counts remain available in the compatibility ledger.

CheckStatusDetailRecommendationCopy
{{ row.label }}{{ row.status }}{{ row.detail }}{{ row.recommendation }}

{{ ledgerExportStatus }}

A signature is part of the message, not a separate advertisement. Its first job is to identify the sender and give the recipient a dependable reply route. A short block also survives forwarded threads, narrow reading panes, and mobile mail more gracefully than a dense banner of links and legal text.

Professional context changes what belongs in the block. A consultant may need a role, organization, phone number, and booking link. An internal team member may need only a name and title. A regulated organization may require a disclaimer, but policy wording should be confirmed rather than copied from another company.

Identity
Keep the name and role recognizable outside the organization; internal abbreviations often mean little to a client.
Contact route
Include a phone number, site, or profile only when a recipient may reasonably use it. Too many links compete for attention and are harder to keep current.
Call to action
One next step, such as booking a meeting, can suit routine client mail. A promotional link can overwhelm ordinary replies.
Disclaimer
Use the exact approved wording when organizational or legal policy requires it. Long text dominates the message and is rarely read.

HTML and plain text serve different mail paths. HTML provides hierarchy, color, and clickable contact links. Plain text keeps the same facts readable when rich formatting is removed by a mail client, ticketing system, security gateway, or recipient preference.

Email clients do not render pasted HTML like ordinary web pages. Some remove styles, alter link colors, or reflow content in replies and dark mode. Conservative signatures therefore use a narrow presentation table, inline formatting, system fonts, and no remote image or font dependency.

A browser preview can catch obvious spacing and content problems, but only a sent message proves how a saved signature behaves. Test the final block in the mail clients and delivery systems that will actually use it.

How to Use This Tool:

Build the essential identity first, then add only the details that belong in routine correspondence.

  1. Enter Full name and a valid Email address. Both are required before a signature is generated.
  2. Add the role, organization, phone number, and website that recipients should use. A bare website domain is accepted and becomes an HTTPS link.
  3. Choose Compact line, Brand bar, or Formal divider, then set a six-digit brand color and a maximum width from 260 to 600 pixels.
  4. Open Advanced for pronouns, location, LinkedIn, a call to action, or a disclaimer. A call-to-action label and URL must be supplied together.
  5. Compare the rendered version with the HTML and plain-text versions, then read the Compatibility ledger. Correct any invalid field before copying the signature.
  6. Paste the signature into its destination and send a test message. Check a new message, a reply, and a mobile view before wider use.

Interpreting Results:

The rendered signature shows the intended arrangement, while the HTML source is the rich version that mail software receives. Plain text is the fallback for systems that remove formatting. Keep the wording and contact facts consistent across both versions.

  • Pass confirms the generated markup meets that local rule. It does not certify Gmail, Outlook, Apple Mail, a CRM, or a support desk.
  • Review marks a width above 480 pixels, HTML longer than 5,000 Unicode characters, or a disclaimer longer than 300 Unicode characters.
  • A high link count is not automatically wrong, but every link should have a clear reason to appear in every message.

Technical Details:

Email-signature HTML has to work inside a constrained document fragment. Presentation tables and inline declarations are widely used because a signature editor may discard a stylesheet or modern layout rule. User text must also be escaped so names, addresses, and disclaimers cannot become unintended markup.

Transformation Core:

Email signature transformation rules
Input Transformation Generated result
Email address Validated as a practical address and escaped for link use. A mailto: link whose visible text remains the entered address.
Phone Visible punctuation is retained; non-dial characters are removed from the link target. A tel: link when at least one dialable digit remains.
Website, LinkedIn, or CTA URL A missing scheme becomes https://; the host must contain a valid dot-separated name. An HTTP or HTTPS link. Display text omits the scheme and leading www..
Signature text HTML-sensitive characters are escaped and optional empty lines are removed. Equivalent table-based HTML and line-based plain text.

The three styles change presentation rather than content. Compact line uses an unadorned table cell, Brand bar adds a four-pixel color bar, and Formal divider adds a two-pixel top rule. All use Arial with Helvetica and a generic sans-serif fallback, and all cap the table at the selected integer width.

Rule Core:

Email signature validation and review rules
Rule Boundary Effect
Required identity Full name and email must both be present. Generation stops when either is missing or the email shape is invalid.
Width Whole number from 260 through 600 pixels; review begins above 480. Invalid values stop generation; wider valid values receive Review.
Brand color Exactly six hexadecimal digits after #. Other color forms are rejected.
CTA pairing Label and URL are either both filled or both empty. An incomplete pair stops generation.
HTML footprint Pass at 5,000 Unicode characters or fewer. Longer valid output receives Review.
Disclaimer length Pass at 300 Unicode characters or fewer; input limit is 600. Longer valid wording receives Review.

The generated HTML deliberately contains no remote image, font, stylesheet, script, or tracking pixel. Adding any of those later changes the privacy and compatibility profile and should be tested separately.

Privacy Notes:

Names, contact details, URLs, and disclaimers are processed in the current browser and are not sent to a server by this generator. Anything pasted into the final signature will, however, travel with every email that uses it.

  • Do not include a personal address or phone number unless it is meant for recipients.
  • Confirm that profile and booking links expose only the information you intend to share.
  • Review legal wording with the responsible organization; generation does not make a disclaimer valid or required.

References: