IRL Commons This site is new and not complete. Something wrong? Let us know

Existing formats

Part of the open data in irl-commons.

Shared across apps 

Apps and services from different makers understand these.

All 15 entries, with details

SRT (Secure Reliable Transport) 

ProtocolIn useOpen

A way of sending live video over the internet. When a piece gets lost on the way, it is sent again quickly, so the picture glitches less. From the glossary

Made by
Haivision (SRT Alliance)
Licence
Open source, MPL-2.0 (libsrt).
Listed
SRT

Described at github.com/Haivision/srtChecked 14 November 2026 Suggest an edit to SRT (Secure Reliable Transport)

Support in each listed product follows its services.json entry.

Sources

libsrt repository

srt:// and srtla:// stream URLs 

FormatIn useOpen

One line that holds the host, port, stream ID and options such as latency, which a receiver hands out and an app pastes in.

Made by
Haivision (srt://); srtla:// has no single maker

Described at github.com/Haivision/srt/…Checked 14 November 2026 Suggest an edit to srt:// and srtla:// stream URLs

srtla:// borrows the srt:// shape, but no maker publishes its rules, and apps differ on which query options they accept.

Sources

srt-live-transmit: URI syntax · Moblin README · OpenIRL srtla-receiver README · IRLhosting tools

SRT Stream ID 

FormatIn useOpen

The text field that tells a receiver which stream you are publishing or playing.

Made by
Haivision (recommended syntax); each receiver sets its own keys

Described at github.com/Haivision/srt/…Checked 14 November 2026 Suggest an edit to SRT Stream ID

The field is shared; the convention is not. Haivision recommends an optional '#!::' key=value syntax, while IRL receivers use their own keys (SRT Live Server style 'uplive.sls/live/<name>', OpenIRL 'live_<key>' and 'play_<key>').

Sources

SRT access control (Stream ID) · irl-srt-server README · OpenIRL srtla-receiver README

SRTLA (SRT link aggregation) 

ProtocolIn useOpen

A way of splitting one live video across several internet connections at once. A computer at the other end joins the pieces up again. From the glossary

Made by
BELABOX
Licence
AGPL-3.0 reference code from BELABOX; no separate spec.
Listed
srtla

Described at github.com/BELABOX/srtlaChecked 14 November 2026 Suggest an edit to SRTLA (SRT link aggregation)

The reference code and its README describe it; there is no separate spec. srtla2 is incompatible with earlier srtla. BELABOX marks its own receiver (srtla_rec) unsupported and points to BELABOX Cloud; the other receivers are independent implementations. Sender support follows the services.json entries.

Sources

BELABOX srtla README · go-irl README · OpenIRL srtla-receiver README

RIST (Reliable Internet Stream Transport) 

ProtocolIn useOpen

A broadcast-industry alternative to SRT for sending video over the internet, with its own multi-link bonding.

Made by
Video Services Forum (RIST Activity Group); librist by VideoLAN
Licence
VSF TR-06 specifications; librist under BSD-2-Clause.

Described at vsf.tv/technical-recommendationsChecked 14 November 2026 Suggest an edit to RIST (Reliable Internet Stream Transport)

Support in the other listed products follows their services.json entries.

Sources

VSF technical recommendations (TR-06) · librist · Moblin README · NOALBS RIST stats parser

NDI (Network Device Interface) 

ProtocolIn useClosed, documented

Video between cameras, computers and apps on the same network, with very little delay; some cameras send it directly.

Made by
Vizrt NDI AB
Licence
Proprietary SDK from Vizrt NDI AB, offered under NDI's own terms.
Used by
OBS Studio, vMix, DistroAV

Described at ndi.videoChecked 15 November 2026 Suggest an edit to NDI (Network Device Interface)

OBS speaks NDI through the DistroAV plugin. NDI|HX cameras send compressed NDI from the camera itself.

Sources

NDI docs: NDI protocols · NDI SDK page · DistroAV README · vMix features

WHIP (WebRTC-HTTP Ingestion Protocol) 

ProtocolIn useOpen

A standard way to send a WebRTC (very low latency) stream to a server with one HTTP request.

Made by
IETF (WISH working group)
Licence
IETF standard, RFC 9725.

Described at datatracker.ietf.org/doc/rfc9725Checked 14 November 2026 Suggest an edit to WHIP (WebRTC-HTTP Ingestion Protocol)

RFC 9725, a Proposed Standard published in March 2025.

Sources

RFC 9725 · OBS Studio WHIP output · Moblin README · MediaMTX supported specifications · Larix Grove

Enhanced RTMP (E-RTMP) 

ProtocolIn useOpen

Brings modern codecs (HEVC, AV1, Opus), multitrack and reconnect to the old RTMP protocol.

Made by
Veovera Software Organization
Licence
Open spec under Apache-2.0 from Veovera.
Used by
OBS Studio, librtmp2-server, Twitch, FFmpeg, XSplit, YouTube

Described at github.com/veovera/enhanced-rtmpChecked 14 November 2026 Suggest an edit to Enhanced RTMP (E-RTMP)

The adopters follow Veovera's own adoption list, not a test of each product.

Sources

Enhanced RTMP repository · librtmp2-server README

OBS WebSocket (v5) 

ProtocolIn useOpen

The remote-control line into OBS: switch scenes, start and stop, read status. It never carries the video.

Made by
OBS Project
Licence
GPL-2.0

Described at github.com/obsproject/obs-websocket/…Checked 14 November 2026 Suggest an edit to OBS WebSocket (v5)

Built into OBS Studio since version 28. Client support follows the services.json entries.

Sources

obs-websocket protocol · Moblin README

Receiver stats endpoints 

FormatIn useNo written spec

The web address a receiver offers with live bitrate, round-trip time and lost packets, which scene switchers and overlays read.

Made by
Each receiver's maker; NOALBS maintains the parsers
Used by
NOALBS, NOALBS Cloud, IRLhosting, BELABOX Cloud, irl-srt-server, OpenIRL srtla-receiver, MediaMTX, librtmp2-server, NGINX RTMP, Nimble Streamer, Node-Media-Server, Xiu, go-irl

Described at github.com/NOALBS/nginx-obs-automatic-low-bitrate-switching/…Checked 14 November 2026 Suggest an edit to Receiver stats endpoints

Not one format but one shape per server: NOALBS keeps 14 parser modules, the nearest thing to a shared reference. Some receivers reuse another's shape; irl-srt-server keeps SRT Live Server's.

Sources

NOALBS stream server parsers · IRLhosting tools

BELABOX Cloud remote 

ProtocolIn useNo written spec

The WebSocket through BELABOX Cloud that lets a bot, switcher or dashboard see and control a BELABOX from anywhere.

Made by
BELABOX
Licence
GPL-3.0 (belaUI code)

Described at github.com/BELABOX/belaUIChecked 14 November 2026 Suggest an edit to BELABOX Cloud remote

BELABOX runs the service; the other tools connect to it. There is no published protocol description, so clients follow belaUI's code.

Sources

belaUI repository · BelaBot repository

RealtimeIRL location API 

ProtocolIn useClosed, documented

A phone pushes its location to rtirl.com with a push key; map and speed overlays read it with a pull key.

Made by
Muxable
Licence
MIT (@rtirl/api client); the service is closed

Described at github.com/muxable/rtirl-obsChecked 14 November 2026 Suggest an edit to RealtimeIRL location API

The pull side and the client library are documented; the push call appears only in the apps' code.

Sources

RealtimeIRL overlays README · Moblin RealtimeIRL settings

DJI camera Bluetooth control 

ProtocolIn useClosed, documented

Bluetooth commands to an Osmo camera, which IRL apps use to start the camera's own RTMP live stream.

Made by
DJI
Used by
Moblin, dji-remote

Described at github.com/dji-sdk/Osmo-GPS-Controller-DemoChecked 14 November 2026 Suggest an edit to DJI camera Bluetooth control

DJI documents the protocol for recording, modes and GPS. The live-stream setup is Moblin's own work, which dji-remote ported; the video itself is plain RTMP. The licence of DJI's demo repository is unclear.

Sources

DJI Osmo GPS controller demo · Moblin README · dji-remote README

App formats 

One app's own format that a second app also reads or writes. Both are named.

All 5 entries, with details

Moblin settings export 

Setup link or fileIn useNo written spec

Moblin's full backup of streams, scenes, widgets and presets, which another tool can read to check a setup.

Made by
eerimoq (Moblin)
Licence
MIT (code)
Also used by
IRLhosting

Described at github.com/eerimoq/moblinChecked 14 November 2026 Suggest an edit to Moblin settings export

Moblin's internal settings JSON; it can change with any release. Scenes, widgets and presets live inside it, with no separate format of their own.

Sources

Moblin README · IRLhosting Moblin settings viewer

Larix Grove (larix://set/v1) 

Setup link or fileIn useClosed, documented

A link or QR code that loads connections and encoder settings into Larix Broadcaster, and also into IRL Pro.

Made by
Softvelum

Described at softvelum.com/larix/groveChecked 14 November 2026 Suggest an edit to Larix Grove (larix://set/v1)

IRL Pro reading it is stated by IRLhosting and IRLToolkit, not on IRL Pro's own pages.

Sources

Larix Grove · IRLhosting setup QR code

Hardware and codecs 

How the picture and sound get compressed, and the cables a camera's picture comes in on.

All 8 entries, with details

H.264 / AVC 

CodecIn useOpen

The video codec every streaming app, box and platform handles; the safe default.

Made by
ITU-T and ISO/IEC MPEG (Joint Video Team)
Licence
Patent pool run by Via LA. Its page says royalties are spread across the value chain, with thresholds below which some aren't charged.
Used by
Moblin, BELABOX, OBS Studio, SimpleStreamer, Twitch, YouTube, Kick

Described at itu.int/rec/T-REC-H.264Checked 15 November 2026 Suggest an edit to H.264 / AVC

Also called AVC or MPEG-4 Part 10. Support in the listed products follows their services.json entries and READMEs.

Sources

ITU-T H.264 · Moblin README · belacoder README

HEVC / H.265 

CodecIn useOpen

The successor to H.264: a sharper picture at the same bitrate, which helps on weak mobile links.

Made by
ITU-T and ISO/IEC MPEG (JCT-VC)
Licence
Patent pools run by Access Advance (HEVC Advance) and Via LA (HEVC/VVC). Via LA's licence covers devices; Access Advance lists devices, software and content on physical media.

Described at itu.int/rec/T-REC-H.265Checked 15 November 2026 Suggest an edit to HEVC / H.265

Support in the listed products follows their services.json entries and makers' pages.

Sources

ITU-T H.265 · Moblin README · belacoder README · CeraLive site · LiveU Solo product page · Haivision Pro product page

AV1 

CodecIn useOpen

An open, royalty-free video codec from AOMedia, newer than HEVC; hardware encoders are still rare on IRL gear.

Made by
Alliance for Open Media (AOMedia)
Licence
AOMedia members license their AV1 patents royalty-free (AOMedia Patent License 1.0). Sisvel separately runs a royalty-bearing AV1 pool for consumer products.
Used by
OBS Studio, YouTube, FFmpeg

Described at aomedia.org/specifications/av1Checked 15 November 2026 Suggest an edit to AV1

OBS and FFmpeg follow Veovera's Enhanced RTMP adoption list, which carries AV1 over RTMP.

Sources

AOMedia: AV1 · YouTube Help: live encoder settings · Enhanced RTMP v2 spec

AAC (Advanced Audio Coding) 

CodecIn useOpen

The usual audio codec for RTMP streams and most platforms.

Made by
ISO/IEC MPEG
Licence
Via LA licenses AAC patents to makers of encoder and decoder products. It says no fees are due for broadcasting or streaming AAC.
Used by
OBS Studio, YouTube, FFmpeg

Described at mpeg.org/standards/MPEG-4/…Checked 15 November 2026 Suggest an edit to AAC (Advanced Audio Coding)

Part of MPEG-4 Audio (ISO/IEC 14496-3). Android phones encode AAC-LC as part of the platform.

Sources

MPEG-4 Audio (ISO/IEC 14496-3) · YouTube Help: live encoder settings · Android: supported media formats

Opus 

CodecIn useOpen

An open, royalty-free audio codec, used by WebRTC (WHIP) and Enhanced RTMP.

Made by
IETF (codec from Xiph.Org and Skype)
Licence
Royalty-free patent licences from Xiph.Org, Broadcom and Microsoft; BSD-licensed code in RFC 6716. Some other companies have disclosed patents with possibly royalty-bearing terms, the Opus site says.
Used by
OBS Studio, FFmpeg

Described at opus-codec.orgChecked 15 November 2026 Suggest an edit to Opus

Every WebRTC endpoint, and so every WHIP sender and receiver, must support Opus (RFC 7874). OBS and FFmpeg follow Veovera's Enhanced RTMP adoption list.

Sources

RFC 6716 · Opus licence page · RFC 7874 (WebRTC audio) · Enhanced RTMP v2 spec

UVC (USB Video Class) 

Hardware interfaceIn useOpen

The standard way a USB camera or HDMI capture stick shows up as a camera, with no driver to install.

Made by
USB Implementers Forum (USB-IF)
Licence
USB-IF specification, downloadable from usb.org

Described at usb.org/document-library/video-class-v15-document-setChecked 15 November 2026 Suggest an edit to UVC (USB Video Class)

Moblin supports UVC cameras on iPad; support in the Android apps and the mixer follows their services.json entries.

Sources

USB-IF: Video Class v1.5 document set · Moblin README

HDMI 

Hardware interfaceIn useClosed, documented

The camera's video-out cable; IRL boxes take it in directly or through a USB capture stick.

Made by
HDMI Forum; licensed by HDMI Licensing Administrator (HDMI LA)
Licence
Licensed to adopters by HDMI LA, with adopter and licensing fees

Described at hdmi.orgChecked 15 November 2026 Suggest an edit to HDMI

The specification is available to adopters; HDMI LA's public page names adopter and licensing fees but no amounts.

Sources

HDMI LA: adopter information · belacoder README · CeraLive site · LiveU Solo product page · Haivision Pro product page · YoloBox Ultra product page

SDI (Serial Digital Interface) 

Hardware interfaceIn useOpen

The locking broadcast video cable on pro cameras; some bonded encoders take it in.

Made by
SMPTE
Licence
SMPTE standards (ST 259, ST 292 and later), freely accessible from SMPTE

Described at smpte.org/standards/overviewChecked 15 November 2026 Suggest an edit to SDI (Serial Digital Interface)

SMPTE says its standards library is freely accessible; HD-SDI and 3G/12G-SDI are later versions.

Sources

SMPTE standards overview · LiveU Solo product page · Haivision Pro product page

From IRL Commons 

Drafts IRL Commons started. They are listed apart, so nobody takes them for standards already in use. See the drafts.

All 3 entries, with details

irl-commons 

DataProposedOpen

Small curated datasets about IRL streaming: words, quick checks, services, guides and standards, with Zod and JSON Schema validation.

Made by
IRL Commons contributors
Licence
CC BY 4.0 (data); MIT (code)
Used by
None named yet

Described at github.com/irl-commons/irl-commonsChecked 15 November 2026 Suggest an edit to irl-commons

A v0 catalogue. No outside users are named yet, and the npm package is not published.

Sources

irl-commons README

Codecs compared 

Video first, then sound. Hardware is what the chip or platform maker lists; a phone app may still fall back to software.

H.264 / AVC, HEVC / H.265, AV1, AAC and Opus, side by side: licence and royalties, how much data they need for the same quality, which chips encode and decode them, and which platforms take them.

Show the table
CodecLicence and royaltiesEfficiencyHardware encodeHardware decodeTwitchYouTubeKick
H.264 / AVCPatent pools Patent pool run by Via LA. Its page says royalties are spread across the value chain, with thresholds below which some aren't charged. [1]The baseline: HEVC / H.265 and AV1 compare with it.Yes [8]Yes [9]Yes [10]
HEVC / H.265Patent pools Patent pools run by Access Advance (HEVC Advance) and Via LA (HEVC/VVC). Via LA's licence covers devices; Access Advance lists devices, software and content on physical media. [11]About half the bitrate of H.264 for the same picture, says ITU-T (2013). [12]Some [18] UYes [19]No [20]
AV1Royalty-free AOMedia members license their AV1 patents royalty-free (AOMedia Patent License 1.0). Sisvel separately runs a royalty-bearing AV1 pool for consumer products. [21]50.3% fewer bits than x264 main profile and 46.2% fewer than x264 high profile at the same quality (BD-rate), in Facebook's 2018 test of 400 videos. [22]Some [29] UYes [30]No [31]
AACPatent pools Via LA licenses AAC patents to makers of encoder and decoder products. It says no fees are due for broadcasting or streaming AAC. [32]The baseline: Opus compares with it.Not listed for audio.Not listed for audio.Yes [33] UYes [34]Unknown [35] U
OpusRoyalty-free Royalty-free patent licences from Xiph.Org, Broadcom and Microsoft; BSD-licensed code in RFC 6716. Some other companies have disclosed patents with possibly royalty-bearing terms, the Opus site says. [36]Rated above HE-AAC at 64 kb/s and above LC-AAC at 96 kb/s in HydrogenAudio's public listening tests on stereo music, linked from opus-codec.org. [37]Not listed for audio.Not listed for audio.Unknown [38] UNo [39]Unknown [40] U
Sources for this table (40 notes)
  1. Sources: Via LA: AVC/H.264 licence Checked 15 November 2026
  2. Not confirmed by the makers' or platforms' own pages. Apple's own docs read here name HEVC, not H.264; iPhones still record and stream H.264. Sources: Apple Support: HEIF and HEVC on Apple devices Checked 15 November 2026
  3. Not confirmed by the makers' or platforms' own pages. Android lists an H.264 encoder (Main profile from Android 6) and decoder. Whether it runs in hardware depends on the phone. Sources: Android: supported media formats Checked 15 November 2026
  4. Encode up to 8K at 30 fps, decode up to 8K at 60 fps. Sources: Rockchip RK3588 product page Checked 15 November 2026
  5. Decode and encode from Broadwell (5th gen Core) in Intel's media driver. Sources: Intel media-driver: decoding/encoding features Checked 15 November 2026
  6. NVENC and NVDEC from the first Maxwell GPUs. Sources: NVIDIA video encode and decode support matrix Checked 15 November 2026
  7. Apple's media engine accelerates H.264 (stated for M3 chips). Sources: Apple Newsroom: M3 chips Checked 15 November 2026
  8. Yes. Twitch's help pages need JavaScript; this follows OBS's services.json, which lists H.264 for Twitch. Sources: OBS services.json (Twitch, YouTube entries) Checked 15 November 2026
  9. Yes, over RTMP/RTMPS and HLS. Sources: YouTube Help: live encoder settings · YouTube Help: set up an HLS stream Checked 15 November 2026
  10. Yes; Kick says it supports only H.264 (x264). Sources: Kick Help: how to stream on Kick Checked 15 November 2026
  11. Sources: Access Advance: HEVC Advance pool · Via LA: HEVC/VVC licence Checked 15 November 2026
  12. Sources: ITU press release, 25 Jan 2013 Checked 15 November 2026
  13. iPhone 7 and later record HEVC, says Apple; older devices play it with limits. Sources: Apple Support: HEIF and HEVC on Apple devices Checked 15 November 2026
  14. Not confirmed by the makers' or platforms' own pages. Android lists an HEVC decoder from Android 5 but no platform encoder; encoding depends on the phone. Sources: Android: supported media formats Checked 15 November 2026
  15. Decode and encode from Skylake (6th gen Core) in Intel's media driver. Sources: Intel media-driver: decoding/encoding features Checked 15 November 2026
  16. Encode from Pascal GPUs, decode from second-generation Maxwell. Sources: NVIDIA video encode and decode support matrix Checked 15 November 2026
  17. Apple's media engine accelerates HEVC (stated for M3 chips). Sources: Apple Newsroom: M3 chips Checked 15 November 2026
  18. Not confirmed by the makers' or platforms' own pages. Not for a normal stream: Twitch's help pages need JavaScript; this follows OBS's services.json, which lists only H.264. Twitch said in 2024 its Enhanced Broadcasting beta was experimenting with HEVC. Sources: OBS services.json (Twitch, YouTube entries) · Twitch blog: Enhanced Broadcasting beta (8 Jan 2024) Checked 15 November 2026
  19. Yes, over RTMP/RTMPS and HLS; HDR needs HEVC. Sources: YouTube Help: live encoder settings · YouTube Help: set up an HLS stream Checked 15 November 2026
  20. No; Kick says it doesn't support H.265. Sources: Kick Help: how to stream on Kick · Kick Help: OBS or Streamlabs not connecting Checked 15 November 2026
  21. Sources: AOMedia Patent License 1.0 · Sisvel: AV1 patent pool Checked 15 November 2026
  22. Sources: Facebook Engineering, 10 Apr 2018 Checked 15 November 2026
  23. Not confirmed by the makers' or platforms' own pages. A17 Pro (iPhone 15 Pro) and later have an AV1 decoder; Apple names no AV1 encoder. Sources: Apple Newsroom: iPhone 15 Pro (A17 Pro) Checked 15 November 2026
  24. Not confirmed by the makers' or platforms' own pages. Android 14 makes an AV1 encoder and decoder mandatory; they may run in software. Sources: Android: supported media formats Checked 15 November 2026
  25. Decodes AV1 up to 8K at 60 fps; Rockchip lists only H.264 and H.265 encoders. Sources: Rockchip RK3588 product page Checked 15 November 2026
  26. Decode from Tiger Lake (11th gen Core); encode on Arc (DG2) and Meteor Lake and later. Sources: Intel media-driver: decoding/encoding features Checked 15 November 2026
  27. Decode from Ampere (RTX 30); encode from Ada Lovelace (RTX 40). Sources: NVIDIA video encode and decode support matrix Checked 15 November 2026
  28. Not confirmed by the makers' or platforms' own pages. M3 chips and later decode AV1; Apple names no AV1 encoder. Sources: Apple Newsroom: M3 chips Checked 15 November 2026
  29. Not confirmed by the makers' or platforms' own pages. Not for a normal stream: Twitch's help pages need JavaScript; this follows OBS's services.json, which lists only H.264. Twitch said in 2024 its Enhanced Broadcasting beta was experimenting with AV1. Sources: OBS services.json (Twitch, YouTube entries) · Twitch blog: Enhanced Broadcasting beta (8 Jan 2024) Checked 15 November 2026
  30. Yes, over RTMP/RTMPS; not for HDR. Sources: YouTube Help: live encoder settings Checked 15 November 2026
  31. No; Kick says it supports only H.264. Sources: Kick Help: how to stream on Kick Checked 15 November 2026
  32. Sources: Via LA: AAC licence Checked 15 November 2026
  33. Not confirmed by the makers' or platforms' own pages. Most likely yes; Twitch's help pages need JavaScript; this follows OBS's services.json, which names no audio codec for Twitch. Sources: OBS services.json (Twitch, YouTube entries) Checked 15 November 2026
  34. Yes; YouTube asks for AAC or MP3, and 5.1 sound only with AAC over RTMP/RTMPS. Sources: YouTube Help: live encoder settings Checked 15 November 2026
  35. Not confirmed by the makers' or platforms' own pages. Kick's help asks for stereo at up to 48 kHz but names no audio codec. Sources: Kick Help: how to stream on Kick Checked 15 November 2026
  36. Sources: Opus licence page Checked 15 November 2026
  37. Sources: Opus comparison page Checked 15 November 2026
  38. Not confirmed by the makers' or platforms' own pages. Twitch's help pages need JavaScript; this follows OBS's services.json, which names no audio codec for Twitch. Sources: OBS services.json (Twitch, YouTube entries) Checked 15 November 2026
  39. Not listed; YouTube asks for AAC or MP3. Sources: YouTube Help: live encoder settings Checked 15 November 2026
  40. Not confirmed by the makers' or platforms' own pages. Kick's help names no audio codec. Sources: Kick Help: how to stream on Kick Checked 15 November 2026

Ways to send a stream compared 

How each protocol gets a stream from the phone or box to the next step. Where a platform doesn't take one, a receiver or production service turns it into RTMP.

SRT, SRTLA, Moblink, RIST, NDI, WHIP and Enhanced RTMP, side by side: whether they can be bonded, licence, delay, how they recover lost packets, and which platforms take them.

Show the table
ProtocolCan be bondedFree to use or licenceLatencyLoss recoveryTwitchYouTubeKick
SRTBuilt in libsrt socket groups send over several links at once (broadcast) or switch to a backup; balancing is still under development. [1]Open code Open source, MPL-2.0 (libsrt). [2]Buffer you set A receive buffer you set (latency, 120 ms by default) that decides how long missing packets may take. [3]Resends and FEC Resends lost packets (ARQ); forward error correction (FEC) can be added. [4]No [5]No [6]No [7]
SRTLABuilt in It is the bonding: one SRT stream spread over several links, balanced by how each link is doing. [8]Open code AGPL-3.0 reference code from BELABOX; no separate spec. [8]Buffer you set SRT's buffer you set; it also covers packets arriving out of order from different links. [8]Resends SRT's own resends, which srtla also uses to balance the links. [8]No [5]No [6]No [7]
MoblinkAdd-on Spare phones become extra SRTLA bonding links. [9]Open code MIT code; no written spec. [9]Buffer you set The SRT buffer of the stream it carries. [9]Resends The SRT resends of the stream it carries. [9]No [5]No [6]No [7]
RISTBuilt in The Main Profile supports several links, load-balanced or redundant (librist). [10]Open spec VSF TR-06 specifications; librist under BSD-2-Clause. [11]Buffer you set A receive buffer you set, from 50 ms to 30 seconds in librist. [10]Resends Resends lost packets (ARQ). [10]No [5]No [6]No [7]
NDINo No bonding of internet links; NDI 4's multipath TCP spreads one stream over several network cards. [12]Proprietary Proprietary SDK from Vizrt NDI AB, offered under NDI's own terms. [13]Real-time NDI's docs describe Reliable UDP as low latency, with minimal delay. [12]Resends and FEC Reliable UDP (the NDI 5 default) asks for lost packets again; a UDP mode with FEC also exists. [12]No [5]No [6]No [7]
WHIPNo RFC 9725 sets up one WebRTC session. [14]Open spec IETF standard, RFC 9725. [14]Real-time Real-time by design: WebRTC aims for the lowest possible latency. [14]Resends WebRTC's NACK and RTP retransmission (RFC 8834). [15]No [5]No [6]No [7]
Enhanced RTMPNo RTMP runs over a single TCP connection. [16]Open spec Open spec under Apache-2.0 from Veovera. [17]Follows TCP No buffer to set; it rides on TCP, which waits for its own resends. [16]TCP resends TCP resends lost data; E-RTMP adds a reconnect request from the server. [16]Some [18] UYes [19]Some [20]
Sources for this table (20 notes)
  1. Sources: libsrt socket groups Checked 15 November 2026
  2. Sources: libsrt repository Checked 15 November 2026
  3. Sources: libsrt socket options: SRTO_LATENCY Checked 15 November 2026
  4. Sources: libsrt README Checked 15 November 2026
  5. Not listed; Twitch's help pages need JavaScript; this follows OBS's services.json, whose Twitch servers are all rtmp:// addresses. Sources: OBS services.json (Twitch, YouTube entries) Checked 15 November 2026
  6. Not listed; YouTube takes RTMP/RTMPS and HLS. Sources: YouTube Help: live encoder settings · YouTube Help: set up an HLS stream Checked 15 November 2026
  7. Not listed; Kick's help gives an RTMPS address. Sources: Kick Help: how to stream on Kick Checked 15 November 2026
  8. Sources: BELABOX srtla README Checked 15 November 2026
  9. Sources: Moblink README Checked 15 November 2026
  10. Sources: librist README Checked 15 November 2026
  11. Sources: VSF technical recommendations (TR-06) · librist README Checked 15 November 2026
  12. Sources: NDI docs: NDI protocols Checked 15 November 2026
  13. Sources: NDI SDK page Checked 15 November 2026
  14. Sources: RFC 9725 (WHIP) Checked 15 November 2026
  15. Sources: RFC 8834, section 6.1 (WebRTC NACK and retransmission) Checked 15 November 2026
  16. Sources: Enhanced RTMP v2 spec Checked 15 November 2026
  17. Sources: Enhanced RTMP repository Checked 15 November 2026
  18. Not confirmed by the makers' or platforms' own pages. Plain RTMP, yes (Twitch's help pages need JavaScript; this follows OBS's services.json). Veovera lists Twitch as an adopter, through Enhanced Broadcasting. Sources: OBS services.json (Twitch, YouTube entries) · Enhanced RTMP repository Checked 15 November 2026
  19. Yes: RTMP/RTMPS, with HEVC and AV1 as well as H.264. Sources: YouTube Help: live encoder settings Checked 15 November 2026
  20. RTMPS with H.264 only, so plain RTMP but none of the newer codecs. Sources: Kick Help: how to stream on Kick Checked 15 November 2026

Building blocks 

Protocol implementations, libraries and general media servers that apps and receivers are built from. For developers and self-hosters; streamers find the finished apps on How to IRL.

Missing an app, a service or a guide? The lists on this site are open data in irl-commons. Suggest it there, or see Open data.