An estimated nine billion faxes still cross the wire every year, mostly in hospitals, law firms, pharmacies, and the kind of government office where the carpet has a pattern that pre-dates the euro. The machines themselves are mostly gone. What's left is a software emulation of the old fax standard, Group 3, running on top of a VoIP trunk, pretending to be a beige plastic box with a thermal-paper roll. The protocol survives. The object it once required has been quietly discarded, then re-summoned in software, because the institutions that depend on it never actually wanted the object. They wanted the legal status the object happened to confer.

This is the part that took me a while to understand. People usually frame the persistence of fax as institutional inertia, old doctors who can't be retrained, old lawyers who won't give up their dedicated line. The inertia is real, but it's not the mechanism. The mechanism is that a faxed document accrued, over about thirty years, a body of case law and regulation treating it as presumptively delivered, presumptively unaltered, and presumptively timely. The transmission confirmation page, with its timestamp and page count, became a kind of evidentiary atom. Courts accepted it. Regulators accepted it. HIPAA explicitly permits fax as an acceptable channel for transmitting protected health information. Email never accreted the same body of presumptions, partly because it lacks the same chain-of-custody artefact and partly because the regulations were written before anybody had thought hard about email at all.

Once that asymmetry hardened, every workflow built downstream of it inherited the dependency. Hospitals could not stop faxing without rewriting their referral procedures, their pharmacy authorisations, their record-release policies, and their malpractice posture all at once. The same is true for law firms filing motions at the close of business and for banks running loan documentation against regulatory clocks. None of those institutions love fax. They love the audit trail it produces and the legal precedent that audit trail invokes, and the cheapest way to keep the audit trail is to keep faxing.

So when the hardware became uneconomic, the protocol did not die with it. It moved into T.38, a real-time fax-over-IP standard that lets a softswitch carry the fax session across packet networks. From the application's point of view, nothing has changed. From the network's point of view, there is no longer a phone line. The dedicated copper pair the fax was always sold as needing has been replaced by SIP trunks running over ordinary internet, which is precisely the medium fax was supposed to be defending against. The compliance argument has quietly inverted. The transmission is now indistinguishable from email at the transport layer. What persists is the paperwork that says it isn't.

There is a particular kind of haunting in this. The persistence of fax is not the persistence of an old machine. It's the persistence of a legal fiction surviving the substrate it was written about. It's similar to the way the AT command set still answers inside a 5G modem, except that AT survives because nobody could be bothered to replace something that worked, while fax survives because somebody would have had to rewrite the law. The first is software inertia. The second is jurisprudential inertia. They look the same from the outside. Inside, they are very different ghosts.

A nurse in 2026 sending lab results to a referring physician is, in a real sense, operating a piece of 1980s telecoms ritual. The beige box is gone. The dial tone is simulated. The phone line is a software illusion. But the moment of transmission, the confirmation page, the timestamp, the page count, are still treated as a kind of legally privileged event, distinct in character from the email she might have sent instead. The ritual was always the point. The hardware was a costume the ritual happened to be wearing.

Sources: