LiveLoop · Free Tool
Find out how many Mbps an online class needs and how many GB it burns — by video quality, participant count and length. Built for low-bandwidth India, so you can plan for students on 2G/3G before class, not during it.
A video bandwidth and data-usage calculator estimates two things for an online class or meeting: the download speed each participant needs, measured in megabits per second (Mbps), and the total internet data the session consumes, measured in gigabytes (GB). As a rule of thumb, one video stream uses about 0.3 Mbps at low quality, 0.8 Mbps at standard definition, 1.5 Mbps at HD 720p and 3 Mbps at full HD 1080p; an hour at SD is roughly 0.35 GB per person, and full HD is over 1.3 GB. Group calls multiply this by the number of cameras each person sees, while audio-only uses about 0.05 Mbps. This tool turns your quality, participant and length inputs into a per-person Mbps figure and a total GB figure, free and entirely in your browser.
Your session
Bandwidth needed
8.0 Mbps
recommended download per person
Data used
3.6 GB
whole session, per person
Per minute
60 MB / min
Indicative figures for planning only. Bandwidth and data depend on your network, devices, codecs, frame rate, screen-sharing and how many cameras are on. Actual usage will vary — confirm in your own environment before relying on a result.
Typical per-stream benchmarks for one-to-one or per-camera video. Multiply the data column by the number of cameras a participant sees for a group call. These are the same figures the calculator above uses.
| Video quality | Bandwidth / stream | Data / hour (per stream) | Best for |
|---|---|---|---|
| Audio only | ≈0.05 Mbps | ≈20–25 MB | 2G links, very tight data plans |
| Low video | ≈0.3 Mbps | ≈0.13 GB | 3G, entry-level Android |
| Standard / SD | ≈0.8 Mbps | ≈0.35 GB | Most online classes |
| HD 720p | ≈1.5 Mbps | ≈0.7 GB | Clear faces, demos, broadband |
| Full HD 1080p | ≈3 Mbps | ≈1.35 GB | Webinars, fibre connections |
Benchmarks reflect typical WebRTC bitrates; H.265/AV1 codecs and aggressive simulcast can reduce them. Treat as planning anchors.
There are two numbers that decide whether a class works: the speed of the connection, in Mbps, and the volume of data it moves, in GB. They sound similar but answer different questions. Mbps tells you whether the video will play smoothly in real time. GB tells you whether a student on a capped mobile plan can afford to attend every day of the week. A class can be comfortable on speed yet expensive on data, which is why both columns matter when you plan for a mixed group.
In a one-to-one call each side sends and receives a single stream. In a class of thirty with cameras on, every participant is downloading many streams at once, so the data each person uses scales with the number of active cameras — not with the size of the class on paper. This is the single biggest lever a teacher controls. Asking students to keep cameras off unless speaking can cut a participant's data use by more than half, turning a 0.7 GB HD hour into something a 1 GB daily plan can sustain across several classes.
For a large share of students in India, the binding constraint is not whether they own a device but whether the connection holds and the data lasts the month. A platform that simply drops to a black screen when bandwidth dips effectively excludes those students. The better behaviour is adaptive bitrate: when the link weakens, the video quality steps down automatically — to low video, then to audio with slides — so the student stays in the lesson with sound intact rather than being thrown out. Planning at SD or low video, rather than defaulting to 1080p, is usually the difference between an inclusive class and one only the well-connected can attend.
Once you have a per-hour figure, multiply by the hours per week and the weeks in a term to see the real demand a course places on a student's data budget. Six hours of HD classes a week is roughly 4.2 GB before anything else they do online; the same six hours at SD is closer to 2.1 GB. Sharing this estimate with parents up front — and offering an audio-plus-slides option for the data-constrained — prevents the quiet attrition that happens when families simply cannot sustain the cost.
A calculator gives you a planning anchor, not a guarantee. Real-world usage shifts with the codec in use, the frame rate, how much the screen-share moves, and whether the platform sends multiple resolutions of each stream. Treat the result as the figure to design around, then validate with one real session before a term begins. The aim is not a precise byte count; it is a confident answer to "will my students be able to attend, and can they afford to?"
"Half our batch is on mobile data, and a few are on patchy 3G in their home towns. I used this to set our default to SD with cameras off, and worked out each student needs under half a gigabyte an hour. Once we moved the live batches to LiveLoop, the weak connections stepped down to audio and slides instead of dropping — attendance from the small-town students stopped sliding."
From the estimate to the live class
This calculator tells you what a session should need. LiveLoop is built to keep working when the connection falls short — adaptive bitrate holds video on 2G/3G and entry-level Android, so rural and Tier-3 students step down to low video or audio-plus-slides instead of staring at a black screen. Students join in the browser with no app download and no plugin, on any device. See how HD holds on low bandwidth.
2G/3G
adaptive bitrate holds quality
Browser
no download, no plugin
Audio-safe
steps down, doesn't drop
Low-end
runs on entry Android
This page answers one question: the live bandwidth and data a session needs. It does not estimate file sizes for saved recordings — that is the recording storage estimator. It does not price the time a meeting consumes — see the meeting cost calculator. And it does not convert a class time across regions — that is the time-zone meeting scheduler. For the product capability behind low-bandwidth delivery rather than the estimate, see HD video & audio on low bandwidth.
Bandwidth & data FAQ
As a planning guide: low ≈0.3 Mbps per stream, SD ≈0.8 Mbps, HD 720p ≈1.5 Mbps and full HD ≈3 Mbps. Each camera on adds a stream a participant downloads, so a large gallery needs proportionally more. Audio-only is far lighter at about 0.05 Mbps.
Roughly 0.35 GB per hour at SD, 0.7 GB at HD 720p and over 1.3 GB at full HD, per participant. Turning cameras off and relying on audio plus screen-share cuts this sharply — useful for students on limited mobile data.
For hosting, plan enough upload to send your own HD stream (around 1.5–3 Mbps up) plus download for the students you see. A stable 5–10 Mbps line comfortably handles a small HD class; larger galleries or 1080p need more. The calculator gives a per-person figure to match to your plan.
Static slides or a shared document usually use less data than full-motion camera video — there's little movement to encode. A fast-moving screen-share, like video playback, can use as much as or more than a camera. The quality setting is a reasonable proxy for mixed use.
It multiplies a typical per-stream bitrate for the chosen quality by the number of streams each person receives, adds a small overhead headroom, then converts to per-minute and total figures across the call length. It's an indicative planning estimate, not a measured value.
No — it's indicative. Real usage varies with network, codec, frame rate, screen-sharing, simulcast and active cameras. Use it to plan, then confirm in your own environment with a real session.
Ask camera-off where possible, rely on audio plus screen-share, and choose a platform with adaptive bitrate that lowers quality automatically instead of dropping the call. That keeps a student on 2G or 3G connected with sound and slides even when full video isn't viable.
No. The calculation runs entirely in your browser. The quality, participant count and length you enter are never uploaded or stored.
In a group call each participant downloads the other active cameras, so more cameras means more data per person. A single viewer watching only the speaker downloads just one stream. The tool lets you switch between the two modes.
Very little — around 0.05 Mbps, roughly 20–25 MB per hour. Audio-only or audio-plus-slides is the most data-friendly option for students on tight mobile plans.
GB of storage your recordings need, by length and resolution.
What a live session really costs in attendee time.
One time across every attendee's zone at a glance.
A cadence of polls, Q&A and breakouts across a session.
LiveLoop holds live classes on weak connections — adaptive video, recording, breakouts and polls, with no app to download.
