Choosing DMX software: an honest comparison

There are three different questions hiding inside “which DMX software should I use”, and they have different answers. If you want a Mac console you program yourself, Lightkey. If you want lighting that runs itself with no computer present, MaestroDMX. If you want to pay nothing on any platform, QLC+. Daslight suits hand-programming across platforms, SoundSwitch suits DJs who script to a track list, and grandMA3 is for professional lighting designers. HitLight generates lighting from room audio and from plain-English descriptions, on macOS only.

Which should you pick?

Pick Lightkey if you are on a Mac, enjoy programming, and want the mature Mac-native console. Pick MaestroDMX if you want autonomous music-reactive lighting with no computer at the gig. Pick QLC+ if you are comfortable learning a console-shaped interface and want to pay nothing, on any operating system. Pick Daslight if you want to program every scene by hand on a mature, cross-platform tool. Pick SoundSwitch if you want scripted tracks, beatgrid-synchronised autoloops and direct DJ-software integration. Pick grandMA3 if lighting design is your profession. Pick HitLight if you own lights, work on a Mac, and want eligible output generated from the music in the room — with everything it produces editable by hand afterwards.

Two of those are the ones most people are actually choosing between, and they are the two that used to be missing from this page. On the Mac, the real head-to-head is Lightkey versus HitLight: two applications built for one platform, splitting on whether you program the look or describe it. And in automatic lighting, the real head-to-head is MaestroDMX versus HitLight: a box you buy and trust, or software whose output you can open and edit.

DMX lighting software compared on price, audience and where each one wins. Last verified 2026-08-01.
SoftwarePriceWho it is forWhere it wins
grandMA3MA Lighting€5,000+Professional lighting designers on touring and large-venue productionsIf your work needs grandMA3, buy grandMA3. It is the industry standard for professional lighting design and HitLight is not trying to replace it.
DaslightNicolaudie€300–1,500Professional and semi-professional operators programming scenes and timelinesDaslight is a mature, cross-platform tool for people who want to program every scene by hand. HitLight is for people who would rather describe the look.
QLC+Massimo Callegari and contributorsFree and open sourceHobbyists and technical users willing to learn a console-shaped interfaceQLC+ is genuinely free, genuinely capable and runs on Windows, macOS and Linux. If you are comfortable learning a console interface, it may be all you need.
SoundSwitchinMusic~$100/yearDJs who want scripted tracks, beatgrid-synchronised autoloops and direct DJ-software integrationSoundSwitch is a DJ-focused tool for scripted tracks and beatgrid autoloops, and it also offers BPM Detection. HitLight has no DJ-software integration; it generates eligible output from room audio.
LightkeyLightkey SoftwareFree up to 24 channels, then €79–379/yearMac operators who want a mature, Mac-native console and are happy to program it themselvesLightkey is the established Mac-native option: one platform, done properly, with a free edition and a channel-based licence ladder. HitLight is the Mac option that programs the look for you and can run the rig from room audio.
MaestroDMXMaestro$899 one-off (hardware)Operators who want autonomous music-reactive lighting with no computer at the gigMaestroDMX is a standalone box: nothing to run on a laptop, and one universe of 512 channels. HitLight is software on a Mac you already own, with multi-universe Art-Net and sACN today and the same show editable by hand.
HitLightMade in Oslo, NorwayFree during the public beta, with no credit card. Launch pricing has not been announced.People who own lights but do not have a lighting designer, working on macOS 14 or later.Describing a look in plain English and letting Auto Show run the rig from the music in the room. HitLight does not run on Windows.

The price bands are approximate and each vendor's own site is the authority on what their software costs today — the names in the first column link there. Everything in the last three columns is a summary of who each tool is built for, not a feature scorecard. Feature comparisons between lighting software age badly and are usually written by the party who benefits from them.

Should I use HitLight instead of grandMA3?

No. grandMA3 is the industry standard for professional lighting design on touring and large-venue productions, and HitLight is not trying to replace it. If your work needs grandMA3, buy grandMA3. There is no comparison page for it on this site, because writing one would mean pretending the two products are alternatives to each other.

The honest framing is that HitLight is for people who do not have time to learn grandMA3, and who in most cases will never need to. A mobile DJ with eight PARs and two moving heads, a bar with a rig somebody installed three years ago, a school hall with a lighting desk nobody can operate — none of those situations are waiting for a better professional console. They are waiting for someone who knows how to program one.

If you already know a grandMA3 console, you will find HitLight's manual tools thin by comparison, and you should say so. The right test is not which tool is more capable; it is whether you are the person who was going to program the show.

What does HitLight do differently?

Three things, and they are the only three worth switching for. HitLight can run a rig live from the music in the room with nothing programmed in advance, it can build scenes from a plain-English description of the look you want, and it can draft a fixture profile from the manual when your light is not in the library. Everything else it does — cue lists, a timeline, palettes, a virtual console, MIDI learn — exists in other software too.

Auto Show runs the rig from the music in the room

Auto Show listens through the Mac's microphone, follows the beat and the structure of the track, and drives your rig live with no scenes programmed first. It reacts to what is actually playing in the room, which means it works for live instruments, unreleased music and anything you did not plan for. It is a starting point rather than a replacement for programming: you can take over at any moment, and Stop, Fade Out and Blackout sit next to the toggle.

Auto Show drives colour, intensity, a steady open shutter and eligible movement. It will not drive lasers, flashing strobes, blinders, UV, smoke, haze, fans, flame, pyro, fixture macros or unverified effect channels — those channel types are removed from every automatic path in code, not by convention. The microphone is its only audio source in v1: there is no line-in, no DJ-software integration and no track pre-analysis. Lighting safety lists the exclusions in full.

The assistant programs scenes from plain English

HitLight's assistant builds scenes from a description of the look you want, working from the fixture profile you patched and the values actually on the wire. It does not invent your fixture's channels, and it cannot arm smoke, haze, fan or flame-ignition channels. You keep the manual surface either way — the matrix scene editor, cue lists with GO and BACK, a multi-track timeline and reusable palettes are all still there, and the assistant is one way of filling them in rather than the only way.

A missing fixture can be drafted from its manual

If your light is not in the library, you can point HitLight at the PDF that came with it — or a photo of the DMX chart on the back of the unit — and it drafts a working profile in seconds. Generated profiles stay marked as drafts: you test the channels on the real fixture and confirm them before they are used in a show. That is deliberately the slow path. We would rather take an extra ten minutes than be confidently wrong about your rig. The fixture library page covers what happens in each case.

What does HitLight not do?

HitLight does not run on Windows or Linux, the browser app cannot output DMX to hardware, and the whole product is public beta software. These are the three facts most likely to disqualify HitLight for you, so they are here rather than three clicks away, and none of them has a workaround.

HitLight's limits, stated plainly. Last verified 2026-08-01.
QuestionAnswerWhat that means for you
Does it run on Windows?No — the app that drives lights is macOS onlyThe browser app runs on Windows and Linux for patching a rig, building scenes and watching them on the 3D stage, but it cannot output DMX. Windows support is the most requested thing on our list and has no announced date.
Can the browser app control real lights?No — hardware output happens only in the macOS appUSB, Art-Net and sACN output all live in the Mac app. Everything you build in the browser is ready to go live the moment you open the same show on a Mac.
Does it work offline?Not fully — sync, collaboration and AI need an internet connectionOffline recovery is being tested during the beta and is not yet promised. Do not plan a show around it.
Is it finished?No — HitLight is public beta softwareFeatures, quotas, file formats and availability may change, it ships without an uptime guarantee, and assistant usage is capped while we validate cost.

Where can I read a detailed comparison?

There is a page for each of the three products people actually cross-shop against HitLight. Each one leads with what the other tool does better, because that is the part you cannot get from the vendor.

If you want to try HitLight before deciding, you do not need to buy an interface first. The 3D stage runs with no hardware attached, so you can patch every fixture you own and watch a whole show play back before anything is plugged in. Supported hardware lists what works when you do connect one.

Last verified .

Try it on your own rig

Patch your fixtures, describe the look you want, and watch it on the 3D stage before you connect anything.

Free during the public beta, with no credit card. Launch pricing has not been announced. Requires macOS 14 or later for hardware output.