Recommended Formats Statement

1. Uncompiled source code: Version of a game that is ready to be sent to console manufacturers for certification. Contains files and folders created by a game developer and is still human readable using either a text editor, visual programming tool, or an integrated development environment (IDE).
2. Gold master build (specific file types will vary depending on company producing build): Version of the software and video game which meets all of a publisher and platform’s requirements and is considered the finished product. If a game is released on multiple platforms, each platform will require its own preferences on how a user interacts with the game. In essence the game’s gold master build release’s look and feel is varied by the publisher and platform.
3. Distribution file (e.g. ipa [Mac iOS], apk [Android], exe [Windows]): The distribution file is disseminated for public use regardless of the means of dissemination (on physical media or via an online source) and is comprised of one or more files from the gold standard build.
   • Media-based release: The version of a distribution file disseminated via a media-based physical object (cartridge, disc- or disk-based media, etc.). This is a type of distribution file.
   • Internet-based release: The release version of a software distributed via an online- or internet-based source, including mobile applications.

1. Hard drive/flash drive/writable disk containing the unpublished version of game/software content
2. Video of use, such as YouTube and Twitch streams, can substitute for the absence of a preservation copy of the game or inability to recreate significant online dependencies.

Operating system (OS): If the software or game is not usable on a commonly-available OS (Windows, Mac, Linux), then a copy of the OS, submitted as a disk image, must be provided with the submission. 

NOTE: If there are different versions released at the same time for different platforms (e.g. for Mac, Windows and Xbox), a submission will be required for each.

If a submission requires a stand-alone or proprietary platform (e.g. a gaming console or handheld device), then a virtual or emulated version of the proprietary platform is required with submission.

If a submission requires a stand-alone or proprietary platform (e.g. a gaming console or handheld device), and a virtual or emulated version of the proprietary platform is not available, submission of the hardware including controllers and power supply is acceptable.

Submissions should include documentation and other accompanying material (e.g., instruction materials, errata, addenda, read me files) and can include blog posts and other publications about the software or game.

NOTE: If the software was a part of a book publication (e.g., a software manual with accompanying discs), then a copy of the book must be submitted with the disc.

Direct File Submission: These submissions would require grouping in a submission package such as BagIt, Tape Archive (tar), ZIP, or AXF object.

Method of transfer may differ by Library of Congress department and should be coordinated with the accessioning librarian.

• External hard drive with USB (universal serial bus) interface
• Commercially-pressed optical disc (CD-ROM/DVD)
• Flash drive with USB interface

1. Metadata that specifies which compiler was used to create the final code for commercial release — including the operating system, version number and build number of the compiler software — must be included.
2. As supported by format:
1. Title
2. Creator
3. Creation date
4. Place of publication
5. Publisher/ producer/ distributor
6. Contact information for publisher
7. Production metadata such as credit, rights and files which are available at the time of production
3. Include if available:
1. Language of work
2. Other relevant identifiers (e.g., UPCDOI, LCCN, EIDR, etc.)
3. Subject descriptors (LC Name Authorities or Subject Headings preferred)
4. Abstracts
5. Metadata schema, if applicable

Submissions of uncompiled source code must include the rights clearance for the Library to install and use the compiler to read and use the provided information.

Files must contain no measures (such as digital rights management [DRM] technologies or encryption) that control access to or prevent use of the digital work.)

A file containing digital rights management (DRM) technologies or encryption which requires a stand-alone or proprietary platform is accompanied by a virtual or emulated version of the proprietary platform or a physical version of the platform. DRM controls and encryption keys cannot contain a time limitation and a copy of encryption keys must also be included with the submission. DRM and encryption keys cannot require connection to a remote server for authentication.