PDF won because it made one promise and kept it: the page looks the same everywhere, on any machine, indefinitely.
The problem it solved
In 1990 sending a document to someone else meant hoping they had your software, your fonts and your printer driver. They usually did not, and the document arrived reflowed, re-substituted and repaginated.
Adobe's answer was to stop sending the document and send the finished page instead — a description of exactly what to draw and where, with the fonts included. The receiving machine needs no knowledge of the software that made it.
That is the whole design, and every characteristic follows from it. Pages look identical everywhere, which is why it won. Text does not reflow and is awkward to edit, which is the same property viewed from the other side.
A short history worth knowing
| Year | What happened |
|---|---|
| 1993 | PDF 1.0 and Acrobat launch — both paid, adoption slow |
| 1994 | Acrobat Reader becomes free; this is what made it win |
| 2001 | PDF/X standardised for print production |
| 2005 | PDF/A standardised for archiving |
| 2008 | Adobe releases PDF as ISO 32000; it stops being proprietary |
| 2012 | PDF/UA standardised for accessibility |
| 2017 | PDF 2.0 (ISO 32000-2), the first Adobe-independent revision |
The 1994 decision to make the reader free is the one that mattered. A format is only portable if everyone can open it, and charging for the reader would have made it another proprietary dead end.
The variants and what each is for
These are restricted subsets, not different formats. A PDF/A file is a valid PDF that has agreed to certain rules — and to forgo certain features.
- PDF/A — archiving. Everything needed to render must be embedded, so no external font or colour profile dependencies. Forbids JavaScript, encryption and external links. The point is that it will still render correctly in fifty years.
- PDF/X — print production. Requires embedded fonts and a defined colour space, mandates trim and bleed boxes, forbids transparency in some versions. What a commercial printer will ask for.
- PDF/UA — accessibility. Mandates the tag tree, reading order and alt text described in how to make an accessible PDF.
- PDF/E — engineering. For technical drawings, with 3D geometry support.
- PDF/VT — variable data printing. Personalised mail merges at volume.
You can generally ignore all of these until someone asks. When a printer says "send it as PDF/X-4" or an archive says "PDF/A-2b", that is a specific export preset in the software that made the file, not a conversion you do afterwards.
What a PDF can do that people forget
The format is far more capable than the static page most people use.
It supports interactive form fields, embedded file attachments, layers that can be toggled, JavaScript, digital signatures, embedded video and audio, 3D models, and internal and external links.
The catch is support. Acrobat implements most of it; browser viewers implement very little; mobile readers less again. Embedded video is the clearest example — it is in the specification, it works in Acrobat, and it will not play for most of the people you send the file to. Build for the reader your audience actually uses, which for anything public means a browser.
What it is bad at
Worth stating plainly, because it is chosen for jobs it does badly.
- Reading on a phone. A fixed A4 page on a six-inch screen cannot reflow. EPUB or HTML is the right format for reading.
- Editing. No paragraphs to reflow, so every edit is a workaround — see why you cannot edit a PDF.
- Collaboration. Annotations work; simultaneous editing does not.
- Structured data. A table in a PDF is text positioned to look like a table, with no cells — the reason extraction is unreliable.
- Accessibility by default. Possible with tagging, absent without it.
The honest rule: PDF when the layout must be identical everywhere and permanent. Something else when the words matter more than the page. Sending a colleague a PDF to edit is choosing the one format designed to resist it.
Frequently asked questions
What does PDF stand for?
Portable Document Format. Adobe created it in 1993, and it has been an open ISO standard — ISO 32000 — since 2008, so it is no longer proprietary.
Why is PDF so widely used?
Because it describes a finished page rather than a reflowable document, so it renders identically on any machine regardless of software, fonts or printer. Making the reader free in 1994 is what turned that property into universal adoption.
What is the difference between PDF/A and PDF/X?
PDF/A is for archiving — everything needed to render must be embedded so the file still works decades later, and it forbids JavaScript and encryption. PDF/X is for print production, requiring a defined colour space and trim and bleed boxes.
Do I need PDF/A?
Only if an archive, a court or a regulator asks for it. It is an export preset in whatever created the file, not a conversion applied afterwards. For everyday documents an ordinary PDF is correct.
Can a PDF contain video?
Yes, the specification supports embedded video and audio. Whether it plays is another matter — Acrobat handles it, most browser and mobile viewers do not. For anything public, assume it will not play and link to the video instead.
When should I not use PDF?
When the words matter more than the layout. For reading on a phone, EPUB or HTML reflows and PDF cannot. For collaborative editing, use a document format. For data, use CSV — a PDF table has no cells, only text positioned to look like one.