WebRTC for .NET, with one API across five platforms.
Every platform has its own WebRTC SDK, and no two look alike: a Java SDK on Android, an
Objective-C framework on Apple, a C++ library on Windows, and the browser's own JavaScript API on
the web. WebRTCme maps all of them onto a single C# surface that mirrors the
W3C WebRTC 1.0 API — so if you have used RTCPeerConnection in
JavaScript, you already know this API.
var window = CrossWebRtc.Current.Window();
var pc = window.RTCPeerConnection(new RTCConfiguration { IceServers = [] });
var offer = await pc.CreateOffer();That runs unchanged on Blazor WebAssembly, Android, iOS, Mac Catalyst and Windows.
📖 Documentation is in the Wiki
| Getting started | Installing the packages and wiring them into a Blazor or MAUI app |
| Hello world | Sixty lines that negotiate a real connection — no server, no camera, no network |
| Platform prerequisites | Read this before filing a bug. Three traps, each of which fails silently |
| What works where | Honest per-platform matrix, including what is unverified |
| Releases | Versions, upgrading from 2.0.0, what is embedded |
| Troubleshooting | Symptoms, and what actually causes them |
Two, and which you want depends on how much you want built for you.
| What you get | When | |
|---|---|---|
WebRTCme |
The unified API and all five bindings, with their native halves. Peer connections, media streams, devices, data channels. | You have your own signalling and UI, or you are building a library. |
WebRTCme.Middleware |
The above, plus a video tile, media managers, view models, and a connection layer that does the signalling for you — peer-to-peer or through a mediasoup SFU. | You want a working call app without writing the plumbing. |
WebRTCme.Middleware depends on WebRTCme, so referencing the middleware brings both. You never
reference a binding directly.
dotnet add package WebRTCme.MiddlewareBoth packages carry every target framework — net10.0 for Blazor, plus net10.0-android,
net10.0-ios, net10.0-maccatalyst and net10.0-windows10.0.22621.0 for .NET MAUI — so you
reference the same package whatever you are building and NuGet picks the slice that matches.
.NET 10 only. The 2.0.0 line is the .NET 8 line and is frozen; there is no back-port. Upgrading from 2.0.0 takes three edits — see Releases.
WebRTCme.Bindings/ per-platform native access — Blazor JSInterop, Java, ObjC, Windows P/Invoke
WebRTCme/ the unified API and the plug-in → package 1
WebRTCme.Middleware/ video tile, managers, view models → package 2
WebRTCme.Connection/ signalling: mesh/P2P and a mediasoup SFU ↳ folded into package 2
WebRTCme.DemoApp/ sample apps, Blazor and MAUI
Tests/ five tiers, from unit tests to on-device runs
doc/ KnownGaps.md, TestingPlan.md, Packaging.md
The native WebRTC libraries are built by a separate repository, WebRTCnative, and consumed here as prebuilt binaries.
dotnet build WebRTCme.slnEverything builds on Windows, including the iOS and Mac Catalyst library slices — only linking and deploying an app for those needs a Mac.
There is no dotnet test; the test projects are invoked directly. See
Testing.
Issues and pull requests are welcome. Two things worth knowing first:
doc/KnownGaps.mdrecords what is missing, half-wired or fragile, and keeps entries after they are fixed with what the fault looked like beforehand. It is the fastest way to recognise something you have just hit.- A
NotImplementedExceptionon a path that matters to you is worth an issue. Most of the unimplemented W3C surface has never been reached by anything, so a real call site is the signal that decides what gets filled in next.
Special thanks to Gøran Yri for his major contributions to the .NET MAUI porting.
WebRTCme is MIT licensed. It embeds Google's WebRTC and its dependencies, which carry their own terms — see what is inside the packages.