Skip to content
All articles
live-present

Speaker Notes for HTML Presentations

Keep speaker notes on your screen while the audience sees only the slides. Add them in the app or from Claude or Cursor, and edit them live in presenter view.

HTML decks usually skip speaker notes because there is no PowerPoint notes pane. So you print a script or juggle a second document and lose your place. You do not have to. Notes live with the deck and show only on your screen.

Here is what you get:

  • A teleprompter for HTML slides. The current slide and your next line, side by side.
  • The audience never sees your notes. They open the view link and get the deck only.
  • Edit the script without rebuilding the deck. Fix a line in the dry run and keep the deck you already have.

This assumes you already host the file. If you still need a URL, start with how to share an HTML presentation or host Reveal.js slides.

Why notes belong on the hosted deck

Notes next to the live slide beat a printed packet:

  • You see the current slide and the next thought without a paper shuffle.
  • You can edit a line during the dry run without rebuilding the whole deck.
  • Your agent can write the notes the same way it writes the slides.

The audience does not see this pane when they open the view link. That is the whole point of presenting without screen sharing: they get the deck, you get the teleprompter. No second monitor to forget, no printed script to lose your place in, and no risk of the notes leaking because you shared the wrong window.

Where notes can come from

You have three ways to add notes, and you can mix them:

  • In the app. On the presentation page, type notes for each slide. You can keep editing them in presenter view while you talk.
  • From your agent. Once you connect Model Context Protocol (MCP), you can ask Claude or Cursor to “read the notes, rewrite slide 3 to 40 words, keep the joke on slide 7.” It updates the notes, not the whole deck.
  • Imported from your deck. If your slides already include per-slide notes, Prezzly picks them up when you upload, so decks your agent wrote arrive with the script attached.

Use whichever fits your workflow. Most people type in the app for a one-off talk and let the agent handle notes when it is already writing the slides. The point is that the script lives with the deck, so when you reopen the link a month later to give the talk again, the notes are still there. You are never reconciling a slide file with a separate document, and there is no “which version of the notes is current” question the morning of the call. One deck, one link, and one script that always travels with it.

How presenter view uses them

Open presenter view while signed in. The notes panel shows the text for the current slide. The font size is for you; it does not change what the audience sees. A talk timer sits in the same view, and none of it appears on the public link. If your deck came from an AI tool, this is the same presenter view you use to present a Claude artifact.

A short workflow that holds up:

  1. Write or generate slides with notes already filled in.
  2. Upload the deck (or let the agent publish it).
  3. Dry-run in presenter view and fix the wording.
  4. If the story changes, rewrite the notes or rebuild the slides and upload again.
  5. On the live call, keep presenter view on your laptop and the view link in the chat.

How notes and versions work together

When a slide has notes from more than one source, the notes you typed in the app win. That lets you keep a clean generated deck and still tweak the script without another build. Delete your typed note if you want the version from the file to show again.

The notes you type stay with the presentation, not with a single upload. So if you restore an older version of the slides, your practised script is still there. That is usually what you want. It surprises people who expected the notes to roll back with the files, so it is worth knowing before a big talk.

If you work with an agent, pick one home for the script per deck. Mixing sources works, but it is harder to explain to a colleague who opens the notes a month later.

What not to do

  • Do not put secrets in notes you might screenshot. Notes are stored with the presentation, and anyone you give access to can read them. A screen share of presenter view will show them.
  • Keep your script in Prezzly, not in a separate PDF. One source of truth means nothing to keep in sync before a talk.
  • Do not assume every imported deck arrived clean. Check the notes after the first upload.
  • Do not keep the only copy of your script in another tool’s speaker view. Move it into Prezzly so it travels with the deck.

Frequently Asked Questions (FAQ)

Can the audience open a “notes” URL?

No. Notes are for the signed-in presenter. The public view link is the deck only.

Do I have to put notes in the deck itself?

No. Typing them in the app, or having your agent write them, is enough. Notes in the file are just convenient when the agent already wrote them.

Why did my notes not import?

Some decks store notes in a format the import does not recognise. Paste them into the app once, and they will show in presenter view.

Can I have notes on a dashboard?

Notes are a slide feature. For a scrolling report, keep a separate outline or a short presentation as your talk track. A shareable live dashboard is a scrolling page, so pair it with a short deck when you need a script.

Will notes use up my storage?

No. Notes are tiny and are not what fills the free storage cap. Your slides and images are.


Put the script next to the slide, not in a side document. Present with notes from a hosted HTML deck. The room sees the slides. You see the next line.

Ready when your presentation is

Present with notes

Host the deck, open presenter view, and keep notes on your screen. The audience never sees them.

Present with notes