Compare VoIP codecs by workflow, network, and interoperability.
Compare G.711, G.729 and Opus across bitrate, overhead, complexity, resilience, interoperability, licensing, transcoding, and business use.
Codec selection crosses the complete media path
Compare codecs across the whole media path; payload rate alone does not determine the best choice.
| Criterion | G.711 | G.729 | Opus |
|---|---|---|---|
| Encoded payload | 64 kbit/s before packet overhead | Lower encoded speech bitrate | Flexible bitrate selected by the application |
| Audio scope | Narrowband telephony baseline | Narrowband speech | Narrowband speech through full-band audio |
| Common strength | Straightforward telephony interoperability | Reduced payload on constrained links | Adaptation and resilience for modern real-time applications |
| Check before use | Total bandwidth, packet interval, and loss | Implementation, licensing, quality, and transcoding | Endpoint, carrier, recording, and transcoding support |
| End-to-end rule | Every segment must support it or transcode | Every segment must support it or transcode | Every segment must support it or transcode |
G.711, G.729, and Opus solve different constraints
G.711 is common in telephone networks and provides straightforward interoperability at a comparatively high payload rate. G.729 was designed for lower-bit-rate speech and may help on constrained links, but requires compatible implementations and review of current licensing or commercial conditions. Opus adapts across narrowband speech through full-band audio and is widely used in modern real-time applications.
Payload bitrate is not the complete bandwidth figure. Add IP, transport, RTP, link, encryption, tunnel, and packetization overhead in both directions, then include concurrency and headroom. Shorter packet intervals can reduce serialization and loss impact while increasing packets and header overhead.
Avoid unnecessary transcoding
When adjacent systems do not share a codec, a media function may decode and re-encode the audio. Transcoding adds processing, can add delay, may reduce quality, and creates another capacity and failure dependency. Multiple transcoding stages can compound the effect.
Choose an endpoint and provider codec policy that supports the required routes, recording, DTMF, conferencing, mobile networks, browser media, and destination interconnection. Confirm the negotiated codec in a real call rather than relying only on configuration preference.
Codec selection checklist
Test representative endpoints, routes, networks, and failure conditions.
Supported codecs and preference order at every endpoint, service edge, provider, and destination
Audio bandwidth and speech-quality requirement
Payload plus packet, encryption, tunnel, and link overhead
Packet interval, jitter buffer, loss concealment, FEC, and DTX behavior
CPU, battery, mobile network, browser, conference, recording, and transcoding impact
Licensing, commercial, regulatory, and interoperability constraints
Further reading
Product information and relevant public resources for readers who want more detail.
Frequently asked questions
Which codec is best for VoIP?
There is no universal best codec. Choose based on endpoint and provider support, audio requirement, network conditions, overhead, resilience, transcoding, CPU, licensing, and the routes the business must use.
Does G.711 use only 64 kbit/s on the network?
64 kbit/s is the encoded payload rate. Actual network use is higher after RTP, transport, IP, link, encryption, tunnel, and packetization overhead.
Why can a wideband call become narrowband?
If any endpoint, provider, public-network segment, conference, recording, or transcoder supports only a narrower format, the end-to-end call can be limited or transcoded.