What is the PCK file format?
.PCK is a resources archive format used by various computer games. It is a type of data archive file. The format is not standardized - each game engine or studio defines its own internal .pck layout, so a .pck from one game is generally not compatible with tools made for another.
A typical .pck file can include such resources as:
- Audio files
- Graphics and textures
- Text and scripts
- Game interface elements
- Maps, scenarios, and level data
Resources can be stored in one large file or divided into smaller, logically organized archives. Most .pck variants begin with an engine-specific magic word followed by a file index (names, offsets, sizes) and then the concatenated asset data. A well-known example is the Godot Engine, whose .pck resource packs begin with the ASCII tag GDPC. Other studios use entirely different layouts under the same extension - similar to the related .PAK archive convention.
.pck archives can be used to add content to a game or update game files when the developer has implemented such a system. This method of updating is clean and minimizes the risk of file corruption by replacing only the relevant assets. Opening a .pck from a specific game generally requires a community unpacker or a QuickBMS script written for that title, as no universal viewer exists.
Security & safety
RISK: MEDIUMA game's own .pck is just data and is safe as part of the installed game. The risk is external: .pck files and 'unpacked' game packs downloaded from random modding/repack sites can hide malware, and QuickBMS scripts run extraction logic that you should get from reputable community sources. Editing or repacking a game's .pck can also break the game or violate its EULA. Stick to the game's official files and well-known modding communities, and scan anything you download.
Format details
in a nutshell- Godot Engine resource pack (.pck) - Godot games ship assets in a .pck (magic 'GDPC') that the engine mounts at runtime; opened with Godot/community tools, unrelated to studio game archives.
- FMOD / Wwise-style audio or texture 'PCK' bundles - Some engines name their packed audio/asset bundles .pck; structure depends entirely on the middleware.
- Python facter / misc data '.pck' (pickle-like) files - A handful of apps use .pck for serialized data; not a game archive.
Programs that open PCK files
Technical details
deep spec| File type | Proprietary game data archive |
| Encoding | Binary |
| Byte order | Typically little-endian on PC titles; varies by engine/studio |
| Container structure | Engine-specific: magic/header + file index (table of contents) + concatenated asset blobs |
| Magic bytes | Engine-specific; no universal signature. Godot Engine uses ASCII tag GDPC at offset 0 |
| Compression | Varies by game - raw, zlib/DEFLATE, or a custom per-entry codec |
| Encryption | Usually none; some titles obfuscate or lightly encrypt the file index or entries |
| Typical file size | A few MB to several GB (bundles large amounts of game content) |
| Asset types bundled | Textures, 3D models, audio, scripts, UI elements, level/map data |
| File index | Per-entry name, offset, and size in an engine-defined format; large packs can index thousands of files |
| Checksum/integrity | Varies - some formats include per-entry CRC/hash; many have none |
| Notable variants | Godot Engine (GDPC brand), Commandos/Pyro Studios, Perfect World Entertainment, Relic Entertainment |
| Compatible OS | Windows (primary); console builds where applicable |
| Unpacking | Game-specific community tool or QuickBMS script required; no universal extractor |
| Released | Used across PC games from the early 2000s onward (e.g. Commandos 2, 2001) |
| Latest version | N/A - no common specification; each game/engine defines its own .pck layout |
PCK conversions
Community Q&A
asked by usersNo questions yet - be the first to ask about PCK files.