How to Make a Presentation with Claude

TLDR: Claude is excellent at presentations because of artifacts: describe the deck and Claude renders a full self-contained HTML slide deck in a side panel you can preview and arrow through, then refine by asking for specific changes. Brief it well (topic, audience, goal, length), get the outline first, then the HTML deck, then iterate. The output is a web page, so the final step is easy: publish it as one live link and send the URL.

If you want to make a presentation with Claude, you are reaching for one of its best features. Ask Claude to build a deck and it does not just hand you bullet points, it renders a real, self-contained HTML slide deck as an artifact you can preview live, step through with the arrow keys, and refine one slide at a time. It feels less like prompting a chatbot and more like briefing a fast, tireless designer.

This guide walks the full workflow with copy-paste prompts, from the brief to a deck you can share as a single link. It sits under our broader guide on how to make a presentation with AI, and it pairs naturally with the ChatGPT version if you use both tools.

Step 1: Brief Claude like a designer

The quality of the deck tracks the quality of the brief. Give Claude the same things you would tell a human: who it is for, what it needs to land, and roughly how long.

I need a presentation. Before you build anything, here is the brief.
Topic: [your topic]
Audience: [who they are, what they already know, what they care about]
Goal: [the single takeaway I want them to leave with]
Length: about 12 slides.
Tone: [confident and plain / playful / formal].

First, give me a slide-by-slide outline. One line per slide:
title plus its purpose. Do not build the deck yet.

Read the outline critically. This is the cheapest place to fix a weak story. Tell Claude what to cut, merge, or add before a single slide gets designed.

The tools got fast enough that the outline is once again the only hard part. Claude does the typesetting; the argument is still yours.

Step 2: Ask for the deck as an HTML artifact

With the outline settled, have Claude build the whole thing as one self-contained HTML file. This is where the artifact panel earns its keep.

The outline is good. Now build the full presentation as a
single self-contained HTML file, rendered as an artifact.
Requirements:
- One full-screen slide at a time, left and right arrow keys to navigate
- All CSS and JavaScript inlined, no external files or CDNs
- Generous whitespace, strong hierarchy, high contrast
- A slide counter and a thin progress bar at the bottom
- A cohesive color theme built around [your brand color]

Claude renders the deck in the artifact panel. You can present straight from it, but the real advantage is what comes next: you refine it in place.

Step 3: Refine slide by slide

You do not regenerate the whole deck to fix one slide. You talk to it. This conversational refinement is what makes Claude feel different from a one-shot generator.

A few changes:
- Slide 4: make it a two-column layout, text left, a simple
  bar chart right
- Slide 7: the headline is too long, cut it to 5 words
- Everywhere: increase the body font size one step
- Add a closing slide with a single call to action

Claude updates the artifact, keeping everything else intact. Keep going until it is right. For a deeper look at this loop across any AI tool, see our guide on iterating on AI-generated pages.

When to reach for reveal.js

Claude’s hand-rolled HTML is great for most decks. When you want speaker notes view, nested slides, fragment animations, and battle-tested keyboard controls, ask Claude to build on reveal.js instead.

Rebuild this deck using reveal.js, loaded so the file stays
self-contained. Use fragments to reveal bullets one at a time
and enable the speaker notes view.

You still get a single web page, and it presents like a real deck: a full-screen slide, a progress bar, and bullets you reveal one at a time.

Nothing about sharing changes, because it is still one file. If you are weighing the whole HTML approach against Office, our HTML slides vs PowerPoint breakdown is the honest version.

Claude vs a traditional slide tool

Here is the trade, laid out plainly.

The pattern most people settle on: build and present with Claude, and only produce a PowerPoint if a specific person needs an editable Office file.

Get the HTML out and preview it

The artifact is live, but sharing it means getting the code out. Use the artifact’s copy button or the code view, or simply ask Claude to print the full HTML in the chat. Then you can see exactly what you are about to publish.

How VisiblePage fits

Claude builds the deck. It does not host it, and the artifact link is not a clean, permanent home you can hand to a client or an audience. VisiblePage is that home. Paste the HTML Claude produced, or drop a ZIP for a multi-file deck, and you get one live URL immediately, with no build step, server, or domain to configure. The slides open full-screen on any device, arrow keys and animations intact, because you are sharing the real page.

Pick public, private, or password-protected at publish time. And because the deck lives at one canonical link, when you revise a slide you re-publish to the same URL and everyone holding the link sees the update, no resending. Once your deck is built, the next step is simply to share the presentation as a link — the same principle behind our full guide to sharing your AI work.

Try it now: Publish your Claude deck with VisiblePage and get a live link in seconds.

A checklist for better Claude decks

• Brief with audience, goal, and length before you ask for slides.
• Lock the outline as its own step.
• Ask for one self-contained HTML file so publishing is trivial.
• Refine in plain language, one slide at a time.
• Reach for reveal.js when you need speaker notes and fragments.

For more on the underlying feature, Anthropic’s own Claude overview is a good primer, and if you are pitching investors specifically, jump to making a pitch deck with AI.

Frequently asked questions

Can Claude make a presentation?

Yes, and it is one of Claude’s strongest use cases. Claude builds a full slide deck as an HTML artifact you can preview and step through, then refine by asking for changes. It does not host the deck, so once it is ready you copy the HTML into VisiblePage to get one live link to share.

What are Claude artifacts for presentations?

An artifact is the side panel where Claude renders a self-contained document, app, or web page it built. For a presentation, ask Claude for the deck as HTML and it appears in the artifact panel as real, arrow-able slides you can preview live before you copy the code out.

How do I get the HTML out of a Claude artifact?

Open the artifact, use its copy or code view to grab the full HTML, or ask Claude to output the complete self-contained HTML in the chat. Paste that into a publishing tool like VisiblePage to turn it into a shareable link.

Is Claude better than PowerPoint for slides?

For building the deck quickly and keeping it interactive, Claude plus HTML slides is faster and more flexible. PowerPoint is better if your team needs an editable Office file. Many people build with Claude, present from the HTML, and only export to PowerPoint if someone specifically asks.

Can Claude turn my document into a deck?

Yes. Paste or attach your document and ask Claude to turn it into a slide-by-slide presentation, then into an HTML deck. We cover this end to end in our guide on turning a document into slides with AI.

The short version

Making a presentation with Claude is a three-move loop: brief it well, ask for a single self-contained HTML deck as an artifact, and refine slide by slide in plain language. Because the deck is a web page, the last step is the easy one.

Ready? Turn your Claude deck into a live link with VisiblePage — your first page is free.