How to Present a Claude Artifact

Claude built you a good-looking deck as an artifact. Then you have to actually present it to a client, and the cracks show. The artifact renders inside Claude’s window. There is no presenter view, no speaker notes on a second screen, no laser pointer, and no way for a remote audience to follow your slide. When the client asks you to “share your screen,” you are back to streaming a video of your laptop.

The fix is to stop treating the artifact as something you present from inside a chat tool. Host it as a browser link and present from that instead:

• One link that renders the same everywhere - your machine, the client’s machine, any browser.
• A real presenter view with speaker notes, a timer, laser and pen.
• A live audience that follows your slide and can pin questions on the exact spot.

Prezzly does not build the deck. Claude does. Prezzly gives it the presenter mode and the platform-agnostic link the artifact never had.

What a Claude artifact cannot do when you present

The artifact is great for looking at. Presenting is a different job, and this is where it falls short:

• No presenter view. You see exactly what the audience sees. Notes have nowhere to live.
• No audience follow. If you send the artifact, everyone is on their own slide. You cannot move the room.
• No pointer or annotation. You end up waving the cursor and describing where to look.
• It is bound to the chat tool. To show it, you screen share the Claude window, which throws away every benefit of clean HTML.

If your instinct is to screen share, read why you should present without screen sharing first - it is the same trap, one layer up.

Get a browser link that always renders the same

Before the meeting, get the artifact off the chat and onto a link. If you have the HTML file or a ZIP, drop it on Prezzly and copy the URL. No login required to try it. If Claude produced the file for you but you have not moved it yet, send it as a hosted link and you are ready.

The point of the hosted link is predictability. It opens in a browser, and a browser renders the same whether you are on Windows in a conference room or the client is on a Mac at home. You are not hoping a screen share survives compression, and you are not asking anyone to install anything. When you walk into the client’s meeting tool, the deck is a URL that just works - that is the whole stress you are trying to remove.

One caveat, stated plainly: hosted HTML runs in a sandbox, so an artifact that depends on advanced standalone-site features may behave differently than it did in Claude. Open your own link once before the call and click through it. If it looks right, it will look right for the audience.

Presenter mode: notes, laser, and audience follow

This is what the artifact was missing. Open presenter view (you need to be signed in) and you get the operator’s side of the deck:

• Speaker notes on your screen only. The audience never sees them. If you want to add or clean up notes, speaker notes for HTML presentations covers where they come from.
• A talk timer and filmstrip so you know where you are.
• Laser pointer and pen to point at a number or circle a line, live.
• Audience questions pinned to a specific slide, grouped by session so today’s call is not mixed with last week’s rehearsal.

When you go live, your slide changes, scrolling, laser, and pen show up for remote viewers, and they can lock to “follow presenter” so nobody drifts. Someone who joins late lands on your current slide. This is not multiplayer editing - you drive, they follow.

Paste it into the client’s meeting tool

You do not present into Prezzly and you do not need an integration. The meeting tool stays the conversation layer:

• Drop the view link in the Meet, Teams, Zoom, or Slack chat.
• Optionally share your camera and the presenter window if you want faces plus notes - but you do not have to share the slides as video at all.
• If someone genuinely cannot click, sharing a tab still works as a fallback, and the link stays the source of truth after the call.

The link works in those tools the way any URL does. There is no plugin, no install, and no “can everyone see my screen okay?” ritual. That is the platform-agnostic part: whatever the client uses, the deck behaves identically.

The link outlives the meeting

When the call ends, a screen share is gone. A hosted artifact is not. Leave the link in the recap and people reopen the current version themselves. When you fix a slide, publish a new revision to the same link - no “v2” attachment, no re-send. Recipients always open the latest.

That is the quiet benefit of presenting from a link: the invite, the live room, and the leave-behind are one URL. You spend zero energy on delivery logistics and all of it on the actual talk.

Frequently Asked Questions (FAQ)

Does a Claude artifact have a presenter mode?

Not really. The artifact renders in Claude’s window with no speaker notes, no laser, and no audience-follow. Hosting it gives you a presenter view with notes, a timer, annotation, and live audience sync.

Can the audience see my speaker notes?

No. Notes stay on presenter view. The audience sees only the deck, your laser or pen, and any questions you choose to reveal.

Do I have to go live to present?

No. The link works in any meeting without live mode. Live sync is opt-in, for when a remote audience should follow your slide automatically.

Will my interactive artifact work once it is hosted?

Usually, but hosted content runs in a sandbox, so features that assume a full standalone site may differ. Open your own link and test it before you present.

Can I present the same artifact in Zoom and in Teams?

Yes. It is one browser link. Paste it into whichever tool the client uses - the deck opens and behaves the same in all of them.

---

Get the artifact onto a link, open presenter view, and Present from a link. Try the flow yourself first with the live demo so the only thing left on the call is the talk.