ffmpeg-whip

Publishes live WebRTC streams to WHIP ingest endpoints via FFmpeg whip muxer.

15|4|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/damionrashford/media-os --skill ffmpeg-whip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ffmpeg-whip
Source: https://github.com/damionrashford/media-os/tree/main/skills/ffmpeg-whip
Command: npx skills add https://github.com/damionrashford/media-os --skill ffmpeg-whip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Publish live WebRTC streams to WHIP ingest endpoints using FFmpeg, enabling browser-ready, sub-second broadcasts without RTMP/HLS delays.

Core Features & Use Cases

  • WebRTC egress via FFmpeg whip muxer (FFmpeg 7.0+).
  • Low-latency delivery to WHIP endpoints (Cloudflare Stream, Mux, Millicast, MediaMTX, etc.).
  • Preconfigured encoder constraints (H.264 baseline/main, Opus audio) and ICE/STUN handling.
  • Flexible publish options: file or screen capture, with adjustable bitrate, resolution, and audio settings.
  • Suitable for browser-based playback using WHEP and live streaming workflows.

Quick Start

Publish a live WebRTC stream to a WHIP endpoint using FFmpeg with the whip muxer and baseline H.264 + Opus.

Frequently Asked Questions about ffmpeg-whip

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish a live WebRTC stream to a WHIP endpoint using FFmpeg?

Publish live WebRTC streams to WHIP endpoints using FFmpeg's whip muxer with H.264 baseline/main video and Opus audio at 48000 Hz. This enables sub-second, browser-ready delivery to Cloudflare Stream, Mux, Millicast, and similar WHIP-compatible platforms.

What FFmpeg version is required for WebRTC WHIP publishing?

WebRTC WHIP publishing requires FFmpeg 7.0 or higher with the whip muxer compiled in. You also need proper ICE/STUN handling, a fixed GOP size, and H.264 baseline or main profile encoding constraints for browser compatibility.

Can I use FFmpeg WHIP with Cloudflare Stream, Mux, or Millicast?

Yes, FFmpeg WHIP supports sub-second WebRTC delivery to Cloudflare Stream, Mux, Millicast, MediaMTX, and other WHIP-compatible ingest endpoints. It replaces RTMP/HLS workflows to achieve browser-ready, low-latency live streaming.

What audio and video codecs work with FFmpeg WebRTC WHIP streaming?

FFmpeg WebRTC WHIP streaming requires H.264 baseline or main profile for video and Opus audio at 48000 Hz. A fixed GOP is mandatory for browser playback, with adjustable bitrate, resolution, and audio settings available.

Does FFmpeg WHIP support screen capture and file inputs for live broadcasting?

Yes, FFmpeg WHIP supports flexible publish options including screen capture and file inputs for live broadcasting. You can adjust bitrate, resolution, and audio settings while maintaining sub-second WebRTC delivery to your target endpoint.

Why use WHIP instead of RTMP for low-latency live streaming?

WHIP enables sub-second, browser-ready WebRTC delivery, eliminating the high latency associated with RTMP and HLS workflows. FFmpeg's whip muxer provides direct WebRTC egress to compatible ingest endpoints, ensuring immediate browser-based playback via WHEP.