Why You Need to Back Up Your Lighting Show Files Before the Lights Go Up

Back up your lighting show file because the console, laptop, or USB stick it lives on can fail, and rebuilding a show from memory takes hours you won't have at load-in. Keep at least three copies in two different places, save a new version after every programming session, and test that the backup actually opens before the gig.

What can go wrong with a single copy

Most small rigs run from one of two places: a hardware DMX controller with internal memory, or a laptop running lighting software through a USB-DMX interface. Either way, all of your programming sits on one device. These are the usual ways that copy disappears:

• The laptop dies, gets stolen, or won't boot after an operating system update.
• The show file corrupts during a save, often because the computer crashed or lost power while writing it.
• Someone else uses the controller and records over your scenes or chases. Church and school rigs shared by several volunteers run into this a lot.
• A software update changes the file format. The new version may not open old files cleanly, and an older version usually can't open files saved by a newer one.
• A hardware controller loses its memory after a factory reset or firmware update.

It helps to count what a show file holds. A 90-minute set with 15 songs and 10 cues per song is 150 looks, plus the fixture patch, groups, a position palette for each moving head target, and effect timing. Even at one minute per cue, that is more than two hours of reprogramming before you check a single look on stage.

What to back up besides the show file

The show file holds your cues, scenes, and usually the patch. Several things it depends on often live somewhere else:

• Custom fixture profiles. If you built or edited a fixture definition yourself, many programs keep it in a separate user library folder rather than inside the show. Without it, the show may open with missing fixtures or plain generic channels. Find that folder and back it up too.
• The software version. Write down the exact version number. If you have to install the software on a new laptop, you'll know which release the show was built on.
• A patch sheet. A plain list of every fixture with its DMX address, channel mode (for example 14CH or 20CH), and universe. If the file won't open at all, this lets you rebuild the patch on any controller.
• Fixture menu settings. Address, channel mode, display orientation, pan/tilt invert, and the no-signal behavior. A phone photo of each fixture's menu screen is enough.
• MIDI and controller mappings, if you fire cues from a pad controller, Stream Deck, or DAW.
• Audio or timecode files that the show is synced to.

Hardware DMX controllers need a different approach. Many basic 192-channel controllers keep scenes and chases in internal memory. Some can send a data dump to another device over MIDI, and many have no export function at all, so check the manual for your model. If yours can't export, your backup is a written record: the patch sheet plus the fader values for each scene, or a photo of the faders for each scene and chase step.

The 3-2-1 rule for a small lighting rig

IT departments use a simple rule that fits show files well: keep three copies, on two different kinds of storage, with one stored away from the gig. On a typical mobile, band, or church rig it looks like this:

Use two USB sticks and alternate between them. Cheap sticks fail without warning, and a stick left in the laptop all the time gets lost or soaked along with it. Pull the stick out of the computer once the copy finishes.

When to save and back up your lighting show

Tie backups to the moments when your programming changes, not to the calendar:

1. At the end of every programming session. In your lighting software or on the console, use Save As with a new version number instead of overwriting the last show file.
2. Before any lighting software, console, or fixture firmware update. If the update causes problems, you can reinstall the old version and still open the old show file.
3. The day before the show. Copy the final version to the USB stick and to the off-site copy.
4. After the show, if you changed anything live. Re-aimed position palettes, busked looks, and quick fixes made during a gig are easy to lose if the show laptop gets shut down without saving.

Keep the last several versions, not only the newest. If the latest show file turns out to be corrupt, or you deleted a fixture group or a cue list by mistake two sessions ago, an older version gets you most of the way back.

Name show files so the right one is obvious

A backup only helps if you can tell which show file matches the rig in front of you. A USB stick holding "show final", "show final 2", and "show NEW" forces you to load each one into the console and guess. A fixed naming pattern fixes that:

• Date first, in year-month-day order: 2026-04-05. It is the only date format that sorts in true date order in every file browser. Month-day-year names (04-05-2026) sort by month, so files from different years get mixed together.
• Then the event or venue, then a version number with a leading zero: v01, v02, up to v12, so v10 doesn't sort ahead of v2.
• No spaces or special characters. Use hyphens or underscores. Some programs, USB file systems, and sync services handle spaces, slashes, and accented letters badly.
• Lowercase only, so the same name can't turn into two different files on systems that treat upper and lower case differently.
• Skip the word "final". The next change makes it wrong.

An example: 2026-04-05_stmarks-easter_v03, followed by whatever extension your lighting software adds. Keep a short text file in the same folder with one line per version: the date, what changed ("re-patched two PARs, new chorus cue for song 4"), and who changed it.

Name things inside the show file too

Whoever opens your show next, whether that's a volunteer on Sunday or another operator covering a gig, has to find things quickly. Name groups by position and fixture type: "MH stage left", "PAR front wash", "Uplights back wall". Name position palettes by where they point: "Pos singer", "Pos drum riser", "Pos audience sweep". Name cues by the moment in the show: "Walk-in", "Song 3 chorus", "First dance". Labels like "Group 4" or "Cue 17" mean nothing to anyone except the person who programmed them.

Cloud sync for shared and multi-venue rigs

A cloud sync folder from any of the common services is the easiest off-site copy, and it lets several operators pull the same file. It has limits you need to plan around:

• Sync alone is not a backup. If a file corrupts or someone deletes it, the service copies that change to every connected computer. Turn on version history and check how far back your service keeps old versions.
• Keep an offline copy on the show machine. Venue Wi-Fi is unreliable, and load-in is the wrong time to wait for a download.
• Let one person edit the master. If two volunteers edit the same file on different laptops, one set of changes gets lost or the service saves a "conflicted copy". Pick an owner, and have everyone else work on their own copy.
• Freeze it before the event. Upload the final version a day or two ahead, and have every operator open it on their own machine before show day.

Bands and DJs who take the same fixtures to several venues can keep one master show with all the looks, then save a separate copy per venue in which only the patch and fixture count change. Looks built on groups and palettes carry over to a venue copy far better than looks programmed fixture by fixture.

Test the restore before you need it

You only know a backup works once you've opened it. Before each season, tour, or major event, run through this once:

1. Copy the backup from the USB stick or cloud folder onto a second computer, or reload it into the controller.
2. Open it in the same software version the show was built on.
3. Check that every fixture appears in the patch with the right address and mode, not as generic dimmer channels.
4. Connect the rig and play a few cues, including one with moving heads, to confirm colors and positions match.
5. Time the whole restore. That number tells you whether reloading during a show is realistic, or whether you also need a backup controller ready to take over.

FAQ

How often should I back up my lighting show files?

After every programming session and again before every show. For a weekly church service, that usually means once a week after rehearsal. Also back up right before any software or firmware update.

Is a USB stick enough of a backup?

As one of your copies, yes. As the only backup, no. Sticks get lost and fail without warning, so pair one with a cloud folder or a drive kept away from the gig.

Can I open my show file on another computer?

Usually, if the same lighting software is installed, ideally the same version. Some programs need a license or a connected interface to send DMX but still let you open and edit the file. Check how yours behaves at home, not at the venue.

My DMX controller has no export function. What can I do?

Keep a written record of the patch and of every scene and chase step, as described above, and store it with your other backups. Rebuilding by hand from notes is slow, but far faster than starting from nothing.