Adaptive
MoQ supports the entire latency spectrum. Simultaneously support real-time, interactive, or lean-back experiences with a unified stack.
Skip to content
Scalable
All content can be cached and fanned-out via a CDN. Serve millions of concurrent viewers across the globe, including via Cloudflare.
Extensible
Supports contribution, distribution, conferencing, and whatever you can dream up. Extend the protocol with custom tracks for any live content.
Modern Web
Utilizes WebTransport, WebCodecs, and WebAudio APIs for modern browser support without hacks.
Cross-Platform
Libraries for Rust (native) and TypeScript (web), plus FFI bindings for C, Python, Kotlin, Swift, and Go. Integrations with ffmpeg, OBS, GStreamer, and more to come.
Efficient
Save resources by only encoding or transmitting data when needed. Built on top of production-ready QUIC libraries.
Secure
Encrypted via TLS and authenticated via JWT. You can optionally self-host a private CDN or end-to-end encrypt your content.
Backwards Compatible
Supports CMAF and HLS for legacy device support. Migrate legacy devices at your own pace.
Decentralized
Host your own CDN, use a 3rd party service, and/or connect P2P via Iroh (native only). Broadcasts are automatically discovered and gossiped.
What is MoQ?
Media over QUIC (MoQ) is a next-generation live media protocol. As the name implies, we use QUIC to concurrently transmit media and avoid latency build-up during congestion. The protocol is being standardized by the IETF and backed by some of the largest tech companies: Google, Cisco, Akamai, Cloudflare, etc.
moq.dev is an open source implementation written in Rust (native) and Typescript (web). We support compatibility with the official IETF drafts, but the main focus is a subset called moq-lite and hang. The idea is to build first, argue later.
See the concepts page for a breakdown of the layering, rationale, and comparison to other protocols.
Setup
Get up and running in seconds with Nix (+Flakes), or be lame and install stuff manually:
bash
# Runs a relay, media publisher, and the web server
nix develop -c justIf everything works, a browser window will pop up demoing how to both publish and watch content via the web.
- Keep reading the development guide to run more advanced demos.
- Skip ahead to the production guide to see what it takes to deploy this bad boy.
Applications
There are a bunch of MoQ binaries and plugins.
Some highlights:
- moq-relay - A server connecting publishers to subscribers, able to form a self-hosted CDN cluster.
- moq-cli - A CLI that can import and publish MoQ broadcasts from a variety of formats (fMP4, HLS, MPEG-TS, FLV, etc), including via ffmpeg.
- obs - An OBS plugin, able to publish a MoQ broadcast and/or use MoQ broadcasts as sources.
- gstreamer - A gstreamer plugin, split into a source and a sink.
- web - A web component you can slap on your website to watch and publish MoQ broadcasts.
- ...and more
Rust Crates 🦀
Integrate MoQ into your application without fear. Focused on native but has token WASM support.
Some highlights:
- moq-net - Real-time pub/sub with built-in caching, fan-out, and prioritization.
- moq-mux - Media muxers/demuxers for fMP4, CMAF, MPEG-TS, and FLV.
- libmoq - C bindings for the above, no finagling Rust into your build system.
- web-transport - A suite of crates required to get QUIC access in the browser, plus some polyfills.
- ...and more
TypeScript Packages
Run MoQ in a web browser utilizing the latest Web tech. Or run on native with polyfills via Node/Bun/Deno.
Some highlights:
- @moq/net - Real-time pub/sub with built-in caching, fan-out, and prioritization.
- @moq/hang - Performs any media stuff: capture, encode, transmux, decode, render.
- @moq/watch - Subscribe to and render MoQ broadcasts.
- @moq/publish - Publish media to MoQ broadcasts.
- ...and more
Other Languages
FFI bindings around the Rust core, with idiomatic APIs in each language: