Working with Transparent PNGs in PowerPoint, Google Slides and Keynote

A cutout that looks flawless in an image editor can look wrong the moment it lands on a slide. A white box appears behind it. A pale halo shows up that was invisible a minute ago. The picture goes soft after you save and reopen the deck. None of these are the same problem, and each one has a specific cause.

This is the slide-deck companion to the same question in Photoshop, Figma, and Canva. Presentation software has its own habits, and they are worth knowing before you build forty slides on top of them.

First, confirm the file is actually transparent

Before blaming the presentation app, rule out the file. A surprising share of "PowerPoint broke my transparency" cases are images that never had an alpha channel to begin with: a cutout exported as JPG, which cannot store transparency at all, or a PNG saved from a program that flattened it onto white on the way out.

Check Transparency answers this in one step. Drop the file in and it reads every pixel, not a sample, and reports how many are fully transparent, how many are partially transparent, and how many are fully opaque. A file with zero transparent pixels is a flat image wearing a PNG extension, and no slide software on earth will make it float.

If the report says the alpha is there, the problem is downstream, and the rest of this article applies.

Insert the file, do not paste the picture

The most reliable way to lose an alpha channel is to copy an image from somewhere and paste it onto a slide.

What travels through a clipboard depends on the source application, the destination application, and the operating system. Sometimes it is the original file. Sometimes it is a bitmap that has already been composited against something, and that something is usually white.

Use the insert or upload path and point it at the file on disk. It takes two more clicks and it removes an entire category of mystery.

Test on a dark slide, because white hides the defect

This is the single most useful habit in this whole article.

Cutouts are almost always produced and reviewed against a light background, and a light background hides two specific defects. A pale fringe left over from a light original blends into white and is invisible. Semi-transparent pixels inside the subject, where a model was uncertain, also disappear against white because white is what shows through.

Put the same cutout on a dark slide and both jump out immediately.

You do not need to build the slide to find out. Add Background will composite the cutout against a solid colour of your choosing, and doing that against the actual colour of your deck takes a few seconds. If a fringe appears, it was in the pixels the whole time and it will appear on your slide too.

Worth knowing about the fringe specifically: it is colour contamination on the partially transparent edge pixels, carried over from the background that used to be there. The Colour Picker will tell you, by reading the colour at a pixel whose alpha is between zero and full. If that colour is the old background rather than the subject, you have found it, and edge decontamination in the editor is the fix.

Slides are measured in pixels even when they pretend otherwise

Presentation software talks in inches and points, which invites people to think about DPI. On a slide, do not. A deck is displayed on a screen or a projector, and what matters is the pixel count.

The practical target: for an image that fills a widescreen slide, start from something at least 1920 pixels wide. For a cutout occupying a third of the slide, 800 to 1000 pixels is plenty. Anything substantially larger than that is bytes you are carrying for no visible benefit.

Resize to the size you need with the Image Resizer before you insert. Dragging a 4000-pixel image down to a corner of a slide makes it look right and leaves the full file inside the deck.

Deck bloat is caused by the images, always

A presentation that will not email is a presentation full of full-resolution PNGs.

PNG is lossless, which is exactly what you want for a cutout with a soft edge, and it is also why the files are large. The honest trade-offs, in order of preference:

• Resize first. This is the biggest win by a wide margin and it costs nothing visible.
• Keep PNG for anything with a transparent edge, because lossy compression damages soft alpha edges more visibly than it damages photographs.
• Use a compressed format for full-bleed photographic backgrounds, which have no transparency and do not need lossless storage. Compare Formats will show you what the same image costs as WebP, AVIF, and JPG next to the PNG.

Presentation apps also have their own picture-compression setting that can re-encode images when the file is saved. If your images look crisp while you are editing and soft after you reopen the deck, that setting is where to look. It is per-file and it can be turned off.

Exporting the deck decides whether transparency survives

Transparency inside the deck and transparency in what you export are different questions.

Exporting slides to PDF keeps the compositing you built, because each slide is rendered as a page. Exporting slides to JPEG flattens everything, because JPEG has no alpha channel; your cutout is baked onto whatever was behind it, which is fine if what was behind it was your slide background, and a problem if you were relying on transparency for something else.

If you need a single slide as a transparent image, the export you want is PNG, and if the app will not give you one, build the graphic outside the deck instead.

The Google Slides difference that is worth a sentence

Google Slides handles transparent PNGs correctly. The thing to know is not about alpha, it is about where the file goes: uploading an image to Slides means the image is on Google's servers, for as long as the deck exists.

For most decks that is entirely fine. For a deck containing an unreleased product shot, a client's brand assets, a medical image, or a photograph of someone who has not agreed to be in a cloud drive, it is worth a moment's thought, because it is a decision you only get to make once.

Everything that happens before that upload, the background removal, the edge work, the resize, the metadata strip, runs on your own machine here and produces a file you choose what to do with.

The checklist

1. Run Check Transparency on the file. Confirm there is a real alpha channel.
2. Composite it against your deck's actual background colour and look for a fringe.
3. Resize to roughly the size it will occupy on the slide.
4. Insert from disk. Do not paste.
5. Keep PNG for anything with a soft edge; use a lossy format for full-bleed photos.
6. Check the app's picture compression setting if things soften after a save.
7. Export to PDF when you need the compositing preserved.