HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
pion
webrtc
Go2018–2026
pion / webrtc

webrtc

Pure Go implementation of the WebRTC API

31Distinct people
113Mentions
1Explicit recommenders
16.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Pure Go implementation of the WebRTC API

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Hey HN, Tech demos don't get cooler then this one. You can control a Spot robot just using the browser. I am especially excited since it uses a Open Source library I work on…

Sean-Der used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year113 dated mentions

Observed mentions: 2018-06-20 16:21:31 UTC to 2026-09-14 17:34:31 UTC.

05101520252018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 25 mentions; 2 submissions, 23 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 22 mentions; 2 submissions, 20 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 11 mentions; 3 submissions, 8 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC927
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC1129
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC25223
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC22220
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC15312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC624
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC826
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC1138
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC615

What Hacker News says

15 sources
What latency are you trying to do? Will the professor being communicating with the students while doing this? Will the students all have the same bandwidth, or will you want multiple renditions (low, med, high quality levels)? If you want AV1 you will not be able to use RTMP. The protocol is orphaned/deprecated, so avoid if possible! If I was building it this is what I would do, and my reasoning. * For capture + encoding I would use OBS. You will want to use something that is easy for users to install configure. Professors will also have lots of custom requirements when it comes to layout etc... it will be tempting to do a ffmpeg command directly, but it will fall apart quick I believe. * To get AV1 out of OBS I would use FFMPEG output. I would have it send RTP. RTP is used to carry video in a sub-second manner. This is the same protocol
Read the rest
that WebRTC uses. You know have AV1 + low latency. * Then for users to watch I would use WebRTC. That will allow them to watch in their web browser. Conceptually it will be like this https://github.com/pion/webrtc/tree/master/examples/rtp-to-w... this takes the RTP packets and puts them in the browser. Lots of great projects exist that you could use for 'RTP -> WebRTC' like https://galene.org/ and https://livekit.io/ I would suggest checking them all out! If you have more questions/want to talk to people in the video space always happy to chat on https://pion.ly/slack :)
In Ask HN: FFmpeg real-time desktop streaming
This is something I have been lightly involved with recently and so excited to see it launch! Before the only supported protocol was RTMP(S). Using WebRTC brings lots of great features like bandwidth estimation. Instead of picking a bitrate ahead of time you dynamically get the best bitrate possible. Because of this and features like Simulcast, ICE Restarts and DataChannels I think WebRTC isn't just the future of web broadcasting but all broadcasting. The other part I am really excited about is that this is built on https://github.com/pion/webrtc. This is a library I have been working on for years and to see it deployed at Twitch's scale is so incredibly exciting. I learned a lot and excited to fold that back into the project itself. So many challenges come up not from WebRTC itself, but the massive scale and complexity that Twitch has to
Read the rest
deal with.
In Amazon adds support to broadcast from browser to IVS (Twitch) using WebRTC
This is something I have been involved with recently and so excited to see it launch! You can now broadcast to IVS using WebRTC. Before the only supported protocol was RTMP(S). Using WebRTC brings lots of great features like bandwidth estimation. Instead of picking a bitrate ahead of time you dynamically get the best bitrate possible. Because of this and features like Simulcast, ICE Restarts and DataChannels I think WebRTC isn't just the future of Web Broadcasting but all broadcasting! The other part I am really excited about is that this is built on https://github.com/pion/webrtc. This is a library I have been working on for years and to see it deployed at Twitch's scale is so incredibly exciting. I learned a lot and excited to fold that back into the project itself. So many challenges come up not from WebRTC itself, but the massive scal
Read the rest
e and complexity that Twitch has to deal with.
In Show HN: Broadcast to AWS' IVS (Twitch) from the Browser Using WebRTC
There's nothing particularly difficult on the server side — a quality SFU should be capable to handle on the order of 400 video flows per core, and there are quite a few high-quality free software SFUs available (Janus, Jitsi, ion-sfu, livekit, Galene). To give some perspective: we're using Galene for lectures, and our single-CPU server uses around 40% CPU usage in a room with 120 students (who keep their cameras switched off during the lecture, of course, and only occasionally switch them on to ask questions). As the grandparent mentioned, the problem is the client side. Since there is no standard videoconferencing protocol, every free software project needs to develop their own clients. And it's difficult for a free software project to have the manpower and expertise to develop quality clients for the web, Android and iOS, so in effe
Read the rest
ct what we currently have are mostly half-baked web clients. There is some hope, though. The IETF have been working on standard protocols for ingress (https://datatracker.ietf.org/wg/wish/), and if their protocols get deployed, you'll be able to use the same streaming software (think OBS) or IP camera with multiple distinct videoconferencing servers. An interoperable interactive videoconferencing protocol is nowhere near, but as more people understand videoconferencing technology, there is some hope that people will get together and start working on multi-protocol clients (remember Pidgin?). Full disclosure: I'm the author of Galene (https://galene.org), and I've been actively participating in the Pion community (https://github.com/pion/webrtc) and collaborating with the authors of ion-sfu (https://github.com/pion/ion-sfu) and LiveKit (https://github.com/livekit).
In Ask HN: Why is there no enterprise grade open-source zoom alternative?
AV1 support is already available in libwebrtc! So when I started building Pion the target use case was to make it easier to build scalable servers. Instead of interacting with a WebRTC servers REST API to query information/load balance I wanted to have it all in one code base. It also is really useful to have Media+Transport decoupled. Lots of use cases I didn't realize grew out of that. * Teleoperation/robotics (https://github.com/Ragnar-H/TelloGo) * Control remote software (https://github.com/m1k1o/neko) * Cross platform file sharing (https://github.com/saljam/webwormhole) * Sending pre-recorded media (RTMP/HLS/RTSP -> WebRTC) * Custom DataChannel servers/bridges (https://snowflake.torproject.org/) Lots of other cool ones in https://github.com/pion/awesome-pion I need to update it. It has been a bit since I have looked through https://p
Read the rest
In Show HN: AV1 and WebRTC
I have had offers to be paid to work on specific things for github.com/pion/webrtc and github.com/pion/dtls. I took one and it wasn't as great as I thought it would be. I really value the autonomy/independence I have now. I enjoy not having to make compromises. No deadlines to meet, no business goals and no creating stories for promotion. Instead I make the software as good as I can. Working a job unrelated to your Open Source project is the best place to be. You will probably make more money. You don't have to worry about clients paying on time. You don't have to worry about things like health insurance or 401k. Open Source is also great for the resume. Since it is all public you have a body of work that makes it much easier to get another job.
In How to Pay Professional Maintainers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.