How to Generate a PowerPoint Deck from a PDF Using Claude's Official Add-In (Beta)

Turn a Sales PDF into a 5-Slide Deck in Under 10 Minutes

You’ve got a PDF full of sales data — monthly revenue, regional breakdowns, rep performance — and someone needs a deck by end of day. The obvious path is to open PowerPoint, manually recreate every table and chart, and spend two hours doing work that should take ten minutes. There’s a better path now. Anthropic’s Claude for PowerPoint add-in lets you upload that PDF directly inside PowerPoint and generate a fully editable 5-slide deck — revenue charts, product line breakdowns, KPIs, all of it — without leaving the application. The primary artifact here is simple: PowerPoint Home > Add-ins > search “Claude” > upload PDF > get a deck.

This is not a third-party wrapper or a “paste your content here” web app. It’s an official Anthropic add-in that reads your slide master, matches your template’s fonts and color scheme, and generates native PowerPoint elements you can click, resize, and edit like anything else in the file.

Here’s the full setup and workflow.

---

What You Actually Get at the End

Before the prerequisites, it’s worth being concrete about the output, because “AI-generated slides” means different things depending on the tool.

When you upload a PDF sales report and ask Claude to build a five-slide deck, you get editable text boxes, real chart objects with modifiable data, and slides that follow your template’s visual structure. The values in the charts are pulled from the PDF — not hallucinated. In the demo from the source video, a sales metrics report containing monthly revenue summaries, revenue by product line, sales rep performance, regional sales breakdowns, and KPIs produced a deck where the cross-checked values were accurate.

The slides aren’t screenshots. They aren’t static images. Every element is a live PowerPoint object. You can click into a chart and change a number. You can restyle a text box. You can delete a slide and rebuild it. The AI generates the structure; you own the result.

That’s the outcome worth optimizing for. Now here’s how to get there.

---

What You Need Before You Start

Accounts and licenses:

You need a Claude Pro account ($20/month) at minimum. Max, Team, and Enterprise plans also work. A free Claude account won’t give you access to the add-in.

You need Microsoft PowerPoint — either the desktop application or the web version. Both work. iPad and Android are not supported; this is desktop and web only. If your PowerPoint hasn’t been updated recently, update it before trying to install the add-in. Older versions may not surface the add-in correctly.

Installing the add-in:

Open PowerPoint. Go to Home > Add-ins. Search “Claude.” Click Add. Log in with your Anthropic credentials.

If that doesn’t work — and sometimes it doesn’t on first try — go directly to the Microsoft AppSource listing for “Claude by Anthropic.” Sign in with the same Microsoft account you use in PowerPoint, click “Get it now,” and restart PowerPoint. The add-in should appear in your sidebar.

Your PDF:

The file size cap is 30MB. If your PDF is larger, split it before uploading. The add-in also accepts Excel files and workbooks natively, so if your data lives in a spreadsheet instead of a PDF, that works too.

---

Step-by-Step: PDF to Deck

Step 1 — Load your template first

Open the PowerPoint file you want to build the deck in. If you have a branded template with specific fonts, colors, and slide master layouts, open that file before you do anything else.

Claude reads the slide master automatically. It uses whatever is already loaded as its visual reference. The reported first-pass accuracy when a template is pre-loaded is around 90% — meaning the generated slides match your template’s structure most of the time without additional prompting. If you start with a blank file and add the template later, you lose that context.

Now you have: a PowerPoint file open with your template loaded.

Step 2 — Configure persistent instructions

Click the settings icon in the Claude sidebar. Find the “Instructions” field.

This is where you set defaults that persist across every prompt in this session: always use a specific font, always use certain brand colors, always add speaker notes to each slide. If you work in PowerPoint daily and have consistent style requirements, fill this in once and you won’t have to repeat yourself in every prompt.

One caveat: chat history does not persist between PowerPoint sessions. Every time you close and reopen PowerPoint, you start fresh. Your Instructions setting saves, but the conversation history resets. Keep that in mind if you’re planning a multi-session workflow.

Now you have: persistent style defaults configured.

Step 3 — Set your edit mode

In the bottom-left of the Claude sidebar, you’ll see two options: “Ask before edits” and “Accept all edits.”

If you’re new to this add-in, use “Ask before edits.” Before Claude modifies any slide, it will show you what it’s about to do and ask for confirmation. This is the right default because the add-in is still in beta, and occasionally Claude will misread the current state of a slide and propose a change that doesn’t make sense. Being able to review before accepting saves you from having to undo a batch of bad edits.

“Accept all edits” is faster but less forgiving. Use it once you’ve built enough intuition for how Claude interprets your prompts.

Now you have: a safety net configured before any generation happens.

Step 4 — Choose your model

The add-in offers two models: Opus 4.6 and Sonnet 4.6.

For PDF-to-deck generation — which involves reading a document, extracting structured data, and building multiple slides with charts and formatted content — use Opus 4.6. It’s the more capable model for complex, multi-step tasks. If you want to understand more about how token usage and model selection affect cost and quality in Claude workflows, the post on how to save tokens in Claude Code using the Opus plan mode covers the tradeoffs in detail.

Sonnet 4.6 is better for quick edits: fixing a typo, reformatting a single slide, adjusting copy. It’s faster and uses fewer credits. Save it for iteration after the initial deck is generated.

Now you have: the right model selected for the task.

Step 5 — Upload the PDF and write your prompt

Click the ”+” icon in the Claude chat input. Select “Files and photos.” Upload your PDF.

Then write your prompt. Be specific about three things: what you want, how many slides, and any style constraints.

A prompt that works:

“Turn this into a five-slide deck. Include monthly revenue trends, product line breakdown, top sales rep performance, regional breakdown, and KPIs. Use the template already loaded. Keep the tone executive-facing.”

The slide count matters. If you don’t specify a number, Claude will generate as many slides as it thinks the content warrants — which can be a lot, consuming more credits and taking significantly longer. Five slides is a reasonable default for a summary deck.

Generation takes roughly 5-6 minutes for a full deck. Don’t close PowerPoint during generation.

Now you have: a complete first-pass deck with charts and data pulled from your PDF.

Step 6 — Review, select, and refine

Once generation completes, go through each slide. Cross-check the values against your source PDF — in the demo, the numbers were accurate, but you should verify.

To edit a specific slide, click on it in the slide panel. The Claude sidebar will show “Slide X selected” — this adds that slide as context to your next prompt. You can then say “Reformat this slide to use two columns” or “Replace the bar chart with a table” and Claude will target only that slide.

For global changes, don’t select a specific slide. “Add speaker notes in English to each slide” will run across the entire deck. “Translate this entire deck into French” works the same way — one prompt, full deck.

Now you have: a reviewed, refined deck ready for final polish.

---

The Real Failure Modes

Claude hallucinating about slide content. This is the most important limitation to understand. In the current beta, Claude cannot visually see the slides it’s editing. It processes the PowerPoint file as markdown internally. This means it sometimes makes incorrect claims about what’s on a slide — saying there’s text overlap when there isn’t, or describing a chart’s values inaccurately. If Claude starts describing slide content that doesn’t match what you see, click the stop button immediately. Don’t let it continue building on a false premise.

Graphics and images losing fidelity. Because the add-in converts PowerPoint to markdown internally, images and complex graphics on existing slides may lose information during that conversion. If your source PDF contains charts or diagrams you want preserved exactly, you may need to recreate them manually after generation. The add-in is better at generating new charts from data than at faithfully interpreting existing visual elements.

Complex custom layouts breaking. Chevron process diagrams, multi-step visual flows, custom SmartArt — these often don’t render correctly. The add-in handles standard layouts (title + content, two-column, chart + text) well. Anything that requires precise spatial positioning of multiple custom shapes is risky. Build those manually.

File size limits. The 30MB cap applies to the entire PowerPoint file, not just the PDF you’re uploading. If you’re working with a large existing deck and adding to it, watch the file size. Large presentations can hit generation limits mid-run.

Session resets losing context. If you close PowerPoint and reopen it, the chat history is gone. If you were mid-workflow — say, you’d generated a deck and were iterating on specific slides — you’ll need to re-establish context in your prompts. Describe what the deck contains and what you want changed, rather than assuming Claude remembers the previous session.

---

Where to Take This Further

The PDF-to-deck workflow is the most immediately useful entry point, but the add-in’s surface area is broader.

Web search is genuinely interesting: paste a URL into the chat, ask Claude to generate a pitch deck based on the site, and it will research the site and match the deck’s color theme to the site’s design. It’s not pixel-perfect, but it’s a useful starting point for competitive analysis decks or client-facing materials where you want to mirror someone else’s brand palette.

Skills and Connectors extend the add-in further. Skills let you define formatting and tone instructions for specific content types — useful if you’re generating decks with consistent copy patterns. Connectors let you pull live data from external sources directly into the generation context, which is relevant if your data lives in a CRM or BI tool rather than a static PDF.

For teams building more complex AI workflows around document processing and structured output generation, the underlying pattern here — ingest a document, extract structured data, generate formatted output — is something MindStudio handles at a broader level: an enterprise AI platform with 200+ models, 1,000+ integrations, and a visual builder for chaining document ingestion, transformation, and output steps across tools and agents.

The translation and speaker notes capabilities are underrated for international teams. A single prompt handles the entire deck. If you’re regularly presenting the same material in multiple languages, that’s a meaningful time save.

One thing worth thinking about as these tools mature: the abstraction level keeps rising. The Claude for PowerPoint add-in takes a document and generates a structured artifact. Tools like Remy apply the same principle to software — you write an annotated markdown spec, and a complete TypeScript full-stack application gets compiled from it, backend, database, auth, and deployment included. The source of truth shifts from the generated artifact to the input document. That’s a pattern worth paying attention to across domains.

For now, the immediate value is concrete: a PDF full of sales data, a five-slide deck with accurate charts and KPIs, generated in under ten minutes, fully editable, directly inside PowerPoint. The add-in is in beta and has real limitations — the markdown-internal processing, the visual blindness, the complex layout failures. But for the core use case, it works.

If you’re interested in how Claude handles other kinds of structured document workflows, the post on Andrej Karpathy’s LLM wiki approach to building a personal knowledge base with Claude covers a related pattern: turning raw documents into queryable structured knowledge. And if you’re thinking about where Claude fits in broader agent and workflow architectures, what Claude is and how it’s used for AI agents is a useful reference. For teams who want to push further into automating content and document pipelines with Claude, the breakdown of how to build a skill-based content machine with Claude Code shows how the same document-in, structured-output pattern scales to ongoing production workflows.

The add-in will improve. The visual blindness limitation in particular feels like something that gets fixed in a future version. For now, work with it: verify your values, use “Ask before edits,” and keep your PDFs under 30MB.