Skip to content

Learning centre

What is a PDF? How the format works and why it lasts

A plain-English guide to the Portable Document Format: what is inside a PDF file, why it looks the same everywhere, and the PDF/A and PDF/UA variants.

By the PDF365 editorial teamUpdated 7 min read

PDF stands for Portable Document Format. It was created by Adobe in the early 1990s to solve a simple, stubborn problem: a document that looked perfect on one computer often looked broken on another, because the other computer had different fonts, a different screen or a different printer. A PDF fixes the appearance of every page so it looks the same wherever it’s opened.

A brief history

Adobe released the format in 1993 alongside the first version of Acrobat. For years it was Adobe’s own specification, although it was published openly so other companies could build compatible software. In 2008 PDF became an international standard, ISO 32000-1, and its development passed to the International Organization for Standardization. PDF 2.0 (ISO 32000-2) followed in 2017. That independence is one reason PDF is trusted for contracts, court filings and government records: no single company controls it.

What is actually inside a PDF file?

Open a PDF in a text editor and you’ll see a mixture of readable words and what looks like noise. Underneath, a PDF is a collection of numbered objects: pages, fonts, images, text instructions and so on. Four parts hold it together:

  • The header, a short line such as %PDF-1.7 that tells software which version of the format to expect.
  • The body, containing every object. Page content is stored as a compact list of drawing instructions: move here, set this font, draw these characters, fill this shape.
  • The cross-reference table, an index recording where each object starts, so a viewer can jump straight to page 400 without reading the first 399.
  • The trailer, which points to the start of the document structure and, if the file is encrypted, to the encryption settings.

Because pages are described as precise instructions rather than flowing text, a PDF behaves more like a printed sheet than a word-processing document. That’s why changing a sentence in a PDF is difficult: there’s no paragraph to reflow, just characters placed at exact positions.

Why a PDF looks the same everywhere

The main reason is font embedding. A PDF can carry the fonts it uses, or just the characters it needs from them (a “subset”), so the reader’s computer doesn’t need to have them installed. Images are stored at their own resolution, and colours can be tied to colour profiles that describe exactly what each value means. The result is a document whose layout is locked.

Specialist types of PDF

Several ISO standards define stricter flavours of PDF for particular jobs:

VariantPurposeKey rules
PDF/ALong-term archivingAll fonts embedded, no encryption, no reliance on external content
PDF/UAUniversal accessibilityContent must be tagged so screen readers can follow it
PDF/XProfessional printingStrict colour management and trim boxes for print shops

Most everyday PDFs don’t follow any of these, and that’s fine. They matter when an organisation asks for a specific variant, for example a court or an archive.

What PDFs are good and bad at

PDF is excellent for documents that must look a particular way: forms, invoices, reports, tickets, CVs and anything you plan to print. It’s less good for content that needs to adapt to small screens, because pages don’t reflow, and for documents that several people will keep editing, where a word-processing format is easier.

Most common tasks don’t need specialist software. You can combine files, rearrange pages or reduce the file size in a browser. Understanding the structure above also explains some limits you may meet: tools that copy pages into a new file can’t always carry over document-wide features such as bookmarks, because those live outside the pages themselves.

Tools mentioned in this guide