Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ZeqMacaw/Crowbar/llms.txt

Use this file to discover all available pages before exploring further.

Crowbar’s Unpack tab reads game package files and extracts their contents to a folder on disk. It supports Valve’s VPK format used by Source engine games as well as Garry’s Mod GMA addon archives. Before extracting anything, you can list the contents of a package to browse its file tree, or use the search field to filter entries by name.

Supported Package Types

The ContainerType enum defines the two package formats Crowbar can read:
FormatEnum ValueExtensionDescription
VPKContainerType.VPK.vpkValve Pack format used by Source engine games, including single-file and split-archive variants.
GMAContainerType.GMA.gmaGarry’s Mod Addon archive created by gmad.exe.
A split VPK package consists of a directory file (pak01_dir.vpk) and one or more data files (pak01_000.vpk, pak01_001.vpk, …). Always point Crowbar at the _dir.vpk file — it will locate the data files automatically.

Input

Enter the path to a .vpk or .gma file in the Package field, or use the Browse button. You can also drag and drop a package file directly onto the field. For folder-based modes, point Crowbar at a directory that contains package files. Crowbar will process all recognised package extensions it finds there.

Unpack Mode

The mode dropdown lets you switch between operating on a single file, a folder, or a game profile:
ModeDescription
FileOperate on the single package file specified in the input path.
FolderOperate on all packages found directly in the specified folder.
Folder and subfoldersRecursively search the folder and all subdirectories for packages.
Below a separator, each configured game profile also appears as a mode — selecting a profile targets that game’s package folder automatically.

Output Path Options

The output path dropdown maps to the UnpackOutputPathOptions enum:
OptionDescription
Same folder (as Package) (default)Extract files into the same folder that contains the package file.
Subfolder (of Package)Create a named subfolder next to the package and extract into it.
Work folderExtract to the work folder path you specify.
Game’s addons folderExtract to the addons/ folder of the selected game profile (useful for GMA addons).

Unpack Actions

The action buttons map to values in the PackageAction enum:
ActionEnum ValueDescription
ListPackageAction.ListRead the package directory and populate the file tree and list view without writing any files to disk.
UnpackPackageAction.UnpackExtract the selected (or all) entries to the configured output path.
(drag-drop preview)PackageAction.UnpackToTempAndOpenUnpack a single entry to a temporary folder and open it with its default application.
Use List mode before unpacking to inspect a VPK’s contents, check file sizes, and verify the structure. This is especially useful for large game packages that would take minutes to fully extract.
The search text box in the Unpack tab filters the displayed file list. Type any part of a filename or path fragment and the tree and list views update to show only matching entries. To clear a search, right-click the tree view and choose Delete Search or Delete All Searches.

Byte Units Option

The size column in the package list view can display file sizes in three formats, controlled by the ByteUnitsOption enum:
OptionDescription
BytesRaw byte count (e.g. 204 800).
BinaryPower-of-1024 units: KiB, MiB (e.g. 200 KiB).
DecimalPower-of-1000 units: KB, MB (e.g. 205 KB).
Right-click the list view and choose Toggle Size Units to cycle through these options.

Additional Unpack Options

OptionSettings KeyDefaultDescription
Folder for each packageUnpackFolderForEachPackageIsCheckedOffCreate a subfolder named after each package and extract its contents there.
Keep full pathUnpackKeepFullPathIsCheckedOffPreserve the full internal directory structure when extracting (e.g. models/props/crate.mdl).
Log fileUnpackLogFileIsCheckedOffWrite a log file to the output folder recording which entries were unpacked.

Build docs developers (and LLMs) love