How Much Data Does Voice Chat Actually Use?
Real numbers for WebRTC voice against video and streaming, what a relay adds, and how long you can talk on a small mobile data plan.
If you are on a metered plan or a slow connection, "will this eat my data?" is a completely reasonable first question about any live chat platform. It is also rarely answered with actual numbers.
Here are the numbers, with the caveats they need.
The rough figures
Modern WebRTC voice uses the Opus codec, which for speech typically runs somewhere in the range of 20 to 40 kilobits per second in each direction, adapting to the connection. Add protocol overhead and the practical figure for a call is roughly 30 to 60 kbit/s each way.
Converted to something useful: that is very approximately 0.3 to 0.6 MB per minute, or 20 to 35 MB per hour of continuous conversation.
For comparison, at the same rough level: a video call is commonly ten to thirty times that, standard-definition video streaming is several hundred megabytes an hour, and high definition is more again. Voice is genuinely cheap.
These are estimates, not measurements of your call. Actual usage varies with the codec settings, your network quality, how much silence there is - Opus sends very little during silence - and whether the connection is direct or relayed.
What a TURN relay changes
WebRTC prefers to connect two people directly. When a network will not allow that, which is common on mobile networks and behind corporate firewalls, the audio is relayed through a TURN server instead.
For your data allowance this makes little difference: you still send one stream and receive one stream, and the relay sits in the middle. It can add a small amount of latency and it costs the platform bandwidth, but it does not double what your phone counts.
TalkLive uses a TURN relay in production for exactly this reason - reliability of connection, not data reduction. Audio stays encrypted through it and is not recorded or stored by TalkLive.
What that means on a real plan
At roughly 25 MB per hour, a 1 GB monthly allowance is on the order of forty hours of talking, if you spent all of it on that and nothing else.
For most people the practical ceiling is not data, it is time. An hour a day of conversation is a lot of conversation and still well under a gigabyte a month.
Text chat is far lighter again - a text session is a few kilobytes of messages plus the page you already loaded. If you are genuinely counting megabytes, text mode is effectively free.
Making it lighter still
Use Wi-Fi where you have it. Obvious, but it is the whole answer for most people.
Close the tab when you are done rather than leaving it idle in the background. An idle connected session still maintains a connection.
Do not stream music in the background of a call. The call itself is cheap; the streaming is not.
On a weak connection, voice degrades gracefully in a way video does not. Opus lowers its bitrate rather than dropping the call, so a poor line usually means slightly rougher audio rather than a failure.
Why this matters for a voice-first platform
A great deal of the world uses the internet on a metered mobile plan, and platforms designed on unmetered home broadband tend to forget it. Voice-only is not just a privacy decision - it is what makes a live conversation practical on a small plan and an older phone.
That is also why TalkLive is browser-based with nothing to install: no app download, no updates, and a voice call that costs less data than the page you are reading this on would if it had video in it.