When you receive a suspicious PDF document on a macOS workstation, executing it or relying on the visible text is a severe security risk. The visual layer can easily be spoofed. To verify the true origin, author, software compiler, and typographic architecture of the file, you must mathematically inspect the hidden XML payload. To force the Core Graphics engine to expose this cryptographic data, you must deploy the Inspector protocol within the native Preview application.
Executing the Metadata Extraction Matrix
Every PDF document contains a hidden header block. This block records the exact timestamp of creation, the specific software used to compile the vectors (e.g., Adobe InDesign vs. Microsoft Word), and the embedded fonts required to render the text. The Preview Inspector forces this data into a human-readable UI.
- Locate the target PDF file in Finder and double-click to open it natively in Preview.
- Look at the absolute top menu bar. Click the Tools menu.
- From the drop-down system matrix, click the critical command labeled Show Inspector (or execute the rapid hotkey: Cmd + I).
Deploying the Inspection Vector
- The Core Graphics engine will spawn a floating Inspector modal. This modal is divided into multiple analytical tabs.
- The General Tab (Magnifying Glass Icon): This is the primary intelligence vector. The engine rips the basic metadata from the XML header. You will instantly see the exact File Size, Resolution, true Author, and the Creator/Producer (the exact software engine used to generate the PDF). If the Author field contradicts the visible signature on the document, you have detected a forgery.
- The Encryption Tab (Lock Icon): Click this to verify the cryptographic security state of the file. It will display the exact bits of encryption (e.g., 128-bit RC4) and define the Boolean permissions (whether Printing, Copying, or Modifying are allowed).
- The Document Info Tab (Pencil Icon): Click this to inspect the embedded typography. If a PDF is rendering incorrectly or slowly, this matrix reveals every single Font file hardcoded into the document architecture. If the font list is empty, the entire document is mathematically just a rasterized image (a scan), not actual text data.