What is the difference between Hidden and Invisible annotation flags?

Hidden (bit 2): The annotation is completely suppressed — not displayed on screen and not printed. It effectively doesn't exist to the viewer. Invisible (bit 1): The annotation is suppressed only if the viewer doesn't recognise its subtype (e.g., a custom annotation type). Standard annotation types (Text, Highlight, Link) are never invisible in conformant viewers. Hidden is an absolute hide; Invisible is a conditional hide for custom types.

Why would an annotation print but not appear on screen?

This is achieved by setting both the NoView flag (bit 6, suppress screen display) and the Print flag (bit 3, include in print output). Common uses: watermarks that should appear on the physical print but not distract the screen reader; security stamps visible only on printed copies; reviewer comments intended for print-only review workflows. The annotation is genuinely invisible on screen but renders on the physical or virtual PDF print.

What does the Locked annotation flag do?

The Locked flag (bit 8) prevents the annotation from being moved, resized, or deleted through the UI. It does not prevent the annotation from being interacted with (clicked, form fields filled). To prevent both modification and interaction, combine Locked with ReadOnly. Locked annotations can still be unlocked programmatically or by users with the appropriate annotation editing permissions.

Which annotation flags are important for accessibility?

For accessibility, the most important flag consideration is NoView. An annotation with NoView set is not visible on screen, so screen readers may encounter it in the tag tree without any visible context for the user — potentially confusing. All visible annotations on screen should be tagged appropriately in the document structure tree. Hidden annotations should be marked as Artifacts to prevent screen readers from encountering them.

How do annotation flags interact with PDF/A?

PDF/A permits most annotation types including Text (sticky notes), Highlight, Underline, and Link. However, all annotations in a PDF/A file must have the Print flag set (bit 3) — annotations that only appear on screen but not in print are non-conformant. The Hidden flag is effectively prohibited in PDF/A files because hidden annotations serve no preservation purpose and may create ambiguity about document content.

PDF Annotation Flags Explained: Visibility, Print, Lock & NoView

Q: What are PDF annotation flags?

PDF annotation flags are a set of bit flags stored in the /F integer field of every annotation dictionary. Each bit controls a specific behaviour: Invisible (bit 1) — hide the annotation if the viewer doesn't know its type. Hidden (bit 2) — hide always, never print. Print (bit 3) — include when printing. NoZoom (bit 4) — don't scale the annotation appearance with the page zoom. NoRotate (bit 5) — don't rotate the annotation when the page rotates. NoView (bit 6) — don't display on screen. ReadOnly (bit 7) — prevent user interaction. Locked (bit 8) — prevent deletion or position change.

Quick Answer

Every annotation in a PDF — a sticky note, a highlight, a hyperlink, a form field, a watermark stamp — carries a single integer in its dictionary: /F. Each bit in that integer is a flag that independently controls one behaviour. Bit 3 (Print) is on: the annotation appears when you print. Bit 6 (NoView) is on: the annotation is invisible on screen. Both on together? You get a print-only watermark — visible on the physical print, invisible in the PDF viewer. Bit 8 (Locked) prevents the annotation from being moved or deleted. Bit 7 (ReadOnly) prevents interaction. Understanding these flags is the difference between annotations that do exactly what you intend and annotations that surprise you.

What Are PDF Annotation Flags?

In the PDF specification, every annotation object (Widget, Text, Highlight, Link, Stamp, etc.) includes a required /F key whose value is an integer. This integer is interpreted as a bit field — each bit position, if set to 1, enables a specific behavioural flag. The flags accumulate additively: an /F value of 36 (binary: 100100) has bits 3 and 6 set — meaning Print + NoView.

💡

Default value: When /F is absent or set to 0, no flags are active. Most annotations created interactively in Acrobat have the Print flag (bit 3 = value 4) set by default — meaning they print. Always verify /F when debugging annotations that appear on screen but not in print, or vice versa.

All PDF Annotation Flags

Bit	Value	Flag Name	Effect When Set
1	1	Invisible	Hide if viewer doesn't recognise the annotation subtype (custom types only)
2	2	Hidden	Always hidden — never displayed, never printed
3	4	Print	Include in print output (most annotations default to this)
4	8	NoZoom	Annotation appearance doesn't scale with page zoom level
5	16	NoRotate	Annotation appearance doesn't rotate when page rotates
6	32	NoView	Not displayed on screen (but can still print if Print flag also set)
7	64	ReadOnly	Prevents user interaction — cannot type in field, click button, etc.
8	128	Locked	Cannot be moved, resized, or deleted via UI
9	256	ToggleNoView	Toggle NoView on mouse click (used for rollover effects)
10	512	LockedContents	Contents and appearance cannot be changed, but position can

Real-World Examples

🖨️ Print Production Scenario

Print-Only Watermark on Confidential Documents

A legal firm distributes draft contracts electronically. On-screen, the draft looks clean — no distracting overlay. But /F = 36 (Print + NoView) on the "DRAFT CONFIDENTIAL" stamp annotation means that every copy printed from the PDF shows the watermark prominently in pink diagonal text across the page. Anyone printing the file for an unauthorised meeting gets a clearly labelled draft — but anyone reviewing the document on screen sees the clean version. One annotation flag combination implements a complete print security policy.

📋 Forms Scenario

Locked Form Template: Staff Can Fill, Not Modify

An HR department distributes a performance review form. Every annotation — section labels, decorative borders, instructional text boxes — has /F = 132 (Print + Locked). Form fields that collect data have /F = 4 (Print only — no Locked flag). Staff open the form, fill in their answers in the interactive AcroForm fields, and cannot accidentally drag or delete the form structure around them. The form's design is permanently locked while the data entry fields remain fully functional. PDF documents that require stable structure with editable content use this flag combination routinely.

🔒 Security Scenario

Hidden Annotations Used for Metadata in Document Processing

A document management system processes incoming PDFs and injects hidden annotation objects (/F = 2, Hidden) containing classification metadata — document class, processing timestamp, originating department — into each file. These annotations are completely invisible to users opening the PDF in any viewer and do not print. The DMS reads them programmatically using its PDF parsing library. When a document is transferred to a secure archive, the archive system reads the hidden annotations to populate its metadata database automatically — zero manual classification required.

Why Annotation Flags Matter

🖨️

Screen vs. Print Control

NoView + Print creates print-only content (watermarks, security stamps). Print omitted creates screen-only content (review comments that shouldn't print). Powerful for document distribution.

🔒

Form Structure Protection

Locked prevents users from accidentally moving or deleting structural elements in form templates — protecting layout integrity while still allowing interactive field data entry.

👁️

Conditional Visibility

Hidden annotations store invisible metadata or reviewer notes that should not affect the user-facing document — useful for DMS systems, workflow automation, and internal classification.

📐

Zoom-Stable Design

NoZoom and NoRotate flags create annotations that maintain their visual size and orientation regardless of how the user zooms or rotates the page — essential for fixed UI overlays and stamps.

🏛️

PDF/A Compliance

PDF/A requires the Print flag to be set on all annotations — hidden or screen-only annotations violate archival requirements. Understanding flags is essential for creating conformant archival PDFs.

🖱️

Rollover Effects

ToggleNoView creates mouse-hover visibility effects — an annotation invisible by default becomes visible on rollover, then returns to hidden. Used for tooltip-style interactive help overlays.

Common Flag Combinations

PDF ANNOTATION — /F FLAG VALUES

% Print only (default for most interactive annotations)
/F  4       % bit 3 = Print

% Print + NoView = print-only watermark (hidden on screen)
/F  36      % bit 3 + bit 6 = Print (4) + NoView (32)

% Print + Locked (locked form label)
/F  132     % bit 3 + bit 8 = Print (4) + Locked (128)

% Hidden (completely invisible, never prints)
/F  2       % bit 2 = Hidden

% ReadOnly + Print (view but no interaction)
/F  68      % Print (4) + ReadOnly (64)

Common Mistakes to Avoid

Confusing Hidden and Invisible flags. Hidden (bit 2) suppresses an annotation completely — no display, no print, ever. Invisible (bit 1) only suppresses custom/unknown annotation types. Setting Invisible on a standard Text annotation does nothing — it will still display normally in any conformant viewer.
Setting NoView without understanding the print interaction. An annotation with NoView set is invisible on screen but will still print if the Print flag is also set. This is intentional for print-only watermarks — but it is a surprise if you set NoView thinking the annotation is completely hidden and then find it appearing on every printed page.
Not setting the Print flag on annotations in PDF/A files. PDF/A requires the Print flag to be set on all annotations. A highlight or sticky note without the Print flag is non-conformant in a PDF/A file. Always set /F to include bit 3 (Print) on annotations in archival documents.
Locking form labels that users need to reposition. The Locked flag is absolute — even the document owner cannot move the annotation without programmatically clearing the flag. If you think you might need to adjust the layout later, use LockedContents (bit 10) instead, which locks the content but allows repositioning.
Using Hidden annotations to store sensitive data. Hidden annotations (/F = 2) are invisible to users but perfectly readable by anyone with a PDF parser, metadata tool, or Acrobat's Object Inspector. Never store confidential data in annotation contents expecting it to be hidden — it is hidden visually, not cryptographically.

Frequently Asked Questions

PDF annotation flags are bit flags stored in the /F integer field of every annotation dictionary. Each bit controls one behaviour: Hidden (always invisible), Print (include in print), NoView (invisible on screen), ReadOnly (no interaction), Locked (no movement/deletion), ToggleNoView (rollover visibility), and more.
Hidden (bit 2): Completely suppressed — never displayed, never printed. Absolute hide for any annotation type. Invisible (bit 1): Only suppresses the annotation if the viewer doesn't recognise its subtype — has no effect on standard annotations (Text, Highlight, Link) in any conformant viewer.
/F = 36 (Print bit 3 + NoView bit 6). NoView hides the annotation on screen; Print includes it in print output. This creates print-only content — watermarks, security stamps, and confidential markers that appear on physical prints but don't distract users viewing on screen.
Locked (bit 8) prevents the annotation from being moved, resized, or deleted via the UI. It does not prevent interaction (typing in a field, clicking a button). Combine Locked + ReadOnly to prevent both structural changes and user interaction. Use LockedContents (bit 10) to lock the content while still allowing repositioning.
PDF/A requires the Print flag (bit 3) to be set on all annotations. Annotations without Print are non-conformant. The Hidden flag is effectively prohibited — hidden annotations have no preservation value and create archival ambiguity. All visible annotations must have Print set; purely decorative elements should be marked as page Artifacts rather than annotations.
In Adobe Acrobat: right-click any annotation > Properties — the Appearance tab shows print/view settings. For programmatic inspection: use iTextSharp, PyPDF2, or Acrobat's Object Inspector to read the /F value directly from the annotation dictionary. Decode as binary — each set bit corresponds to one active flag.

Annotate & Edit PDFs — Free

PDFlyst's PDF Editor lets you add, manage, and control annotations on any PDF directly in your browser.

Open PDF Editor — Free

PDF Annotation Flags: Visibility, Print, Lock & NoView