keepcalculator

06 Numbers and Powers

PDFs Must Die: What Can Replace Them?

Card No. 06·83753 · Updated · Standard formula, shown below

The short answer: nothing fully replaces PDFs yet, but for most everyday document tasks, HTML, Markdown, and collaborative cloud documents (like Google Docs or Notion) are superior. You should switch to those formats when you need live editing, version control, or accessibility, and keep PDFs only for final, print-ready output.

Why PDFs Are So Frustrating

The PDF (Portable Document Format) was invented by Adobe in 1993 to solve a real problem: making documents look identical on any computer. Before PDFs, sending a file meant risking that fonts, margins, and images would shift or break on the recipient’s machine. PDFs fixed that by locking the layout into a fixed page image.

But that same fix is now the source of the pain. A PDF is essentially a snapshot of a page. It doesn’t flow like a web page, it doesn’t reflow on a phone screen, and it doesn’t know what a paragraph is. That leads to the classic frustrations:

  • Editing is a nightmare: You can’t just click and type. You need dedicated software, and even then, changing one line can break the whole layout.
  • Copying text is unreliable: Text is often stored as vector outlines or embedded fonts that don’t map cleanly to Unicode, so pasting gives you gibberish or missing characters.
  • Accessibility is poor: Screen readers struggle with PDFs that lack proper tags, and many PDFs are just scanned images with no text layer at all.
  • Version control is nonexistent: You email a PDF, someone edits it, emails it back, and now you have two different versions with no way to merge.

The Real Alternatives: HTML, Markdown, and Cloud Docs

Three formats cover most of what people actually need from a document. They each solve the core problems of PDFs: editability, accessibility, and versioning.

  • HTML: The web’s native format. It reflows on any screen, is fully accessible when built correctly, and is trivial to edit with any text editor. You can print to PDF from a browser when you need a fixed layout.
  • Markdown: A plain-text format that’s easy to read and write. It converts to HTML, PDF, or Word documents. It’s ideal for notes, documentation, and any text that doesn’t need complex layout. Tools like Pandoc convert Markdown to PDFs (via LaTeX) when you need the fixed output.
  • Cloud documents (Google Docs, Notion, etc.): These are live, collaborative, and always up-to-date. They handle comments, suggestions, and version history natively. They’re the best choice for anything that is still being written or reviewed.

When PDFs Are Still the Right Choice

Don’t throw out PDFs entirely. There are cases where a fixed layout is exactly what you need:

  • Print-ready files: If you’re sending a file to a printer, you need exact page dimensions, margins, and color profiles. PDF is the industry standard.
  • Legal and official documents: Contracts, tax forms, and government documents often need to be immutable and look identical everywhere. PDFs provide that.
  • Archiving: PDF/A is a specialized PDF standard for long-term preservation. It embeds all fonts and metadata, ensuring the document remains readable decades later.
  • Forms that must be printed: Some forms are still designed for paper. A PDF with fillable fields is the only way to make that work digitally.

How to Choose the Right Replacement

Ask yourself two questions: Is the document still being worked on? and Does it need to look exactly the same everywhere?

  1. If it’s a draft or a work in progress: Use a cloud doc or Markdown. You want live collaboration, comments, and version history.
  2. If it’s a final report or a document that will be read on screens: Use HTML or a cloud doc. Readers will appreciate the reflowable text and the ability to zoom without panning.
  3. If it must be printed or filed as-is: Use PDF. Export from your source format (Word, Google Docs, LaTeX) to PDF as the final step.
  4. If it’s a long-form document with complex layout (books, manuals): Use a proper typesetting system like LaTeX or InDesign, and export to PDF for distribution. The source is editable; the PDF is the output.

Common Problems and Misconceptions

One common misconception is that PDFs are secure. A PDF can be password-protected or encrypted, but that doesn’t make it tamper-proof. Anyone with the password can edit it, and there are tools to remove passwords. For true immutability, you need digital signatures or a blockchain-style hash, not just a PDF.

Another issue is that PDFs are often used for web content, which is a mistake. Posting a PDF on a website means the reader has to download it, open it in a separate app, and zoom in and out. A simple HTML page loads instantly, is searchable, and works on any device. If you’re putting a document online, convert it to HTML first.

Finally, there’s the myth that PDFs are smaller than HTML. That’s rarely true. PDFs embed fonts and often contain high-resolution images. An HTML page with the same text and compressed images is usually much smaller.

The Future: What’s Coming Next

The web itself is the most obvious replacement for PDFs. The W3C’s Web Publications standard and the Readium project are trying to make the web work better for long-form reading. E-book formats like EPUB are essentially zipped HTML files, and they reflow beautifully on any screen. The only reason they haven’t replaced PDFs is that they’re not great for print.

Another trend is the rise of “canvas” tools like Figma and Miro, which are replacing PDFs for design and brainstorming. These are interactive, collaborative, and live. They don’t have pages at all; they have infinite canvases.

For now, the practical answer is to stop treating PDFs as a default. Use the right tool for the job: HTML for the web, Markdown for notes, cloud docs for collaboration, and PDF only for the final print or archive copy.

Frequently Asked Questions

Can I edit a PDF without buying Adobe Acrobat?

Yes. Free tools like LibreOffice Draw, Inkscape, and online editors like Smallpdf or Sejda can handle basic edits. For text changes, it’s often easier to edit the original source file (e.g., Word or Google Docs) and re-export to PDF.

Is HTML really better than PDF for my resume?

For applying online, yes. An HTML resume is searchable, accessible, and can be styled responsively. Many applicant tracking systems (ATS) can’t parse PDFs reliably, so an HTML or plain-text version is safer. For printing or emailing to a human, a PDF is fine.

What about scanned documents? Can they be replaced?

Yes, with OCR (Optical Character Recognition). Tools like Tesseract (open-source) or Google Drive’s built-in OCR can convert scanned PDFs into searchable, editable text. The output is often a text file or an HTML page, which is far more useful than an image PDF.

Why do government agencies still use PDFs?

Because they need a fixed, immutable record that looks the same on any system. PDF/A is specifically designed for archiving. However, many agencies are now also providing HTML versions for accessibility, as required by law in many countries.

Is Markdown good for long documents like books?

Yes, with a tool like Pandoc. You write in Markdown, then convert to PDF via LaTeX for print, or to EPUB for e-readers. The source is plain text, so it’s easy to version-control and collaborate. Many technical books are written this way.

Will PDFs ever disappear completely?

Probably not in the next decade. They’re too entrenched in legal, print, and archival workflows. But their role will shrink to a final-output format, not a working format. The future is live, reflowable, and collaborative.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →