In this video I walk you through the exact workflow I use to upload a Unity build to Steam using Steamworks Console / SteamPipe (ContentBuilder). I start from the Steamworks partner site, downloading the Steamworks SDK, extracting it somewhere easy to find, and then navigating into the SDK path you actually need: tools > ContentBuilder > content. That “content” folder is basically the staging area—so I create a new folder there (name doesn’t matter) and drop my Unity build inside, because that’s the folder Steam’s uploader will read from. After that, I launch Steampipe and show what each field in the Steam build uploader means. I explain where your AppID lives in the Steamworks dashboard and why you must enter it correctly so Steam updates the right game. Then we go over DepotID—how depots usually represent platforms (Windows/Mac/Linux) and how your first upload often starts with a single depot. Finally, I generate the VDF files, hit upload, and watch the console logs to catch issues early. Once it’s done, I show the last step: verifying the build in Steamworks under the correct branch (and switching branches when needed).