• Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/
  • Weve updated the Tripwire Privacy Notice under our Policies to be clearer about our use of customer information to come in line with the EU General Data Protection Regulation (GDPR) rules that come into force today (25th May 2018). The following are highlights of our changes:

    We've incorporated the relevant concepts from the GDPR including joining the EU and Swiss Privacy Shield framework. We've added explanations for why and how Tripwire processes customer data and the types of data that we process, as well as information about your data protection rights.

    For more information about our privacy practices, please review the new Privacy Policy found here: https://tripwireinteractive.com/#/privacy-notice

Mod Workshop Command Line Uploading


In Soviet Russia, Yoshiro is a cake
Staff member
Oct 10, 2005
Workshop upload command line:

For those having issues can you also try running the workshop upload via command line. Instructions are as follows:

While there is a GUI tool to build scripts, brew data, and upload mods and maps to the Killing Floor 2 Steam workshop, the command-line tool that it invokes to upload to workshop can be invoked directly. This makes it possible to automate updating with a batch file or other script.

This guide applies to the Community Workshop for maps and mods, not the Curated Workshop where art assets and other items can be uploaded for consideration for inclusion in the game.

The newest version of the Steam Workshop uses directory trees as items, not single files. Workshop items do not need to be zipped or archived into single files any more, but they do need to be arranged correctly in a directory tree.

The name of the command line uploader is WorkshopUserTool.exe. It takes a single parameter: the name of a configuration file that is used to define the upload. It is installed as part of the Killing Floor 2 - SDK tool in Steam to the ...\SteamApps\common\killingfloor2\Binaries directory (the game and editor executables are in Win64 subdirectory of that path). It uses the base Killing Floor 2 user directory as its working directory (something like "C:\Users\<username>\Documents\My Games\KillingFloor2", depending on your version of windows). Wherever WorkshopUserTool.exe is on disk, it will only look in that directory for the configuration file it uses to define the upload. Here is an example of its format:

$Description "Another test of workshop."
$Title "Workshop Test"
$PreviewFile "C:\Users\NameHere\Pictures\WorkshopTest.png"
$Tags ""
$MicroTxItem "false"
$PackageDirectory "C:\Users\NameHere\Documents\My Games\KillingFloor2\TestMapUpload"

Those lines must be in that exact order in the file. The quotes are also necessary. The Description and Title lines are the title and description the item will be listed under on Steam Workshop. The PreviewFile is the picture that will be displayed for the item. The full path to the file must be given. The Tags line is a space-separated list of tags to associate with the item in the Workshop. MicroTxItem needs to be "false" to indicate this is not for the curated workshop. The PackageDirectory setting is the directory to be uploaded as the Workshop item. It's best to keep this as a subdirectory of ...My Games\KillingFloor2, since that's where the files will be coming from.

The contents of PackageDirectory will be installed to the user's KillingFloor2\KFGame\Published directory, and the content directory under it is BrewedPC, so usually the PackageDirectory will contain the directory BrewedPC with other directories like Maps, Packages, etc. Note that a limitation of Unreal Engine 3 is that all packages and maps must have distinct names even if they are in separate directories, so keep that in mind.

An example directory tree that was used to upload the Workshop Test map was:

  • BrewedPC
    • KF-WorkshopTest.kfm
    • Packages
      • ENV_WorkshopTest
        • ENV_WorkshopTest_MAT.upk
        • ENV_WorkshopTest_TEX.upk
      • Config
        • .ini
      • Localization
        • .int

The workshop uploader tool is run with the name of the configuration file on the command line. The configuration file above was named wsinfo_testmap.txt, so the workshop test map was uploaded by running:

WorshopUserTool wsinfo_testmap.txt

As a heads up you can use the Tags field by doing any of the following:

$Tags "Maps,Mutators,Gamemodes,Weapons"

That would include all the current tags for Maps and Mods. Separate the tags by a single space. Let me know if there are other tags you feel would be useful for the Maps and Mods workshop.


Dec 17, 2015
Following the help of posts everywhere on the forum + my own stuff, I almost managed to upload my map.

Unfortunately now, I got this error when using the command line (see link below).

It does the same on my laptop, I have no idea what I could do.

Yoshiro, do we have some more time for Grindhouse requirement of Workshop upload?

Edit: the betaupload tool allowed me to upload my map from another computer.

Last edited:


In Soviet Russia, Yoshiro is a cake
Staff member
Oct 10, 2005
Added documentation for folder structure to support .int and .ini files for the tool.


Active member
Mar 23, 2015
Is there something im missing for INT file support? I set up my directories like that in a folder and uploaded it to the workshop. When I downloaded it from the workshop, the int files got downloaded correctly, but in game, the text still displays as ?INT?packagename.stuff as though the int isn't there.


Jan 22, 2017
I tryed all. The SDKFrontEnd.exe does not open, nothing happens, checking windows log i see a error KERNELBASE.DLL.
I tryed to reinstall the game 3 times, I Tryed to install another windows, still no sucess,
i tryed that method with cmd and WorkShopUserTool.exe, i receive a error: "Falied to load workshopdll.dll" and the app crash.
Please, someone!
Last edited: