Welcome to the OpenRS2 Archive

The OpenRS2 Archive is a collection of caches and XTEA keys for all versions of RuneScape that use JS5, and its precursor, to manage assets (mainline RuneScape builds 234 and greater, and all builds of Old School RuneScape).

The archive uses content-addressable storage, converting caches to the client's native .dat2/.idx format on demand. This provides several benefits: the disk space required to store all available caches is reduced, and groups or XTEA keys missing from one copy of the cache can be sourced automatically from other copies - provided the checksums and version numbers match.

The archive is highly automated: OSRS and RuneScape 3 cache updates are downloaded automatically, and XTEA keys are pulled from various sources and verified automatically. However, third-party contributions must be imported manually to verify the data's provenance (see the "Contributing" section below).

Support for archiving clients/gamepacks, loaders and native libraries is also planned for a future update.


A significant amount of data in the archive was, or is, obtained from the following projects, which we'd like to thank:


Please contact Graham in OpenRS2's Discord server if you have data (old clients/gamepacks, loaders, native libraries, caches and XTEA keys - ideally original or only lightly modified copies) to contribute.

Contributing data is important even if the cache or keyset already exists in the archive. Older copies of the cache are often incomplete, and your copy may have data missing from the archive.

By pooling all the community's data together in a single location, the whole community will benefit from access to more complete caches and keysets.


An rsync server is available at rsync://archive.openrs2.org/pub. Daily Postgres dumps are available in the db subdirectory in the custom dump format.

A public-facing Postgres instance, for complex queries and replication, may be made available in the future.

The software used to import and export data is open-source. Combined with the database dumps, this ensures the longevity of the archive if the main instance ever disappears.