TL;DR: SteamPipeGUI for macOS is my free, open source Unity Editor tool that builds and uploads your game to Steam on both macOS and Windows without touching the CLI or .vdf scripts. Install via Package Manager using the GitHub URL, create a Deployment Target per platform, hit Build Target. Publish time drops from roughly 30 minutes to under one.

SteamPipeGUI for macOS: Ship Your Unity Game to Steam Without the CLI

SteamPipeGUI for macOS is a free, open source Unity Editor tool that lets you build and upload your game to Steam directly from Unity on both Windows and macOS, without using Steam's command line. It brings Steam deployment on Mac in line with the Windows SteamPipeGUI experience. If you release on Steam and develop in Unity, this tool can cut your publish time from around 30 minutes to under a minute.

Summary

SteamPipeGUI for macOS (Unity) is a Unity Editor extension for Steam build and upload. It works on Windows and macOS. You need a Steamworks account, Steamworks SDK, and an app plus depot set up in the Steamworks dashboard. Install via Unity Package Manager from the GitHub repo, create a Deployment Target per platform, then use Build Target to build and upload. Author: Darko Tomic. Repository: https://github.com/tomicz/steam-pipe-gui-macos-unity.

What is SteamPipeGUI for macOS?

SteamPipeGUI for macOS (Unity) is a Unity-native tool that streamlines building and uploading games to Steam. On Windows, Valve's SteamPipeGUI offers a simple UI; on macOS there is no official GUI, so developers usually rely on Steam CLI and .vdf scripts. This tool adds a GUI workflow inside the Unity Editor on both Windows and macOS, so you can build and upload to Steam without leaving the editor or running terminal commands manually.

Why use SteamPipeGUI for Unity?

Without a GUI on macOS, Steam deployment means configuring launch options, depots, and .vdf files by hand. That is slow and error-prone. With SteamPipeGUI for macOS, the same flow takes under a minute from the Unity Editor. You get one workflow for building and uploading from Unity on Windows or macOS, fewer copy-paste mistakes with depot config, and a faster release loop for betas and patches.

Requirements

You need a Steamworks account, an app and at least one depot set up in the Steamworks dashboard, and the Steamworks SDK installed on your machine. The repo README explains how to create an app, get your App ID and Depot ID, and configure launch options and depots. Once that is done, the tool handles the build and upload steps.

How to install SteamPipeGUI in Unity

1. Open your Unity project.
2. Open Window > Package Manager.
3. Click + and choose Add package from Git URL.
4. Enter https://github.com/tomicz/steam-pipe-gui-macos-unity.git and click Add.

How to deploy to Steam from the Unity Editor

1. In the Project window, right-click and go to Create > Tomicz > Steam > Deployment Target.
2. Create a target per platform (e.g. one for macOS, one for Windows).
3. Fill in the target: game name (must match your Steamworks launch options), description, Steam username, App ID, Depot ID, and the path to your Steam SDK.
4. Click Build Target to build and upload. When finished, your build appears under Steamworks > SteamPipe > Builds.

Use a clear description for each build (e.g. "Target: StandaloneOSX 0.0.x") so you can tell them apart later.

Git repository and more Unity open source

Git repository: https://github.com/tomicz/steam-pipe-gui-macos-unity

For more Unity open source projects, see github.com/tomicz.