One 1080p camera streaming around the clock sends roughly 650 GB of video a month. Six of them on a 50 GB SIM run through the allowance in less than a day, and the remote CCTV monitoring the client pays for turns into a black screen at the alarm receiving centre. The cameras work, the installation is sound, and the data sum was simply never made.
That sum is simple once you know the inputs, and it decides almost everything else: which plan to buy, whether to stream continuously or on events, and whether a 4G connection suits the site at all. This article shows how to calculate CCTV data usage per camera, what the typical numbers look like per resolution, how the monitoring mode changes the bill by a factor of a hundred, how to make cameras reachable from outside, and how to size a SIM plan for a camera system on security and surveillance connectivity.
Why CCTV data usage is an upload problem
Most consumer and shared mobile networks are built around people who download: web pages, video, apps. A camera sends video out, hour after hour, and a 4G CCTV camera spends almost all its data in the upload direction.
That matters for two reasons. The first is capacity. On most consumer and shared mobile connections, upload capacity is a fraction of download capacity, and it is shared with every other device on the same mast. A connection that shows an impressive download speed can still struggle to carry four camera streams upward at the same time. The second is cost. Because the traffic is constant, a camera consumes data at a steady rate every hour of the day, including the hours when nothing happens in front of the lens.
Built for upload: symmetric speed
Weconnect designs its connectivity for exactly this traffic pattern. Symmetric speed means upload and download run at the same rate: a 100 Mbit link is 100 down and 100 up, where most consumer or shared mobile connections deliver something like 100 down and 10 up. For CCTV, the direction that counts is outbound: cameras push footage to a VMS or cloud recorder, and alarm clips travel to the monitoring centre.
Weconnect profiles therefore treat the uplink as a first-class direction. Routing is fixed, the APN is dedicated, and there is no shaping or fair-use throttle that quietly lowers the upload after a few hundred gigabytes. What is provisioned on day one is what the camera system gets in month twelve, in both directions. The network is tuned for devices that send more than they receive, which is what a camera estate does all day.
Before choosing a plan, test the upload at the actual camera position, more than once and including at a busy time of day, and size the streams to that measured figure.
How to calculate CCTV data usage per camera
Every calculation starts with one number: the bitrate of the stream, in megabits per second (Mbps). The camera’s web interface or the recorder shows it. From there, the sum is fixed:
- Per hour: bitrate in Mbps × 0.45 = GB per hour.
- Per day: GB per hour × 24.
- Per month: GB per day × 30.
A camera streaming at 1 Mbps uses 0.45 GB per hour, 10.8 GB per day and about 324 GB per month. Double the bitrate and every figure doubles. Multiply by the number of cameras for the site total.
What determines the bitrate
Four settings drive the bitrate, and the installer controls all of them:
- Resolution. A 4K stream carries roughly four times the pixels of a 1080p stream.
- Frame rate. 25 frames per second looks smooth. For most security purposes, 10 to 15 frames per second is enough and cuts the bitrate substantially.
- Compression. H.265 typically needs 30 to 50 percent less bitrate than H.264 for comparable image quality.
- Scene activity. Trees in the wind, rain, passing traffic and night-time noise all push a variable bitrate stream upward. A quiet warehouse wall uses less than a busy car park.
Typical 4G security camera data usage per resolution
The table below uses common bitrates for continuous streaming. Actual values vary by camera brand, scene and settings, so treat these as planning figures and check the real bitrate on site.
| Stream | Typical bitrate | Per hour | Per day | Per month (30 days) |
|---|---|---|---|---|
| Substream / low-res live view | 0.5 Mbps | 0.23 GB | 5.4 GB | ~160 GB |
| 1080p, H.265 | 2 Mbps | 0.9 GB | 21.6 GB | ~650 GB |
| 4MP, H.265 | 3 Mbps | 1.35 GB | 32.4 GB | ~970 GB |
| 1080p, H.264 | 4 Mbps | 1.8 GB | 43.2 GB | ~1,300 GB |
| 4K, H.265 | 8 Mbps | 3.6 GB | 86.4 GB | ~2,600 GB |
The conclusion is direct: one camera streaming full resolution around the clock uses hundreds of gigabytes a month. Six of them on a 50 GB SIM last a few hours.
Remote CCTV monitoring: three modes, three very different bills
Remote CCTV monitoring is the practice of watching, recording or verifying camera footage from a location away from the site, such as a control room, an alarm receiving centre or a cloud platform. How the footage reaches that location determines the data bill far more than the choice of camera.
Continuous streaming to the cloud or a control room
Every camera sends its full stream all the time, and recording happens off site. This gives the most complete picture and survives theft or destruction of on-site equipment, and it uses the most data by far. It fits sites where continuous off-site recording is a requirement and the connection is sized for it.
Event-based upload to an alarm receiving centre
The camera or recorder stores footage locally and only sends video when something happens: a motion trigger, a line crossing or an intruder alarm. The monitoring centre receives a short clip plus a live view to verify the alarm. A 30-second clip at 2 Mbps is about 7.5 MB. Twenty events a day adds up to roughly 4.5 GB per month per camera. This is the dominant model for professionally monitored sites, and it is where 4G is most economical.
On-demand live view with local recording
Footage is recorded on an SD card or a local recorder, and someone connects remotely only to look. Half an hour of live viewing per day at 0.5 Mbps on the substream uses around 3.4 GB per month. The data use is low, and the site depends on the local recorder surviving an incident.
| Mode | Data per camera per month (indicative) | Fits |
|---|---|---|
| Continuous full-resolution streaming | 300 to 2,600 GB | Off-site recording required, strong upload available |
| Event-based upload to a monitoring centre | ~5 to 30 GB | Professionally monitored sites, alarm verification |
| On-demand live view, local recording | ~2 to 10 GB | Small sites, owner-monitored cameras |
Most installations end up as a mix: local recording at full resolution, event clips to the monitoring centre, and a low-resolution substream for live checks. That combination keeps the evidence quality high and the data bill predictable.
Is a 4G CCTV camera connection fast enough?
For event-based monitoring and live checks, a well-placed 4G CCTV camera connection is sufficient on most sites. Continuous streaming of several high-resolution cameras depends on sustained upload, day and night. On a symmetric, upload-first Weconnect profile, the uplink is provisioned as a first-class direction and stays at the same level over the life of the contract, which gives continuous streaming a stable base. Radio conditions at the camera position still set the ceiling, so three measures improve the margin:
- External antenna. A camera or router inside a metal enclosure or cabin loses a large part of its signal. An external antenna at height often makes the biggest difference.
- Multi-network SIM. With nicht gesteuerter Multi-Netzwerk-Zugriff, the router connects to the network with the strongest signal at that exact position and can move to another network when the first one weakens.
- Streams matched to the upload. If a site measures 6 Mbps of reliable upload, four cameras at 4 Mbps each will fail. Four cameras at 1 Mbps with event clips on top will run.
Remote access: why port forwarding fails on 4G
Many installers discover this on day one: the camera works, and the monitoring software still cannot reach it. Mobile networks usually place devices behind carrier-grade NAT (CGNAT), a shared address that blocks incoming connections. Port forwarding, the standard method on a fixed line, has nothing to forward to.
Fixed public IP: the standard for remote CCTV monitoring
A fixed public IP is a permanent, publicly routable address assigned to the SIM, so the camera, recorder or router is reachable at the same address every time. It removes the CGNAT barrier completely: the VMS, the alarm receiving centre or the installer’s service desk connects directly to the site, and no tunnel or third-party platform sits in between. That is why a fixed public IP is the most common solution for remote CCTV monitoring, and used more often than a VPN. Weconnect delivers fixed public IPs on its CCTV SIMs as a standard option, and access can be restricted to the monitoring centre’s own addresses with the recorder’s firewall rules.
Cloud relay and dedicated VPN as alternatives
Two other routes exist for specific situations. Many camera brands offer a cloud relay, where the camera connects outward to the manufacturer’s platform; it works without extra network set-up and ties the site to that platform. A dedicated VPN places the camera connection inside the security company’s own network, which suits organisations that want all sites in one private network. Weconnect also supplies dedicated VPN and private APN options, and they combine with a fixed public IP where a site needs both.
Choosing a data plan for a camera system
With the monthly total known, the plan choice follows from the monitoring mode:
- Event-based and on-demand sites. A plan billed on actual usage fits best. Data use is low and varies with the number of alarms, so paying per GB used keeps the cost in line with reality.
- Continuous streaming sites. Large volumes call for a high-volume plan or an unlimited SIM. Weconnect also offers local SIM contracts from hundreds of gigabytes up to 1,000 GB per SIM for data-heavy locations.
- Mixed estates. Data pooling is available on all CCTV plans, so a site with a busy month draws from the same shared allowance as the quiet ones.
- Sites that must stay online. Plans can be combined for redundancy: a usage-based SIM next to an unlimited SIM, or two SIMs on different networks in a dual-SIM router, so the cameras keep reporting when one network has a problem.
Whatever the plan, set a usage alert. A camera that suddenly doubles its data use usually means a changed setting, a tree growing into the view or a firmware update that reset the compression. The alert shows up before the bill does.
For rapid-deploy towers and cameras that move between sites, the same principles apply, with extra attention to activation and suspension between jobs. That scenario is covered in our article on Temporäre und mobile Videoüberwachung. The broader question of which SIM type suits which camera installation is covered in our guide to die richtige SIM-Karte für CCTV auswählen.
Managing data across a camera fleet
An installer or security company with fifty 4G sites needs to see which ones are online and which ones are consuming more than expected. Through the Plattform für Konnektivitätsmanagement, every SIM is visible in one overview, with usage per SIM, alerts on thresholds and the option to block data use above a set limit. Cost places separate customers or projects, so each client’s connectivity can be invoiced correctly. A site that goes quiet shows up in the platform before the client notices a black screen. For security companies with sites in several countries, Weconnect SIMs support permanent roaming by default, as part of how the service is designed and contracted.
Häufig gestellte Fragen
How much data does a 4G CCTV camera use?
It depends on the bitrate. A camera streaming continuously at 2 Mbps uses about 0.9 GB per hour, 21.6 GB per day and around 650 GB per month. The same camera sending only event clips to a monitoring centre uses roughly 5 to 30 GB per month.
How do you calculate CCTV data usage?
Multiply the stream bitrate in Mbps by 0.45 to get GB per hour, then by 24 for a day and by 30 for a month. Repeat for each camera and add them up. Use the bitrate shown in the camera or recorder settings, since it varies with resolution, frame rate, compression and scene activity.
What is remote CCTV monitoring?
Remote CCTV monitoring is watching, recording or verifying camera footage from a location away from the site, such as an alarm receiving centre or a cloud platform. It can run as continuous streaming, event-based upload when an alarm triggers, or on-demand live viewing with local recording.
Is 4G good enough for security cameras?
Yes, for most event-based and on-demand monitoring. Continuous streaming of several high-resolution cameras needs strong, sustained upload, which is why Weconnect builds its CCTV connections with symmetric speed, fixed routing and no throttle on the uplink. An external antenna and a multi-network SIM add further margin.
How can I reduce 4G security camera data usage?
Record locally at full resolution and send only event clips and a low-resolution substream over 4G. Use H.265 compression, lower the frame rate to 10 to 15 frames per second where that is acceptable, and set usage alerts so unexpected increases are caught early.
Why can’t I reach my 4G camera remotely?
Mobile networks usually use carrier-grade NAT, which blocks incoming connections, so port forwarding has no effect. The standard solution is a fixed public IP on the SIM, which makes the camera or recorder reachable at one permanent address for remote CCTV monitoring. A cloud relay or a dedicated VPN are alternatives for specific set-ups.
Nächste Schritte
Weconnect connects CCTV systems over non-steered multi-network 4G and 5G across 700+ networks in 195 countries, with symmetric upload, fixed public IP for remote access and central management for camera fleets. Whether you run event-based monitoring for dozens of sites or continuous streaming at one high-risk location, we help you calculate the data and choose the plan that fits, on security and surveillance connectivity built for upload. For the SIM choice itself, see our guide to die richtige SIM-Karte für CCTV auswählen. Challenge us with your connectivity requirements. Direkte Antwort innerhalb von 4 Geschäftszeiten.