View source for VPK

{{LanguageBar}}
{{split|reason=[[VPK (file format)]] and [[vpk.exe]]}}
'''VPK''' (Valve Pak) files are uncompressed archives used to package game content, first introduced in {{l4d|3.1}}, later backported {{src13|1}} during SteamPipe update. Valve's post [[GCF]] games store [[VMT|material]]s, [[MDL|model]]s, [[particles]], [[VCD|choreography scenes]] and many other file types in VPK files. Executable and some archive files are discarded by [[vpk.exe]]: [[.zip]], [[.reg]], [[.rar]], [[.msi]], [[.exe]], [[.dll]], [[.com]], [[.cmd]] and [[.bat]]. Some third-party games (even using an engine as old as {{src04|3.1}}) can load depot VPK files as long as Steam is running.<br>
VPKs are also used to distribute mods via the the [[addoninstaller]] tool that ships with some games, such as {{l4d2|4}}.

VPKs can be created with the [[command line]] tool <code>[[vpk.exe]]</code>.

= VPK.exe =

== Creation ==

The tool can be located in the bin folders for most Source games, such as the ones below. The tool is not game dependent, however it is suggested that you use the tool that corresponds to the game you are creating the vpk for. The version in one game may not be as up to date as the version in another due to game updates.

{|class="standard-table" style="background-color:black;"
! &nbsp;Game || &nbsp;Path to VPK.exe  || Version
|- 
| {{as|4}} || ..\steamapps\common\Alien Swarm\bin || v1
|-
| {{css|4}} || ..\steamapps\common\Counter-Strike Source\bin || v2
|-
| {{csgo|4}} || ..\steamapps\common\Counter-Strike Global Offensive\bin || v2
|-
| {{l4d|4}} || ..\steamapps\common\Left 4 Dead\bin || v1
|-
| {{l4d2|4}} || ..\steamapps\common\Left 4 Dead 2\bin || v1
|-
| {{portal2|4}} || ..\steamapps\common\Portal 2\bin || v1
|-
| {{src13|4}} || ..\steamapps\common\Source SDK Base 2013\<Singleplayer or Multiplayer>\bin || v2
|-
| {{tf2|4}} || ..\steamapps\common\Team Fortress 2\bin || v2
|}
{{bug|For some reason sometimes when vpk.exe is used to extract VPKs it gives empty folders, {{portal|4}}'s vpk.exe 
(..\steamapps\common\Portal\bin) seems to extract the files fine
(there might be a corruption when used since it is a diffrent version).
{{workaround|Third party extractors like [[GCFScape]] can extract every .VPK file with no errors}}}}


For servers installed using [[SteamCMD]], it is located in the server's bin\ directory.  On Linux, it is named vpk_linux32 instead of vpk.exe.

=== Linux / Unix ===

Note: The vpk binary makes VPK files of version 2.0, which are '''not''' compatible with games like {{l4d2|3}} that use an older version of the VPK format (in fact {{l4d2|3.1}} will not even start if it detects an unsupported vpk). There is a Python package that can be installed with <syntaxhighlight lang="bash">pip install vpk</syntaxhighlight> which supports the older format. It is also far more convenient than using the built-in tool. Instructions can be found on the [https://github.com/ValvePython/vpk Github page]. 

On Linux / Unix clients, the vpk file can be found replacing "<code>..\steamapps\common</code>" for "<code>~/.steam/steam/steamapps/common/</code>". However, it is named <code>vpk_linux32</code> instead of <code>vpk.exe</code>. '''Note:''' If you installed Steam via Flatpak, the path is slightly different. Look in <code>~/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common</code>


If you are running on a 64-bit system, this binary will not work by default. You must tell it to use the 32-bit libraries located in the same directory. This can be done by setting the <code>LD_LIBRARY_PATH</code> variable.<br>
The following script, if created in the above listed bin directories, will create a wrapper to properly launch the 32-bit executable; then a link (or desktop shortcut) to <code>vpk.sh</code> (if saved as said name) can be created, from there:
<syntaxhighlight lang="bash">
#!/bin/bash
DIR=$(dirname "${BASH_SOURCE[0]}")
export LD_LIBRARY_PATH=$(cd "$DIR" && pwd)
exec "$DIR/vpk_linux32" "${@}"
</syntaxhighlight>

Alternatively, if you're running 64-bit Linux, you can use this script to execute the <code>vpk_linux32</code> binary successfully. Save this script to "<code>/usr/local/bin/vpk</code>" and set it as an executable in the file's properties, for ease of use:
<syntaxhighlight lang="bash">
#!/bin/bash
VPK_LINUX=$(find "${HOME}/.local/share/Steam" -type f -iname "vpk_linux32" -print | head -n 1)
VALVE_LIB_DIR=$(dirname "${VPK_LINUX}")
LD_LIBRARY_PATH="${VALVE_LIB_DIR}:${LD_LIBRARY_PATH}" "${VPK_LINUX}" "${@}"
</syntaxhighlight>


'''HELPFUL NOTE:''' The "<code>${@}</code>" is for drag-and-drop with *.desktop files and arguments when using the <code>vpk</code> command via console.

=== Windows ===

On Windows, you can easily drag-and-drop folders onto <code>vpk.exe</code> file in the <code>bin</code> folder and get a *.vpk file in return, and vice-versa by drag-and-dropping a *.vpk file instead.

{{tip|Some users may find it easier to create a shortcut (*.lnk) linked to <code>vpk.exe</code> as it can be placed anywhere, like a folder that you often are packaging files from, making packaging folders into VPKs and vice-versa quicker and easier than having to return to the <code>bin</code> folder to do so. A good example of this is the <code>custom</code> folder, where placing a shortcut there could make debugging of custom vpk files much quicker.}}

== Commands ==

==== Usage ====
::<code>vpk [options] <directory></code>
::<code>vpk [options] <vpkfile></code>
::<code>vpk [options] <command> <command arguments...></code>

==== Example ====
::<code>vpk -?</code>
:; Lists all of the help info, list of available arguments, and info about each argument.

=== Create VPK/Add Files ===
; <code>vpk <directory></code>
: Create VPK from directory structure. Must be an existing location. The VPK will appear next to the directory. {{note|This is invoked when a directory is dragged onto the VPK tool.}}
; <code>vpk a <vpkfile> <filename1> <filename2> ...</code>
: Add file(s).
; <code>vpk a <vpkfile> @<filename></code>
: Adds the files referenced in a "response file" (''not'' response rules). Note the <code>@</code> symbol.
: The added file will not be added with its file path if the default file path matches that of CMD
; <code>vpk k <vpkfile> <keyvalues_filename></code>
: Add files references in a [[keyvalues]] control file. {{bug|They will appear inside the VPK with their full path (<code>C:\etc\</code>) intact - is there a way to avoid this?}}

=== Extract Files ===
; <code>vpk <vpkfile></code>
: Extract all files from VPK.  {{note|This is invoked when a .VPK file is dragged onto the VPK tool.}}
; <code>vpk x <vpkfile> <filename1> <filename2> ...</code>
: Extract file(s). {{bug|Selective file extraction doesn't seem to work}}

=== Display VPK Info ===
; <code>vpk l <vpkfile></code>
: List contents of VPK.
; <code>vpk L <vpkfile></code>
: List ''Detailed'' contents of VPK.
=== VPK Integrity/Security ===

; <code>vpk checksig <vpkfile></code>
: Verify signature of specified VPK file. Requires -k to specify key file to use.
== Misc. ==
; <code>vpk generate_keypair <keybasename></code>
: Generate public/private key file. Output files will be named ''<keybasename>.publickey.vdf'' and ''<keybasename>.privatekey.vdf'' {{note|Remember: your private key should be kept private.}}

=== Options ===
; {{tip|Please note the case of these options. A capital letter is different than a lowercase letter.}}
; <code>-v</code>
: Verbose output.
; <code>-M</code>
: Produce a multi-chunk VPK. {{note|Required if creating a VPK with key values.}}
:* Each chunk is a file limited to around 200MB.
:* To reduce patch sizes, chunks are never overwritten. New/modified files are instead written to a brand new chunk every time you run the tool. {{note|{{l4d}}{{l4d2}} Multi-chunk generations only works when creating a VPK from a response file. This is not required on {{src13|2}}.}}{{tip|To inspect a multi-chunk VPK open the '_dir' file.}}
; <code>-P</code>
: Use SteamPipe-friendly incremental build algorithm. Use with 'k' command. For optimal incremental build performance, the control file used for the previous build should exist and be named the same as theinput control file, with '.bak' appended, and each file entryshould have an 'md5' value. The 'md5' field need not be theactual MD5 of the file contents, it is just a unique identifierthat will be compared to determine if the file contents has changedbetween builds.
; <code>-c <size></code>
: Use specified chunk size (in MB). Default is 200.
; <code>-a</code>
: Align files within chunk on n-byte boundary. Default is 1.
; <code>-K</code>
: With commands 'a' or 'k': Sign VPK with specified ''private'' key.
; <code>-k</code>
: With commands 'a' or 'k': Public key that will be distributed and used by third parties to verify signatures.
: With command 'checksig': Check signature using specified key file.

== Examples ==

Listed below are some examples of using the tool and what they will do.

==Creating your own VPKs for a mod==

Your mod's assets must be packaged within the appropriate content folders ("sound," "materials," "models," etc.) in the root directory of your VPK. Otherwise you won't be able to see or use your assets in Hammer!
For a specific example, imagine you're packing the content for your mod called "MyMod," and want to include a sound .wav named "ocean_ambient.wav". In your MyMod folder to be packed, you would probably want to place ocean_ambient.wav under "MyMod/sound/", or better, in a specific subdirectory of that one, like "MyMod/sound/ambient/". The same principle is easily applied to other assets like compiled model files, or materials and textures. These would be best placed in subdirectories of "MyMod/models" and "MyMod/materials", respectively.

VPKs must be mounted in gameinfo.txt.

===Creating A Key Value File and VPK===
:1. Create a folder with the correct directory structure and files that you wish to use such as <code>MyMod/resource/ui/<file.res></code>
:2. Use the command line in a prompt or a bat: 
::<code>vpk generate_keypair <name></code>
::<code>vpk -M -k <name>.publickey.vdf -K <name>.privatekey.vdf "..\SteamApps\common\Team Fortress 2\bin\MyMod"</code>
:3. In the folder where the VPK tool is located there will now be a public key VDF, a private key VDF, a VPK named mymod_000 and a VPK named mymod_dir. 
::{{Warning|Never disclose or share your private key VDF or the key. Only share the public key.}}
::* You must distribute your mod with both the mymod_dir and mymod_000 VPKs for the keyvalue to work.

== Response File ==

A "response file" contains a list of files to be added to a VPK. Paths are relative to the current directory of the <code>vpk</code> tool.

Below is a Python script which generates a response file and then builds a multi-chunk VPK. Put it in your mod folder. You will need to edit the three variables at the top.

<source lang="python">
#What folders to look for, and pack into the pak01 vpk set.
target_folders = [ "materials", "models", "resource", "media", "particles", "scripts", "maps", "expressions", "scenes" ]
#What files to look for, in the aforementioned folders.
file_types = [ "vmt", "vtf", "mdl", "phy", "vtx", "vvd", "ani", "pcf", "vcd", "txt", "res", "vfont", "cur", "dat" , "bik", "mov", "bsp", "nav", "lst", "lmp", "vfe" ]
#which vpk.exe to use. do not use \!
vpk_path = "../steamapps/common/SourceFilmmaker/game/bin/vpk.exe"

# Script begins
import os,subprocess
from os.path import join
response_path = join(os.getcwd(),"vpk_list.txt")

out = open(response_path,'w')
len_cd = len(os.getcwd()) + 1

for user_folder in target_folders:
	for root, dirs, files in os.walk(join(os.getcwd(),user_folder)):
		for file in files:
			if len(file_types) and file.rsplit(".")[-1] in file_types:
				out.write(os.path.join(root[len_cd:].replace("/","\\"),file) + "\n")

out.close()

#the "pak01" here specifies the multi-chunk vpk names. Could be changed to "pak02" or "hl2_textures", or whatever your mod needs.
subprocess.call([vpk_path, "-M", "a", "pak01", "@" + response_path])
</source>

To handle this process for {{portal2|4}} you can also use the [[P2 Multichunk Tool]], to automate the response file creation and the creation of the vpk files.
::{{Warning|[[P2 Multichunk Tool]] will ''probably'' work for other games aside {{portal2|3}} if the .vpk path is changed accordingly, it's functions have been expanded to make it easier to experiment, but since it haven't tested outside {{portal2|3}} there is no guarantee it will work with other games.}}
=== Excluded files ===

Executable and some archive files are discarded by the VPK tool:
<pre>
.zip .reg .rar .msi .exe .dll .com .cmd .bat
</pre>
{{warning|Other VPK files are not excluded from compilation, and will be compiled into the new VPK if present in the search paths!}}

= See also =

* [[VPK File Format]] (technical details)
* [[L4D Campaign Add-on Tutorial]]
* [[L4D2 Campaign Add-on Tutorial]]
* [[Releasing A Portal 2 Map]]
* [[P2 Multichunk Tool]] (Easy handling of mass vpk packing)
* [[Swarm Campaign Add-on Tutorial]]
* [https://github.com/geotavros/VpkCompare/releases/ VPK Compare GUI Tool] for finding conflicts between VPK files 
* [https://web.archive.org/web/20160628021955/https://facepunch.com/showthread.php?t=1327883 Source Multi-Tool] (VPK Creator - GUI)
* [[Fixing VPK mounting for older Source SDK Bases]] (for {{src06|1.bold}} & {{src07|1.bold}})
[[Category:Modding]]
[[Category:Steam]] <!-- Like the page about GCF itself, Steam not only use it, but also requiring it if you want to play Source 2004, 2006, 2007 and 2009 games without the loose branch, or without unpacking depot VPK files. -->
[[category:File formats]]