# AlexxIT/go2rtc

Ultimate camera streaming application

Repository: https://github.com/AlexxIT/go2rtc
Canonical: https://ross.abutalabs.com/products/go2rtc
Homepage: https://go2rtc.org
Language: Go
License: MIT
License Family: permissive
Topics: ffmpeg, hassio, home-assistant, rtmp, rtsp, webrtc, streaming, webcam-streaming, hls, mjpeg, homekit, media-server, rtsp-server, mp4, xiaomi, wyze, onvif, tapo, go, golang
Last push: 2026-07-13T10:54:06+00:00

## Health v2 (maintenance only)
Score: 84/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 92, release rhythm 66, longevity 100
- inputs: {"age_days": 1476, "days_push": 51, "days_rel": 226, "gap_med": 28, "n_releases_24m": 10}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 14050, forks 1282 (observed 2026-08-28T04:11:05.394438+00:00)

## What it is
go2rtc is a zero-dependency camera streaming application and media server written in Go that supports dozens of streaming formats and protocols (WebRTC, RTSP, RTMP, HLS, MJPEG, MP4) with zero-delay streaming. It can run standalone, in Docker, or as a Home Assistant add-on/integration, and offers two-way audio, on-the-fly FFmpeg transcoding, and stream publishing to services like YouTube and Telegram.

## Use cases
- view ip camera streams in a browser with low latency
- convert rtsp camera streams to webrtc
- restream a webcam to youtube or telegram
- add two-way audio to home assistant cameras
- self-host a media server for security cameras
- stream wyze or tapo cameras into home assistant
- mix audio and video tracks from multiple sources into one stream

## When to choose
- you need low-latency browser viewing of RTSP/IP cameras
- you use Home Assistant and want native camera integration
- you need protocol conversion between RTSP, WebRTC, HLS, RTMP, and MJPEG
- you want a single small binary with no dependencies
- you need two-way audio with cameras

## When to avoid
- you need heavy always-on transcoding pipelines rather than on-the-fly codec negotiation
- you need a full NVR with recording schedules and motion detection
- you need a GUI-first video editor or player
- you need VOD/OTT platform features like DRM or adaptive bitrate ladders

## Facets
- artifact type: application
- maturity: active
- function: video-processing, streaming, http-server, websocket, audio-processing, self-hosted
- domain: media, self-hosted, iot
- platform: windows, bsd, self-hosted, go, cross-platform
- tags: webrtc, rtsp, rtmp, hls, mjpeg, home-assistant, onvif, ip-camera, media-server, two-way-audio, ffmpeg, homekit, video, audio, linux, macos, docker

## Member repositories
- AlexxIT/go2rtc (main) score 84

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:05.394438+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:12:50.931082+00:00, confidence not recorded.
  - readme: https://github.com/AlexxIT/go2rtc (fetched 2026-08-28T04:11:05.394438+00:00, sha c276a7dbfc41)
  - homepage: https://go2rtc.org (fetched 2026-08-29T08:06:38.577068+00:00, sha 21fddce07e45)
- Data as of 2026-08-30T08:39:29.467469+00:00.