🖥️ How to Set Up a Self-hosted Clipify Runner
A Clipify Runner runs the streaming work on a computer or server you control. Use it to broadcast a clip overlay or
prepare fallback playback when your normal OBS feed disconnects.
✨ It keeps that work separate from the browser tab you use to manage Clipify.us.
💎 Runner access is a separate add-on. It is not automatically included with Pro. You also need access to the overlay you
want to broadcast; the creator's normal plan limits still apply.
🖥️ Choose where it should run
- Your OBS computer: Convenient, but it cannot keep running if that computer shuts down or loses its connection.
- Another computer or server: Separates the Runner from the OBS machine. If both share the same internet connection or
power, they still share that failure point.
- Hosted hardware: Runs outside your local setup. Contact us if you want to discuss a hosted Runner.
The host needs a stable connection and must remain awake while you want it to stream. Choose hardware appropriate for
your intended resolution and frame rate.
📥 Download the correct Runner
1. Open your Clipify dashboard, select Runners and add or open a Runner.
2. Download the build for the computer that will run it.
3. Choose the correct architecture: Windows, Linux x64 or ARM64, or macOS Intel or Apple Silicon, as offered by the
dashboard.
4. Follow the installation steps displayed for that build.
On Windows, open the downloaded Runner file. On Linux, make the file executable and run it using the commands shown in
the dashboard. On macOS, follow the displayed system approval steps if the downloaded app is blocked.
🔑 Approve enrollment
The Runner opens an enrollment prompt in your browser. If it cannot open a browser, use the URL and one-time code it
displays on another device.
1. Sign in to the correct Clipify.us account.
2. Approve enrollment for the intended Runner.
3. Return to the dashboard and wait for it to show as online.
Do not share enrollment codes or saved credentials. If a code expires, restart the enrollment flow to request a fresh
one.
🎬 Configure a stream
Once the Runner is connected:
1. Select the overlay you want to use.
2. Choose the stream mode and target platform.
3. Enter the required destination and stream key. Twitch and YouTube targets require a stream key; a custom RTMP target
may handle credentials differently.
4. Review the quality settings and select Save Configuration.
5. Select Start when you are ready to broadcast.
6. Check the destination platform and the Runner's reported status. Use Stop when the test is finished.
🔒 Keep your stream key private. It can authorize a broadcast to your channel. Do not include it in screenshots, public
messages or a support request.
🛟 Set up Failsafe mode deliberately
In Failsafe Mode (Local OBS Fallback), OBS sends its feed to the Runner, and the Runner forwards the stream to your
destination. If the OBS feed drops while the Runner remains online, it can switch to the configured overlay playback.
Follow the ingest address shown in your dashboard. When OBS and the Runner are on the same computer, the displayed local
address applies. If they run on different computers, use the Runner host's reachable address instead of pointing OBS at
its own localhost.
Test the connection and fallback before relying on it during a stream. A Runner cannot continue broadcasting if its own
host loses power or internet, and it cannot prevent a Twitch or destination-platform outage.
🔄 Keep it healthy and up to date
The dashboard shows Runner status, the last heartbeat, version and stream information. If an update is available,
download the correct current build and follow the dashboard instructions.
If a Runner is offline, check that its process is running, the host is awake and the network can reach Clipify.us. If it
is online but a stream will not start, check the overlay source, destination configuration and active Runner access.
🐳 Advanced Docker setup
The Runner page includes Advanced / Docker Setup. Use the commands for your current Clipify environment rather than
copying an old image tag or another account's credentials.
Only make the OBS ingest endpoint reachable where you need it. Keep the Runner's credentials and your destination stream
key private.
Next step: Open your Runners.
Related guide: What happens when Pro access ends.