START HERE
Create a Google Desktop app OAuth client with YouTube Data API v3 enabled, authorize the channel in a YouTube Read Account, and select that account in the chat widget. Verify an active broadcast and a new message before changing OBS. Slippy2's current YouTube integration reads chat; it does not send messages.
Check which fork and build you are using
Slippy2 Desktop is Maskarauder's independent fork of Slime2 Desktop. It is not affiliated with, supported by, or endorsed by Zaytri or the upstream Slime2 project. Use this fork's repository for support.
As checked on November 18, 2026, the latest published release was v1.6.1, whose download filenames still use Slime2. The current source uses the Slippy2 name. Release v1.6.1 already includes YouTube Read Accounts and the widget ZIP update workflow (introduced in v1.6.0), while installers older than v1.6.0 lack that workflow and newer post-release source changes must not be assumed present in earlier installers. This guide cites source revision e9fa701.
Prepare the Google project and the right client type
- In Google Cloud, select the project you intend to use for this integration and enable YouTube Data API v3.
- Configure the OAuth consent screen. If the project is in Testing, add the Google account owning the intended YouTube channel as a test user.
- Create an OAuth client with application type Desktop app. Keep the client ID and corresponding secret together so you do not accidentally combine values from different clients.
- Read the requested permissions when authorizing. Use the channel you intend to display, especially if your browser can choose among multiple Google accounts or channels.
The app uses Google's installed-application flow. A Web application client, service-account key, or ordinary API key is not a substitute for its Desktop app OAuth credentials. Keep credential screenshots out of the stream and out of public support posts.
Connect the account to a widget
In the desktop app, add a Read Account, choose YouTube, enter the Desktop client credentials, and complete authorization in the system browser. Then use Slime2 Chat Box version 1.6.0 or newer and choose that YouTube read account in the widget's YouTube account slot, or intentionally make it the default.
Authorization and widget assignment are separate steps. A saved account alone does not establish that the displayed widget uses it. For the first test, use one widget and one explicitly selected account. Confirm the channel has an active broadcast with live chat, then post a recognizable new test message through YouTube's normal chat interface.
The integration reads the authenticated channel's active chat. It is not a general URL-based scraper for arbitrary channels, and a quiet chat is not by itself evidence of a broken connection.
Separate account, message, and display failures
| Observation | Next check |
|---|---|
| Authorization cannot finish | Check Desktop client type, enabled YouTube API, test-user access, and the selected Google account. |
| Account is saved but no messages appear | Check the active broadcast, live-chat availability, widget version, and its selected read account. |
| The local widget shows messages but OBS does not | Check the widget's browser-source URL, OBS source visibility, crop/size, and whether OBS is running on the same computer. |
| Chat worked but now reports quota or retry status | Read the reported reason and allow its retry interval. Adding duplicate accounts or sources does not repair exhausted API quota. |
If a local widget URL points to localhost, an OBS instance on another computer will interpret localhost as itself. Do not solve that by exposing the desktop app publicly; first reproduce with OBS on the same machine.
Understand reauthorization and widget updates
Google documents that external OAuth apps in Testing generally receive seven-day refresh tokens when requesting scopes beyond basic profile information. A weekly authorization expiry can therefore reflect project status rather than a lost OBS setting. Check the actual error before recreating your account; temporary network failures and rejected credentials call for different responses.
Slippy2 Desktop v1.6.0 and newer (including v1.6.1 and current source) include a widget ZIP update flow that preserves the layout and its browser-source URL; installers older than v1.6.0 lack that flow. Use the instructions matching your build, and back up the configuration before changing widget packages. Updating a widget does not silently upgrade the desktop application's code.
Verify one message through the complete route
Keep OBS off-air for setup. Send a new message containing a unique short phrase, observe it in the widget, then make a local OBS recording showing it. Confirm the message appears once, remains readable against your scene, and does not expose setup panels or credentials. Repeat after restarting the desktop app and OBS.
If it still fails, report the app build, widget version, account type, whether the message reached the local widget, and a sanitized error reason. Keep client credentials, authorization tokens, and private browser-source URLs out of the report. These observations identify whether the next fix belongs in Google authorization, the chat reader, the widget, or OBS.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.