Best of WebRTC2025

  1. 1
    Article
    Avatar of notedNoted·1y

    FileDrop: Self Hosted WebRTC File Transfer with Chat

    FileDrop is a self-hosted, end-to-end encrypted, peer-to-peer file transfer platform built on React and Node.js. It supports both file and text transfers and features a minimalist user interface. The post provides a Docker Compose configuration for easy setup and explains that files are relayed directly between devices without being stored on the server. Coturn is used as the TURN server for relaying data when direct peer-to-peer connection is not possible.

  2. 2
    Article
    Avatar of huggingfaceHugging Face·1y

    FastRTC: The Real-Time Communication Library for Python

    FastRTC is a new real-time communication library for Python designed to simplify the building of real-time audio and video AI applications. It supports features such as automatic voice detection, WebRTC-enabled Gradio UI, and integration capabilities with FastAPI. The library also includes utilities for text-to-speech, speech-to-text, and other key functionalities, making it easy to develop and deploy real-time applications.

  3. 3
    Article
    Avatar of helixmlHelixML·30w

    Technical Deep Dive on Streaming AI Agent Desktop Sandboxes: When Gaming Protocols Meet Multi-User Access

    Helix adapted Moonlight, a gaming streaming protocol designed for single-player sessions, to stream GPU-accelerated desktop environments for AI agents to multiple users simultaneously. The team initially used "apps mode" with a workaround where their API pretended to be a client to start containers, but are migrating to "lobbies mode" which natively supports multi-user access to shared sessions. The solution enables low-latency (50-100ms) streaming of full Linux desktops with AI agents working in real IDEs and browsers, though challenges remain with input scaling and video corruption across different client resolutions.

  4. 4
    Article
    Avatar of webrtchacksWebRTC Hacks·29w

    WebRTC vs. MoQ by Use Case

    Analyzes whether Media over QUIC (MoQ) will replace WebRTC across different use cases including 1:1 calls, voice AI, meetings, traditional streaming, live streaming, and webinars. Concludes that WebRTC will likely remain dominant for peer-to-peer calls and meetings due to its optimized architecture, while MoQ shows strongest potential in live streaming scenarios where it can bridge the gap between WebRTC's low latency and HLS's scalability. For voice AI, the analysis questions whether current implementations prioritize low-latency media enough to justify either protocol. The comparison considers technical factors like latency requirements, infrastructure costs, and quality demands.

  5. 5
    Article
    Avatar of hnHacker News·1y

    kern/filepizza: :pizza: Peer-to-peer file transfers in your browser

    FilePizza is a peer-to-peer file sharing service using WebRTC to eliminate the need for intermediary servers. It features a modern UI with dark mode, mobile browser support, direct browser-to-browser transfers, password protection, and the use of Redis for out-of-process storage. Users can upload multiple files at once and monitor transfer progress, and files are encrypted during transfer. A hosted instance is available at file.pizza.

  6. 6
    Video
    Avatar of t3dotggTheo - t3․gg·32w

    Finally.

    Firefox 144 brings significant improvements for web developers, including support for view transitions API, proper gradient dithering (fixing a 15-year-old bug), the element.moveBefore API, and better WebRTC capabilities. These updates address long-standing compatibility issues that have held back modern web development, bringing Firefox closer to Chrome and Safari in supporting current web standards. The view transitions feature enables smooth animations between page states without JavaScript, while gradient rendering fixes eliminate visible banding artifacts.

  7. 7
    Article
    Avatar of webrtchacksWebRTC Hacks·33w

    Is everyone switching to MoQ from WebRTC?

    Analysis of Media over QUIC (MoQ) adoption claims versus reality, using Chrome usage metrics to debunk assertions that developers are switching from WebRTC. Chrome data shows WebTransport usage remains minimal (0.035% peak vs WebRTC's stable 0.35%), with multiple failed experiments over five years. Addresses misconceptions about WebRTC architecture, noting that server-based deployments (SFUs/MCUs) have been standard for years, not peer-to-peer full mesh. Concludes that despite marketing claims, no successful large-scale migration from WebRTC to MoQ has occurred yet.

  8. 8
    Article
    Avatar of helixmlHelixML·23w

    We Mass-Deployed 15-Year-Old Screen Sharing Technology and It's Actually Better

    A team built a sophisticated H.264 video streaming pipeline over WebSockets for their AI coding platform, only to discover that simple JPEG screenshot polling works better on unreliable networks. The article details their journey from WebRTC (blocked by enterprise firewalls) to a custom 60fps H.264 solution (failed on poor connections) to a hybrid approach that adaptively switches between high-quality video streaming and stateless JPEG screenshots based on network conditions. The key insight: stateless JPEGs (100-150KB each) provide better reliability and lower bandwidth than stateful video codecs when network quality degrades, while maintaining responsive keyboard/mouse input over WebSockets.

  9. 9
    Article
    Avatar of huggingfaceHugging Face·1y

    Hugging Face and Cloudflare Partner to Make Real-Time Speech and Video Seamless with FastRTC

    Hugging Face and Cloudflare have partnered to provide AI developers with seamless real-time speech and video capabilities using FastRTC. This collaboration allows developers to use enterprise-grade WebRTC infrastructure with minimal setup and reliable global connectivity via Cloudflare's TURN servers. AI developers can now access 10GB of free data streaming per month using a Hugging Face token and easily scale using Cloudflare's network.

  10. 10
    Article
    Avatar of opensourcefrontendOpen Source Front End·1y

    Built an OSS implementation of WEB-RTC in Next.JS and Shad CN, with self hosted coturn

    Developed an open-source video-call and chat application using WebRTC and Socket.IO for signaling. The app, created with Next.js, Shad CN, Tailwind, and Flask, supports rooms with up to 3 people due to its mesh architecture. The platform ensures privacy with features like password-protected rooms, no storage or interception of data, and direct peer-to-peer communication without server-side processing. Configuration of self-hosted coturn was emphasized for effective traversal across ISPs.

  11. 11
    Article
    Avatar of hnHacker News·31w

    Control any computer remotely

    JetKVM is an open-source KVM-over-IP solution offering 1080p@60fps video streaming with 30-60ms latency using H.264 encoding and WebRTC. Built with Golang backend and React frontend, it provides optional cloud access through STUN/TURN servers for NAT traversal. The system runs on minimal BusyBox Linux and features an RJ12 extension port for hardware customization. All components including the cloud API, dashboard, and documentation are open source and hackable.

  12. 12
    Article
    Avatar of awegoAwesome Go·37w

    Making a game with Pion

    Explores building cross-platform multiplayer games using WebRTC datachannels with Pion (a Go WebRTC library) and Ebitengine. Covers the advantages of WebRTC over WebSockets for real-time gaming, discusses various WebRTC implementations, and presents a practical example of peer-to-peer game networking without dedicated servers or port forwarding.

  13. 13
    Article
    Avatar of telerikTelerik·48w

    How to Use NestJS as Signaling Server for WebRTC Video Chat

    A comprehensive guide to building a peer-to-peer video chat application using WebRTC for direct browser communication and NestJS as the signaling server. Covers the complete setup including HTTPS configuration with SSL certificates, WebSocket gateway implementation for handling offers/answers/ICE candidates, and frontend client code. Explains the four-stage WebRTC connection process, signaling requirements, and provides practical code examples for both server and client sides with troubleshooting tips.