Curating Open-Access and Public-Domain Games

A game is not a single rights object: its code, artwork, music, documentation, and packaging may each carry different legal terms. Before an archive collects or provides access to a release, it needs to identify the exact version, establish where its files came from, and record what the rights holder actually permits.

Published November 15, 2026

Start with the release, not the label

Words such as free, open, and public domain are often used casually in game communities, but they do not describe interchangeable legal conditions. A no-cost download may be copyrighted freeware. An open-source game may permit modification under a license while restricting how its name or artwork is used. A public-domain work, by contrast, is generally not subject to copyright restrictions in the relevant jurisdiction, though other rights or legal obligations can still apply.

For an archive, the useful unit of description is not simply “the game.” It is a particular release and its associated components: for example, a named version of the executable, the source code archive, a soundtrack, a manual, and a set of promotional images. Those components may have different authors, dates, licenses, and permissions. A rights statement copied from a project homepage may cover the source code but say nothing about a separately commissioned soundtrack or a bundled font.

That distinction has practical consequences. An archive might be allowed to preserve a source-code release and make it available under its license while lacking permission to reproduce the original box art. It might be authorized to host an installer for personal use but not to create translations or distribute modified versions. Good curation makes those boundaries visible instead of flattening them into a single “free game” claim.

Three categories that need different treatment

Public-domain works

Public domain generally means that copyright does not restrict the work in a particular territory, either because protection has expired, the work was never eligible for copyright, or the rights holder has validly dedicated it to the public domain where that dedication is recognized. Determining public-domain status can be difficult: rules vary by country, and the relevant date may depend on publication, authorship, and other facts. A title’s age alone is not proof.

In the United States, the Copyright Office’s guidance and records can help researchers investigate ownership and registration, but a search result is not necessarily a complete rights determination. A work may have been published without an obvious copyright notice and still be protected. Conversely, old material may have entered the public domain under applicable law. For materials published in other countries, the applicable term and rules may differ. Archives serving international audiences should state the jurisdiction behind a status assessment rather than presenting it as universal.

There is also a difference between a rights holder dedicating a work to the public domain and releasing it under a permissive license. Creative Commons’ CC0 tool is designed to waive copyright and related rights to the extent legally possible, with a fallback license where a waiver cannot be fully effective. That is not identical to a conventional open-source license, which grants specified permissions subject to conditions. An archive should preserve the wording and provenance of the dedication or license, not replace it with its own shorthand.

Open-source releases

Open-source software is made available under terms that grant defined permissions to use, inspect, modify, and redistribute code. The conditions matter. A permissive license may require retention of notices and disclaimers. A copyleft license may require derivative works distributed under specified conditions to remain available under the same or compatible terms. The label “open source” does not mean “no rules,” and it does not automatically cover every asset found in the game’s directory.

NetHack is a useful example of why the actual license must be consulted. It is distributed under the NetHack General Public License, not a generic promise that every part of the game may be reused without conditions. An archive should retain the license text and notices associated with the specific release it holds, then check whether the license covers the code, data files, documentation, and any bundled third-party material. If the project’s own documentation identifies exceptions or separately licensed components, those need to be recorded too.

When software is distributed with a license file, preserve that file alongside the release. If the license is supplied in a repository rather than the packaged archive, record the repository URL, commit or tag, access date, and the relationship between that source and the deposited files. A current project page may change; an archival record should show what evidence supported the rights description at the time of acquisition.

Freeware and developer-authorized releases

Freeware usually describes a price or distribution model, not a standardized copyright license. A creator may allow people to download and play a title without charge while reserving the right to control copying, modification, commercial use, or redistribution. Permission to download is not, by itself, permission for an archive to mirror the installer, preserve it in a public repository, or provide it to researchers.

Some developers do grant archival or public distribution permission, and that authorization can be valuable. The archive should preserve the evidence: the rights holder’s statement, its date, the location where it appeared, and the exact files or versions it covers. If permission is granted through email or a signed agreement, retain it in the collection’s restricted administrative records when appropriate, and publish a clear rights note that does not disclose private contact details.

Where the permission is ambiguous, ask a precise question. “May we archive your game?” could mean storing a preservation copy, making it available to named researchers, hosting a public download, or distributing modified versions. These are different activities. Explain the intended access model and ask separately about code, artwork, audio, documentation, and any third-party components.

Build a component-level rights record

A compact rights record can make a collection more reliable than a broad claim pasted onto a catalog page. For each candidate release, record at least the following:

  • Identification: title, developer or credited creator, platform, version or build identifier, release date if known, and the filename or package name.
  • Acquisition provenance: who supplied the files, the original source or repository, the date acquired, and any chain-of-custody notes.
  • Rights evidence: license name and version, public-domain dedication, written authorization, or other source supporting the rights statement.
  • Covered components: code, data files, music, sound effects, images, fonts, manual, packaging, and promotional material, noting exceptions or unresolved components.
  • Permitted actions: preservation copying, format migration, emulation, public access, redistribution, modification, and commercial reuse, as applicable.
  • Conditions: attribution, notice retention, share-alike requirements, noncommercial restrictions, or limits on use of trademarks.
  • Review status: who assessed the evidence, when it was checked, and what remains uncertain.

This record should distinguish fact from inference. “License file included in version 1.2 archive” is an observable fact. “All artwork is covered by the software license” is a conclusion that requires evidence. Where a repository’s license applies only to files in a particular directory, document that scope rather than assuming it reaches every file in the project.

Use stable identifiers and ordinary preservation practices alongside rights metadata. A fixity value such as a SHA-256 checksum can help establish that a stored file has not changed since it was received; it does not establish that the file was lawfully acquired or that its license permits public access. Technical integrity and rights provenance answer different questions, and a strong collection records both.

Trace the file to a credible source

Acquisition source is part of the evidence. Prefer an official project repository, developer-controlled website, authorized distributor, or a documented institutional transfer over an unidentified mirror. A file’s presence on a well-known download site does not prove that its uploader had permission to distribute it. Nor does a page’s use of “abandonware” create a legal category or confer rights to reproduce a game.

“Abandonware” is a community term for software perceived to be unsupported or unavailable through ordinary commercial channels. Copyright generally does not expire merely because a publisher has stopped selling or maintaining a title. The rights holder may still exist, and a company’s closure does not necessarily place its assets in the public domain. Archives can document the history of inaccessible software without treating inaccessibility as permission.

Institutions such as the Library of Congress and the National Archives and Records Administration have established preservation and rights-management practices that offer useful models for documenting collections. The Video Game History Foundation also conducts research and public education focused on game history and preservation. These organizations operate in different contexts and do not make every game in a collection openly downloadable; their work illustrates why preservation, rights assessment, and public access are related but distinct responsibilities.

For open-source projects, a version-control repository can provide valuable context: release tags, commit history, issue discussions, and license files. But a repository is not automatically a complete archival package. Dependencies may be hosted elsewhere, assets may have separate terms, and the current branch may differ from the historical release. Record the specific tag or commit, capture relevant project documentation according to institutional policy, and describe any missing dependencies.

Access decisions are not all-or-nothing

Preservation and access can be separated. An archive may have a legitimate reason to retain a restricted preservation copy while it investigates rights, even when public distribution is not authorized. A catalog record can describe the item and explain that access is limited, subject to institutional policy and applicable law. This is often more responsible than either discarding historically significant material or quietly placing it online without a clear basis.

In the United States, Section 108 of the Copyright Act contains specific provisions for eligible libraries and archives, including conditions and limits. It is not a blanket exemption for every collector, website, or preservation project. Fair use under Section 107 is a case-specific analysis that considers factors including purpose, nature of the work, amount used, and market effect; educational intent alone does not guarantee that a use is fair. Other jurisdictions have different exceptions and limitations.

Technical protection measures add another layer. In the United States, the Digital Millennium Copyright Act includes anti-circumvention provisions, alongside a rulemaking process that periodically establishes limited exemptions. An exemption is not a general license to distribute circumvention tools or copyrighted games, and its scope can be narrow. Because legal rules and exemptions change, archives should consult current institutional counsel or qualified legal advice before designing access workflows involving protected software.

Possible access choices include a public catalog record without files, on-site consultation, controlled access to authorized files, or open online access where the rights evidence supports it. The choice should be documented and revisited when a license changes, a rights holder responds, or new evidence emerges. A restriction is not a failure of preservation; it is an accurate statement of the conditions under which the collection can responsibly serve researchers.

A worked example: one game, several rights questions

Imagine an archive receives a freeware title from 1998 containing a game executable, a manual, original music, and a typeface. The developer’s old website says, “Download and play for free,” but says nothing about redistribution. A fan-maintained page hosts a copy of the installer, and the manual credits a composer and a font designer.

The archive should not infer that the installer is safe to republish. It can record the received package, preserve its checksum and provenance, and search for an official source or direct permission. It should inspect the credits and package for notices, then research whether the developer controls the music and font rights. If the developer authorizes preservation but not public redistribution, the archive can record that distinction and choose an access route consistent with the permission. If no answer is available, it should leave the rights status unresolved rather than relabeling the game as public domain.

Now imagine the developer publishes the source code under an open-source license while stating that the original soundtrack remains copyrighted. The source may be reusable under the license’s conditions, but the soundtrack does not become open merely because it ships with the program. The archive might describe the executable and source separately, preserve the license notices, and restrict or omit public access to the soundtrack unless it has a separate basis for providing it.

This kind of component-level account is less tidy than a single green “open access” badge, but it is more useful to researchers. It explains what the archive knows, how it knows it, and where uncertainty remains.

Describe uncertainty without obscuring it

Rights statements should be precise enough to guide reuse without pretending to provide legal certainty. “License: GNU GPL-3.0-or-later, as stated in the project’s release archive” is more informative than “free to use.” “Developer authorized preservation storage; public redistribution not addressed” tells a user what permission does and does not cover. If the archive cannot identify a rights holder or locate a license, say so and describe the search performed.

Standardized rights vocabularies can improve catalog interoperability. RightsStatements.org offers labels such as “In Copyright” and “Copyright Undetermined” for cultural heritage collections; these communicate a status, not a substitute license. Creative Commons’ Rights Expression Language and license identifiers such as those used by the SPDX project can help encode terms, but a machine-readable label is only as accurate as the evidence behind it. Keep a human-readable explanation and link the statement to its supporting documentation.

A rights note should also avoid promising more than the archive controls. The archive may be able to authorize use of its own descriptive record or a scan it created, while having no authority to grant rights in the underlying game. Separate the institution’s rights in its catalog text or digitization from the rights in the historical work itself.

A practical review before a title enters a collection

  1. Identify the exact object. Record platform, version, package, date, and component inventory. Do not rely on a title name alone.
  2. Locate primary evidence. Check the release archive, official project site, repository, license file, and any written authorization.
  3. Separate components. Determine whether code, art, music, documentation, and third-party assets share the same terms.
  4. Verify provenance. Record who supplied the files and whether the source appears authorized; do not treat a mirror as proof of permission.
  5. Map permissions to actions. Assess preservation copying, emulation, public access, redistribution, and modification separately.
  6. Write a qualified rights statement. State the evidence, jurisdiction where relevant, conditions, and unresolved questions.
  7. Set an access decision and review date. Reassess when new evidence or permissions arrive, and keep the decision trail.

Where the collection is institutionally managed, involve the archivist, rights specialist, and technical staff rather than placing the entire decision on a volunteer cataloger. For a small community archive, a documented escalation path can still help: preserve the evidence, avoid public redistribution while permission is unclear, and seek advice from a qualified professional where the stakes warrant it.

Curate for future researchers

A useful open-access collection does more than gather files. It preserves the evidence that makes those files intelligible: release notes, license notices, source details, version identifiers, and records of permission. It keeps uncertainty visible and separates a technical preservation decision from a legal access decision. It also recognizes that a game can be culturally significant even when its rights status prevents unrestricted distribution.

For researchers, a carefully qualified record is not a dead end. It can identify the developer to contact, point to an authorized source, or explain why a particular build is available only under controlled conditions. For rights holders, it demonstrates that an archive is distinguishing preservation from commercial substitution and is prepared to honor the limits of granted permission.

The strongest collection is therefore not necessarily the one with the most downloadable titles. It is the one whose descriptions let another archivist retrace the decision: which release was acquired, from where, under what evidence, and for which uses. That record is part of the game’s preservation history, as important to responsible access as the files themselves.

Theme