4 min read

Tagged vs Untagged PDFs: What Is the Difference?

If you remember one distinction about PDF accessibility, make it this one: tagged versus untagged. It is the difference between a document a screen reader can read and one it largely cannot.

An untagged PDF

An untagged PDF has no structure tree. The file knows where to draw each character on the page, but nothing about what is a heading, a paragraph, a list, or a table. A screen reader has to guess at the text and the order, and usually gets both wrong. Tables, headings, and navigation are simply unavailable.

A tagged PDF

A tagged PDF carries a structure tree that labels each element and defines the reading order. With correct tags, a screen reader can announce headings, read tables cell by cell, describe images, and let the user navigate — and the content reflows properly when zoomed.

Tagged does not automatically mean accessible. Tags can be wrong — bad reading order, missing alt text, mis-tagged tables. But untagged always means inaccessible. Tagging is the necessary first step.

How to tell which you have

  • In Acrobat, open File > Properties — the "Tagged PDF" field says Yes or No.
  • Open the Tags panel; an untagged file shows "No Tags available".
  • Or simply run an accessibility check, which reports tagging status first.

Upload your PDF here to instantly see whether it is tagged and what to fix next.

Check your PDF for free

See exactly which PDF/UA and WCAG 2.1 AA issues your document has — instant, no signup.

Check My PDF

Frequently asked questions

How do I tell if a PDF is tagged?
In Acrobat, open File > Properties and check the "Tagged PDF" field (Yes or No), or open the Tags panel — an untagged file shows "No Tags available". Running an accessibility check also reports tagging status first.
Does a tagged PDF mean it is accessible?
Not necessarily. Tags can still be wrong — incorrect reading order, missing alt text, or mis-tagged tables. But an untagged PDF is always inaccessible, so tagging is the required foundation the other fixes build on.
Why can a PDF look fine but be unreadable to a screen reader?
Because the visual layout (where characters are drawn) is separate from the structure (what the content means). An untagged PDF has the visuals but no structure, so a screen reader has to guess at the text and order — and usually gets both wrong.

Related how-to fixes