What Is a PDF? The Complete History of The PDF

Right now, somewhere in the world, a student is downloading a syllabus, a lawyer is signing a contract, a government office is issuing a certificate, and a company is sending an invoice — and there's a very good chance every single one of them is doing it through the same 32-year-old file format. Not because anyone chose it deliberately today. Because The PDF simply won, decades ago, and nothing has managed to replace it since.

This is the complete story of how that happened: what a PDF actually is underneath the icon, who built it and why, the decade it spent nearly failing, the year it stopped belonging to one company, and why — even in 2026, with better-funded, more "modern" formats available — it's still the thing you reach for when a document absolutely has to look the same on every single screen it lands on.

If you've ever wondered why a Word document can arrive looking completely different from how you sent it, but a PDF never does — or why government forms, contracts, and boarding passes all default to this one format specifically — the answer isn't really about technology at all. It's about a problem that existed for years before anyone solved it properly, and the surprisingly deliberate story of the person and company that finally did.

What Is a PDF?

PDF stands for Portable Document Format. That word "Portable" is doing more work than it looks like — it's not about file size or convenience, it's the entire reason the format exists. A PDF is a document built to travel: to leave the computer, program, and printer it was created on, arrive somewhere completely different, and look exactly the same when it gets there.

Open a PDF on a decade-old laptop, a brand-new phone, or a library computer halfway around the world, and every line break, every font, every margin sits in precisely the same place. That single guarantee — that a document won't quietly rearrange itself depending on what it's opened with — is the whole idea The PDF was built to deliver, and it's a guarantee that word processor files, web pages, and most other document formats simply don't make.

Technically, a PDF is a self-contained description of a page: exact coordinates for every letter, line, shape, and image, along with (optionally) the actual font files needed to draw that text correctly, all bundled into one file. Nothing about how it looks depends on software the recipient happens to have installed. The document carries its own instructions for exactly how to render itself, every time, everywhere — which is a fundamentally different approach from a Word document, which is really just a set of editing instructions that get reinterpreted (and sometimes misinterpreted) by whatever program opens it.

The World Before PDF: A Genuine Mess

To understand why The PDF was such a big deal, it helps to actually sit with how broken document sharing was before it existed. It's easy to take "a document just looks right, everywhere" for granted in 2026. In the late 1980s and early 1990s, it was closer to a fantasy.

Say you wrote a report on your computer, using your word processor, with your fonts, laid out exactly how you wanted it. The moment you needed to send that file to someone using a different computer — a different operating system, a different version of the same word processor, or worse, entirely different software — there was a very real chance it would arrive looking like something else altogether. Fonts your system had but theirs didn't would get silently swapped for whatever was available, sometimes shifting every line of text as a result. Page breaks would land in different places. Carefully placed images would drift. Formatting that took an hour to get right could unravel in the time it took to open an email attachment.

Printing made it worse, not better. A page that looked perfect on your monitor might print completely differently on someone else's printer, because printers of that era each interpreted formatting instructions slightly differently, and there was no universal, exact description of the page being sent to them — just a set of instructions that different hardware would carry out slightly differently.

Offices dealt with this the only way they reliably could: by not really trying. Important documents got printed, faxed, or physically mailed, because paper was the one format guaranteed to look the same no matter who received it. The idea of a genuinely "paperless office" — a phrase that gets used constantly today — was, at the start of the 1990s, a running joke as much as a goal. Computers had made it trivially easy to create a polished document. They had done almost nothing to make it possible to reliably share one.

This was the exact problem sitting on John Warnock's desk at Adobe in 1990.

The Camelot Project: Where The PDF Actually Began

John Warnock wasn't a random executive stumbling onto a good idea. He co-founded Adobe Systems in 1982 after inventing PostScript, the page-description language that had already reshaped desktop printing by giving software an exact, unambiguous way to describe a printed page. Adobe was, by the end of the 1980s, a genuinely dominant force in graphics and printing software. And Warnock, watching document chaos play out across the industry he'd helped build, kept circling back to a problem PostScript hadn't actually solved: PostScript was built for printers, not for people reading documents on a screen, and it wasn't remotely lightweight enough for everyday document sharing.

In 1990, Warnock began outlining a solution. In 1991, he wrote it up formally in an internal memo, under the codename "The Camelot Project." The name had nothing to do with King Arthur — it was simply an internal project name, the way tech companies have always given ambitious ideas evocative code names before anyone's sure they'll work. What Warnock proposed inside that memo, though, was genuinely ambitious: a simplified, lighter version of PostScript, one built specifically to be viewed and shared on screen rather than only printed, which he initially called Interchange PostScript (IPS).

The vision, in Warnock's own words at the time, was almost disarmingly simple: imagine sending a complete document — full text and graphics — over an electronic network, and having it open, looking identical, on any machine, running any operating system. In 1991, before the web was mainstream and most email was still plain text, that wasn't an obvious idea. It was a genuinely new one.

Warnock didn't just write the memo and hand it off. He personally led the Camelot team, staying closely involved for years as the idea moved from a rough internal proposal toward an actual, shippable product — no small task, since it required solving several hard problems simultaneously: how to compress documents enough to be practical to share, how to embed fonts directly inside a file so text would never again depend on what happened to be installed on the receiving computer, and how to design a file structure flexible enough to add new capabilities for decades to come without breaking everything that came before it.

The project's name changed twice before the world ever saw it. Camelot became the internal codename for the early development effort, but as the product took shape, Adobe renamed it Carousel. That name lasted until the team discovered Kodak had already registered it for their own products — a genuinely inconvenient collision this late in development. So the format got its third and final name, one meant to suggest skill and strength: Acrobat. Documents built with it, meanwhile, kept the name that actually described what they did — Portable Document Format, or PDF for short. (One small piece of trivia survives from the Carousel days: for years, the four-letter Mac file type code for a PDF was simply "CARO.")

After roughly two years of development, Adobe Acrobat 1.0 — and with it, The PDF itself — launched on June 15, 1993. Adobe backed the release with real confidence: an eight-page advertisement in the Wall Street Journal, a genuinely large bet for a document format nobody outside the industry had heard of yet.

The Full Timeline: From Memo to Global Standard

The short version of PDF's story fits in a paragraph. The real version took thirty years, several near-death moments, and one company voluntarily giving up exclusive control of a format it had every reason to keep locked down. Here's the whole arc.

Notice how much of that timeline happened after PDF stopped being Adobe's private property. That's not a coincidence — it's close to the entire reason PDF is still the default today, and it's worth slowing down on before moving to how the format actually works under the hood.

How a PDF Actually Works

You don't need to understand the internals of PDF to use one, the same way you don't need to understand internal combustion to drive a car. But the "why" behind PDF's most useful properties actually makes a lot more sense once you know roughly what's happening inside the file — and it explains a few things people assume are true about PDFs that actually aren't.

PDF's foundation is PostScript, Adobe's page-description language originally built for printers. A PostScript file isn't really a document in the way a Word file is — it's closer to a small program: a precise set of instructions describing exactly what to draw, and exactly where. Move to this coordinate. Draw a line to that one. Place this letter, in this font, at this exact position. A printer receiving PostScript doesn't have to guess how to lay out a page; it's simply told, unambiguously, step by step.

PDF takes that same fundamentally instruction-based approach and adapts it for screens rather than only printers, then wraps it in a self-contained file structure with a few genuinely important additions:

• Embedded fonts. A PDF can carry the actual font files it needs inside itself. This one feature alone solved most of the "it looks different on my computer" problem that made document sharing so unreliable before PDF existed — the text no longer depends on what fonts happen to be installed on whatever device opens the file.
• A structured object system. Internally, a PDF is a collection of individually addressable "objects" — text blocks, images, fonts, page definitions — referenced through a cross-reference table that lets a viewer jump directly to any part of the document without reading the whole file from the start. This is part of why you can open page 400 of a huge PDF almost instantly.
• Built-in compression. Modern PDFs use several compression schemes (Flate for general content, JPEG or JPEG 2000 for photographic images) to keep file sizes manageable despite embedding fonts and high-quality graphics directly in the file.
• An extensible structure. Warnock's team specifically designed the format so new capabilities — encryption, digital signatures, interactive forms, accessibility tagging — could be added over three decades without breaking documents built under the original 1993 specification. A PDF made this year still opens correctly in software built for the 1990s spec, and vice versa in most cases.

That last point is easy to undervalue, but it's a genuinely rare achievement in software. Most file formats either stay frozen to avoid breaking compatibility, or evolve and leave older files behind. PDF has spent thirty years doing neither.

Becoming a Global Standard: Why Adobe Gave PDF Away

For its first fourteen years, PDF was technically Adobe's proprietary format. The specification was published openly — anyone could read exactly how a PDF was structured — but Adobe controlled its direction, and in principle could have changed course at any time. That's a genuinely uncomfortable position for a format that thousands of governments, banks, and courts were beginning to build permanent record-keeping around. Betting your organization's document archive on a format one company could change or deprecate at will is a real risk, not a theoretical one.

Adobe resolved that risk directly. In January 2007, the company formally donated its PDF 1.7 specification to the International Organization for Standardization. Through ISO's "fast-track" process, that specification was published as ISO 32000-1:2008 in July 2008 — and from that point forward, PDF was no longer Adobe's to unilaterally change. Control passed to an ISO technical committee made up of volunteer experts from across the industry, and Adobe simultaneously published a public patent license, granting royalty-free rights to every patent it held that was necessary to build fully PDF-compliant software.

That combination — an open specification plus a royalty-free patent grant — is what actually made PDF safe to build a global document infrastructure on top of. Nobody had to trust Adobe's future intentions anymore. They just had to trust an open, published standard, the same way engineers trust standards for screw threads or shipping containers: not because any one company promises to behave, but because the specification itself is public, stable, and no longer owned by a party with a commercial incentive to change it unfavorably.

The process didn't stop there. In 2020, ISO published ISO 32000-2:2020 — what's commonly called PDF 2.0 — and it holds a distinction none of the versions before it can claim: it's the first PDF specification developed entirely under the ISO process, with no Adobe authorship at all. The format that started as one executive's internal memo had, by 2020, become something no single company controlled in any sense.

The PDF Family You've Probably Never Heard Of

"PDF" isn't really one single thing anymore — it's a base standard with several specialized dialects built on top of it, each locking down or extending the core format for a specific job. You've almost certainly used files built to these standards without ever seeing their names.

Every one of these builds on the same ISO 32000 foundation rather than reinventing anything from scratch — which is exactly the extensibility Warnock's original design made room for. A government archive using PDF/A and a print shop using PDF/X are, underneath, using the same fundamental format, just with different rules layered on top for their specific needs.

Why PDF Won, When Plenty of Competitors Tried

PDF was never the only company trying to solve the document-portability problem. Over the years, several genuine competitors made real attempts to unseat it — some backed by companies just as large as Adobe. None of them managed to displace PDF as the default. A few reasons explain why, and they're worth understanding because they're not really about marketing at all.

It became free to open, everywhere, immediately. Adobe's decision to give away the PDF reader while still charging for creation tools meant there was never a barrier on the receiving end. You never had to ask whether someone could open what you sent them — a genuinely underrated advantage that compounds every single time a document changes hands.

It became truly open at exactly the right moment. By 2008, businesses, governments, and courts needed to commit to a format for permanent records. An open ISO standard, with a royalty-free patent license, was simply a safer long-term bet than any proprietary alternative — and PDF became that safe bet before most competitors had matured enough to be considered at all.

It solved printing and screens at the same time. Many rivals optimized for one or the other. PDF's PostScript ancestry meant it was print-accurate from day one, while its structure adapted cleanly to on-screen viewing — a combination that mattered enormously in an era when most important documents still ended up printed eventually, even after being shared digitally.

It kept adding capability without ever starting over. Forms, digital signatures, encryption, accessibility tagging, 3D models — PDF absorbed all of it into the same extensible structure, decade after decade, without forcing anyone to abandon existing PDFs or relearn the format. Competitors that required a clean break from what came before consistently lost momentum against a format that never asked users to start from zero.

It never depended on one company's continued success. This is easy to miss, but it matters more than almost anything else on this list: once PDF became an ISO standard, its survival stopped being tied to Adobe's business decisions. A proprietary format lives or dies with the company that owns it — if that company pivots, gets acquired, or simply loses interest, everything built on that format is stranded. PDF, by 2008, had no such single point of failure. Governments, courts, and archives could commit to it for the next fifty years without betting on any one company's roadmap.

The PDF Today: Quietly Running Everything

It's genuinely hard to find a sector that doesn't run on PDF at this point. A few places where it's become so standard it's practically invisible:

• Government and public services. Tax forms, certificates, exam admit cards, official notices — almost universally distributed as PDF, precisely because a government needs a document that looks legally identical to every citizen who opens it.
• Law. Contracts, filings, and court documents rely on PDF's fixed layout as part of their legitimacy — a contract that could silently reflow would undermine the very idea of a signed, fixed agreement.
• Academia. Research papers, theses, and textbooks are published almost exclusively as PDF, valued for consistent citation formatting and long-term archival stability.
• Business. Invoices, reports, and proposals move as PDF specifically because a spreadsheet or word processor file can be too easily altered — intentionally or not — after it's sent.
• Publishing. Ebooks, manuals, and print-ready files rely on PDF/X and PDF/A to guarantee a design looks the same on a reader's screen as it did on the designer's.

What ties all of these together isn't convenience, exactly — it's trust. Every one of these situations needs a document that can't quietly change after it leaves someone's hands. That's not a minor feature. It's the entire reason The PDF was invented in the first place, thirty-plus years later, still doing precisely the job it was built for.

The Newest Chapter: Who Actually Gets to Touch Your PDF

PDF's story didn't end when it became an ISO standard — it just entered a new phase, one that's arguably still being written. For most of PDF's history, actually doing anything to a PDF — compressing it, merging two together, unlocking a password, converting it — meant one of two things: expensive desktop software, or uploading your file to an unfamiliar website and hoping for the best.

That second option quietly became the norm for millions of people, and it introduced a problem nobody was really talking about: every time you "used a free online PDF tool," your actual document — sometimes a bank statement, a signed contract, a medical form — was leaving your device and landing on someone else's server. Maybe it was deleted immediately afterward. Maybe it wasn't. Most people had no real way to know, and most tools never told them either way.

The most recent shift in PDF's story is a direct response to that gap: the rise of tools that process your file entirely inside your own browser, using the same WebAssembly and JavaScript technology that powers modern web apps, without ever transmitting the file anywhere. The compression, splitting, merging, translating, and redacting all happen locally, on your own device, the same way it would in desktop software — except with nothing to install and nothing to upload.

It's a fitting continuation of the same idea Warnock started with in 1991: a document that behaves consistently and predictably, without asking you to trust an unknown middleman along the way. This site — The PDF Mechanic — is built entirely on that model, which is worth being direct about, since it's genuinely the reason it exists: every tool here, from compression to password protection to translation, runs on your device, not a server somewhere you'll never see.

Actually Working With a PDF: The Practical Side

History and standards aside, most people land on a page like this one because they have an actual PDF in front of them and a specific problem to solve. Here's the practical landscape, since the format's flexibility means "working with a PDF" can mean a dozen genuinely different tasks.

Opening a PDF

Every modern browser — Chrome, Firefox, Safari, Edge — opens PDFs natively, with no extra software required. Dedicated readers like Adobe Acrobat Reader add extra functionality (annotation, form filling, more advanced printing controls) but are no longer strictly necessary just to view a file, which is a genuinely recent and welcome development in the format's history.

Creating a PDF

Almost any modern application can export directly to PDF — word processors, spreadsheet software, design tools, and web browsers (printing a webpage "to PDF" is one of the most common creation methods today, and didn't exist as an option for most of PDF's history). For scanned paper documents, a scanner or phone camera app typically saves directly to PDF as well, though as covered earlier, that output starts as an image, not searchable text, unless OCR is applied afterward.

The Most Common Things People Actually Need to Do

In practice, a small set of tasks covers the overwhelming majority of real-world PDF needs:

• Reducing file size — for emailing, uploading to a portal with strict size limits, or simply saving space, typically by re-encoding embedded images at a lower resolution.
• Combining or splitting pages — merging several documents into one file, or pulling specific pages out of a longer one, both of which rely on the object-based structure covered earlier: individual pages can be copied between files without re-rendering anything.
• Converting to and from other formats — turning a PDF into an editable Word document, or a spreadsheet into PDF, bridging the gap between PDF's fixed layout and formats meant to be actively edited.
• Adding or removing password protection — PDF's encryption, built into the format since its earliest versions, controls who can open a file or what they're permitted to do with it once it's open.
• Filling and locking forms — PDF has supported genuinely interactive form fields since the mid-1990s, and "flattening" a filled form converts those answers into permanent page content that can no longer be accidentally changed.
• Extracting content — pulling embedded images, tables, or specific text back out of a PDF for reuse elsewhere, treating the file as a source rather than a final destination.

What's genuinely changed over the last few years isn't the tasks themselves — people have needed to compress and merge PDFs since the format existed — it's where that work happens. The same task that once required installing desktop software, or trusting an unfamiliar website with a sensitive file, can now run entirely inside a browser tab, on your own device, using nothing more than the browser you already have open.

PDF vs. Everything Else: When to Actually Use It

PDF isn't the right choice for every situation — it was never meant to be, and knowing when to reach for something else is as useful as knowing PDF's history.

PDF vs. Word (.docx). Word documents are built to be edited; that's their entire purpose. Use Word while a document is still being actively drafted, reviewed, or collaborated on. Convert to PDF once it's finished and needs to be shared, signed, printed, or archived — the moment editability stops being useful and consistency starts mattering more.

PDF vs. image formats (JPG, PNG). An image file is just a picture — a scanned receipt saved as a JPG has no text layer, no page structure, no way to add more pages later. PDF adds structure images alone don't have: multiple pages in one file, real (or OCR'd) selectable text, and metadata like a title and author. A scanned document belongs in a PDF, not left as a folder of loose image files.

PDF vs. HTML / web pages. A web page is intentionally fluid — it reflows to fit whatever screen it's displayed on, which is exactly right for browsing but exactly wrong for anything that needs to look identical for every reader, like a legal notice or an official form. PDF trades that flexibility for guaranteed consistency, which is precisely the trade-off documents like contracts and certificates need.

PDF vs. spreadsheets (.xlsx). A spreadsheet is a working tool — formulas, sortable data, ongoing calculation. A PDF is a snapshot. Export a finished report or invoice from a spreadsheet to PDF specifically so the numbers can't be accidentally recalculated or edited after the fact by whoever receives it.

PDF vs. presentations (.pptx). A slide deck is built for editing and presenting live, with speaker notes and animations that only make sense inside presentation software. Once a deck is finalized and needs to be distributed as a handout or read-only reference — sent to people who weren't in the room — converting it to PDF locks in exactly what was presented, without depending on the recipient having the same presentation software installed at all.

The pattern across every comparison is the same: reach for PDF at the exact moment a document is done — the point where you want it to stop changing and start being reliably, permanently readable, by anyone, on anything, forever. That's the one job PDF has always done better than any format built before or since.

PDF Security: What's Actually Built Into the Format

Because so many important documents ended up as PDFs — contracts, financial records, medical files — security stopped being optional fairly early in the format's history. What's genuinely built into the specification is more substantial than most people realize.

Encryption: Two Different Passwords, Two Different Jobs

PDF's encryption system, part of the format since its early versions, actually supports two separate passwords doing two separate jobs — a distinction most people never learn because most tools only ever ask for one.

A user password controls whether the file can be opened at all. Without it, the document is unreadable, full stop. An owner password, by contrast, controls what someone can do after opening a file they're otherwise allowed to read — restricting printing, copying text, or further editing, independent of whether an open password exists at all. A PDF can use either one alone, both together, or neither. Modern PDF encryption uses AES-256, the same encryption standard used to protect classified government information, which is a considerably higher bar than the weaker encryption early PDF versions shipped with in the 1990s.

Digital Signatures: More Than a Scanned Signature Image

A genuine digital signature in a PDF isn't a picture of someone's handwriting pasted onto a page — that's just a visual signature, which proves nothing on its own. A real digital signature uses cryptography to verify two specific things: that the document was signed by whoever holds a particular private key, and that the document hasn't been altered by even a single byte since the moment it was signed. Change one character after signing, and the signature verification fails immediately, visibly, in any PDF reader capable of checking it. This is precisely why digitally signed PDF contracts hold up as legal evidence in ways that an emailed Word document with a typed name never quite can.

Redaction: Where Most People Get It Wrong

This deserves repeating from earlier, because it's genuinely one of the most consequential misunderstandings about PDF still in circulation: covering text with a black rectangle is not redaction. It's decoration. The underlying text object is still sitting there in the file, completely intact, waiting to be selected, copied, or extracted the moment someone knows to try — and people who need documents redacted, whether for legal, medical, or government purposes, have learned this the hard way often enough that it's a well-documented category of embarrassing, sometimes serious, disclosure failure.

Actual redaction has to remove the underlying content, not just obscure it visually — typically by rebuilding the affected page entirely, with the sensitive content genuinely gone rather than merely covered. It's a small technical distinction with enormous real-world consequences, and it's exactly the kind of detail that separates a PDF tool built by people who understand the format from one that simply looks like it works.

Common Misconceptions About PDF, Cleared Up

PDF is so ubiquitous that a lot of confidently-held assumptions about it have built up over the years — some of them genuinely wrong, and worth correcting properly.

"PDF is an Adobe product." Not since July 2008. It's an ISO standard, maintained by an international technical committee, with a royalty-free patent license from Adobe covering the whole thing. Adobe makes excellent PDF software, but so do hundreds of other companies and open-source projects, all building against the exact same public specification.

"You need Adobe Acrobat to open a PDF." Every major web browser has built-in PDF viewing today, no separate software required at all. Reading a PDF requires nothing beyond what's already on virtually every device made in the last decade.

"All PDFs contain searchable text." Only born-digital PDFs do, by default. A scanned PDF is fundamentally a picture until OCR is specifically applied to add a text layer — which is why searching inside some PDFs works instantly and others turn up nothing at all, even when the words are clearly visible on the page.

"A PDF can't be edited." It can — the file format itself doesn't prevent editing any more than a photograph format prevents someone from opening it in an image editor. What actually protects a PDF from casual editing is either a password specifically set for that purpose, or simply the fact that most people don't have — or don't bother opening — the software to do it easily.

"Redacting a PDF means covering text with a black box." Genuinely, no — and this misconception has caused real, embarrassing leaks over the years, including in official government and legal documents. Drawing a shape over text in a PDF doesn't delete the text underneath it; it just visually covers it, and that "hidden" text is often still fully selectable and extractable. Real redaction has to actually remove the underlying content, not just obscure it — which is exactly the distinction a properly built redaction tool has to get right.

"A bigger PDF means a higher-quality document." Not reliably. File size in a PDF is driven almost entirely by what's embedded inside it — high-resolution scanned images, uncompressed photos, unnecessarily large embedded fonts — rather than by the quality of the actual content. A ten-page text-only report might be a few hundred kilobytes; a single scanned photo saved at unnecessarily high resolution can outweigh it by a factor of a hundred, without the resulting document being any more useful to read.

What's Next for The PDF?

Thirty-plus years in, PDF isn't coasting on inertia — the standard is still actively evolving, largely in three directions.

Accessibility is becoming non-negotiable. PDF/UA, and the tagged-PDF structure it relies on, is increasingly required by law rather than treated as an optional nicety — several countries now mandate accessible PDF for government and public-facing documents, pushing the entire ecosystem toward documents that genuinely work with screen readers, not just ones that happen to render visually correctly.

Processing is moving off servers and onto devices. As covered above, this is arguably the most significant practical shift happening in the PDF world right now — the same privacy-driven move toward local, client-side processing that's reshaping other categories of software is reshaping how people interact with PDF tools specifically.

The specification keeps absorbing new document needs. Since PDF 2.0 in 2020, the ISO committee has continued refining encryption standards, 3D and geospatial support, and structural tagging — the same pattern of careful, backward-compatible extension that's defined the format since Warnock's original design brief in 1991.

What seems unlikely, even looking forward, is any of this displacing PDF outright. The format's core promise — a document that looks the same everywhere, forever — hasn't stopped being valuable, and nothing else on the market has managed to make that same guarantee as thoroughly, for as long, while remaining genuinely open to anyone who wants to build on it.

The PDF: Fast Facts

A format invented by one person's memo, delayed by its own price tag for half a decade, and ultimately made permanent by a company choosing to stop owning it — that's an unusually specific set of events for something now this quietly universal.

Frequently Asked Questions About The PDF

The Short Version

A tired executive at Adobe looked at a genuinely broken problem — documents that fell apart the moment they left the computer that made them — and spent two years building a fix nobody had quite managed before. It nearly failed in its first five years. It succeeded, decisively, once Adobe gave away the one thing that mattered most: the ability for anyone, anywhere, to simply open what they were sent. And it became something bigger than any one company the moment Adobe let it go entirely, handing a format used by billions of people to an open standard nobody controls alone.

That's The PDF: not a coincidence, not an accident of timing, but a specific, deliberate answer to a specific, painful problem — one that turned out to matter for a lot longer, and a lot more universally, than anyone involved in a 1991 internal memo could have reasonably guessed. Thirty-plus years later, the problem it solved hasn't gone away, and neither has the format built to solve it.