How to Archive a Digital Theatre Production

A digital theatre production leaves an archive that is partly made of files and partly made of conditions: which software rendered the projection, which version of the script the surtitles were timed against, who consented to being recorded, and what a future researcher would need in order to understand what an audience actually saw. Archiving such a work means deciding early and deliberately what to keep, how to describe it, and who will be able to reach it later. It differs from marketing capture or from keeping a showreel. The National Theatre’s guidance on creating digital archive projects treats this as a project in its own right, organised into a discovery phase and a building phase, and preceded by work on funding and staffing, collective and organisational buy-in, and planning for sustainability.

What counts as a digital theatre production archive

A digital archive project, in the National Theatre’s usage, is any project that catalogues and remembers performance online, aiming to share information from past performances, resources, or the records of a practitioner, group or organisation. For theatre made with digital elements — live-streamed work, hybrid staging, remote rehearsal, networked or telepresent performance — the archive has to hold two kinds of material at once. One is documentation of the event: video, audio, photographs, reviews, programmes. The other is the born-digital material that constituted the work: projection content, cue sheets, show-control files, caption and surtitle files, patch notes, network configurations, and the versions of the tools that made them run.

It helps to separate three functions that are often bundled together. Documentation records that something happened. Preservation keeps the records readable and verifiable over time. Access decides who may see what, where and under which conditions. A production can be well documented and badly preserved; it can be preserved and impossible to publish for rights reasons. Naming which function a given task serves prevents the common mistake of treating an uploaded video as an archive.

Performance is also, as Deborah Kay Zammit notes in a 2025 study of archiving theatrical performance, a transient event that cannot be captured in its original form: only aspects of it can be preserved, whether material remains or the functional documentation created to record it. She identifies two persistent difficulties — deciding which performance documents should be preserved, and organising and describing them in a way that remains usable.

Start with users and scope, not with storage

The first practical question is not “which hard drive?” but “who is this for?”. The National Theatre guidance places audience and users early in its discovery phase, before collecting and collating data, because the intended users determine what is worth keeping and at what level of detail. A company documenting a hybrid production for future restaging needs different material from a researcher studying audience interaction, a funder auditing an access commitment, or a translator looking for how surtitles were versioned.

Write the scope down. Useful boundaries include: the production and its dates; whether rehearsal and development material is in scope; whether only finished work or also works-in-progress are covered; which languages and versions are represented; and what will explicitly not be collected. Selection is a judgement, not a failure of completeness.

Secure funding, staffing and organisational buy-in first

Archiving competes for the same attention as production, and it is usually cheaper to resource it during the run than to reconstruct it afterwards. The National Theatre’s digital preservation case study, prepared by the APAC Digital Preservation Working Group, describes the internal work of building a case: explaining the situation in the archive meticulously, drawing workflows and diagrams, and helping a senior sponsor understand what was at stake if nothing was done. In that account the Head of Archive reported to a Director of Learning, who — although not from an archival background — was key to presenting the case to senior management; bringing the Director of IT and IT staff on board was described as equally important.

That pattern is widely applicable. A digital theatre archive needs a senior sponsor who can speak to the rest of the organisation, and an IT ally who understands storage, backup and systems. It also benefits from a short written business case and a preservation policy that states, in plain terms, what will be kept, in which formats, for how long, and who is responsible. Without those documents, decisions get remade by each new production team.

Phase one: discovery and collecting

During discovery, assemble an inventory of what exists and where it is — the case study’s principle of knowing what you have and where it is applies to production assets as much as to institutional holdings. A workable collection list for a digital or hybrid production includes:

Collect as close to the run as possible, from the people who made the files. Ask each collaborator for their working folder rather than their exported highlights, and record who supplied what. Where a production exists in several versions — a live-stream edit, a captioned version, a differently timed international stream — treat each as a distinct manifestation with its own description.

Rights, consent and cultural context

The National Theatre guidance pairs copyright protections with digital distribution during the discovery phase, and this is where digital productions are most often caught out. A recording that was cleared for a one-night stream is not automatically clearable for permanent online access; music, archive footage, guest performers and commissioned visual work may each carry separate terms. Consent from performers and collaborators should specify the purposes covered — preservation, research access, public exhibition — and not merely that recording took place.

Where work crosses languages and jurisdictions, record which territory’s rights and data rules were considered, and keep the paperwork with the assets. This article cannot substitute for legal advice; the practical point is that rights information is part of the archive, not an administrative afterthought, and that unclear rights should be documented as unclear rather than assumed cleared. Cultural protocols attached to specific material — community restrictions, attribution requirements, sacred content — belong in the description too, so that future users do not have to rediscover them.

Phase two: building the archive

Building covers digital infrastructure, description, and distribution. Three practical principles carry most of the weight.

Preserve masters separately from access copies

Keep unaltered masters in preservation-friendly formats, and generate smaller access or viewing copies from them. Store more than one copy, in more than one place, and check integrity on a schedule using fixity information such as checksums, so that silent corruption is detected rather than discovered years later.

Describe for people who were not there

Description is the part most often underestimated. Zammit’s study places organisation and description alongside selection as one of the two central difficulties in archiving performance, and digital work compounds it: a file called final_v3.mp4 tells a future user nothing. Record titles, dates, venues, credited roles, languages, versions, technical dependencies and access conditions in consistent fields, following whichever standard your institution or funder already uses. Consistency matters more than elegance; a simple, disciplined schema that survives staff turnover beats an elaborate one that does not.

Plan for distribution and reuse

The National Theatre guidance also covers marketing and distribution and additional archive resources, recognising that an archive which nobody can find serves few of its purposes. Decide in advance how records will be discovered — catalogue entry, institutional website, research repository, or an internal-only system — and make sure the public description does not promise access the rights position cannot support.

Archiving hybrid and networked work over its lifespan

Hybrid work needs explicit life-cycle planning. The Hybrid Theatre Toolkit published by DEN describes the production phase as a time of iteration and refinement rather than new invention, in which live rehearsals and digital development run in parallel and clear objectives, communication lines and decision-making structures mitigate the risk of drift. It also notes that every element, live or digital, has a lifespan, and that without active planning live work fades and digital components decay.

For archivists, that is a scheduling instruction. Ask at the planning stage what happens to the digital layer when the run ends: which accounts and platforms will be closed, which servers switched off, which licences lapse. Capture the digital element while it is still running, and record the dependencies needed to re-present it — even if the honest answer is that it can be documented but not re-performed.

A working checklist

1. Name anowner for the archive and a senior sponsor; agree whether IT is a partner or a supplier.
2. Define users, scope and exclusions in one page, signed off before the run.
3. Budget for storage, staff time, rights clearance and periodic integrity checking.
4. Collect masters, source files and technical context during the production, not after.
5. Record rights, consents and restrictions per item, with the territory and purpose stated.
6. Describe every manifestation consistently: date, venue, credits, language, version, dependencies.
7. Separate preservation masters from access copies; keep more than one copy in more than one place.
8. Write a short preservation policy and a schedule for review and format migration.
9. Document the digital layer’s lifespan and switch-off plan at the point of production.
10. Publish a clear access statement, and log any material you hold but cannot yet make available.

Common problems

The most frequent failures are predictable. Teams archive the stream recording and lose the show-control files, so the work can be watched but not understood. Rights are negotiated at the point of publication rather than commission. Storage is bought without a migration plan, or a plan is written without anyone to execute it. Description is written by the person with least context, weeks after the run. And access and preservation are confused, so that a fragile master is put online because it is the only copy.

None of these require a large institution to avoid; they require decisions made early, written down, and given to someone with the authority and time to carry them out. Because funder requirements, institutional policies and platform terms change, readers should verify current expectations against their own organisation’s records management or digital preservation policy, and against the specific requirements of the funder or venue involved, rather than relying on any single guide.