Present live

Lumdeck has two ways to present: present mode on your own screen, and live sessions where your audience follows along on theirs.

Present mode

Open a deck and choose Present. The deck fills the screen with nothing around it. Use the arrow keys, space or a presentation clicker. Press Esc to leave.

Viewing on iPhone and iPad

For decks with embedded live modules that use the deck-stage slide format, Lumdeck loads only the current slide's bundled HTML modules on iPhone and iPad. Leaving a slide releases its embedded modules to reduce memory use; returning starts those modules again. Selections or other temporary state inside a restarted module reset. The presentation itself keeps its slide position. These decks also use lower canvas resolution and simpler backgrounds on iPhone and iPad to reduce graphics memory. Text, slide animations and interactive controls remain available. Complex decks can still exceed a device's available memory.

Live sessions

In present mode, choose Go live. Pick who may join:

• Workspace members: colleagues signed in to your workspace.
• Members and a link: also anyone holding one of the deck's active share links. They join from the share page with Live · Join, without an account.

Everyone who joins sees the slide you are on and follows as you move. When you end the session, their screens return to the normal deck.

Good to know

• One live session runs per deck at a time. How many viewers can join and how many sessions run at once depends on your plan; see Pricing.
• Guests can only watch: they cannot take control or end the session.
• Revoking the link removes its guests from the session. For a password-protected link on Pro or Team, Share → Edit → New password → Save link also removes its current guests; they must unlock the link again with the new password before rejoining. See editing share links.
• Joining a live session counts as a view of the link, the same as opening it.

Decks that move by themselves

Live sync follows the slide position the deck reports. reveal.js decks and decks that use the URL hash work as they are; for others, add the events in the deck protocol.