go2rtc

A lightweight, zero-dependency video streaming server that ingests live camera feeds from RTSP, WebRTC, HomeKit, USB, and other sources and redistributes them…

  • Home Automation
  • Media Servers
  • Tools & Utilities
A lightweight, zero-dependency video streaming server that ingests live camera feeds from RTSP, WebRTC, HomeKit, USB, and other sources and redistributes them as low-latency RTSP, WebRTC, or MJPEG streams for home automation and surveillance use cases.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
77last commit 27 days ago
Popular
8314,554 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM
Security check
09 serious findings, 6 minor, CI, tests

Availability: platform listings confirmed today, links checked 7 days ago

GitHub stars
14,554
Open issues
1040
Last commit
2026-10-25
Latest release
v1.9.15
License
MIT
Activity
rising

Checked 20 days ago - source: GitHub (AlexxIT/go2rtc)

Resources & Compatibility

Minimum requirements: 2 GB RAM. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add your camera streams before starting In your go2rtc streams configuration, add each camera with its protocol, username, password, and address, for example an ONVIF camera: onvif://admin:[email protected]. Without these entries, go2rtc starts but has no cameras to show. source
  • Open the ports you plan to use By default go2rtc listens on port 1984 for its API (the app's control endpoint), 8554 for RTSP (a common live-video protocol), and 8555 for WebRTC (a browser/app video method). If you don't open the ports your apps need, cameras may work inside the server but won't appear in phones, Home Assistant, or other players. source
  • Import cameras from Home Assistant If your cameras are in Home Assistant, add the hass section and reference those cameras in streams; for another Home Assistant instance include its address and a long-lived token (a personal API key you create in Home Assistant). Without this, go2rtc can't import cameras that only exist in Home Assistant. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which ports do I need to open for go2rtc to work with phones, Home Assistant, or other players?

Open port 1984 for the API, 8554 for RTSP, and 8555 for WebRTC. If the needed ports are closed, cameras may work inside the server but not in phones, Home Assistant, or other players.

Why does go2rtc start but show no cameras?

You must add each camera in the streams configuration before starting go2rtc, including protocol, username, password, and address. Without these entries, go2rtc starts but has no cameras to show.

How do I import cameras that only exist in Home Assistant into go2rtc?

Add the Home Assistant section and reference those cameras in streams. For another Home Assistant instance, include its address and a long-lived token.

Answers sourced from deepwiki.com, deepwiki.com, deepwiki.com

Community

Collected 53 days ago - public community threads