Feature Library

Slide-show player for HTML slides

<0.01 CPU ms
A still of the Slide-show player for HTML slides demo
Still
The live demo starts when it’s in view.Click, → or the wheel for the next build or slide · right-click or ← to undo a build · Home / End · Full screen in the tools

Plays a deck of HTML slides the way PowerPoint presents.

What it costs a frame

<0.01 ms
GPU
not used
CPU, median
<0.01 ms
CPU, 95th pct
0.01 ms
Draw calls
0
Weight
Light

Measured 4 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 156, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: Measured stepping through the deck from code, one press every 28 frames (each build, then the next slide with a push transition, back to the first at the end): the player loading the next slide into its frame, parking and dropping frames, and the slide’s steps. The transitions and builds are CSS and Web Animations, run by the compositor. Nothing runs between presses. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed<0.010.01
apple · Apple A19 Proin a browser tab · 16 November 2026not timed<0.010.02
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed<0.010.01

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Presenting HTML or exported slide decks
  2. Product tours and onboarding steps
  3. Kiosk and lobby screens
  4. Step-by-step explainers and stories
  5. Showing generated reports one page at a time

Pitfalls, in brief

  1. Slides must be same origin (srcdoc, or src on your own host): the player reaches into each frame for its keys, clicks and window.Deck.
  2. Hand the player your page’s keys yourself (player.key(e, false) in a keydown listener) on the element that holds the deck, not on document, unless the deck is the whole page: otherwise arrows and Space stop working everywhere else.
  3. The stage must be positioned with overflow hidden: parked frames wait at left: 300%, and without the clip they widen the page.
  4. A wheel over a slide in a page that scrolls also scrolls the page (the frame chains it up).
  5. Install the slide side in loaded(), and put SLIDE_STEPS_CSS in each slide’s head too, or the builds show for a frame before they hide.
4 more in brief
  1. Only the current slide and its neighbours are kept (two frames at most besides it): state in a slide that is dropped is lost.
  2. Back shows the previous slide finished (toEnd), not from its start, as PowerPoint does.
  3. Clicks on a slide’s own controls (button, a, input, label, [data-no-advance]) don’t step: mark anything else clickable with data-no-advance.
  4. Screen readers: each frame has a title, and the host should announce the slide (the shown callback) from a polite live region outside the frames.
9 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

From DeckStudio. Fully custom code.

slidespresentationslide showdeckiframepreloadingtransitionsweb animationsbuildskeyboardwheelfull screendomno dependencies

Near it in the frame