How to use Claude for PowerPoint properly
There is one fact about the Claude for PowerPoint add-in that decides whether the output is usable, and almost nobody is told it: it builds slides using the template already open in front of it.
Claude reads the slide master, layouts, fonts and colour scheme of the deck you have open and works inside them. So a deck built from a blank default file gets default slides, and no amount of asking for brand compliance afterwards fixes it. Open your template first. Everything below assumes you did.
Checked against Anthropic's published documentation in September 2026.
Getting it installed
Install it from the Claude for Microsoft 365 listing on Microsoft AppSource, then open PowerPoint, activate the add-in and sign in. It is generally available on Pro, Max, Team and Enterprise plans.
It runs on PowerPoint for the web, on Windows with a Microsoft 365 subscription (build 16.0.13127.20296 or later), and on Mac from version 16.46. It does not run on the 2016 or 2019 perpetual and volume licences, on iPad, or on Android.
Ask for the outline before the slides
This is the single highest-value habit available, and it costs two minutes.
I need to present [subject] in 15 minutes. Propose a slide-by-slide outline first, with the argument each slide is making. Do not build anything until I approve the outline.
Arguing with a list of one-line slide titles takes two minutes. Arguing with a finished deck takes an hour, and by then you are editing rather than deciding. Splitting decide what to say from make the artefact produces better decks than asking for both at once, and it is the pattern that recurs through everything else here.
The same applies when you are working from a document. Rather than "turn this report into a deck", try: first tell me the six things an executive audience actually needs from this. Do not write slides yet.
Editing: select, then say what changes
Claude makes pinpoint edits to specific slides without regenerating the whole deck, and it preserves the formatting and the surrounding context while doing it. Select the slide or the element, then describe the change. That is far more reliable than describing which slide you mean.
It is not limited to one slide at a time — restructuring a storyline across a run of slides is a perfectly ordinary request. But the narrower the target, the more predictable the result.
Useful edits that are easy to forget you can ask for: combining two slides that make one point, splitting one that makes two, adding an executive summary using a layout already in the template, and reordering the deck so it leads with the recommendation rather than saving it for the end.
Native charts, not pictures of charts
Claude converts bullets into diagrams, process flows and editable native PowerPoint charts — visuals you can edit directly rather than static images. This is worth asking for explicitly, because the difference only shows up later, when somebody needs to update a number and discovers whether they can.
Create a bar chart comparing Q1 to Q4 performance, as a native PowerPoint chart I can edit.
And when a slide is a wall of text, ask for options before a rebuild: propose three ways to make this visual, then build the one you think is strongest.
Titles carry the deck
A reader who only reads your slide titles should get the whole argument. Most decks fail that test, and the fastest single improvement available is to fix it in one pass:
Rewrite every slide title so it states the point rather than the topic. Show me the before and after list first.
"Q3 results" is a topic. "Renewals carried Q3; new business did not" is a point. The second one survives being read alone on a phone.
The subtraction prompt
Asking what could be removed produces better results than asking what could be improved, because it forces a judgement about what is load-bearing.
Cut this deck from 18 slides to 10. Tell me what you cut and why before you do it.
Related, and just as useful: an executive will look at this for four minutes — which four slides should they see?
Persistent instructions worth setting
Settings has an Instructions field that applies to every conversation in PowerPoint, separate from the ones in Excel and Word. Good candidates are the house rules you would otherwise repeat every time: one-line bullets, never more than five per slide, titles as statements in sentence case, and the accent colour for emphasis only, never decoration.
One is worth setting on day one: tell it never to invent a number, and to write a visible placeholder when a figure is not in the source. It turns the most dangerous failure mode into something you can search for.
Working across Excel, PowerPoint and Word
The add-ins can share one conversation, so a chart on slide four can be built from the model open in Excel. The setting is "Let Claude work across files", in each add-in's settings. It is on by default for Pro and Max and off by default for Team and Enterprise, and the toggle is per device.
Two limits before you rely on it: Claude can only read and write files that are currently open, and it cannot create, open, close or switch files itself.
What to check before you send it
Anthropic's guidance is explicit that the add-in is not recommended for final client deliverables without human review, and that it does not replace your judgement on design and narrative flow. Treat what follows as the minimum.
Every number, against the source — not against another slide. Numbers that disagree between slides are the error most likely to be spotted by exactly the person you did not want to spot it.
Every claim that names someone else. Competitors, customers, market figures.
The template. Fonts, colours and layouts, especially on slides built early in a long session.
The argument. Read only the titles, in order. If they do not tell the story, the deck does not either.
Files from outside. Anthropic warns that downloaded templates, vendor files and shared decks can carry hidden instructions designed to manipulate the add-in. When Claude asks you to confirm an operation, read the confirmation rather than clicking through it — particularly on a file somebody else sent you.
Where to go from here
Everything above works better with a template worth opening. The Claude for PowerPoint Deck Toolkit is built for exactly that: four .pptx templates with 41 designed pages between them — executive summary, SWOT, strategy grid, process chevrons, roadmap, segment blocks, native charts, tables — plus a 14-page prompt library of 56 prompts organised by task, and four finished sample decks that each carry the prompt that produced them in the speaker notes.