Compressing a 1.4 GB Field Deck Under a 30 MB LMS Limit
A regional sales team maintains a 96-slide PowerPoint deck distributed to 400 field reps through an LMS with a hard 30 MB upload limit; the current .pptx is 1.4 GB. It contains a 42-minute MP4 product demo, 18 full-resolution PNG screenshots, two charts linked to an Excel workbook on a shared drive, and three licensed TrueType brand fonts installed on the designer's PC but not on rep laptops. It also carries 60 speaker notes, 11 hidden slides, and a legal comment thread. Reps must open it offline, read the notes, see the charts exactly as designed, and they never edit data. The designer's plan is to zip the file and, if that fails, export to PDF. The training lead insists the file stay .pptx, keep the video inside the file, and remain under 30 MB.
1. The training lead asks you to sequence the changes that will bring the deck under 30 MB while keeping the video embedded, the notes intact, and chart appearance unchanged. What sequence do you propose, and what would you refuse to do?
Read the worked answer
Start by checking whether the constraints are mutually satisfiable. A 42-minute video at roughly 100 kbps is already about 31 MB, which leaves nothing for 96 slides, screenshots, and notes. At any usable quality the video alone will exceed 30 MB, so the real decision is editorial: trim the demo to a few minutes, split it into chapters across several files, or host it externally. That conflicts with the offline requirement, so the lead must choose which constraint gives.
Assuming a trimmed video, work in this order:
- File > Compress Media (Standard/480p) to shrink embedded audio and video, then trim and set a poster frame.
- Compress Pictures at about 150 ppi and delete cropped areas. Keep UI screenshots as PNG where text legibility matters; JPEG artifacts will make small text worse.
- Remove unused masters, layouts, and off-slide objects.
- Save as .pptx and verify the size before touching notes or chart data.
Do not zip: the LMS expects a .pptx, and zipping does not solve quality. Do not export to PDF: the video and speaker notes are lost. Do not delete the notes the reps need.
2. The three brand fonts are missing on rep laptops, and the deck must look identical. Compare embedding fonts with the alternatives, and state the risks you would test before release.
Read the worked answer
Use File > Options > Save > Embed fonts in the file, choosing Embed only the characters used to limit size. Embedding is the only way to keep the exact typeface inside a single .pptx. Risks: not every font license permits embedding, some fonts cannot be embedded at all, file size grows, and rendering can still differ by platform and PowerPoint version, especially on Mac and PowerPoint for the web. Test on an actual rep laptop before release.
Alternatives have trade-offs. Installing the fonts on 400 machines is an IT project, not a deck fix. Substituting a standard font (Arial or Calibri) for body text and reserving the brand font for headings is more robust and smaller, but changes the look. Converting headings to pictures or shapes preserves appearance but destroys editability and accessibility, so avoid it for anything a screen reader must read.
My recommendation: embed the fonts, and in the theme set a safe fallback font so substitution degrades gracefully if embedding fails. Check line breaks and text overflow on a machine without the fonts, because embedded fonts can still reflow slightly.
3. Legal wants its comments removed, but the 60 speaker notes must stay and the 11 hidden slides contain pre-release pricing. How do you handle inspection and distribution?
Read the worked answer
Run File > Info > Check for Issues > Inspect Document, but read the checkboxes before running it. Document Inspector can remove comments and annotations, document properties, speaker notes, hidden slides, off-slide content, and embedded files. Removing speaker notes would break the rep requirement, so clear that checkbox, remove comments only, and keep the notes deliberately.
Do not rely on hiding for confidential pricing. Hidden slides remain in the file, can be unhidden by anyone, and still count in slide numbering. Delete those slides from the distributed copy and keep them in a separate internal deck. If the pricing must travel with the file, it needs a protected location, not a hidden slide.
Also inspect the linked charts: the link path can expose server and share names, and a broken link shows cached data that may be stale. Break the links and embed the chart data for distribution. Check the video for confidential content and confirm the final file opens cleanly on a rep machine before publishing.