You paste a report into Claude, type "make this into slides", and get back eight good-looking slides that say almost nothing. The headlines are topic labels, the numbers are rounded or missing, and one chart quietly shows a figure you never gave it. You spend 40 minutes fixing a deck that took 40 seconds to make.
The tool is not the problem. Claude Slides, the deck builder Anthropic added in September 2026, is now one of the fastest ways to turn notes into a presentation. The problem is the brief. This guide shows you where Slides fits, what it can and cannot do, and a six-part prompt that produces a deck you can actually present.
What is Claude Slides, and who can use it?
Claude Slides is a presentation builder inside Claude. You ask for a deck in any conversation, Claude drafts it from your notes, files or connected apps, and you edit slides directly or by asking for changes. You can present from Claude, share a link, or export to PowerPoint or PDF. Anthropic says it is now on every plan, including Free.
Anthropic launched Slides alongside Claude Docs on 16 September 2026, according to Fello AI's step-by-step guide. On 8 October, in the same announcement that introduced Dashboards and Motion, Anthropic said Docs, Slides and Design were out of beta and available on every plan, Free included.
Some help pages written before that change still list Slides as paid only, so the quickest check is your own account. Open a new chat and look for Output in the message box. If Slides appears there, you have it.
Two settings can hide it:
--- Code execution and file creation must be switched on under Settings, then Capabilities.
--- Enterprise workspaces need an owner to enable Slides, and organisations using customer-managed keys, zero data retention or HIPAA-ready setups cannot use it yet.
Claude Slides vs a .pptx file vs the PowerPoint add-in: which should you use?
Use Claude Slides when you have raw material and no deck yet. Ask for a .pptx file when you just need something to download and send. Use Claude for PowerPoint when the deck must follow your company template. Use the Google Slides connector when your team lives in Google Workspace. Each route solves a different problem.
Claude now has four ways to make slides, and mixing them up is the most common reason people get frustrated:
--- Claude Slides: a live, editable deck inside Claude. You type on a slide, move elements, comment on a slide or ask in the chat. Exports to PowerPoint or PDF.
--- .pptx file creation: Claude writes code in a sandbox and hands you a finished PowerPoint file, up to 30MB. Any change means a new file.
--- Claude for PowerPoint: an add-in from Microsoft AppSource that reads your slide master, fonts and colours. It is on paid plans, not Free.
--- Google Slides connector: in beta, edits a real Google Slides file in a pane beside the chat. It cannot add charts there yet.
A practical rule: draft in Slides, then finish in PowerPoint if the deck has to sit in a corporate template. There is no direct Google Slides export from a Slides deck, so export to PowerPoint and open that file in Google Slides if you need it there.
Why do Claude Slides decks look polished but say too little?
Because a one-line request gives Claude no audience, no decision and no rules for numbers, so it fills the gaps with safe, generic choices. You get topic headlines like "Q3 Overview" instead of takeaways, bullets that summarise instead of argue, and occasional figures Claude inferred rather than copied. A better brief fixes all three.
A deck exists to move a specific audience toward a decision. If the prompt does not say who is in the room and what you want them to decide, Claude cannot choose what to cut. It keeps everything and makes it pretty.
Users who build decks with Claude every day say the same thing. One Hacker News commenter quoted by eesel's Claude Slides explainer said they dislike the default formatting but find the ideas good enough to treat the draft "as a starting point and replace the bad parts." That is the right expectation. Your job is to make the starting point much closer to the finish.
How do you write a prompt for Claude Slides?
Write an evidence-first deck brief with six parts: the audience and decision, the source, the storyline, slide rules, a rule for guesses, and a checkpoint. The key move is telling Claude to flag every guess as a slide comment instead of writing it into the slide, so you see uncertain numbers before your audience does.
Here is the brief I use for any deck built from a report or spreadsheet:
--- AUDIENCE AND DECISION: who will see it, and the one decision you want from them.
--- SOURCE: which file or conversation to use, and that nothing else counts as a source.
--- STORYLINE: headlines that state the takeaway, not the topic.
--- SLIDE RULES: number of slides, bullets per slide, how numbers appear.
--- GUESSES: any inferred figure goes into a comment, never onto the slide.
--- CHECKPOINT: show the headlines first and wait for approval.
Try this prompt:
Make a Claude Slides deck from the attached [report name].
AUDIENCE AND DECISION: [Our management team]. I want them to approve [a HK$ budget for X] at the end of the meeting.
SOURCE: Use only the attached file. Every number on a slide must appear in the file exactly as written.
STORYLINE: 7 slides. Each headline is a full sentence stating the takeaway, for example "Repeat customers drove 62% of Q3 sales", not "Q3 Sales".
SLIDE RULES: Maximum 3 bullets per slide, 12 words per bullet. Put trends in charts, not text. Last slide: the decision, the cost and the owner.
GUESSES: If you calculate, estimate or infer anything, keep it off the slide and add a comment on that slide explaining what you assumed.
CHECKPOINT: First show me only the 7 headlines in order. Wait for my "go" before building the slides.
The headline-first checkpoint costs one extra message. It is the cheapest way to catch a wrong storyline before Claude spends your usage allowance building it.
How do you edit and check a Claude Slides deck before presenting?
Edit in three passes: fix the storyline in chat, fix individual slides directly on the canvas, then run a skeptical-reviewer prompt that leaves comments on weak claims. Finally, check every number against the source yourself. The review prompt finds logic gaps quickly; it does not replace your own number check.
Slides gives you several ways to edit. You can type straight onto a slide, select an element and move it, ask for changes in the chat, or leave Claude a comment on a specific slide. Use chat for structural changes ("merge slides 3 and 4") and the canvas for wording, because a chat request can quietly rewrite slides you were happy with.
Then run a review pass in the same conversation:
Review prompt:
Review this deck as a skeptical [finance director] who has 10 minutes. Leave a comment on every slide where the claim is weak, the chart could mislead, or the headline does not match the evidence. Do not edit the slides yet. Then list the three comments that matter most.
When the deck is ready, export it. Shared links only open for people with a Claude account, so send a PowerPoint or PDF to clients and anyone outside Claude.
What are Claude Slides' limits and gotchas?
The main gotchas are usage, sharing and formats. Building a deck draws on the same limits as your chats, viewers of a shared link need a Claude account, there is no direct Google Slides export, and mobile apps are view-only. Plan access was also inconsistent in Anthropic's own pages during the change, so verify in your account.
Five things to know before you rely on it:
--- It uses your allowance. A deck built from several files costs more than a normal message. On Free, expect to hit limits sooner.
--- Viewers need Claude. Export a file for anyone without an account.
--- Google Slides users take a detour. Export to PowerPoint, or start with the Google Slides connector instead.
--- Mobile is view-only. Editing and sharing need the web or desktop app.
--- Connected data needs care. Anthropic's help centre warns that features which run code can be manipulated by malicious content into leaking data, so watch what Claude reads when you build decks from shared files or connectors.
Try it now: rebuild last month's deck in 20 minutes
Take a deck you already presented, give Claude the same source report and the evidence-first brief, then compare. Twenty minutes is enough to see whether Slides saves you time, and which parts of your deck process to hand over. Start with a recurring deck, because a good brief can be reused every month.
--- Minutes 0 to 5: fill in the six-part brief for the deck. Be specific about the decision.
--- Minutes 5 to 10: approve or fix the headlines at the checkpoint, then let Claude build.
--- Minutes 10 to 15: run the skeptical-reviewer prompt and read every comment.
--- Minutes 15 to 20: check five numbers against the source, then export to PowerPoint.
Save the brief as a note or a project instruction so next month starts at minute 10. If your team already works in Google Docs and Sheets, our guide to using Claude in Google Workspace covers the scoped-edit approach for those files. Tools change monthly; a clear brief keeps working. We understand AI. We understand you better. With UD by your side, AI doesn't feel cold.
Reviewed by the UD AI team. Details reflect Anthropic's 8 October 2026 announcement and help-centre guidance as reported by Fello AI and eesel AI. Plan access, limits and features may change while Claude Slides evolves.
Which tasks has AI already overtaken?
Fast decks are only one example of work that AI now does in minutes. Test yourself against AI in UD's free AI Battle Staff challenge, and when you are ready to turn tools like Claude Slides into a dependable team workflow, we'll walk you through every step, from tool setup to workflow design and deployment.
