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 images, logos, videos and GLSL. The audience sees the composition; you keep the controls.
48scenes included in Free
239scenes in the web catalog
94MIDI targets: scenes, live controls, video and text
Local mediaimages, videos 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 an image or video as the main visual or as a separate, adjustable layer over the show. Custom GLSL enters through Shader Lab. Free provides one media slot and one shader; Web Pro expands each bank to 21.
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
94 current targets.
Map 48 scene pads, 6 moods, 14 direct controls, 22 video launchers and 4 text cues. The direct group includes next scene, SHOW NOW, 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 launchers and the four text cues can be mapped alongside the scene pads.
Local media + custom GLSL
Bring your own visual language.
Add a JPG, PNG, GIF or video from the device. Each media item can stay Normal on the main A/B bus or become a separate Layer over the scene or video. Custom shaders enter through Shader Lab.
- Position, size and rotate a Layer; set opacity, Normal/Screen/Add blend and Off/Energy/Beat/Both reactivity.
- Choose one of eight entry FX, a 3–30 second visible time and a 10–120 second return interval.
- Free: one local media item up to 15 MB. Web Pro: up to 21 at 30 MB each. Their contents are never uploaded.
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.
Same local network
Visuals through Google Cast
Send the master to a compatible Google Cast TV or receiver. Video output is 1920×1080, up to 30 fps, with no audio. No extra LumaDeck TV app or Output Bridge is required. Smoothness depends on the sender, receiver, content and network. Set up Cast →
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 Pro 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; Free reaches them by reorganising which ones sit on its 24 pads.
- MIDI
- Web Pro · 94 targets. 48 scene pads, 6 moods, 14 direct controls, 22 video launchers and 4 text cues. Requires WebMIDI exposure and a user permission gesture.
- Custom media
- Free: 1 × 15 MB. Web Pro: up to 21 × 30 MB. Images and videos remain local, are relinked when needed, and can work in Normal or Layer mode.
- Custom shaders
- Free: 1. Web Pro: up to 21. GLSL source stays local to the browser profile and, when in doubt, admission rejects instead of admitting.
- Cloud shows
- Web Pro account capability. Stores configuration, catalog references and local-media metadata—not image or video contents, GLSL source or MIDI mappings.
- Google Cast
- H.264 · 1920×1080 · up to 30 fps · video only. Compatible browser and receiver on the same local network. Free keeps the lumadeck.app watermark; active Web Pro removes it. Tested reference: desktop Chrome on Linux with Mi Box; other setups are not validated by that test. Transport dimensions do not guarantee native source detail or zero latency.
- 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, second window and compatible Google Cast. 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.
Google Cast
Send your visuals to the TV
Connect from the Master, send video only and check your setup before the show.
Read guide →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
Layer your logo over the show
Place it, animate its entrance and make it respond to audio.
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