{{ summaryTitle }}
{{ summaryValue }}

{{ summaryLine }}

Profile{{ selectedProfile.label }} PrivacyLocal only Verification{{ computation.values.warning_count ? 'Review' : 'Passed' }}
{{ sourceFile ? sourceFile.name : 'Drop one PPTX here' }}
{{ sourceFile ? sourceFileSummary : 'Browse for a local presentation or use the safe demo.' }}
PNG transparency is preserved. Image optimization can be lossy, so review important slides before replacing the original.

{{ workflowMessage }}

Optional cleanup; slides, notes, masters, layouts, transitions, and playback media are not selected.
{{ remove_thumbnail ? 'Remove an eligible preview' : 'Keep preview thumbnail' }}
Compression review
{{ row.label }}{{ row.display }}
{{ handoffGuidance }}
SHA-256 {{ outputSha256.slice(0, 16) }}…

The chart renderer is unavailable; the same byte values remain in Compression review.

CheckEvidenceStatusCopy
{{ row.label }}{{ row.detail }}{{ row.status === 'pass' ? 'Pass' : 'Review' }}
Package partDecisionBeforeAfterSavedCopy
{{ row.path }}{{ row.actionLabel }}{{ formatBytes(row.original_bytes) }}{{ formatBytes(row.output_bytes) }}{{ formatBytes(row.saved_bytes) }}
Online File Compressor Compress one local file into a compatible archive or stream and review size change with split delivery plus SHA-256 integrity before downloading.
PDF Compressor Compress a PDF locally in your browser, compare structural and production estimates, and catch encryption or image-quality risks before download.
PDF to File Converter Convert a PDF locally into editable text or page-faithful images with page-range checks, document handoffs and no source-file upload.
File to PDF Converter Turn images and text sources into local PDF output while preflighting Office files for renderer needs, layout risks and fidelity limits.

Slide decks often grow because camera images, screenshots, and design exports contain far more pixels than the presentation needs. A PowerPoint file is also a ZIP-based collection of related parts. Slides, masters, layouts, notes, themes, charts, images, fonts, embedded objects, audio, video, and relationship files work together to produce the deck. Shrinking a PPTX safely means changing a narrow set of heavy parts while proving that the rest still points to the same content in the same order.

Images are often the best compression target because cameras, screenshots, and design exports can contain far more pixels than a slide needs. Downscaling a large image reduces its dimensions. Re-encoding a JPEG at lower quality can remove more detail. PNG behaves differently: it can preserve transparency and sharp interface graphics, but photographic PNG files may remain large unless their dimensions are reduced.

Presentation content Compression treatment Review need
Referenced JPEG and PNG images May be downscaled and re-encoded in the same image format. Check small text, diagrams, screenshots, and transparency.
Slides, notes, masters, layouts, transitions, and charts Preserved rather than selected for media optimization. Open the rebuilt deck and confirm order, layout, and playback behavior.
Audio, video, fonts, embedded objects, and unsupported image formats Kept without transcoding or subsetting. Do not expect those parts to contribute to savings.
Presentation preview thumbnail May be removed as optional cleanup. The thumbnail is not a slide; removing it usually saves little.

A profile is a quality boundary, not a guaranteed file size. Compact settings can help screen sharing, Balanced keeps more detail for ordinary presentation use, and Print retains larger images. A deck dominated by video, fonts, already-small images, or embedded objects may show little or no gain.

Package integrity checks can prove that required parts, relationships, and unselected bytes survived the rewrite. They cannot prove that every slide looks correct in PowerPoint. Keep the original and visually review important slides before replacing it, especially when the deck contains brand artwork, fine labels, animations, external links, or playback media.

How to Use This Tool:

Pick an image profile for the deck's destination, then use the package checks and a PowerPoint review as separate acceptance gates.

  1. Choose one standard PowerPoint presentation without macros and no larger than 25 MiB. Digitally signed packages are not rewritten because any change would invalidate the signature.
  2. Select Compact for a 1280-pixel maximum edge and 72% JPEG quality, Balanced for 1920 pixels and 82%, or Print for 2560 pixels and 90%.
  3. Turn on Preview thumbnail cleanup only when removing the optional package preview is acceptable. Slides, notes, masters, layouts, transitions, and playback media are not selected by that option.
  4. Start compression and wait for package inspection, image optimization, rebuilding, and verification to finish. If the verified rebuild is not smaller, keep the original; no replacement download is offered.
  5. Review Package checks and Media ledger, then open the downloaded PPTX in PowerPoint and inspect important slides, transitions, links, notes, and audio or video playback.

Interpreting Results:

Savings percent compares the original file with the verified rebuilt package. Images optimized counts only referenced JPEG or PNG parts whose replacement was smaller enough to keep. Unsupported images, already-small images, and re-encoded candidates that failed the savings rule remain unchanged.

A warning under Package checks usually identifies a preserved feature, not a failed rewrite. Embedded objects, ActiveX parts, fonts, audio, video, external relationships, transitions, and animation timing may be retained without being rendered or transcoded in the browser. Verify those features in PowerPoint.

Keep original means the rebuilt ZIP was the same size or larger. It does not mean the presentation is invalid. It means the selected image and thumbnail changes did not produce a smaller verified file.

Technical Details:

PresentationML stores content in package parts connected by relationship records. A safe media rewrite must resolve those relationships, identify the main presentation, slides, masters, layouts, notes, images, playback media, and thumbnail, then preserve every unselected part. Repacking a ZIP without checking the relationship graph is not enough.

Formula Core:

Measured savings use the final rebuilt package size, rounded to two decimal places for display.

Savings percent = Bsource - Boutput Bsource × 100

Negative savings are clamped to zero in the review because a non-smaller package is discarded. The original and rebuilt byte counts remain the evidence for that decision.

Transformation Core:

Stage Mechanism Acceptance rule
Inspect Reload the ZIP with CRC checking, validate its standard PPTX content type, and resolve internal relationships. Corrupt, macro-enabled, signed, unsafe-path, or structurally incomplete packages stop.
Select media Follow image relationships and select JPEG or PNG targets. Other image formats remain unchanged. No more than 40 referenced images enter the optimization review.
Resize Scale width and height proportionally so the largest edge does not exceed the profile maximum. Images already within the limit keep their dimensions.
Re-encode Encode in the same image format. JPEG uses the profile quality; PNG keeps transparency. The candidate replaces the source only when it saves at least 1,024 bytes.
Rebuild Optionally remove the preview relationship and part, then rebuild the package with ZIP compression. Unselected package-part content must remain byte-identical.
Verify Reload the output with CRC checking and repeat package, image, content-type, and relationship checks. Slide, master, layout, notes, and playback relationship inventories must match.

Rule Core:

PNG images are re-encoded only when downscaling is needed. JPEG images are considered for re-encoding when they are downscaled or are at least 100 KiB. If a candidate is larger or saves less than 1,024 bytes, the original image bytes are retained. The ledger distinguishes optimized, unchanged, unsupported, larger-candidate-kept, and thumbnail-removed decisions.

A presentation may contain up to 500 package entries and 120 MiB of expanded data. One image may contain at most 24 million pixels, and selected images together may contain at most 80 million pixels. Processing has a 45-second limit, and verified output cannot exceed 30 MiB. These are browser-work limits rather than PowerPoint format limits.

The final checks preserve the entry inventory except for an approved thumbnail removal. Required slide, master, layout, and presentation relationships must resolve. Unselected content bytes are compared directly, while changed image parts must still have a valid JPEG or PNG signature and dimensions.

Limits and Verification:

The presentation is inspected, rebuilt, and verified in the browser rather than uploaded to a presentation-processing service. Compression support may still need to load over the network. Image optimization is lossy even when the package itself remains valid, so package verification and visual verification are both needed before the compressed deck replaces its source.

  • Macro-enabled and digitally signed presentations are rejected.
  • Audio, video, embedded fonts, ActiveX parts, and embedded objects are preserved without size optimization.
  • Transitions and animation timing are retained but not rendered during browser verification.
  • External relationships are preserved, but their destinations are not fetched or tested.
  • Keep the original until the downloaded deck opens correctly and important slides pass a visual review.

References: