The build you send is the build that leaks
Sending a playtest build is usually a chain of small problems:
- You upload a multi-GB build and hope the tester has the right GPU, drivers, and runtime.
- The build sits in a downloads folder after the test ends. You cannot revoke it.
- Every new build means another upload, another link, another “which version are you on?”.
- Screenshots and footage can leak before you are ready to show the game.
- Testers on Macs, tablets, or locked-down machines simply cannot run it.
For a closed alpha, a press preview, or a publisher pitch, distributing the executable is often the riskiest part of the process.
What a playtest link changes
A playtest link is a URL that starts a session on a Windows host you control. The game runs there; the tester’s browser only receives video and sends input. There is no build to forward, install, or forget to delete.
- Access is revocable: take the host offline and the link stops working.
- The build stays home: no executable, no assets, no source on the tester’s disk.
- No install friction: a browser is the only requirement.
- One current build: update the host and every tester gets the new version.
- Works across devices: Windows, Mac, Linux, tablets, and low-end laptops can join.
How it works
- Create the game in Gamespace. Bind the process name or Steam AppID, set the session length, and choose the URL players go to when the session ends.
- Connect the Windows host. The host joins the game and picks an edge region. The build stays on that machine.
- Create a private campaign link. Add a password if the test is under NDA, and keep the link out of public pages.
- Watch the session funnel. See who clicked, who got a host, who connected, who played, and who completed the session.
When the test is over, stop the host. You do not have to chase testers to delete a file.
Access control checklist
- Password: add one for closed tests; rotate it between waves.
- Session cap: limit the demo to the length you actually need feedback on.
- Fallback URL: send expired or hostless sessions to a “test is closed” page, not a dead end.
- NDA and watermark: put the tester ID on screen if you need to trace leaks.
- Feedback loop: pair the link with a form or Discord thread; the link gets you in, the questions get you signal.
- Version discipline: one host per build, and a clear note in the invite about what changed.
Steam Playtest vs build upload vs a link
| Steam Playtest | Build upload | Playtest link | |
|---|---|---|---|
| Where the build lives | Steam depot | Tester’s disk | Your Windows host |
| Who can join | Steam users with access | Anyone with the file | Anyone with the link and password |
| Revoke access | Remove from Playtest | Impossible | Take the host offline |
| Install required | Yes | Yes | No, just a browser |
| Mac / tablet testers | Limited | Usually no | Yes |
| Best for | Public or large-scale tests inside Steam | Internal builds on trusted machines | Closed alpha, press, publishers, cross-device tests |
What to measure in a playtest
A link gives you session data, not just “did they install it”. Track:
- invite clicked → host allocated (did they get in?)
- host ready → web connected (did the stream start?)
- session length and completion (did they play long enough to have an opinion?)
- where they stopped (a specific level, a menu, a crash)
- post-session survey or call notes, tied to the build version
FAQ
No. They open a link in a browser. The game runs on your Windows host; the browser receives video and sends input.
No. The executable and assets stay on your host. Testers never receive the build, which makes the link safer for closed tests, press previews, and NDA sessions.
Yes. Add a password, keep the link private, cap session length, and stop the host to end access. You can also set a fallback URL for when no host is online.
No. Steam Playtest distributes a build through Steam. A playtest link runs the build on your own machine and works outside Steam, including for press, publishers, and testers without the store client.
Input goes to the host and video comes back over WebRTC. Latency depends on the distance between the player and the host. For playtests, place the host near your testers or pick a close edge region.