01Start here
Auto
Choose a mood and let the conductor rotate eligible scenes and local video while the visual engine responds to the selected audio source. A manual scene choice temporarily takes priority.
LumaDeck Web · Feature guide
One instrument.
Three ways in.
Let the show move in Auto, play scenes and FX by hand, or bring your own videos and GLSL. The audience sees the composition; you keep the controls.
48scenes included in Free
239scenes in the web catalog
48 + 19MIDI targets: scene pads + live controls
Local mediavideos and custom GLSL stay in the browser profile
The stage contract
One screen for you.
One for the audience.
The Master keeps scene pads, audio controls, layers, FX, text and branding within reach. A visual-only surface carries the live composition without the control interface.
This is an output layout, not a hardware promise. The way a second display is connected and arranged depends on the computer, operating system, browser and display hardware in the setup.
Auto · Perform · Create
Start simply.
Go deeper when needed.
These are three depths of the same live instrument, not separate applications. A show can move between automation and direct control.
02Live control
Perform
Launch scenes, mix the composition, set BPM, trigger performance states and FX, and add text or branding from the Master. Web Pro can map the instrument's current MIDI target set.
03Your material
Create
Use local video clips or custom GLSL alongside the built-in scenes. Free provides one slot for each; Web Pro expands the working bank to 21 video clips and 21 shaders.
Performance control
From pointer
to muscle memory.
The on-screen Master remains the reference surface. MIDI Learn adds a physical route to a finite, explicit list of controls when WebMIDI is available and permission is granted.
MIDI Learn · Web Pro
67 current targets.
Map all 48 scene pads and 19 live controls. The current control group includes mood selection, next scene, performance states, three live FX and five continuous Master parameters.
- Learn one control at a time, then delete or replace individual mappings.
- Mappings and MIDI device identifiers stay in the current browser profile.
- Video pads are not MIDI targets in the current release.
Local video + custom GLSL
Bring your own visual language.
Add clips from the device or load GLSL into Shader Lab. Custom shaders are analysed and compiled locally before they can enter a show; accepted shaders use the same time, resolution and audio-reactive inputs as the instrument.
- Free: one video up to 15 MB and one custom shader.
- Web Pro: up to 21 videos at 30 MB each and 21 custom shaders.
- Local assets can be assigned to the working show without uploading their contents.
Visual output
Choose the route
that fits the room.
LumaDeck provides visual-only surfaces. The final path to a projector, television, capture setup or stream is still governed by the user's browser, system and hardware.
Same device
Visual fullscreen
Open the composition in the app's visual fullscreen surface. Browser fullscreen support and user permission determine whether system chrome can be hidden.
Desktop workflow
Second browser window
Open a visual-only window and place it on another configured display. Popup permission and the operating system's display arrangement remain part of the setup.
External display
Your connection path
Use the connection and adapter supported by the computer and display in front of you. LumaDeck does not detect, certify or supply that hardware path.
Web Pro · local bridge
Native NDI® video source
Publish the visual master to OBS, vMix, Resolume or another NDI receiver. This route requires LumaDeck Output Bridge and the official NDI runtime installed on the same computer; the browser cannot create the native source by itself.
Before a show: test the exact browser profile, audio permission, MIDI permission if used, display arrangement, cable or adapter, and projector or capture input. Compatibility is a property of the complete setup, not a universal claim. NDI® is a registered trademark of Vizrt NDI AB. ndi.video
Current web specifications
The boundaries
are part of the instrument.
Figures below describe LumaDeck Web in the current public catalog. LumaDeck Desktop is a separate product.
- Runtime
- Browser-based WebGL instrument. The core app requires no application install. NDI OUT is the explicit exception and requires its local bridge. Browser APIs, permissions and GPU capabilities vary by environment.
- Catalog
- 239 renderable scenes across 20 packs: 48 included in Free plus 191 paid scenes; 10 General and 10 Artistic packs.
- Scene launchpad
- 24 scene pads in Free; 48 in Web Pro. The Free catalog still includes 48 scenes, reached through its available controls.
- MIDI
- Web Pro · 67 targets. 48 scene pads plus 19 live controls. Requires WebMIDI exposure and a user permission gesture.
- Custom video
- Free: 1 × 15 MB. Web Pro: up to 21 × 30 MB. Files remain local and are relinked when needed.
- Custom shaders
- Free: 1. Web Pro: up to 21. GLSL source stays local to the browser profile and is admitted fail-closed.
- Cloud shows
- Web Pro account capability. Stores configuration, catalog references and local-media metadata—not video contents, GLSL source or MIDI mappings.
- NDI OUT
- Web Pro · video only · up to 1920 × 1080. Requires desktop Chrome, LumaDeck Output Bridge and the official NDI runtime on the same computer. Windows/macOS use the official Tools/Runtime; Linux uses libndi from the official SDK. The bridge is local and uploads no frames.
- Output
- Visual fullscreen and a visual-only browser window. External-display transport depends on the user's complete hardware and software setup.
Practical guides
Take one path
into the instrument.
The guides go deeper into setup and operation, including the limits that matter before a live session.
Perform
Map your MIDI controller
The Learn workflow, current target set and local mappings.
Read guide →Create
Use your own shaders
Load GLSL, understand the reactive inputs and test locally.
Read guide →Create
Use your own videos
Prepare local clips and keep the working files on the device.
Read guide →Timing
Sync visuals to your set
Audio return, internal beat, BPM and nudge in practice.
Read guide →Output
From laptop to big screen
A grounded checklist for the display path before doors open.
Read guide →NDI · Web Pro
Send LumaDeck to an NDI receiver
Install the required bridge, publish the local source and receive it in your video workflow.
Read guide →LumaDeck Web
Start performing
tonight.
Open the instrument for free. Move into Web Pro when the show needs the full launchpad, MIDI, larger local banks and cloud show configuration.
Open LumaDeck