MachineTradecraft
Global site search

Search guides, labs, glossary, and research

Type two or more characters to search.

Start with a channel, artifact, or defense term

Examples include zero-width, metadata, tokenizer, or prompt injection.
    Documents & Metadata · Complex container

    Defensive PDF Structure Inspector

    The inspector never executes PDF actions or JavaScript. It reads a bounded byte sample, reports structural indicators, and clearly marks unsupported rendering and OCR stages.

    Browse all labs Open universal Machine View
    Quick answer

    What does the PDF Inspector show?

    The inspector never executes PDF actions or JavaScript. It reads a bounded byte sample, reports structural indicators, and clearly marks unsupported rendering and OCR stages.

    Human visibility
    Rendered pages omit many structures
    Machine receiver
    PDF object parser
    Robustness
    Parser- and conversion-dependent

    Research boundary: this page uses bounded, inert data and fixed safe examples. It never executes decoded content, requests secrets, calls third-party services, or performs actions against external systems.

    FIRST RUN / THREE STEPS

    Start with the prepared, bounded workflow.

    Nothing runs automatically
    1. Choose one supported file

      The file stays in PHP’s temporary upload for this request and is not retained by the application.

    2. Run Inspect PDF

      Inspect the selected file as inert bytes and containers. No embedded content is executed.

    3. Scan before expanding

      Read the summary and findings first, then inspect extracted metadata, views, and table rows.

    INPUT / CONTROL PLANE

    Prepare the input and choose one action.

    Ready

    The recommended first run is separated from alternate analyses. Inputs and selected files stay on this host.

    Current input state No file selected yet

    Choose one supported local file, then run the recommended inspection. Browsers do not repopulate file selections after a reload.

    Maximum 4 MB. The file is processed from the temporary upload and not retained.

    Maximum file size: 4 MiB. Accepted file types: PDF.

    ACTION HIERARCHY

    Run the recommended first pass.

    Alternate actions remain available below, but the first pass is the clearest place to start.

    Inputs remain on this host. Text operations are size-limited; uploaded files are processed from PHP’s temporary upload and are not retained by the application.

    OUTPUT / MACHINE VIEWS

    Scan the result from summary to evidence.

    Run Inspect PDF to create the first result.

    Choose a supported file first. The output will lead with a summary and visible qualifications before the expandable machine views.

    SummaryFindingsMachine views
    Interpretation framework

    The same artifact can produce several valid observations.

    01

    Human view

    What a person naturally reads, sees, or hears.

    02

    Structural view

    What a parser, DOM, container reader, or metadata extractor exposes.

    03

    Decoder view

    What becomes meaningful only with a rule, key, tokenizer, model, or tool.

    04

    Defensive view

    What normalization, rendering, OCR, canonicalization, or policy changes.

    Evidence and decision boundary

    Use the result as bounded evidence, not as a universal verdict.

    The inspector never executes PDF actions or JavaScript. It reads a bounded byte sample, reports structural indicators, and clearly marks unsupported rendering and OCR stages.

    Interpretation rule

    Record the receiver and transformation.

    Machine-decodable is receiver-relative. Record the parser, preprocessing, codebook, tokenizer, key, model, and transformation path before generalizing from one result.

    Limitations

    What this page does not prove

    This dependency-free build does not render pages or run OCR. High-assurance analysis should add isolated rendering, object-aware libraries, and an independent OCR comparison.

    Continue the investigation

    Related labs and source reports

    Document Metadata Document parser or indexer Metadata Generator Parser under test DOCX/XLSX/PPTX Inspector ZIP/XML package parser Document Metadata Exploitation in AI Retrieval and Processing Research report Defensive Preprocessing for Hidden Instructions Research report
    Continue exploring

    Move from the current explanation to a related guide, evidence source, or controlled workbench.

    Laboratory catalogChoose a focused local experimentBrowse 40 bounded laboratories spanning representation, files, messages, models, provenance, agents, supply chains, and defense.Open this path Topic guideInspect document metadata as a separate planeCompare application fields, container properties, image chunks, PDF objects, and model-facing serialization.Open this path Defensive architectureBuild a safer model-ingestion boundaryPreserve evidence, compare representations, canonicalize allowlisted fields, retain provenance, and minimize privilege.Open this path