Compress PowerPoint

1. 1

   Add your presentation

   Drop a .pptx, .pptm, .ppsx, .ppsm, .potx or .potm file onto the page, or browse for it. Nothing is uploaded — the deck is read on your device.

2. 2

   Choose a resolution

   Print (220 ppi) suits anything that will be projected or printed. Web (150 ppi) is right for a deck that will only ever be looked at on a screen. E-mail (96 ppi) is the smallest that still reads.

3. 3

   Pick what else to clean up

   Unused slide layouts, co-authoring history, duplicate pictures and the file thumbnail are all removed by default. Embedded fonts are left alone unless you ask.

4. 4

   Compress and check

   The breakdown says which change recovered which bytes, and the preview shows the deck's largest picture before and after. Download when you are happy.

A PowerPoint file is a package: slides, a template of masters and layouts, the pictures those slides and layouts draw, and a quantity of bookkeeping nobody ever sees. Most compressors only look at the pictures, and only at their pixel dimensions. This one resizes pictures to the resolution they are actually shown at, throws away the parts a crop hides, and removes the layouts, duplicates and editing history the file is carrying for no reason — then tells you exactly which of those recovered which bytes.

Decks are the largest files most people send. A twelve-slide deck with a photograph on each slide is thirty megabytes before anyone embeds a video, which is past Gmail's 25 MB attachment limit, past most learning-management upload caps, and slow enough over conference wifi that people give up on it. Compressing before you send is the difference between a link and an attachment.

Where a smaller deck actually helps

• E-mail attachments: Gmail and Outlook both stop at 25 MB, and a deck over it silently becomes a cloud link the recipient may not be able to open.
• Learning platforms: Moodle, Blackboard and Google Classroom set per-file upload caps that a photograph-heavy lecture deck goes past routinely.
• Presenting from a shared drive: a 200 MB deck opened over hotel wifi five minutes before a talk is the classic reason a talk starts late.
• Version sprawl: a deck that has been round a review cycle carries every editing session's bookkeeping, and it never gets cleaned up on its own.
• Storage and backup: template decks duplicated across a team multiply every unused layout background by however many copies exist.

The deck is opened on your device and read as what it is — a set of parts with relationships between them. Every picture is identified from its own bytes rather than from its file name, resized against the box the slide draws it in, and re-encoded in the format that suits it. Parts nothing references are removed, and the package is written back with its pictures stored rather than re-compressed. The file you download is the same kind of file you put in, and it opens in PowerPoint without a repair prompt.

What you can change

• Resolution: Print, Web or E-mail expressed in ppi, or a flat pixel cap if you prefer to think that way. This is the setting that matters most.
• Picture quality: four steps from Low to Maximum. Maximum still re-encodes; the honest lossless option is to turn re-encoding off entirely.
• Flat artwork: logos, icons, charts and screenshots are stored with a limited palette instead of as photographs, which is both smaller and sharper.
• Cleanups: cropped areas, duplicates, unreferenced media, unused layouts, change history and the file thumbnail — each one a separate checkbox.
• Embedded fonts: off by default, because dropping them changes how the deck looks on a machine that does not have the font.

Every other web compressor caps pictures at a pixel width. PowerPoint's own Compress Pictures dialog does not: it asks for a target ppi, because that is the only form of the question with a correct answer. A photograph stored at 3000 pixels and displayed 4.2 inches wide on a ten-inch slide is being shown at over 700 ppi. Capping it at 1920 pixels still leaves it two and a half times more detail than a projector will ever draw. A PPTX records the size of every picture's frame, so the right cap can be worked out per picture rather than guessed once for the whole deck.

What each setting means

• Print — 220 ppi: more resolution than a projector or a 4K screen can resolve, and enough for a printed handout. The safe default for anything you will present.
• Web — 150 ppi: indistinguishable on a screen. The right answer for a deck that will be read rather than projected.
• E-mail — 96 ppi: visibly softer if you go looking, and by far the smallest. Use it when getting under an attachment limit matters more than anything else.
• A pixel cap instead: 1280, 1920 or 2560 pixels on the long edge, applied to every picture regardless of how large it is drawn. Simpler, and always larger than the ppi setting that matches it.
• No limit: keeps every picture's full resolution and only re-encodes. For an archive copy where the file size is not the point.

Cropping a picture in PowerPoint hides part of it. It does not remove anything. The whole original stays inside the file and the slide records which rectangle of it to draw, which means a portrait cropped out of a wide landscape shot is carrying the entire landscape around with it. Microsoft's own advice for shrinking a presentation starts with "delete cropped areas of pictures" for exactly this reason, and it is a thing PowerPoint can do that no other web compressor does.

How it is done safely

• The kept region is the union of every use: a picture placed twice and cropped differently keeps whatever either placement needs, so nothing is lost from either.
• The crop rectangles are rewritten to match: trimming the pixels without updating what the slide draws would move the picture. Both happen together or neither does.
• A picture shown whole anywhere is never trimmed: one uncropped placement is enough to keep the whole thing.
• A trim that does not pay is abandoned: if the trimmed picture would encode larger than the original, the original is kept unchanged.

Copy one slide from another deck and PowerPoint brings that deck's whole slide master with it — typically eleven layouts, each a full slide's worth of markup, several with their own background photograph. Nothing in PowerPoint's interface shows you the total, and none of it is drawn unless a slide is using it. Separately, any deck that has been edited in PowerPoint for the web carries a change-history store recording who altered what in each co-authoring session. It is documented, it is legitimate, nothing reads it back once the session is over, and on a text-only deck it can be most of the file.

What is removed, and what it costs you

• Layouts no slide uses: removed by default. Every slide keeps the layout it is on, so nothing visible changes — but a layout that is gone cannot be picked for a new slide later. Turn it off for a deck you are still building.
• Change history and revision data: removed by default, and there is no cost: PowerPoint writes a fresh one the next time the deck is co-authored.
• Duplicate pictures: the same logo saved as twelve separate copies becomes one copy referenced twelve times. Nothing about the deck changes.
• Media nothing references: pictures left behind in the file after the slide using them was deleted.
• The file thumbnail: the preview image your file browser shows. It is regenerated the next time the deck is saved.
• Templates are exempt: in a .potx or .potm the unused layouts are the deliverable, so layout removal is skipped entirely.

Three things account for almost every deck that stays large after a picture-only compression, and being told which one it is saves more time than another few per cent would. Embedded fonts are a checkbox most people tick once and forget; PowerPoint embeds every character by default, and a couple of faces is easily several megabytes. Embedded video and audio are simply large — five to twenty megabytes for a single clip. This tool names both in the breakdown rather than letting you conclude it failed.

How each is handled

• Embedded fonts: removable, but off by default. Dropping them means a machine without the font installed substitutes another, and substituted text reflows. Worth it when the deck is going to a PDF or to people on the same corporate build.
• Embedded video and audio: passed through untouched, and reported. Re-encoding a clip is a different job with different trade-offs; getting it wrong is not recoverable from the output.
• Vector artwork and metafiles: charts and diagrams pasted from Excel are vector drawings. They are left exactly as they are, because there is nothing to resample.
• Animated pictures: an animated GIF is passed through whole. Re-encoding one keeps the first frame and silently discards the rest.

"73% smaller" is half an answer. The missing half is whether a disappointing result means the tool gave up or means the deck had nothing left to give — and those need completely different responses from you. Every run here is accounted for by cause, so you can see at a glance that the pictures gave up nine megabytes, the unused layouts gave up five, and the fourteen megabytes that did not move are a video.

The causes it reports

• Pictures: everything the resize and re-encode recovered, across every picture in the deck.
• Unused layouts: the layout markup itself, plus the pictures those layouts were the only user of.
• Change history: the co-authoring store and per-slide edit stamps, counted as they will actually appear in the saved file.
• Embedded fonts: the font data, when you asked for it to go.
• Duplicates and unused media: copies collapsed and orphans dropped.
• The archive: this one can be negative, and it is shown as a cost rather than hidden. Storing pictures instead of re-compressing them adds a fraction of a percent and is more than ten times faster.

A compressor that reports a smaller number has not necessarily produced a better file. The two failure modes that matter are a deck PowerPoint offers to repair, and a picture that comes out worse than it went in — and neither shows up in a size comparison.

Key points

• No picture is ever allowed to grow. Every candidate encoding is measured against what is already in the file, and if none of them is smaller the original is kept untouched.
• A picture's format is read from its own bytes. A logo with a transparent background stays a transparent logo. Re-encoding one as a photograph flattens that transparency to black and usually makes the file bigger as well.
• Changing a picture's format renames its part and updates the package's type table. PowerPoint guesses when those disagree, which is how the mismatch goes unnoticed until some other program opens the file.
• Removing a part means removing everything that pointed at it. A leftover reference is what produces "PowerPoint found a problem with content" and a repair prompt.
• The stored orientation is what PowerPoint draws. A phone photo carries a rotation tag that slide software ignores, so applying it here would turn the picture inside your deck.

Runs on your device, with the work spread across the cores it has. A 30 MB deck is unpacked and repacked in about 120 milliseconds because the pictures inside it are stored rather than re-compressed — there is nothing left to squeeze out of a JPEG, and trying costs ten times as long for a fifth of a percent.

Change any setting after a run and the results that no longer match are marked out of date rather than quietly left as they are. They stay visible and downloadable — an old result is out of date, not invalid — and the button becomes "Re-apply", so one press brings the whole queue up to the current settings. It is worth trying Web where you started with Print: on a photograph-heavy deck that alone is often the difference between eight megabytes and one.

• Start with Print (220 ppi). It is more resolution than any projector can show, and it is usually enough on its own.
• If the deck will only be read on a screen, use Web (150 ppi). Nobody will be able to tell.
• Read the breakdown before changing anything else. If it says the deck is mostly video, no picture setting will help.
• Leave layout removal on unless you are still building the deck — it costs nothing visible and often recovers megabytes.
• Try dropping embedded fonts only if everyone opening the file has the fonts, or if it is heading for PDF anyway.
• Check the before-and-after picture view rather than trusting the percentage: it shows the deck's largest picture at full size.
• For a deck that has been through review, keep change-history removal on. It is free and it is often the biggest single win on a text deck.

Embedded video and audio are passed through rather than re-encoded — their size is reported so you know that is where the bytes are. Metafiles and vector artwork (the EMF and WMF drawings PowerPoint creates from pasted Excel charts) cannot be resampled by any browser and are left untouched. Animated pictures are passed through whole. The WebP option produces the smallest photographs available but is only read by PowerPoint 2021 and later, so it is off by default and clearly marked. Older binary .ppt files are not supported at all — save one as .pptx first.

A .pptx file is a ZIP archive with a documented structure inside it. Open one and you find an XML file per slide, another per layout and master, a folder of the pictures those slides draw, and a set of relationship files tying them together. That is why a presentation can be made smaller without opening PowerPoint: the pictures are ordinary picture files and the structure is readable. It is also why the parts nothing draws are so easy to miss — they are inside the archive, they are perfectly valid, and nothing in PowerPoint's interface lists them.

• Getting a client pitch deck under an e-mail attachment limit without turning it into a shared link.
• Uploading a lecture deck to a learning platform that caps file size per upload.
• Cleaning up a template deck that has accumulated masters from every deck it borrowed a slide from.
• Shrinking a conference talk so it opens quickly from a USB stick or a shared drive.
• Preparing a deck for a PDF export, where embedded fonts and full-resolution photographs are pure overhead.
• Archiving a year of team decks without paying for the storage twice over in duplicate logos.
• Compressing decks under an NDA, where uploading to a compression service is not an option.

• Change Slide Size
• Merge PowerPoint
• Add Watermark to PowerPoint
• Split PowerPoint
• Extract Text from PowerPoint
• PowerPoint Word Count