What actually consumes data
Cellular plans meter the bytes that cross the link. Cameras produce a lot of bytes, so the question is which of those bytes you choose to send.
Four things drive volume.
- How long video is sent. A stream running all day sends far more than a clip that runs for a few seconds per event.
- How heavy each stream is. Resolution, frame rate and compression set the bitrate. Compression matters too, as explained in H.264 vs H.265.
- How many streams are sent. Each additional camera sent in full adds to the total.
- How often events occur. On event-based systems, a busy site generates more clips than a quiet one.
Anything that touches the network also adds a little overhead, such as status messages, health checks and software updates. These are usually small next to video but are not zero.
Continuous streaming versus event-based
The largest design choice is whether video flows constantly or only when needed.
| Approach | How it works | Data use | Best suited to |
|---|---|---|---|
| Continuous streaming | Video is sent to a remote location all the time | Highest and steady | Sites with a wired or high-capacity connection |
| Event-based | Clips or snapshots are sent when analytics detect something | Lower, varies with activity | Cellular and remote sites |
| On-demand live view | Video is sent only while someone is watching | Low most of the time, spikes during viewing | Verification and spot checks |
| Local recording only | Nothing leaves the site unless pulled later | Near zero | Backup, or sites reviewed after the fact |
Most cellular designs combine the last three. Events and alerts travel across the link, an operator can pull live video when needed, and a full recording sits on local storage. For a detailed comparison of the first two approaches, see event-based vs live video monitoring.
Why event-based works well on cellular
On a cellular link, bandwidth and data volume are both limited and both cost something. Event-based sending spends them only on moments that matter.
It depends on analytics being good. If detection is accurate, the clips that cross the link are the ones worth seeing. If detection is noisy, a swinging branch or a passing animal can trigger clips all night and turn a light-data design into a heavy one. Tuning detection to cut false alarms has a direct effect on the data bill.
Event-based sending has a tradeoff. You only see what the system decided was worth sending. That is why recording the full-quality stream locally matters, so the surrounding context is available when you need it.
Where recording happens
Storage location changes data use more than almost any other choice. If recording happens on site, normal operation sends nothing to the cloud. If recording happens in the cloud, every recorded second has to cross the link.
That makes cloud recording over cellular expensive in data terms. The tradeoffs between the two are covered in cloud vs local video storage. A common compromise is local recording for the full record plus cloud storage of selected clips and snapshots.
Designing a plan in general terms
You do not need exact figures to design well. You need a method.
- Decide what must leave the site. Alerts, snapshots and short clips, or live video on request, or both.
- Decide what stays on site. Full-quality recording, with a retention period that fits your needs.
- Estimate activity. Think about how many events a normal day, a busy day and a storm produce.
- Choose stream weight. Use lighter streams for remote viewing and keep the heaviest stream local.
- Add margin. Plan for months that are busier than average.
- Test before relying on it. Run the real configuration for a period and look at actual use.
Your measured usage after a trial period is more reliable than any estimate made in advance.
Questions to ask about the plan itself
Cellular plans differ in ways that change how a camera system behaves. Ask these before committing.
- How is data metered, and over what period?
- What happens at the limit? Does service stop, slow down or bill extra?
- Is speed reduced after heavy use, and does that affect live video?
- Is there more than one carrier or SIM, in case one has weak coverage?
- What happens to alerts if the link drops, and does the system catch up afterward?
Coverage is a separate question from data volume. A strong plan on a weak signal still delivers poor video. Testing at the mounting location is the only reliable check. For how the technology itself performs, see cellular security cameras on 4G and 5G.
When cellular is not enough
Some locations have weak or no cellular coverage. In those cases, a different link may be needed, with its own tradeoffs in speed, delay and cost. Satellite is one option, covered in satellite internet for security cameras. The same principles apply on any limited link. Send less, keep the full record local, and make sure the system degrades gracefully when the connection does.
Watching for drift
Data use changes over time, so check it. A sudden jump usually has an identifiable cause.
- A settings change raised resolution or frame rate.
- A new analytics rule started generating many more events.
- Weather or seasonal activity increased motion.
- Someone left a live view open for a long period.
- A software update or sync consumed a burst of data.
Reviewing usage monthly, and after any configuration change, catches these before they become a problem.
How VDS fits
VDS mobile surveillance units use dual-SIM 4G/5G cellular, so they can run at sites with no internet, no site power and no trenching. The unit is solar-powered, with a 900W bifacial solar array charging an 11.8 kWh LiFePO4 battery bank. AI detection for people, vehicles, loitering, objects and license plates helps focus attention on events, and a 24/7 US-based security operations center verifies them and can respond with live talk-down, then police dispatch with video. See the mobile surveillance unit or talk to our team about connectivity at your location.