Thunder Viewer

Second Life on Mobile · · 4 min read

WebRTC Voice Is Live in Second Life: What Changes

Illustration of glowing sound waves rippling from a speaking avatar across a night landscape

The quietest big change in Second Life is one you hear rather than see: voice across the grid now runs on WebRTC, the modern real-time audio standard built into every browser and phone. For most residents the migration announced itself only as clearer audio and one less thing to install. But this is infrastructure with consequences, and if you use voice at all, or have been waiting for a reason to start, it is worth understanding what actually changed.

What WebRTC is, in one paragraph

WebRTC is the open standard for real-time voice and video that powers the calling features in browsers and apps you already use every day. It lives natively inside Chrome, Safari, Firefox, Edge, and both mobile operating systems: no plugin, no separate voice client, no mystery process. When a platform adopts WebRTC, it is trading a proprietary audio stack for the one the entire internet standardized on, with modern codecs (Opus) and modern echo cancellation and noise handling along for the ride.

What changed for Second Life

For roughly fifteen years, Second Life voice meant a separate proprietary voice service riding alongside the viewer, a system famous for its own special failure modes. The move to WebRTC replaced that stack grid-wide, and the practical differences land in three places:

  1. Quality. The Opus codec and modern audio processing simply sound better: fuller voices, less crunch, better handling of noisy rooms.
  2. Reliability. Voice now uses the same battle-tested transport as every video call on the internet, including its firewall-friendly connection tricks.
  3. Reach. This is the big one. Because WebRTC is native to browsers and phones, "voice needs the desktop viewer" stopped being a law of nature. Anything that can open a browser tab can, in principle, join Second Life voice.

What did not change is the part that makes SL voice special: it is still spatial. Voices come from where avatars stand, pan as they move, and fade past about 50 meters. Under the hood, Second Life's voice servers mix a unique audio stream for each listener's ears; the stereo image you hear is the room.

What it unlocks: voice from anywhere

We can speak to this firsthand, because Thunder Viewer's voice support is built directly on Second Life's WebRTC infrastructure. Our browser client performs the same voice handshake as the official viewer, byte for byte where it matters, which means:

None of that would be possible if Second Life still spoke a proprietary audio protocol. The grid adopting the browser's native standard is precisely what lets browser-native clients treat voice as a first-class feature.

Getting the best out of voice in 2026

A few practical notes, learned from operating voice sessions daily:

The bigger pattern

Put this next to the official mobile app's beta year and the browser streaming experiment, and 2026's theme is clear: Second Life is methodically dismantling the assumption that participating requires a gaming PC and an installer. Some experiments end, some ship; the direction does not wobble. Voice moving to the web's own standard is the piece of that story residents will still be using in ten years.

FAQ

Did Second Life voice change?

Yes. Voice across the grid now runs on WebRTC, the standard behind browser and app calling everywhere, replacing the proprietary voice stack that served Second Life for its first two decades. Most residents notice it as clearer audio.

Is Second Life voice still spatial?

Fully. Voices still come from where avatars stand and fade with distance (about 50 meters); the servers mix a positioned stream for each listener. WebRTC changed the plumbing, not the experience of a room.

Can I use Second Life voice without the desktop viewer?

Yes, and this is the migration's real gift: WebRTC is native to browsers, so clients like Thunder Viewer offer full spatial voice, listening and speaking, in a browser tab on a laptop or phone.

Why does my voice not work in a browser client?

The most common cause is a denied microphone permission: check the padlock icon in the address bar and re-allow the mic. After that, confirm the parcel has voice enabled and that you are within range of the people you expect to hear.