Beta. AI Presentations is currently in beta. Access is available on request and requires an extra usage plan. Ask us to enable it for your account or team.
AI Presentations is a native deck maker and editor built into the assistant. It doesn't script PowerPoint from the outside. It works on the real PowerPoint file, so what you get back is a fully editable .pptx, not a set of flattened images. This guide covers what it does and how to get the best results.
What it can do
Create a deck from scratch. Describe what you want and it researches the topic (using web and knowledge base tools), plans a storyline, and authors a complete deck.
Create a deck from a template. This is the strongest workflow. You can:
- Upload your own branded PowerPoint template. It analyzes every slide, catalogs the reusable layouts (cover, section, content, image-led, chart, table, and so on), then duplicates and fills those slides with new content while preserving your design 1:1.
- Pick a stored template from the Slides gallery in the composer and it builds on that directly.
Review the outline before building. After it picks the template and plans the story, it shows you the proposed outline: each slide's title, key message, and chosen layout, plus any flagged gaps. You approve or correct it before a single slide is generated.
Edit slides after generation. Once the deck exists, keep refining it conversationally and it edits the same deck in place instead of piling up copies. Supported edits include:
- Replacing or rewriting text in a specific placeholder
- Adding, deleting, duplicating, and reordering slides
- Replacing or adding images
- Updating native tables, cell by cell or whole tables
- Replacing native chart data
- Editing speaker notes
- Deleting stray or defective shapes
Generate or edit images inline. Ask it to create a new image for a slide, or to recolor, restyle, or change an existing one, in a single step. It sizes generated images to the actual picture box so they fill the slot instead of letterboxing.
Self-check with visual QA. After building or editing, it renders the real slides to images and reviews them for blank image regions, overflow, leftover placeholder text, and broken layouts. It fixes what it finds and re-checks, within bounds, before declaring the deck ready.
Export and download. The finished deck arrives as an editable .pptx shown as a preview card in the chat, with its own download button. Slides are rendered to PDF and images internally for previews and QA.
How to create your first deck
- Provide a template. Upload your branded .pptx, or pick one from the Slides gallery in the composer. Using your own template is what makes the output on-brand.
- Describe the deck. State the audience, the goal, the tone, and roughly how many slides. Point it at source material: attach files, reference a knowledge base, or ask it to research a topic. For example: "Build a 7-slide board update on Q3 pipeline for our leadership team, using the attached sales export and our standard template."
- Review the outline. It comes back with a proposed outline. This is the most valuable checkpoint. Fix the storyline, adjust the layouts, and fill in any figures it flagged. Correcting the plan here is far cheaper than fixing a finished deck.
- Let it build and self-check. It generates the slides, renders them, and runs its visual pass. You'll see a preview strip of the slides.
- Refine conversationally. Ask for specific changes ("shorten the title on slide 3", "swap the cover image", "add a risks slide after slide 5", "update the chart with these numbers"). It edits the same deck in place.
- Download. Open the preview card in the chat and use its download button to get the editable .pptx.
Best practices
Use your own template. This is the single biggest quality lever. A good branded template with clear cover, section, content, image, chart, and table slides gives it a rich design system to work from and guarantees an on-brand result.
Bring the content, don't make it guess. Attach the data, report, or knowledge base you want the deck built from. Source-backed slides are more accurate and leave fewer gaps to flag.
Treat the outline as the real decision point. Read it properly before approving. Reordering the story or changing a layout at the outline stage costs nothing. Doing it after a full build costs a rebuild.
Give figures and specifics. If the deck needs ROI numbers, dates, or metrics, provide them. Otherwise it flags them as assumptions, which is honest but leaves gaps.
Keep slot content the right size. Narrow title slots need short titles, multi-card layouts need enough distinct points to fill each card, and roadmap or timeline slides need real phases. If content is too long, ask to split it across slides rather than cramming it in.
Edit in place, don't restart. To change a finished deck, ask for the edit. Don't ask for a brand-new deck. It deliberately edits the existing file so you keep one clean deck and its history instead of a pile of near-duplicates. To start a genuinely different presentation, open a new conversation.
Let the QA loop finish. After edits it may render and fix a couple of times. That's the self-check working. It's bounded on purpose, so it won't loop forever, and it tells you if any minor issue remains rather than hiding it.
Plan for the extra usage plan. Deck generation, image creation, and repeated rendering are compute-heavy, which is why the beta requires an extra usage plan. Approving a solid outline up front is also the best way to keep usage efficient.
Limits during beta
- It preserves your design by default and won't redesign slides unless you ask.
- Complex objects like SmartArt or embedded OLE content may be flagged as non-editable rather than altered.
- It renders with LibreOffice for QA, so previews are faithful but can differ slightly from Microsoft PowerPoint. Always open the downloaded .pptx for the final check.