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 · Structured container

    OOXML Package Inspector

    The inspector applies entry-count, compressed-size, uncompressed-size, and compression-ratio limits before reading selected metadata parts.

    Quick answer

    What does the DOCX/XLSX/PPTX Inspector show?

    The inspector applies entry-count, compressed-size, uncompressed-size, and compression-ratio limits before reading selected metadata parts.

    Human visibility
    Package internals are not normally visible
    Machine receiver
    ZIP/XML package parser
    Robustness
    Converter-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 OOXML package

      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.

    Laboratory status: 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. Recursive archives are not processed.

    Maximum file size: 4 MiB. Accepted file types: DOCX, XLSX, PPTX.

    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 OOXML package 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 applies entry-count, compressed-size, uncompressed-size, and compression-ratio limits before reading selected metadata parts.

    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

    The local ZIP reader supports ordinary central-directory entries and common deflate storage. Encrypted, ZIP64, malformed, or unusually complex packages are rejected or reported as unsupported.