A Complete History of the Email Signature (1982–2026)
From the .sig file and ASCII art to HTML templates, banners and AI generators.
By Editorial Team, Editors, SignatureCraft · Updated 2026-05-30 · 12 min
The signature block is older than the World Wide Web. This is the story of how it evolved from a Unix convention into a legal document, a marketing surface, and now a computed identity artefact.
The .sig file and the four-line rule (1982–1993)
The email signature predates the World Wide Web by about a decade. Its origin story starts on Unix systems in the early 1980s, where the mail program (originally the Berkeley mail utility) would look for a file called ~/.signature in the user's home directory and append its contents to the bottom of outgoing messages. That convention — a small text file, appended automatically — is the ancestor of every signature block that has appeared in email since.
The earliest .sig files were purely functional: a name, a job title, an address at a research institution, sometimes a phone number. As Usenet grew through the mid-1980s, the .sig file became something more social. It became a place to declare an identity — a favourite quote, an ASCII rendering of one's cat, a small map of the sender's university department. The convention among careful Usenet users was the 'four-line rule': keep your signature to four lines or fewer, because Usenet posts were paid for by the byte on many university networks, and everything below the delimiter line (dash, dash, space, newline) was signature that some readers would auto-strip.
The four-line rule is still visible today in the vestigial delimiter that many mail clients insert when you configure a signature. Nobody remembers why, but the character sequence is the archaeological trace of a bandwidth-conscious network where a five-line signature was considered rude.
The HTML email arrival (1993–1998)
HTML email was standardised in RFC 2110 (1997) and RFC 2557 (1999), building on multipart MIME. Microsoft Outlook 97 and Netscape Communicator 4 both shipped rich HTML composition by default. Overnight, the signature stopped being a plain-text file and started being a layout problem.
The early HTML signatures were catastrophically bad. Companies pasted in centred tables full of animated GIFs, WordArt titles, and background music tags that would play Für Elise when the email opened. The professional community pushed back against HTML email as an abomination throughout the late 90s; some of the earliest email standards documents include semi-serious pleas to please, please, not do this.
The lasting technical legacy of this era is the table-based layout. When Netscape and Internet Explorer diverged in their handling of CSS in the late 1990s, email designers who wanted a consistent rendering across clients retreated to HTML tables with inline styles. That decision — forced by browser fragmentation — is why HTML email in 2026 still looks structurally like 1998 web design. Email clients have never converged enough to allow anything else to be reliable.
BlackBerry, sent from my, and the birth of the mobile signature (1999–2007)
The BlackBerry 5810 shipped in 2002 as the first mainstream phone with full push email. Its default outgoing signature — 'Sent from my BlackBerry Wireless Handheld' — was the first widely-deployed automatic mobile signature. It was doing two things at once: apologising for typos, and quietly advertising the device. Both functions turned out to be sticky.
When the iPhone shipped in 2007 with 'Sent from my iPhone' as its default signature, this pattern was already culturally understood. What was new was the aspirational element. 'Sent from my iPhone' was, briefly, a status marker as much as a typo apology. Users left it on deliberately for the first year or two. When iPhone ownership became mundane a few years later, the signature stopped signalling anything except that its owner had never gone into Settings > Mail > Signature.
'Sent from my iPhone' is now the longest-running default text string in the history of consumer software. It has been in the default iOS mail signature since June 2007, unchanged.
The corporate template era (2008–2016)
Around 2008–2010, email signatures became a formal branding surface at large companies. Marketing departments started shipping mandatory signature templates with brand colours, approved fonts, and stipulated banner images below each employee's contact block. The stated goal was consistency; the actual goal, often, was a low-cost internal-advertising channel that reached every recipient of every employee email.
This era produced the signature marketing industry — companies like Exclaimer, Rocketseed, and CodeTwo built businesses around centrally-managing signatures on Exchange servers so that IT could push updates without emailing 5,000 employees a new HTML block every month. The category is still healthy, and the underlying pain point (keeping signatures consistent across a workforce) has not gone away.
The 2010s also introduced the signature banner as a marketing surface — a wide image below the signature promoting a webinar, ebook, or product launch. Well-run programmes attribute measurable pipeline to signature banners; poorly-run ones produce cluttered signatures that recipients ignore or mildly resent.
The mobile-first rewrite (2016–2020)
By 2016, mobile email had crossed 50% of all reads. This exposed a decade of accumulated technical debt in signature templates that had been designed around 600-pixel-wide desktop viewports. Signatures with three-column photo layouts, wide banners, and social-icon rows started rendering as ugly stacks or, worse, horizontal-scrolling messes on iPhones.
The mobile-first rewrite of the signature happened quietly, mostly at the level of the generator tools. Templates started defaulting to two-column layouts with photo-left, text-right and mobile-linearised social rows. Banner sizes shrank. The vertical-stack signature — everything in one column — began to displace the horizontal-photo signature as the sensible default.
This period also produced the first serious dark-mode-safe signature designs. Apple introduced system dark mode in 2018; Gmail followed in 2019; Outlook in 2020. Signatures that used hard-coded white backgrounds suddenly looked broken for a significant share of recipients. The reliable fix — using no background at all and relying on the client's theme — is still the current best practice.
The AI generator wave (2023–present)
GPT-3.5 became widely-available in November 2022. Within six months, a wave of 'AI signature generator' tools appeared, most of them thin wrappers around a language model that would produce a signature from a short natural-language brief. The output was often visually competent and functionally sound, and it eliminated a lot of the friction that had previously kept people from ever revisiting their signature.
The interesting evolution has been in the direction of what an AI signature generator actually does. The naive version writes text: 'Best regards, Jane Doe, Senior Product Manager at Acme'. The useful version generates full HTML — table structure, inline styles, dark-mode-safe colours — that survives paste into Gmail and Outlook. The distinction matters because the second class of tools is doing genuine work; the first class is doing autocomplete.
By 2026, most new signature generators (including SignatureCraft) do some hybrid: an AI-composed textual identity, hand-tuned HTML templates, and a preview-in-context editor that shows the signature against a mocked Gmail or Outlook thread. The AI component is the copywriter; the template engine is the compositor; the preview is the safety net.
What comes next
Three trends worth tracking. First, signature blocks are being pulled into identity verification. BIMI (Brand Indicators for Message Identification) landed in Gmail in 2021 and puts a verified logo next to your name in the inbox, sourced from your DMARC-authenticated domain. It is the first mainstream cryptographically-verified visual element in mail. Expect the trust boundary between 'signature you drew' and 'identity your domain proves' to keep blurring.
Second, the mobile signature is starting to fork from the desktop signature in ways that matter. Shorter, punchier, and increasingly aware that it is being read on the lock screen preview. Some enterprise generators now ship a mobile-specific signature variant that swaps in when the device sends.
Third — and most speculatively — signatures are becoming computed rather than authored. A signature that reads your calendar and adds 'In meetings until 4pm PT' automatically, or that adjusts its promotional banner based on the campaign your marketing team is currently running, or that suppresses the banner entirely for replies. The .sig file, forty-four years later, is finally becoming a program.
Put these tips into practice
The SignatureCraft editorial team writes about email tooling, deliverability and the small design details that quietly shape how professional we look online.