bluenviron/mediamtx

Ready-to-use Media-over-QUIC / SRT / WebRTC / RTSP / RTMP / LL-HLS / MPEG-TS / RTP live media server and media proxy that allows to read, publish, proxy,...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 20 minutes ago
Added to GitGenius on September 2nd, 2026
Created on December 28th, 2019
Open Issues & Pull Requests: 190 (+0)
GitHub issues: Enabled
Number of forks: 2,365
Total Stargazers: 20,052 (+0)
Total Subscribers: 193 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

MediaMTX is a live media server and media proxy that enables publishing, reading, proxying, recording, and playback of real-time video and audio streams across multiple protocols.

The tool solves the problem of routing media streams between different sources and destinations while supporting protocol conversion. It acts as a central hub that accepts streams via Media-over-QUIC, SRT, WebRTC, RTSP, RTMP, HLS, MPEG-TS, and RTP from sources like FFmpeg, GStreamer, OBS Studio, and browser clients, then automatically converts and forwards them to consumers using any of these same protocols. The server handles multiple simultaneous streams on separate paths, supports hot reloading of configuration without disconnecting clients, and can serve always-available streams even when publishers go offline.

Adoption suits projects requiring a unified streaming infrastructure that bridges incompatible protocols without external dependencies. The tool is particularly valuable for setups involving broadcast ingestion, multi-protocol distribution, or stream recording and playback. It runs as a single executable on Linux, Windows, and macOS with no runtime dependencies.

Development activity shows consistent engagement with protocol support expansion and infrastructure refinement. The project maintains active issue triage and responds to user reports. Pull requests receive review and integration, indicating ongoing maintenance of the codebase. Documentation is kept current alongside feature additions, reflecting attention to user onboarding and reference material.