PowerPoint Slides & Aspect Ratio Auditor

PowerPoint Slides & Aspect Ratio Auditor: Reads `ppt/presentation.xml` `<p:sldSz>` dimensions (dx: 12192000, dy: 6858000 in EMUs).

About this powerpoint slides & aspect ratio auditor

PowerPoint Slides & Aspect Ratio Auditor — browser-based utility.

How this tool works

Implements client-side PowerPoint Slides & Aspect Ratio Auditor operations. Reads `ppt/presentation.xml` `<p:sldSz>` dimensions (dx: 12192000, dy: 6858000 in EMUs) specifically designed for an event av technician verifies whether speaker presentation slides are 16:9 widescreen or 4:3 standard format.

  1. OpenXML ZIP Decompression: Unpacks DOCX/PPTX archive structures in memory via fflate, validating package integrity against Zip Bomb attacks.
  2. XML DOM Parsing & Relationship Mapping: Parses word/comments.xml and word/_rels/document.xml.rels to resolve comment ranges, authors, and dates.
  3. Thread & Status Reconstruction: Reconstructs parent-child reply relationships and resolved states from commentsExtended parts.
  4. XLSX Workbook Compilation: Compiles parsed records into a typed Excel workbook with frozen header rows and auto-filters.

Worked example

Scenario: An event AV technician checks the slide count and declared screen ratio in a speaker PPTX.

Sample input:

File: 'speaker_presentation.pptx' (one slide, 12192000 × 6858000 EMUs)

Processing: Reads p:sldSz cx/cy from ppt/presentation.xml, counts slideN.xml entries, computes and rounds the ratio, then selects a label.

Illustrative output:

{ "slides": 1, "widthEmu": 12192000, "heightEmu": 6858000, "ratio": 1.78, "label": "16:9" } — no inches, preview, or repair output.

Limits and verification

Legacy binary formats (.doc, .ppt, .xls) must be converted to modern OpenXML (.docx, .pptx, .xlsx) before processing. Password-encrypted Office packages must be unlocked prior to parsing.

Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.

Browser processing boundary

Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.

Relevant references

These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.

Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology

How to use it

  1. Enter, paste, or select your input data into the PowerPoint Slides & Aspect Ratio Auditor workspace controls.
  2. Review available parameter fields, units, formats, or options configured for your task.
  3. Click the action button or observe immediate live calculations rendered in your browser runtime.
  4. Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.

Frequently asked questions

How does PPTX Ratio Auditor calculate its report?+

It reads p:sldSz cx and cy EMU attributes from ppt/presentation.xml, counts ppt/slides/slideN.xml entries, rounds cx/cy to two decimals, and returns slides, widthEmu, heightEmu, ratio, and label.

Which controls and output are available?+

The page provides one local PPTX chooser and Process locally. It has no unit or ratio target, slide selection, conversion, repair, preview, export, or download control; the result is read-only JSON.

What label limits apply?+

16:9 needs a difference below 0.02 and 4:3 below 0.03; every other nonzero ratio is custom. If size is missing, ratio is null and the label is custom. It does not inspect slide content or validate rendering.

What did isolated browser verification establish?+

For a one-slide PPTX whose ppt/presentation.xml declares 12192000 by 6858000 EMUs, the read-only JSON is expected to report one slide, those EMUs, ratio 1.78, and label 16:9. This checks the declared XML geometry path, not slide content or rendering.