How to compress images for Google Slides and PowerPoint

Most oversized decks are not oversized because of slides, text, layouts, or animations. They are oversized because of the embedded images. A single 12-megapixel phone photo dropped onto a slide adds 4 to 8 MB to the file. A 4K screenshot adds 3 to 6 MB. Twenty slides with one large photo each easily produces a 100 MB file before any other content is added.

PowerPoint embeds every image at the resolution it was inserted at. Even if you shrink the image visually on the slide so it only covers a quarter of the canvas, the original pixel data is still stored in the file at full size. Google Slides handles this slightly differently — it does some automatic compression on upload — but the principle holds: a deck cannot be smaller than its biggest images allow.

This matters because the fix is almost always the same regardless of which tool you use. You either compress and resize the images before adding them, or you compress the existing file afterward. Both work. Doing it before is faster and produces cleaner results.

• Image data is the main reason most decks are heavy, not slide content.
• PowerPoint stores full-resolution image data even if the visible size is small.
• Google Slides auto-compresses on upload but cannot fix already-huge source files.
• A 20-slide deck with one large photo per slide can easily reach 100 MB.

The most common mistake is assuming a presentation needs print-quality images. It does not. The largest realistic display surface for a presentation is a 4K projector or a 4K monitor, both of which top out at 3840 by 2160 pixels. Most projectors are 1920 by 1080 or lower. Zoom and Google Meet compress video aggressively, so screen-shared slides arrive on the viewer end at a much lower effective resolution than the original.

For most workflows, these targets are safe and produce visibly clean slides on any modern display. Full-slide background image: 1920 by 1080 pixels at JPG quality 80 to 85. Half-slide hero image: 1280 by 720 pixels at JPG quality 80. Thumbnail or icon-sized photo: 600 to 800 pixels on the long edge. Screenshots with text: match the screen capture native resolution and save as PNG.

The single biggest win is resizing down before compression. A 4000-pixel-wide phone photo that will only ever be displayed at 1280 pixels is carrying three times more pixel data than the slide can ever show. Resizing to the actual destination width and then compressing usually saves more than aggressive compression alone.

• Full HD (1920 by 1080) is enough for almost any slide background.
• Resize photos to the destination width before compression for the biggest gains.
• Use PNG only for screenshots with text or graphics; use JPG for photographic content.
• Zoom and Meet re-compress shared slides anyway, so ultra-high resolution is wasted bandwidth.

The cleanest workflow is to prepare images before they ever touch the deck. This avoids re-compression artifacts and keeps the final file small without any after-the-fact cleanup.

The basic sequence is the same whether you are building a deck in PowerPoint or Slides. Start by running your raw photos through the Image Compressor at quality 80 to 85. For photos that are also larger in dimensions than your slides need, use the Image Resizer first to bring them down to your target width — 1920 pixels for full-width images, 1280 pixels for half-slide content. Once the images are sized and compressed, drag them straight into your slides. The final deck will be a fraction of the size it would have been otherwise.

This pre-compression workflow also makes the deck noticeably faster to navigate during editing. Large embedded images slow down PowerPoint autosave and Google Slides real-time collaboration. Lighter images mean less lag, fewer rendering hiccups, and faster export to PDF if you eventually need that format.

• Resize first, then compress, before importing into the deck.
• Quality 80 to 85 JPG is a safe default for photographic content.
• Pre-compressed images speed up editing as well as the final file size.
• This workflow works the same way in PowerPoint and Google Slides.

PowerPoint includes a compression feature that handles already-imported images, useful when you inherited a deck or only realize there is a problem after the fact. Open the file, click any image, go to the Picture Format tab, and choose Compress Pictures. Two settings matter: which images to compress (the selected image only, or all images in the file), and the target resolution.

The resolution choices map roughly to display contexts. 220 ppi is print quality and rarely needed. 150 ppi is suitable for high-resolution screens and Zoom presentations. 96 ppi is appropriate for email and web sharing and produces the smallest files. For a typical deck that needs to land under 25 MB to send by email, choosing 96 ppi or 150 ppi on all images usually solves the problem in one pass.

Always work on a copy. PowerPoint compression is destructive — once applied and saved, the original resolution is gone. If you might need the high-resolution source images later, keep an untouched copy of the file before compressing.

• Picture Format then Compress Pictures handles the whole deck in one click.
• 96 ppi for email and web, 150 ppi for general use, 220 ppi only when needed for print.
• Apply to all pictures unless you have a reason to keep specific images at full quality.
• Compression is destructive — keep a backup copy of the file first.

Google Slides does not expose a manual compression slider, but it does compress images during upload. The amount it compresses depends on the source. A 50 MB phone photo uploaded directly to Slides will end up smaller in the deck than the original — but still much larger than if you had compressed it to a sensible size first.

The most reliable way to keep a Slides deck small is to compress and resize before uploading, exactly as with PowerPoint. There is no equivalent of the PowerPoint Compress Pictures button inside Slides. If a deck is already too large in Slides, the fastest fix is to download it as a PowerPoint file (File then Download then Microsoft PowerPoint), run Compress Pictures inside PowerPoint, then re-upload the result to Drive.

If your final delivery format is PDF — common for client decks or course materials — compress the deck normally, export to PDF from Slides or PowerPoint, then run the resulting file through the PDF Compressor for a final size reduction. This two-step approach often produces the smallest deliverable possible.

• Google Slides has no manual compression button; pre-compress images before uploading.
• To compress an existing Slides deck, download as PowerPoint, compress, re-upload.
• For PDF delivery, export the deck and compress the PDF as a final step.
• Images uploaded to Slides cannot be re-compressed individually after the fact.

A few habits silently produce oversized decks even when you think you are being careful.

Copy-pasting from email or a browser tab almost always pastes the highest-resolution version of the image available, even if the rendered preview was small. The pasted image inside the slide can be many times larger than what you saw. The fix is to download the image to a file first, compress and resize it, and then insert it through Insert then Image, not paste.

Using PNG for photographic content is another quiet bloat source. A photo saved as PNG is often 5 to 10 times larger than the same photo saved as JPG with no visible difference at slide-display sizes. Reserve PNG for screenshots, logos, and diagrams.

Finally, Save image as from a slide is a misleading button. It often extracts the image at the original embedded resolution, not at the visible slide size. Sharing an extracted image expecting it to be small can hand a 10 MB file to someone who only needed a 200 KB version.

• Do not paste images from email or browsers — save and insert them properly.
• Use PNG only for screenshots and graphics, never for photographs.
• Save image as extracts the original file, not the visible slide thumbnail.
• Insert via Insert then Image to keep workflow consistent and predictable.