Jump to a Category
Livestreaming has its own dense vocabulary, much of it inherited from broadcast engineering and network protocol design, and almost none of it explained anywhere a working creator would actually look. This glossary covers the terms that genuinely come up — in OBS settings, in platform error messages, in conversations with other streamers, in articles throughout this blog — organized into four practical categories rather than a flat alphabetical list, since understanding why a term exists in relation to its neighbors is often more useful than the definition alone.
46
Terms covered across four practical categories
4
Categories — protocol, encoding, platform delivery, and monetization/rights
Plain Language
Every definition includes why the term practically matters, not just what it means
Cross-Referenced
Linked to deeper guides elsewhere on this blog where a topic deserves fuller treatment
These terms describe the "plumbing" — the rules and methods that move your video data from wherever it's produced to the platform that broadcasts it.
R
RTMP Real-Time Messaging Protocol
The dominant method for sending live video from an encoder (like OBS) to a streaming platform, by breaking the stream into small chunks sent continuously over one persistent connection.
Why it matters: it's what your stream key and ingest URL actually use — see our full RTMP deep-dive for the complete mechanics.
R
RTMPS RTMP Secure
RTMP with TLS encryption added on top — the same data and structure as plain RTMP, but the connection itself is encrypted in transit.
Why it matters: protects your stream key and video data from being read if intercepted; use it whenever your platform offers it.
H
HLS HTTP Live Streaming
The method most platforms use to deliver a live stream out to viewers — breaking it into small downloadable segments served over standard web infrastructure.
Why it matters: it's the reason there's a delay between your "ingest" (RTMP) and what a viewer actually sees — HLS adds its own buffering for stability at scale.
S
SRT Secure Reliable Transport
A newer ingest protocol with built-in error correction over UDP, designed to handle unstable or long-distance network connections better than RTMP's reliance on raw TCP.
Why it matters: worth using instead of RTMP if your specific encoder and platform both support it and your connection is genuinely unreliable.
W
WebRTC Web Real-Time Communication
A browser-native protocol built for true sub-second latency, the same technology underlying video calls like Zoom and Google Meet.
Why it matters: the right choice for genuinely real-time interaction, but architecturally harder to scale to huge one-to-many audiences than RTMP-into-HLS.
I
Ingest
The process and endpoint of sending your live stream into a platform's servers — distinct from "delivery," which is how the platform then sends it back out to viewers.
Why it matters: "ingest URL" and "stream key" together are what your encoder needs to start broadcasting.
S
Stream Key
A unique credential, appended to your ingest URL, that authenticates your specific encoder connection as authorized to broadcast to your specific channel.
Why it matters: functions like a password — anyone with your stream key can broadcast as you; treat it as sensitive and regenerate it if ever exposed.
H
Handshake
The brief exchange of packets between your encoder and a server that confirms both sides are ready before any actual video data is sent.
Why it matters: when a stream "fails to connect" instantly, the handshake is usually where it's failing — often due to a wrong stream key.
T
TCP Transmission Control Protocol
The underlying network protocol that guarantees data arrives in order and without loss, retransmitting anything that doesn't make it the first time.
Why it matters: RTMP runs on top of TCP — this is why poor network conditions cause buffering rather than just dropped/glitchy frames.
U
UDP User Datagram Protocol
A network protocol that sends data without guaranteeing delivery or order — faster but less reliable than TCP by default, requiring its own error-handling if reliability matters.
Why it matters: SRT and WebRTC build their own reliability handling on top of UDP, trading TCP's automatic guarantees for lower latency.
M
Multistreaming
Sending the same live stream simultaneously to multiple platforms (YouTube, Twitch, Kick, etc.) at once, rather than broadcasting to just one.
Why it matters: typically requires either a relay service or enough local upload bandwidth to push multiple simultaneous RTMP connections.
F
Failover / Backup Stream
A redundant secondary stream or system that automatically takes over if the primary stream connection drops, minimizing visible downtime.
Why it matters: the single most important feature for genuine unattended 24/7 streaming — often gated behind expensive tiers on bundled platforms.
These terms govern the actual settings in OBS or any encoder — the choices that determine your stream's quality, file size, and compatibility.
B
Bitrate
The amount of data used to represent one second of video or audio, typically measured in kilobits per second (kbps) for streaming.
Why it matters: higher bitrate generally means better quality but requires more upload bandwidth — set too high for your connection and you'll see buffering or dropped frames.
K
Keyframe (I-Frame)
A complete, fully-detailed video frame that doesn't depend on any other frame to be decoded — unlike most frames, which only store what changed since the last frame.
Why it matters: platforms require a specific keyframe interval (usually every 2 seconds) to properly generate different quality levels for viewers.
G
GOP Group of Pictures
The set of frames between one keyframe and the next — essentially the structural unit defined by your keyframe interval setting.
Why it matters: a consistent GOP structure is what lets a platform seek, switch quality levels, or generate thumbnails reliably throughout your stream.
C
Codec
The specific algorithm used to compress (encode) and decompress (decode) video or audio — H.264 and AAC are the most common standards for streaming video and audio respectively.
Why it matters: platforms require specific codecs for ingest; using an unsupported one causes a stream to fail entirely rather than just look worse.
T
Transcoding
Converting video from one format, codec, or quality level to another — for example, a platform creating 1080p, 720p, and 480p versions of your single incoming stream.
Why it matters: this is how a single uploaded stream becomes available at multiple resolutions for viewers with different connection speeds.
R
Resolution
The pixel dimensions of your video — 1920×1080 ("1080p"), 1280×720 ("720p"), and similar standard sizes.
Why it matters: higher resolution requires proportionally higher bitrate to maintain visual quality, not just more pixels for free.
F
Frame Rate (FPS)
The number of individual frames displayed per second — 30fps and 60fps are the most common streaming standards.
Why it matters: fast motion (gaming, sports) benefits noticeably from 60fps; static or slow content rarely needs more than 30fps, and lower fps reduces processing/bandwidth demand.
C
CBR vs VBR Constant vs Variable Bitrate
CBR keeps bitrate fixed throughout the stream; VBR allows it to fluctuate based on scene complexity, using less data on simple scenes and more on complex ones.
Why it matters: most live streaming platforms specifically require CBR for stable, predictable delivery — VBR is more common for offline video encoding.
A
ABR Adaptive Bitrate Streaming
Automatically switching a viewer's stream quality up or down in real time based on their current network conditions, using the multiple transcoded quality levels a platform generates.
Why it matters: this is why a viewer's stream might briefly drop to a lower resolution rather than buffer entirely when their connection slows.
L
Latency
The total delay between something happening in front of your camera/microphone and a viewer actually seeing/hearing it.
Why it matters: typical RTMP-to-HLS latency runs 2-5+ seconds — normal and expected, not a sign of a problem, though it matters more for interactive content than pre-recorded loops.
B
Buffering
A player pausing playback to accumulate more data before continuing, usually because incoming data isn't arriving fast enough to play smoothly.
Why it matters: persistent buffering on the streaming side (not viewer side) usually points to insufficient upload bandwidth relative to your set bitrate.
E
Encoder
The software (OBS, Streamlabs) or hardware device that compresses raw camera/screen/audio input into a streamable format before sending it via RTMP or another protocol.
Why it matters: the encoder is where most of your actual stream-quality settings (bitrate, resolution, codec) are configured.
H
Hardware vs Software Encoding
Hardware encoding uses a dedicated chip (like NVENC on NVIDIA GPUs) to compress video; software encoding uses your CPU to do the same job.
Why it matters: hardware encoding is generally less demanding on system performance, making it the better default for most streaming setups, especially while gaming simultaneously.
Once your video arrives at a platform, an entirely separate set of systems and terminology governs how it actually reaches viewers and gets categorized.
C
CDN Content Delivery Network
A geographically distributed network of servers that caches and delivers content from a location physically close to each viewer, reducing load times and buffering.
Why it matters: this is how platforms serve millions of simultaneous viewers without every single one connecting to one distant central server.
V
VOD Video on Demand
Pre-recorded content available for on-demand playback, as opposed to a live broadcast — most platforms automatically convert a finished live stream into a VOD.
Why it matters: a 24/7 channel's archive segments often become individual VODs, which is also where Content ID scanning actually occurs.
D
DVR Digital Video Recorder
The ability for a viewer to pause, rewind, or seek backward within a currently live stream rather than only watching the live edge.
Why it matters: ultra-low-latency streaming modes sometimes disable or limit DVR functionality as a tradeoff for reduced delay.
S
Simulcast
Broadcasting the same live stream to multiple platforms or destinations at the same time — functionally synonymous with multistreaming in most streaming contexts.
Why it matters: often used interchangeably with "multistreaming" in platform documentation and marketing material.
A
API Application Programming Interface
A structured way for software to communicate with a platform programmatically — used to automate tasks like scheduling streams or pulling analytics without manual dashboard use.
Why it matters: many platforms gate full API access behind higher-priced tiers, limiting automation options for smaller creators.
U
Uptime
The percentage or duration of time a stream remains live and accessible without interruption.
Why it matters: the core metric that actually defines whether a 24/7 channel is succeeding at its basic job, independent of audience size.
R
Reconnection / Auto-Reconnect
A system's ability to automatically detect a dropped stream connection and re-establish it without manual intervention.
Why it matters: the speed of reconnection (measured in seconds) is one of the most important differentiators between streaming platforms for genuine unattended 24/7 use.
P
Playlist / Rotation
An ordered sequence of video files set to play one after another continuously, forming the actual content loop of a 24/7 channel.
Why it matters: how a rotation is structured (sequential, shuffled, time-of-day-aware) directly shapes viewer experience for any continuous channel.
E
Embed / Embeddable Player
A video player that can be placed directly on a third-party website (like your own), rather than requiring viewers to visit the streaming platform itself.
Why it matters: a key differentiator between bundled platforms offering CDN-hosted embedding and lighter delivery-focused tools that don't.
G
Geo-Restriction / Geo-Blocking
Limiting stream or content availability to specific countries or regions, often due to licensing or rights agreements.
Why it matters: relevant if your content licensing (particularly music) has territory-specific restrictions you need to account for.
S
Scheduling
Setting a stream to automatically begin (and sometimes end) at a predetermined future time, without requiring manual start.
Why it matters: different from genuine 24/7 looping — scheduling triggers a single future event, while continuous streaming requires the rotation to never actually end.
These terms matter for understanding both how your stream can earn money and what protects (or exposes) you legally while it runs.
C
Content ID
YouTube's automated system for detecting copyrighted material in uploaded or streamed content by matching audio/video fingerprints against a reference database.
Why it matters: it scans the archived recording of a stream, not the live broadcast in real time — see our music licensing guide for the full mechanics.
C
CC0 Creative Commons Zero
A public domain dedication where the creator waives all rights — content can be used commercially with no attribution required.
Why it matters: the safest, simplest license type for sourcing footage and music for a long-running monetized channel.
C
CC BY Creative Commons Attribution
A license permitting free commercial use, provided the original creator is credited in a specified way.
Why it matters: requires building attribution into your description template consistently — easy to forget on a long-running rotation.
R
Royalty-Free
A licensing model where you pay once (or nothing) rather than ongoing per-use fees — does NOT automatically mean unrestricted or license-free.
Why it matters: the single most commonly misunderstood licensing term in this entire industry — always read the actual specific terms.
S
Sample Clearance
The legal process of obtaining permission from a rights holder to use an excerpt of their existing recording or composition in a new work.
Why it matters: a major hidden risk specifically in sample-based genres like lofi, where a finished track can sound identical whether properly cleared or not.
I
Interpolation
Re-recording or re-performing a recognizable melody, chord progression, or rhythm from an existing composition, rather than sampling the literal original recording.
Why it matters: carries its own clearance requirement separate from sample clearance — re-playing isn't automatically safer than sampling.
M
Monetization Eligibility
The specific requirements (subscriber count, watch hours, content policy compliance) a channel must meet before a platform allows ad revenue or other monetization features.
Why it matters: requirements and thresholds vary by platform and change over time — verify current criteria directly rather than relying on outdated figures.
C
Cuepoint / Ad Cuepoint
A marked point in a stream where an advertisement can be inserted, ideally placed at a natural break to minimize viewer disruption.
Why it matters: some platforms offer automatic or assisted cuepoint placement as a paid feature specifically to optimize ad revenue timing.
P
Paywall
A feature requiring viewers to pay directly before accessing a stream or specific content, separate from platform-administered ad revenue.
Why it matters: a genuine differentiator between bundled hosting platforms (which often include this) and pure delivery-focused streaming tools (which typically don't).
A
Affiliate Marketing
Earning a commission by promoting another company's product or service through a tracked referral link.
Why it matters: often a stronger revenue driver than ad revenue alone for niches with clear viewer purchase intent, like fitness or pet/aquarium content.
F
Fair Use
A legal doctrine permitting limited use of copyrighted material without permission for purposes like commentary, criticism, or education — evaluated case by case, not a fixed checklist.
Why it matters: particularly relevant for news commentary content, where it has real limits and doesn't function as a guaranteed exemption.
This glossary covers the terms that come up across nearly every guide on this blog. For deeper treatment of specific topics — RTMP's full mechanics, music licensing and Content ID specifics, or live troubleshooting — the cross-referenced guides linked throughout cover each one in genuine depth rather than a one-paragraph summary.
None of these terms are difficult once explained plainly — the dense, acronym-heavy way they're usually presented is what makes streaming terminology feel more intimidating than the underlying concepts actually are. Keep this page bookmarked as a working reference rather than trying to memorize all 46 terms at once; most creators only need to genuinely understand the dozen or so terms relevant to whatever they're actually setting up or troubleshooting at a given moment.