deck-file-size-optimizerlisted

# Deck File Size Optimizer ## When to use Use this skill when a deck will not send, opens slowly, saves slowly, or is simply absurd for what is on the slides — the classic case being a 40-slide deck that weighs 180 MB and contains eight photographs. Also use it before a template ships firm-wide, because whatever bloat is in the template is inherited by every deck built on it. Do not use it for playback lag caused by animations or transitions; that is a rendering problem, not a size problem. ## What it does It measures where the bytes actually are, then applies the fixes in descending order of payoff, and states the expected saving for each. The output is a before/after size with an itemised list of what was removed. ## Method **1. Measure before you cut.** A `.pptx` is a ZIP container. Copy the file, rename the copy to `.zip`, and open it. What you are looking for: - `ppt/media/` — every image, video and audio file, at its original size. Sort by size. This is nearly always where the weight is. - `ppt/embeddings/` — embedded workbooks and OLE objects. - `ppt/slideMasters/` and `ppt/slideLayouts/` — count them. - `ppt/fonts/` — embedded fonts, a few hundred KB per weight. Do this first. Guessing wastes an hour on a 200 KB problem while a single 90 MB video sits untouched. **2. Delete cropped pixels.** This is usually the single biggest win and the least known. When you crop an image in PowerPoint, the cropped-away pixels are still in the file; the crop is a display ins