Roughly half a megabyte a minute, or 30 MB an hour, for a normal one-to-one voice call in a browser. That is about a fortieth of a video call and a quarter of streaming music, which is why data is almost never the thing that limits a voice conversation.
| Roughly per minute | Per hour | |
|---|---|---|
| Voice call (Opus, what WaveTalk uses) | ~0.5 MB | ~30 MB |
| Music streaming | ~2 MB | ~120 MB |
| Video call | ~8–15 MB | ~500–900 MB |
| Video streaming (HD) | ~25 MB | ~1.5 GB |
On a 1 GB daily data pack, 30 MB an hour means you could talk for most of a waking day and still have most of the pack left.
Where the number comes from
Browser calls encode speech with Opus, which for voice runs somewhere between 24 and 64 kbit per second. At the top of that range, 64 kbit/s works out at 0.48 MB a minute, and the packet headers that carry it add ten to fifteen per cent. Hence the half-megabyte rule of thumb — and it is a rule of thumb rather than a measurement, because three things move it.
Silence is nearly free. The codec detects when nobody is speaking and sends a trickle instead of a stream. A conversation with ordinary pauses in it costs noticeably less than a continuous hour of talking.
A weak connection costs less, not more. When the network gets worse the encoder drops its bitrate rather than stalling, down to around 16–24 kbit/s, which is still perfectly intelligible for speech. This is the opposite of video, which degrades by freezing. It is also why a bad-sounding call is usually a latency or packet-loss problem and not a bandwidth one.
Stereo and music cost more. Voice chat sends mono speech. If a site offers high-fidelity audio for music, that is a different setting and a different number.
The case where it is much larger: group calls
This is the part nobody mentions, and it is worth understanding before you join a sixteen-person room on a metered connection.
A WaveTalk group call is a full mesh: every browser connects directly to every other one, rather than everyone sending audio to a server that mixes it. So in a room of N people you are sending your voice N-1 times and receiving N-1 separate streams. The data cost goes up with the size of the room:
| Room size | Roughly per minute (down) | Per hour |
|---|---|---|
| 2 (one-to-one) | ~0.5 MB | ~30 MB |
| 4 | ~1.5 MB | ~90 MB |
| 8 | ~3.5 MB | ~210 MB |
| 16 (the maximum) | ~7.5 MB | ~450 MB |
A full room costs about what a video call costs. That is the honest trade for a mesh, and it is the same trade that caps rooms at sixteen: a server that mixed the audio could hold hundreds and would use a fraction of the data, and it would also be able to hear the call. How group calls work covers the rest of that choice, and is voice chat encrypted covers why the mesh is there.
If you are on a small pack, the practical advice is simple: one-to-one calls cost nothing worth tracking, and big rooms are a wifi activity.
Does relaying double it?
No — and this is a common worry, because WaveTalk routes every call through a relay to keep IP addresses hidden. Your phone still sends one stream and receives one stream; the relay is the thing paying for the extra hop. Relaying changes who carries the bytes, not how many leave your device.
What actually drains your phone
Not the data. In an hour of talking the costs are, in order:
- The screen, if it is on. Lock it — the call continues, and this is the
single biggest saving available.
- The radio, especially on a weak signal, where the phone transmits
harder to stay connected.
- The audio path. Bluetooth earbuds cost a little more than wired ones;
the speaker costs more than either.
An hour of voice with the screen off is a modest battery cost. An hour with the screen on is mostly the screen.
What this means per country
It matters most where mobile data is metered and expensive, which is why it comes up in some places and not others — see the Philippines guide and Nigeria, where the voice-versus-video difference is the whole argument for the format. On home broadband, 30 MB an hour is not a number anyone needs to think about.
The short answer, again
One-to-one voice: about 0.5 MB a minute, 30 MB an hour, forty times cheaper than video. Group calls scale with the room, up to roughly 450 MB an hour in a full one. Nothing about a normal conversation will trouble a data cap.
Related
- Random Call: How to Make a Free Random Voice Call With Strangers
- Why Voice Chat Sounds Bad (and 8 Ways to Make It Crystal Clear)
- How to Start a Group Voice Call With Just a Link
- Is Voice Chat Encrypted? What Actually Protects a Call
Questions people ask
How much data does a one-hour voice call use?
About 30 MB for a one-to-one call in a browser, which is roughly half a megabyte a minute. A video call of the same length uses 500 to 900 MB, and an hour of HD video streaming about 1.5 GB. Pauses in the conversation cost almost nothing, because the codec sends a trickle rather than a stream when nobody is speaking.
Does voice chat use more data than streaming music?
No, considerably less — about 30 MB an hour against roughly 120 MB for music streaming. Speech is mono and heavily compressed, and silence is nearly free, so a conversation is one of the cheapest things you can do with a connection.
Do group voice calls use more data than one-to-one calls?
Yes, and the difference is large. A mesh group call sends your voice to every other person and receives each of theirs separately, so a four-person room costs about 90 MB an hour and a full sixteen-person room about 450 MB — comparable to a video call. One-to-one calls are the cheap case; big rooms are better on wifi.
Does a relayed call use twice as much data?
No. Your device still sends one stream and receives one stream; the relay pays for the extra hop between the two of you. Relaying changes who carries the bytes rather than how many leave your phone, which is why hiding your IP address this way costs you nothing in data.