Main Menu

Steam Site Server

Steam Site Server

Step-By-Step Instructions

The Steam Site Server allows licensees of the Steam PC Café Program to share commercial licenses in their local network. The following instructions will walk you through the setup of the Steam Site Server. Additional information about the program can be found here.

  • Visit the Steamworks website and login with your Steam master account credentials.
  • Download the Steam Site Server file by clicking the link located under the "Tools + Links" section on the right.
  • Unzip the server files to your hard drive.
  • Create a new Steam account here that will be used at the individual location as a Site Server account. If you have multiple physical locations, you will need one Steam Server account per location.
  • Once the account has been created, go back to the Steamworks website (make sure you're logged in with your Steam master account), navigate to the "Users & Permissions" menu option and select "Manage Users". On this page click the "Add User" button and fill in the required information about the Steam server account you've just created. Don't give it any special permissions.
  • Go to the "Manage Sites" page and add a new site location. The name you select here will also be displayed in the Steam client library of your patrons. Once the site has been added, move the cursor over the site definition. You should see a key symbol appear under the "Server Account" section. Select this and then select the Steam server account you just added. Repeat this step if you have multiple site locations.
  • Run The Local Server

    Once you have extracted the documents from the zip file and added the server account to your site location, it’s time to run the server in your local network.

    First, create a shortcut for the “steamcmd.exe” by right clicking the file and selecting “Create shortcut”. After you’ve successfully created the shortcut, right click the file and select “Properties”.


    In the Target field, add the following command right after the location and save the changes:

    -sitelicense +login (insert server account name) (insert password)

    Your Target field should now look something like this:

    C:\Users\computer name\downloads\site_server\steamcmd.exe -sitelicense +login accountname password

    Note: Make sure you remove any quotation marks or parenthesis around your password and account name

    Next, run the steamcmd.exe shortcut that you have created with the above commands. You may need to enter the Steam Guard code that will be sent to the email address associated with the Site Server account.

    Steam Guard

    Once you've successfully logged in, the CMD will present you with the screen below.

    Logged in

    Content Cache


    The content cache allows you to download game files once and then distribute them through your local network to the individual game stations. Patrons that bring their own computer or laptop can also access the game files instead of using your location's Internet bandwidth. Please note that the game files will be saved on your server machine and you may need to increase your hard drive space depending on the amount of games that you will offer.

    Navigate to the folder where you previously extracted the server files to. The folder will be named "site_server".

    In order for the content cache to work properly, you will need to un-comment the command lines in the "steamconsole.cfg" file. Un-commenting can be done by removing the "//" at the beginning of each line. You will at least have to un-comment and edit the following lines:


    In our sample arcade, we have chosen to create a content folder on the main hard drive and set the cache limit to 500GB. Click the button below to expand our sample configuration.

    // Content cache configuration
    // The location of the game download cache on the server machine.
    // You should create the cache directory before running the server.

    // ----- This must be set for the content cache to operate -----
    @sSiteLicenseProxyCacheDirectory C:\sls_cache_public

    // The maximum size on disk of the game download cache (default = 100GB)
    @nSiteLicenseProxyCacheMaxGB 500

    // Steam client game downloads will proxy through this port on the site server
    // ----- This must be set for the content cache to operate -----
    @nSiteLicenseProxyPort 3128

    // Optional flag to enable the Steam clients on your network to share downloads with each other, reducing traffic
    @nSiteLicenseProxyEnableP2P 1

    When a game is launched for the first time in your network, the download request will be sent to the server machine. If the game files are not cached on the server yet, the server will download them automatically, cache them, and return them to the client machine. If the game content cache is already available on your server, the server will automatically send the files to the client machine.

    Are there any special requirements for the type of hardware I use for the Steam Site Server?


    To run a Steam Site Server, you just need a secure Windows 7 or Windows 10 PC connected to the location's network. You will also be able to run it on Windows Server 2012 R2 and 2016. If you are also using the Site License Server as a content server cache we recommend that it has enough storage to support 1TB of content data.

    What ports are being used by the Site Server?


    The communications between the Steam client and the Site License Server use UDP broadcast packets over port 27036. If the client machine is not receiving those packets, then it won’t be able to discover and connect to the Site License Server. You can find a list of required ports for Steam here.

Problem with Steam?

Help Me With My Issue