Presentation summarizer: summaries that keep slide numbers, so you can check them

Echo the structure first

Ask for every slide number and title before any summary. If a number is missing or the order drifts from your deck, the file did not come through the way you expect. Fix that first.

Cite a slide for every claim

Ask for a slide number on every bullet. A claim with no slide behind it is the first one to check, and the cheapest way to catch an invented one.

Check numbers and chart values

Compare each figure with the slide. For charts, ask the model to state the axis labels and the values it read, then look at the chart. If a value is not printed on the slide, treat it as an estimate.

Test the speaker notes

This page does not document how speaker notes are handled. Ask the model to quote any note it relied on. If nothing comes back and your deck has notes, they were not read.

A prompt that builds the checks in

Summarize this deck.
1. First list every slide number and its title.
2. Then give a one-sentence TL;DR.
3. Then bullets in slide order, each ending with (slide N).
4. Then action items with an owner, each ending with (slide N).
5. Quote any speaker note you relied on.
6. Mark any number or chart value you could not read clearly as [unclear].

For a high-stakes deck, send the same file to a second model and read only the claims where the two disagree. Once the summary is checked, you can turn the reviewed summary into a new presentation.

What this page has not measured

• How long a summary takes. No latency was measured for this page, and it depends on deck size, the model and whether images are read.
• The largest deck that works. No slide-count or file-size limit is published here.
• How closely each model follows a chart. The matrix above is reasoning, not a test.
• How speaker notes, tables and embedded objects come through. Run the structure check on your own file.

Use this workflow if

You have a deck and want a summary you can verify

You are not inside PowerPoint, or you want to choose the model and compare two on a slide-heavy deck.

Use Copilot in PowerPoint if

You work in Microsoft 365 and Copilot is included

Microsoft's support page says Copilot in PowerPoint can summarize presentations of up to about 40,000 words and shows references to where it drew information, and that Copilot may not be available depending on your subscription or organisation settings (Microsoft Support, read October 2026).

Use the PDF summarizer if

The deck is a PDF or a long report

Slide structure is gone once a deck is flattened, so a long PDF suits AI PDF summarizer better.

Use Google Slides tools if

Your deck lives in Google Slides

Start from Chat with Google Slides, or export the deck and upload the file, then run the structure check.

Summarize when

• You are forwarding a long deck and want a one-paragraph cover note.
• You are triaging a backlog of updates and need to pick the ones that matter.
• You missed a review and need the decisions and action items.

Read it yourself when

• The design is the content: brand books, storyboards, stage keynotes.
• You are accountable for the exact figures, such as a financial or legal disclosure.
• The slides are mostly images with little text and you cannot check what the model saw.