PDF is one of those file types everyone uses and almost nobody could actually define. Here's the plain-English version, without the standards-committee jargon.
By the end you'll know what's inside one of these files, why the format behaves the way it does, and when to reach for a PDF instead of the alternatives โ which is most of the time, once the reasoning is clear.
PDF stands for Portable Document Format
Adobe created it in the early 1990s to solve one specific problem: a document that looked right in one program, on one computer, often looked wrong โ different fonts, different spacing, shifted page breaks โ when opened somewhere else. A PDF fixes that by embedding everything it needs (fonts, layout, images) directly into the file itself, so it renders identically wherever it's opened.
The problem it solved was everywhere at the time. Offices traded documents between machines that agreed on almost nothing โ different operating systems, different font sets, different printer drivers, each with its own opinion about where a line should break. Documents arrived subtly (or grossly) mangled: a two-page letter spilling onto a third page, bullets becoming question marks, tables collapsing. The fix wasn't a better word processor; it was a format that carried its own appearance with it. Think of it as digital paper: the file is the finished page, not a recipe for reconstructing one.
What's actually inside a PDF file
Under the hood, a PDF is a collection of objects โ pages, fonts, images, and drawing instructions โ cross-referenced so a reader program can find each piece quickly. A page doesn't contain a paragraph in the word-processor sense; it contains instructions like "place this glyph at this exact position" along with whatever font that glyph needs. The layout isn't computed when the file opens; it was decided when the file was created.
That one design choice explains most of what people notice about PDFs, good and bad. The good: identical rendering everywhere, forever โ the file travels with everything it needs. The bad: editing is structurally awkward, because there are no paragraphs to flow โ just positioned marks. When you select what looks like a sentence in a PDF reader, the reader is reconstructing a sentence from placed glyphs after the fact.
One wrinkle worth knowing: not every PDF page contains text instructions. A scanned page is just a full-page image โ a photograph of text stored inside a PDF container. It looks identical but contains no characters at all, which is why you sometimes can't select or search a PDF. (That's fixable โ OCR adds a real text layer back in โ but it explains the mystery of the unselectable document.)
Why that matters more than it sounds like it should
Send someone a Word document and the result depends on what software they have, what fonts are installed, even what operating system they're on โ the layout can genuinely shift. Send them a PDF and what you designed is what they see, full stop. That reliability is the entire reason PDFs became the default for contracts, invoices, forms, and anything else where "it has to look right" actually matters.
It also explains the format's role in workflows where order is the point. A signed contract has to be the same document for both parties, page for page, with signatures on the pages they were signed on. A court filing has to match its paper original. An invoice has to print identically on any office printer. In each case the format's stubbornness โ its refusal to reflow, substitute, or "helpfully" reformat โ isn't a limitation; it's the feature being paid for.
PDF vs. other formats
A Word document (.docx) is meant to be edited โ it's a working file. A PDF is meant to be the finished, final version โ locked down on purpose. An image (JPG/PNG) can only ever be one flat picture; a PDF can hold multiple pages, real selectable text, embedded fonts, and even interactive form fields, none of which a plain image format supports.
The practical rule that falls out of this: work in the editable format, deliver in the fixed one. Draft the report in Word or Google Docs where revision is easy; convert to PDF at the moment it leaves your hands. The same logic runs in reverse โ when a PDF arrives and needs real editing, the pragmatic move is converting it back to an editable format rather than fighting the fixed layout.
Variants you'll meet in the wild
- Regular PDFs โ the overwhelming majority. Text and graphics, opens anywhere.
- Scanned PDFs โ images of pages, no text inside. Searchable once OCR'd.
- PDF forms โ pages with fillable fields (the boxes you type into). "Flattening" a filled form bakes the answers into the page so they can't be edited afterward.
- Password-protected PDFs โ encrypted so a password is required to open them, or to lift restrictions on printing and copying.
- PDF/A โ an archival subset of the standard, designed for documents that must remain readable for decades; archives, governments, and regulated industries specify it.
They're all PDFs โ the same container, different features switched on. Every variant is workable with the right tool, which is the other thing a format this ubiquitous guarantees: an enormous ecosystem of software that speaks it.
Can you edit a PDF?
Yes, though it goes against what the format was originally built for. Modern tools can add text, annotations, and shapes directly onto a PDF, or extract its content back into an editable format like Word. If you need to genuinely rewrite a PDF's content, Edit PDF handles direct annotation; if you'd rather work in a familiar word processor, PDF to Word converts it to an editable document first.
The honest framing: a PDF is a snapshot, and editing a snapshot is always a little more effort than editing the live scene. It's doable โ reorganizing pages, redacting content, adding signatures and watermarks are all routine โ but if a document still needs heavy revision, the cleanest path is usually back to its source format until it's truly final.
Where to start
If you're new to working with PDFs day-to-day, the three most common needs are combining files, splitting one apart, and shrinking a file that's too large โ all covered on the PDFlyHQ homepage, along with everything else.