Email Signature Generator

An email signature is one of the few pieces of branding almost everyone sends dozens of times a day without thinking about it. A well-formed one adds a name, role and a couple of easy ways to get in touch or find you online, without turning every email into a wall of text. A badly-formed one — built by pasting formatted text from a word processor, or hand-typed with random line breaks — tends to look inconsistent between the sender's own outbox and the recipient's inbox, because desktop word processors and email clients don't share the same rendering rules. This tool builds signatures the way professional HTML email actually has to be built: as a `<table>` with every style declared inline on the elements themselves, and no `<style>` block or CSS class anywhere in the output. That is not a stylistic preference — it is a hard requirement of the medium. Gmail, Outlook, and most corporate mail gateways strip `<style>` blocks and CSS classes from both composed and received mail as a security and consistency measure, and modern layout tools like flexbox or grid are unevenly supported inside the sandboxed rendering engines email clients use. Tables with inline styles remain the one layout technique that renders predictably across essentially every client in use today, which is why every major transactional email platform still generates markup this way even in 2026. Three templates are offered because different roles call for different tones. Classic places a circular photo to the left of a text block with a thin rule under the name — friendly and personable, well suited to client-facing roles like sales or account management. Modern drops the photo in favor of a 4-pixel colored bar down the left edge, which reads as tidy and design-forward without needing an image to load. Minimal strips out the photo and the accent color entirely, leaving plain stacked lines of text — the safest choice for internal or highly formal correspondence, and the one least likely to look strange in a client that partially fails to render other markup. The optional photo is resized to a 120×120 square directly in your browser using a `<canvas>` element, then embedded as a base64-encoded `data:` URI inside the `<img>` tag — so the finished signature is entirely self-contained with no external image request required to display it. That convenience comes with one well-known real-world limitation worth knowing before you rely on it: Outlook for Windows desktop, in particular, is known to strip base64-embedded images from signatures in some configurations, especially when a signature is set through Outlook's own signature editor rather than pasted fresh into a compose window. If your organization is on desktop Outlook and the photo doesn't appear for some recipients, hosting the image externally and linking to it by URL — rather than embedding it — is the standard workaround, though that trades away the self-contained convenience this tool defaults to. All typed values — name, title, company, phone, email, website and each social URL — are HTML-escaped before they are placed into the generated markup, so a name containing an apostrophe, an ampersand in a company name, or angle brackets typed by accident cannot break the table structure or inject unintended markup into the signature that ends up in every email you send.