Essential
4 cores · 8 GB RAM · integrated GPU
Patch, Programmer, groups, cues, playback, effects, attributes, DMX output, Art-Net/sACN, OSC, MIDI, RDM and one display.
Workload-based requirements
Hardware for the show
you actually intend to run.
Opening the app and running a 64-universe previsualization system are different workloads. DMXpressions publishes a practical console minimum, a professional sweet spot and dedicated high-end targets instead of reusing the Windows operating-system baseline.
Requirements are workload-dependent. An Essential machine can be a reliable console, but 64+ universes, advanced 3D, Atmosphere, pixel mapping, audio analysis and multiple displays require more CPU, memory and GPU headroom. DMX output timing remains the priority.
Capability tiers
Choose by workload, not by launch screen
These profiles are guidance, not feature locks. Always validate the exact show file, interface, output node and display layout before load-in.
Professional
6–8 performance cores · 16 GB RAM · 4–8 GB VRAM
Full console operation, timelines, visualizers, audio/MIDI/OSC and moderate StageCraft3D on two or three displays.
Production / Previs
8+ cores · 32 GB RAM · 8 GB+ VRAM
Advanced 3D, AtmoSPHERE, complex scenes, large fixture counts, pixel or multisegment rigs and high-resolution visualization.
Enterprise / Large Previs
12+ cores · 64 GB RAM · 12–16 GB+ VRAM
Massive shows, multiple visualizers and displays, demanding media workflows and the highest practical previsualization headroom.
Windows desktop
Official desktop requirements
The full desktop experience is optimized around 16 GB RAM, a modern 6–8-core CPU and a dedicated 4–8 GB GPU. Windows 11's own 4 GB / 2-core minimum is not a DMXpressions production target.
ComponentMinimum / CompatibilityRecommended / ProfessionalHigh-End / Full Production
Operating system
MinimumWindows 11, 64-bit
RecommendedWindows 11, 64-bit
ProductionWindows 11, 64-bit
Processor
MinimumModern 4-core CPU
RecommendedModern 6–8 performance-core CPU
Production8–16+ performance cores
Example class
MinimumCore i5 8th Gen / Ryzen 5 3000 or newer
RecommendedCore i5/i7 12th+ / Ryzen 5/7 7000+
ProductionCore i7/i9 14th+ / Ryzen 7/9 7000–9000+
Memory
Minimum8 GB RAM
Recommended16 GB RAM
Production32–64 GB RAM
Graphics
MinimumDirectX 12 GPU · about 2 GB VRAM
RecommendedDedicated GPU · 4–8 GB VRAM
ProductionDedicated GPU · 8–16 GB+ VRAM
Storage
Minimum256 GB SSD
Recommended512 GB NVMe SSD
Production1 TB+ NVMe SSD
Display
Minimum1280 × 720
Recommended1920 × 1080 or higher
Production2560 × 1440 / 4K · multiple displays
Show network
MinimumGigabit Ethernet recommended
RecommendedWired Gigabit Ethernet
ProductionWired 2.5/10 GbE where appropriate
Expected workload
MinimumConsole / DMX · limited 3D · large shows not guaranteed
RecommendedFull console · moderate 3D · large shows
ProductionAdvanced 3D / Atmosphere · complex and large shows
macOS and modern Linux can run the browser console where the required WebGPU, Web Serial, Web MIDI and hardware-acceleration APIs are available. Apply the same workload tiers and verify hardware-output compatibility before show use.
Tablet and phone
Professional tablets; focused phone remotes
Tablets can be serious console surfaces. Phones are best treated as remote and rapid-control devices rather than mandatory full-parity previsualization workstations.
iPad
Minimum
A14-class or newer · 4 GB+ RAM · current iPadOS
Recommended
M1 or newer · 8 GB+ RAM · 11-inch+ display · USB-C
A professional tablet target for console work. Use Wi-Fi 6/6E or a USB-C Ethernet adapter for show networking.
Android tablet
Minimum
Android 12+ · 4 GB RAM · modern 64-bit ARM · hardware graphics
Recommended
Android 14+ · 8–12 GB RAM · Snapdragon 7/8-class or equivalent
Suitable for demanding mobile control when WebAssembly and hardware-accelerated graphics are available.
iPhone / Android phone
Minimum
Modern 64-bit device · 4 GB RAM · current browser
Recommended
8 GB RAM where available · Wi-Fi 6+ · modern mobile GPU
Positioned as DMXpressions Mobile / Remote for playback, fixture selection, cue triggering, busking, status, RDM and diagnostics—not mandatory full-desktop previsualization.
Show networking
Reliability beats internet speed
Use wired Gigabit Ethernet as the preferred primary show-output connection for Art-Net, sACN, RDMnet, OSC, output nodes, tracking and show-critical control. A dedicated LAN or VLAN is recommended.
Wi-Fi 6/6E is useful for tablets, phones and remote-control surfaces, but it should not be the preferred path for primary show output. High-end multi-node or media-heavy systems may benefit from 2.5/10 GbE.
Art-Net and sACN require the DMXpressions local bridge because browsers cannot transmit raw UDP lighting packets. Install the PWA, cache show assets and test the bridge, interface and network before load-in.
Validate your complete show.
Open the console, load the actual patch and run every output, visualizer and display you plan to use before production.