Claude for PowerPoint can build slides from a deck's loaded template and make targeted edits. That gives a presentation owner a way to draft a new section inside an existing file. The useful result is a saved PowerPoint copy whose claims, layout and editable objects the owner has inspected. This guide uses an approved fact brief as its input; BIG CHANGE has not installed the add-in or tested a generated deck.

The big change

What changed: Anthropic documents a PowerPoint add-in that can create slides using the loaded template's layouts, fonts and colors, and edit selected slides. Why it matters: A presentation owner can ask for a bounded section in the native deck, then check it against the records used to approve the underlying facts. What to watch: Template compliance and editable output are claims to verify in the resulting file. The add-in's manual does not establish automatic retrieval of arbitrary web pages or verified slide citations.

The task here is specific: add exactly three slides to a copy of an existing, authorized deck. Begin with a short, approved brief that maps each material fact to its source. Finish only when the saved copy reopens with those three slides in the intended place, the surrounding slides intact, and every required claim and object checked in PowerPoint.

For other presentation tasks, our guide to creating and exporting a local AI slide deck produces an HTML viewing export. Our Excel-to-PowerPoint chart guide updates one existing native chart from workbook cells.

Before opening the add-in

You need permission to use the deck and its template, the facts you intend to send to Claude, and a supported client. Anthropic lists PowerPoint on the web; Windows PowerPoint with a Microsoft 365 subscription at build 16.0.13127.20296 or later; and Mac PowerPoint 16.46 or later. It lists PowerPoint 2016 and 2019 perpetual or volume editions, iPad, Android and older Microsoft 365 builds below the SharedRuntime threshold as unsupported.

Claude for PowerPoint is generally available on Claude Pro, Max, Team and Enterprise. For an individual installation, use Anthropic's Claude for Microsoft 365 listing in Microsoft AppSource, then activate the add-in and sign in with your Claude account. Office Store access and organizational policy can restrict installation. Administrators can deploy it through Microsoft 365 Admin Center, including a documented custom-manifest route when the Store is disabled. An administrator may instead configure a third-party AI platform; that route can change sign-in, model availability and billing. Follow your organization's approved route.

Create a working copy of the deck before requesting edits. In your fact brief, list the audience, the decision the section supports, the three slide purposes and the exact insertion point. For each material claim, record the underlying source, its date, the wording the source supports and any qualification. Mark a missing fact as missing; leave it out of the proposed slides until someone verifies it. Use only material you are allowed to put into this add-in, and check any externally supplied template or file before use. Anthropic warns that external files may contain hidden instructions intended to redirect the add-in.

Make a bounded proposal

  1. Open the deck copy and Claude pane. Confirm that the intended template is already applied. Keep the original available for comparison. If your team uses recurring PowerPoint preferences, the add-in's Settings > Instructions field can hold them; those instructions apply to PowerPoint conversations, not to Excel or Word. This one-app procedure needs no connector.
  2. Ask for a plan before slide creation. Enter the approved brief manually. Adapt this request to your approved slide purposes:
Snippet
Plan exactly three slides after the current overview slide. Slide 1 states the documented problem, slide 2 explains the approved evidence, and slide 3 states the supported decision. For each slide, list the proposed claim and the source label from my brief. Mark anything the brief cannot support. Do not change existing slides yet.

These slide purposes are an example to replace with your own approved purposes. A plan-first request is an editorial check, not a guaranteed product approval screen. Compare the plan with the brief and source records; remove or correct any extra assertion.

  1. Request the section after the plan checks out. Adapt this request to the checked plan and actual insertion point:
Snippet
Add only the three approved slides after the overview slide in this deck copy. Use the loaded template's appropriate layouts, fonts and colors. Keep the preceding overview and following section unchanged. Use only the checked claims and source labels in the plan. Leave unsupported items out.

Anthropic documents building slides from templates and making pinpoint edits. This exact prompt and its result have not been tested by BIG CHANGE. Inspect the actual changes rather than assuming the requested boundary was obeyed.

  1. Check every factual element. Compare each sentence, number, date and qualification on the new slides with the approved brief and its underlying record. Check every visible source label too. A label generated on a slide is text, not proof that Claude opened or cited that source. Add or correct references yourself where the audience needs them. If a chart or diagram appears, check the displayed values, categories and labels against the same records.
  2. Inspect the PowerPoint file. Confirm the slide count, insertion point and surrounding content. Check the applied layouts, fonts, color contrast, text overflow and any image's factual implication. Select and edit each text box, chart or diagram that must remain editable; a slide that merely looks native does not prove its objects are editable. Anthropic documents editable native charts and diagrams as capabilities, but this guide does not assume every generated visual uses them.
  3. Keep, repair or discard the copy. If a fact fails, correct or remove it and repeat its source check. If a layout fails, repair that slide manually or request a narrower edit, then repeat the affected layout and object checks. If the add-in changed the wrong slides, restore the working copy from the original and start again with a narrower request. Save and reopen the final copy. Keep it only if the intended three slides and surrounding deck survive that check; sharing it is a separate human decision. “Keep” and “discard” describe your file decision, not per-slide Accept/Reject controls or tracked changes in the add-in.

Usage, records and limits

The manual states no fixed per-deck price, processing time or accuracy guarantee, and the add-in offers a curated set of models that may be restricted by the organization. Usage and billing depend on the account route. Individual and seat-based plans can have usage limits; Anthropic's current Enterprise guidance says usage-based Enterprise plans bill consumption separately at API rates, with organization and user spend controls. Check your plan and administrator's settings before a substantial job. A failed output can still require another attempt and more usage.

Anthropic says add-in inputs and outputs are deleted from its backend within 30 days, subject to exceptions, while conversation history is stored locally in the browser. The PowerPoint add-in does not inherit an organization's custom retention settings, and its activity is absent from Enterprise audit logs; Anthropic describes separate Compliance API coverage for eligible organizations. Review those rules before using sensitive or regulated material. Inspect any confirmation for a risky operation, and review the saved slides before treating them as a final deliverable.

Sources & further reading