How Much Mobile Data Does Remote CCTV Viewing Use?
Essential Security Supplies
Remote CCTV data use depends on the total bitrate being received and how long viewing lasts. As a decimal-unit estimate, one stream averaging 1 Mbps uses about 450 MB in an hour, before protocol overhead and other traffic. Four independent 1 Mbps streams viewed together use about 1.8 GB per hour. These are calculated examples, not measured figures for a particular camera or app.
For NZ installers specifying remote viewing over mobile connections, calculate the expected use, then measure the commissioned system. Camera resolution alone cannot tell you the data allowance required. The selected stream, number of views, playback habits, cloud traffic and actual network path all matter.
Separate the phone's allowance from the site's allowance
Remote viewing normally transfers footage out of the site and into the viewing device. If the recorder uses fibre and the phone uses mobile data, the video contributes to the phone's cellular usage. If the recorder connects through a 4G or 5G router, the site's SIM carries the outbound stream too. Where both ends are cellular, both allowances can be affected by the same session.
Watching through Wi-Fi moves the phone's traffic to that Wi-Fi connection; it does not remove traffic from a cellular connection serving the camera site. Similarly, an on-site camera-to-NVR recording stream should not be counted as internet traffic when it stays entirely on the LAN. Cloud upload, remote viewing and local recording need separate entries in the data budget.
Use carrier and router counters to establish how your particular service meters traffic. Do not assume every plan counts upload, download, rounding or reporting periods identically.
Calculate video data from bitrate and time
Data in GB = average total bitrate in Mbps × viewing time in hours × 0.45.
The conversion uses eight bits per byte, 3,600 seconds per hour and decimal gigabytes. For MB over a shorter session, use Mbps × minutes × 7.5. These equations estimate the encoded stream payload. Add measured allowances for transport overhead, audio where not already included in the bitrate, background services and the difference between configured and observed bitrate.
| Average stream bitrate | 10 minutes | 1 hour | 30 days at 1 hour/day |
|---|---|---|---|
| 0.25 Mbps | 18.75 MB | 112.5 MB | 3.375 GB |
| 0.5 Mbps | 37.5 MB | 225 MB | 6.75 GB |
| 1 Mbps | 75 MB | 450 MB | 13.5 GB |
| 2 Mbps | 150 MB | 900 MB | 27 GB |
| 4 Mbps | 300 MB | 1.8 GB | 54 GB |
All table values are illustrations excluding overhead, not recommended camera settings. A displayed value of 512 kbps may be implemented using a manufacturer's particular unit convention. Read the interface and manual rather than silently substituting 0.5 Mbps for every value labelled 512.
A worked viewing schedule
Suppose an operator opens four independent streams averaging 0.5 Mbps each for ten minutes a day. The total bitrate is 2 Mbps, so the calculated use is 2 × 10 × 7.5 = 150 MB per day. Over 30 days that is 4.5 GB before additional traffic. If the same four streams average 2 Mbps each, the identical schedule becomes 18 GB.
This example assumes the client receives four separate streams. Some viewing platforms generate a composite stream, adapt quality automatically or reuse server-side sessions. Measure the actual arrangement before multiplying camera count. For separate viewers receiving independent copies, include each active copy; a cloud relay may change the site's upload pattern.
Use the stream intended for the viewing task
A recording stream and a remote preview stream can serve different purposes. TP-Link's VIGI stream configuration guide documents separate main-stream and substream settings. A lower-bitrate preview can reduce routine viewing traffic without necessarily lowering the local recording stream, provided the chosen system supports independent configuration.
Confirm what the app actually requests in single-camera view, multi-view, full screen and playback. Labels such as clear, fluent or HD are not a universal bitrate specification. Selecting a camera tile may switch to a higher-quality stream; recorded playback may use the stored recording rather than the preview setting.
When reviewing the UniView camera and network range, treat stream configuration and client behaviour as specification questions. This guide does not assert that the illustrated camera has been tested with the other equipment shown.
Plan for changing scenes and bitrate controls
A configured maximum is not always the average traffic rate. Motion, image noise, lighting, frame rate, compression and scene detail can change the encoded bitrate. Axis explains these dependencies in its hardware planning guidance. Check an occupied entrance and a difficult night scene, not just a quiet daytime image.
Axis's bitrate-control white paper also explains why limiting bitrate can compromise useful detail. Do not promise a fixed saving from switching codec or lowering frame rate. Assess the resulting image for the task, and confirm that cameras, recorder, app and viewing device support the chosen stream format.
A useful remote preview need not carry all the detail required for evidence review. Keep that distinction explicit in the handover. If the operator needs to read a specific identifier or assess fast movement remotely, test that task rather than optimising solely for the smallest data counter.
Include traffic that occurs outside live viewing
- Recorded playback: footage still has to cross the remote connection when reviewed off site.
- Clip downloads: exported files add transferred bytes, even if live viewing is infrequent.
- Cloud recording: ongoing uploads can exceed occasional phone-viewing traffic and require their own calculation.
- Event clips and thumbnails: frequent events can accumulate traffic without an operator opening the live view.
- Other site users: a shared cellular router may also carry office devices, updates or other applications.
- Retries and reconnections: weak links can make simple payload estimates less representative of metered usage.
For scale, a hypothetical continuous 1 Mbps upload is 10.8 GB per day, or 324 GB over 30 days, before other traffic. That is a different use case from ten minutes of daily viewing. Do not size a continuously uploading installation from an occasional-viewing example.
The TP-Link NVR range provides a starting point for recorder selection. Check supported remote sessions, stream handling and export behaviour for the selected recorder and client versions.
Measure usage before setting the final allowance
- Record the camera, recorder, app and firmware versions, active stream settings and number of visible cameras.
- Identify the counters being tested: phone cellular usage, dedicated site router traffic or carrier-reported consumption. Note their update delays and reporting units.
- Take a baseline reading. Where practical, record a comparable idle period so background traffic is visible.
- Run a timed viewing session on the intended connection, with Wi-Fi disabled on the phone if testing its cellular allowance.
- Take another reading after counters update. Calculate the difference, recording whether unrelated traffic could have contributed.
- Repeat for multi-view, full screen, playback, clip export and the expected number of simultaneous users.
- Retest busy and low-light scenes, then monitor several representative days before finalising alerts and operating guidance.
As a hypothetical measurement, a counter increase of 120 MB over ten minutes corresponds to about 1.6 Mbps of metered traffic: 120 ÷ 75. It is not proof of a 1.6 Mbps camera setting because the counter may include overhead and other activity. Retain both the calculated payload budget and the measured operational result.
Check upload capacity as well as the data allowance
Data allowance describes volume; available upload throughput affects whether footage can leave the site smoothly. A large allowance cannot fix an overloaded uplink. Test at the time the service is used and with the intended concurrent sessions. Leave operational room for other required traffic and variation in mobile performance.
If a camera is unreachable locally as well as remotely, follow the IP camera offline troubleshooting guide. Establish whether the failure is in the local recording path or external connection before adjusting video quality.
Frequently asked questions
How much mobile data does one hour of CCTV viewing use?
One stream averaging 1 Mbps transfers about 450 MB per hour before overhead. Add the bitrates of independently received streams, then multiply by viewing time. Actual metered use also includes relevant additional traffic.
Does recording to an NVR use mobile data continuously?
Not when camera-to-NVR traffic stays on the local network. Mobile data is used when traffic crosses a cellular connection, such as remote viewing, cloud upload or off-site clip transfer.
Will the substream setting reduce playback data too?
Not necessarily. Remote live preview and recorded playback may use different streams. Confirm which recording the client retrieves and measure playback separately from live viewing.
Does watching over Wi-Fi stop the site's SIM using data?
No. Wi-Fi can avoid using the phone's cellular connection, but the site's SIM still carries footage if the camera site uses cellular internet for that remote session.
Build the viewing requirement into the trade specification
Tell Essential Security Supplies the camera count, expected viewing schedule, concurrent users, connection type and required remote detail. Use the surveillance systems collection to start a specification discussion, then confirm the final data budget against the commissioned system rather than a generic per-camera estimate.
