PowerPoint inspection guide

The slide canvas is only one view of the file.

A PPTX can contain notes, comments, source images, embedded workbooks, hidden objects, paths, identities, macros, and application data that never appears in the normal presentation view.

PPTX package12-point checklistNo upload

What to inspect

RiskWhy it matters
Speaker notesStored as separate note parts and readable by recipients.
Hidden slidesExcluded from normal presentation flow but still fully present.
Hidden and off-slide objectsText or shapes can remain outside the canvas or be marked hidden.
Comments and authorsCan expose draft decisions, names, review history, and internal language.
Embedded workbooks or documentsRecipients may extract the original file and all underlying rows, formulas, sheets, or metadata.
Cropped imagesThe package can retain the uncropped source image.
Image metadataOriginal images can carry GPS coordinates, camera serials, dates, authors, or software fields.
External linksLocal paths can reveal usernames, servers, folders, and internal sources.
Document propertiesCreator, last editor, company, manager, template, and custom properties are inspectable.
Custom XMLApplication-specific records may travel even when no slide displays them.
MacrosVBA is executable content and may carry code or concealed data.
Package anomaliesEncrypted entries, duplicate paths, CRC errors, or extension mismatches weaken confidence in any inspection.

Why package-level inspection is different

A modern PowerPoint file is a ZIP package of XML, media, relationship, and binary parts. The application composes those parts into a slide view. A recipient can inspect the package directly or use software that exposes material omitted from the normal canvas.

Safe to Send validates the archive, verifies entry checksums, follows slide and note relationships, inspects hidden flags and geometry, reads metadata, checks embedded image metadata, and identifies unlinked package parts. It does not need to upload the file or render the presentation.

Use both controls. PowerPoint Document Inspector knows application-specific behavior. An independent package scan checks what actually remained in the saved file. Neither should be treated as an absolute guarantee.

A disciplined release workflow

  1. Create a distribution copy.
  2. Remove notes, comments, hidden slides, embedded working files, and unneeded links.
  3. Permanently crop and strip metadata from images.
  4. Run PowerPoint Document Inspector on the copy.
  5. Save, close, and reopen it.
  6. Scan the final file with Safe to Send.
  7. Resolve findings and repeat until the report reflects the intended content and complete coverage.
  8. Record the SHA-256 fingerprint or attach the report to the release record.

Inspect a PowerPoint file now →