A Show Without Internet: Offline Licences, Exported Configuration and Plan B.

Most live shows today depend on a network nobody controls: the library lives in the cloud, the licence validates on opening, mappings sync between computers, and set notes live in a shared document. When the network disappears—the venue’s Wi-Fi is overloaded, a cable fails, the service goes down—all of that fails together, turning what should be a minor incident into silence in front of the audience.

The answer is not to reject the cloud: it is to design the show to work equally well without it. This guide covers Designing a Show That Keeps Working Without Internet, what to do if a cloud service fails, preparing Offline Licence Copies and Exported Configuration, and why inexpensive Spare Cables/Adapters solve more faults than any sophisticated configuration.

What Fails When the Network Disappears

Before designing the plan, list your actual dependencies. A typical set has five points touching the internet, and almost none is essential if prepared in advance:

• Licences. Many DAWs and plugins check activation at startup. Without validation, some restrict their features and others do not open.
• Remote Libraries and Samples. Any platform downloading material on demand stops serving you exactly when needed.
• Work Synchronisation. Changes made on the rehearsal laptop that have not yet uploaded to the live computer.
• Documentation. Setlists, riders, schedules and contacts hosted in online documents.
• External Support Services. Remote visuals, lighting control over a poorly configured local network, and messaging with the team.

The rule organising everything: live material lives locally, and the cloud copies it, rather than the other way round. With that reversal, each dependency becomes pending synchronisation rather than a threat.

Design a Show That Keeps Working Without Internet

The design has three layers, from the inside out: what plays, what controls it and what documents it.

Sound Layer. Everything you play is on the computer: analysed tracks, samples, stems and loops downloaded before leaving home. Sync the library at the hotel and check that nothing remains cloud-only. If you use players, exporting to the drive already brings all the material with it.

Control Layer. Mappings, templates and preferences saved as files, rather than only as the program’s internal state. If the laptop dies and you start the backup, the Exported Configuration restores the same behaviour within minutes. Practise at home: importing configuration onto a clean computer is the only way to know the file works.

Documentation Layer. Rider, schedules, song list and contacts as PDFs on the phone and on paper. A printed setlist needs no battery, permissions or coverage.

Cybersecurity organisations make the business-continuity recommendation explicit: know how to access critical files without a connection and test recovery routes before needing them. In booth terms: if you have never performed without a network, your first attempt will be in front of the audience.

When the setup includes multiple computers, visuals or synchronisation, review the full hybrid-show synchronisation and redundancy layout beforehand; if the local network is part of the system, internet redundancy through bonding and failover explains communications support.

What to Do If a Cloud Service Fails

A service outage during setup is not an emergency if your material is local. The protocol is short and leaves no room for improvisation:

1. Identify the Dependency. Is the missing part a file, a licence or merely synchronisation? Each needs a different response; mixing them up wastes minutes.
2. Confirm the Local Copy. If the material is on the computer, continue preparation and leave synchronisation until later; avoid repeated retries consuming bandwidth.
3. Activate the Prepared Alternative. Emergency file, setlist PDF, offline-authorised licence. In front of the audience, switch rather than diagnose.
4. Keep Diagnosis Outside the Performance. Note what failed and solve it afterwards; on stage, execute the plan.
5. Communicate on the Planned Channel. If working as a team, an agreed phrase prevents three people trying to fix the same thing.

Prepare cloud-hosted material beforehand: mark working folders as available offline, download tracks and check on the actual computer, without a network, that everything opens. The synchronisation tool allows this; the common mistake is assuming “it will already be downloaded”.

Offline Licence Copies and Exported Configuration

Offline Licence Copies prevent activation from depending on the moment you switch on the computer. Manufacturers offer offline authorisation flows: the software displays a hardware code, you generate the activation file from your account on a connected computer, and install it on the live machine. Keeping that file on your main and backup USB drives covers a venue with no internet or an unresponsive licence server.

Three habits prevent surprises:

• Authorise Both Computers you will bring, rather than only the main one: manufacturers often allow multiple activations, limiting simultaneous use rather than preparation.
• Store the Activation File and Serial Number outside the computer, with the show documentation.
• Test Startup Without a Network the night before, deliberately disconnecting Wi-Fi.

Exported Configuration serves the same purpose for program behaviour: controller mappings, audio preferences, session templates, effects profiles and, where relevant, lighting scenes. Export through the software’s own feature, date the file and keep it alongside the set. Replacing a laptop then means importing the file and checking controls respond, rather than rebuilding the setup.

Spare Cables/Adapters: The Cheapest Plan B

Spare Cables/Adapters are the plan’s most honest part: inexpensive, almost weightless, and capable of solving most real setup faults. A typical venue technician’s list includes spare XLR and TRS cables, 3.5 mm-to-jack adapters, couplers, a couple of USB cables in your required versions, HDMI and DisplayPort, and extra power supplies.

How to prepare:

• A Bag Labelled by Function, rather than a drawer of loose cables. Label both ends: in darkness, a cable identical to the broken one is indistinguishable.
• Duplicate Precisely the Critical Links: the connection to the interface, the signal cable to the venue system, and the live computer’s power connection.
• Test Every Adapter on Your Own Equipment before touring; an adapter bought “just in case” and never tested is often the one that fails.
• Bring Non-Electrical Spares Too: tape, cable ties, batteries and a pair of headphones. The most frequent fault is in the accessory rather than the port.

To expand your selection according to event type, the pre- and post-performance checklist already covers cabling and setup equipment.

The Disconnected Rehearsal

The final check before declaring the show prepared happens with the network off: disable Wi-Fi and mobile data, then run the complete list. Check that software opens, tracks load, effects respond, the setlist is readable, the backup computer starts with imported configuration, and the activation file is where you said it was. A failure found now costs a rehearsal; found later, it costs a performance.

With this completed, the material’s security chain is complete: protected accounts, verified backups, distributed storage, redundant equipment and a show operational without a network. The last layer to build is making the connection as redundant as everything else.

Next Step

Once the show survives without a network, make the network survive too: internet with bonding, failover and preparation of the live connection.