You're three rounds into editing a Word doc that someone insists on calling 'the PDF'. You're fighting Acrobat to change a paragraph. You wish someone had explained when to use PDFs and when not to.
Here is that explanation.
PDFs are for finals, not drafts
The PDF format is designed for finished documents — fixed layout, no further editing expected. People misuse it by trying to draft in PDF, which means fighting the format the whole way.
Drafts belong in Word, Pages, Docs, Notion. Convert to PDF only when the document is final. Edit a PDF when truly needed, but think of it as a finishing pass, not a drafting surface.
PDFs are for distribution, not editing
If a document will be edited collaboratively, it shouldn't be a PDF. PDFs are what you send when the editing is done. When you receive a 'PDF for review', what you usually want is the underlying editable document.
The lazy compromise — emailing a PDF and asking for 'comments back' — creates worse versions of both editing and distribution.
PDFs are for fixed layout, not flexible content
A PDF preserves layout: positions, fonts, page breaks. That's its job. People misuse PDF when the content is naturally flexible (tabular data that grows, lists that change, reference material that updates).
For flexible content, use a tool that supports it (spreadsheets, databases, wikis). PDF the snapshot when you need an archived version.
PDFs are for archives, not active work
An active document — one you'll touch in the next month — should be in its native editable form. A PDF is what you produce at the end of active work, for archiving or distributing.
The test: 'Will I edit this again?' If yes, keep it in the source format. If no, convert to PDF and archive.
PDFs are for sharing, not storing
Sometimes people store PDFs they could store as the source files. This compounds when the source is also stored elsewhere — now there are two artefacts to keep in sync. Store one canonical source; produce PDFs on demand.
For everything you've truly finished, the PDF is the archive. For active sources, archive the source and re-export when needed.
FAQ
What about PDF forms with editable fields?
Legitimate use of PDF — interactive forms with fixed layout but fillable fields. Different from 'editing a PDF', which usually means changing the underlying layout or text.
Is sending a PDF for review always wrong?
Not wrong, just often inefficient. If you genuinely want only feedback (no edits), PDF is fine. If you want substantive edits, send the editable source.
What about long-term archive?
PDF/A is the proper format for long-term archival. Standard PDFs are also durable but PDF/A is the gold standard for compliance archives.
Should every final document become a PDF?
Most. Some genuinely belong as static HTML, others as printed paper, but for portable, fixed-layout deliverables, PDF is the right default.
PDFs are powerful when used as designed. Use Flint for the finishing pass and feel the workflow click into place.