Platform compatibility and setup

Reviewed against official documentation on 2026-10-07. LeanCast sends H.264 video and AAC audio to selected RTMP/RTMPS destinations. It is an independent encoder frontend, not a platform-approved integration or an account-eligibility service. A saved key means configured; Connecting/Sending describes the local transport, not verified public delivery. Enable only the platforms you want to use; every enabled destination needs valid setup.

YouTube

Enable live streaming on a verified, unrestricted channel; first-time activation can take up to 24 hours. Copy the actual server and key from Live Control Room. The editable RTMPS preset is rtmps://a.rtmps.youtube.com:443/live2. For launch from the encoder, turn on Auto-start for the intended broadcast bound to that key, and choose its privacy setting deliberately. Scheduled broadcasts can otherwise require Go live in Live Control Room. LeanCast does not create broadcasts or query their readiness. Encoder setup, eligibility, Auto-start and stream settings.

YouTube supports RTMP/RTMPS with H.264 and AAC, recommends CBR and two-second keyframes, and says not to exceed four seconds between keyframes. Its current H.264 table lists 3 Mbps minimum / 8 Mbps recommended for 720p at either 30 or 60 FPS. LeanCast's 4.5 Mbps default is above that minimum, below that recommendation, and a compromise for shared multi-platform output. YouTube recommends 44.1 kHz / 128 Kbps stereo audio; LeanCast currently emits 48 kHz / 160 Kbps, so exact conformity with that recommendation is not claimed. Encoder settings.

RTMPS needs the correct hostname/application, TLS with SNI, and port 443. LeanCast delegates the transport to installed OBS libraries; successful local RTMP tests do not verify YouTube's TLS or ingest acceptance. YouTube RTMPS requirements.

Twitch

Copy the primary stream key from Creator Dashboard. Twitch's public ingest directory provides both cleartext and secure endpoints; its secure default currently maps to rtmps://ingest.global-contribute.live-video.net/app. Put only the server/application in Server, and the key in Stream key. Use the current official ingest list when choosing a region. Broadcast URLs and keys, official ingest directory.

Twitch's published baseline recommends H.264, CBR, two-second keyframes, and AAC audio up to 160 Kbps. Its examples use 3,000 Kbps for 720p30; 4,500 for 720p60 or 1080p30; and 6,000 for 1080p60. These are recommendations, not a claim that every higher rate is accepted. LeanCast's 160 Kbps AAC fits this published audio limit. Viewer transcode availability and playback quality remain service-dependent. Broadcasting guidelines.

Twitch Inspector supports an official bandwidth-test parameter, but LeanCast's ordinary Start action does not add it. Treat Start as a real publishing request. Developer guide.

Kick

Copy both Stream URL and Key from the account's dashboard; there is no universal hardcoded account endpoint in LeanCast. Keep the supplied scheme, port, and /app path. Kick's setup examples use RTMPS with port 443. Set the title/category before publishing. Official settings specify H.264, CBR, two-second keyframes, at most 8,000 Kbps video, 1920x1080 and 60 FPS. Its examples recommend Main profile; LeanCast uses High, so these examples are not matched exactly. Kick encoder setup.

Kick's connection troubleshooting further specifies stereo audio at no more than 48 kHz and rejects H.265/VBR. LeanCast's H.264/CBR and 48 kHz stereo match those basic requirements. A correctly shaped stream is still subject to the actual endpoint/key and account state. Kick connection requirements.

TikTok: direct access is required

LeanCast requires an authorized direct publishing server and stream key that work with an independent encoder. Enter them exactly as supplied by TikTok. There is no default server, OAuth/keyless TikTok integration, credential generator, or LIVE Studio/virtual-camera fallback. Leave TikTok disabled unless you have working direct access; mobile LIVE or LIVE Studio access alone is not evidence of usable direct credentials.

TikTok's official help states that creators must be at least 18 to go LIVE; eligibility and follower/access criteria vary by region and account. Its LIVE Studio guidance describes a separate application/access process with changing regional requirements. Neither establishes approval of LeanCast. Do not use a universal follower count as a promise of RTMP access. Some English pages were blocked to automated retrieval during this review; account controls remain authoritative. Age requirements, LIVE eligibility, official LIVE Studio access guidance.

We did not obtain an authoritative, generally applicable TikTok external-encoder bitrate/keyframe specification during this review. LeanCast's 720x1280 portrait H.264 at 3,500 Kbps, two-second keyframes and shared AAC is an application default, not a verified TikTok ingest guarantee. Use any settings TikTok supplies with the account's direct access, and check its actual LIVE dashboard after a deliberately authorized test.

For comparison, Streamlabs documents a keyless workflow for its own products. That is primary evidence about Streamlabs' integration, not evidence LeanCast can reuse its access or obtain a transferable key. Streamlabs integration guidance.

Simultaneous streaming

Shared encoding, upload and secrets

Three widescreen destinations can reuse one H.264 encoder; the separate portrait composition requires a second video encoder. AAC is shared. Every direct destination still uploads its own copy. At 4,500 Kbps wide, 3,500 Kbps portrait and 160 Kbps audio per connection, four streams total 17.64 Mbps before protocol overhead. This is arithmetic for those settings, not a measured bandwidth guarantee or a speed-test recommendation. Using fewer selected destinations reduces upload requirements.

Prefer a platform-issued rtmps:// endpoint when available. rtmp:// is not encrypted in transit; DPAPI encryption of the saved profile does not change that. Keep keys out of screenshots, logs and support messages. The profile is encrypted for the current Windows account, but running code under that account can access it, and active keys exist in process memory. Use only trusted official server values; LeanCast's URL syntax validation does not certify a host belongs to a platform.

Local loopback and file decoding demonstrate encoder/transport behavior. They do not verify platform authentication, TLS acceptance, public visibility, moderation, audience delivery, or real gameplay performance. See release review and public validation.

Back to LeanCast · Download this document