How Much Data Does a Camera Trailer Use? Upload Bandwidth, Monthly Volume and Coverage

Two bills surprise hire fleets in the first quarter of a contract. One is the callout for a unit that went dark. The other is the mobile data overage. Both trace back to the same gap: nobody modelled the network before the trailer went out. This guide answers how much data does a camera trailer use, and the two questions that sit underneath it — what the site’s upload can actually carry, and what the unit does when the signal drops. Network capacity itself belongs to the carriers. What happens to a trailer sitting on that network is the equipment maker’s ground, and it is where this guide stays. The Optraffic team builds surveillance trailers and camera trailers with 4G/5G routers as standard equipment, which puts the router, cameras and recorder on one bench during testing rather than across three vendors.

Upload Bandwidth for Remote CCTV Is the Real Constraint, Not Download Speed

Mobile networks are built around downloads. A camera trailer does the opposite, and that inversion is where most connectivity assumptions break.

Upload bandwidth for remote CCTV decides how many live streams a site can serve at once, and how fast an operator can pull historical footage. The constraint is not the network alone. A trailer carries several cameras behind a single router, so every stream contends for the same upload path, and a bench signal test with one camera running tells you very little about the same site with four.

Two device-side behaviours follow from that, and both show up in fleet reports rather than in carrier coverage maps:

• Contention scales with camera count, not site quality. A site that supported two streams last season can stall when a fourth camera is added to the same trailer.
• Retrieval competes with live view. Pulling an hour of recorded footage while streams run degrades both, which is why scheduled retrieval beats ad-hoc retrieval on busy units.

The Only Setting That Moves the Bill

Resolution, frame rate and stream count all change upload demand. They do it through one variable, so specify that variable directly: the bitrate of each stream, in Mbps. Encoder settings are a means of hitting a bitrate target. The bitrate is what the carrier charges for.

Most systems carry a high-quality stream for local recording and a lighter sub-stream for remote viewing. Only the streams that leave the trailer appear on the bill.

Camera Trailer Data Usage Per Month: One Constant Does the Whole Calculation

Fleets estimate from camera count. That is the wrong input. Work from bitrate instead, using a single conversion.

1 Mbps of continuous upload ≈ 324 GB per 30-day month

1 Mbps = 0.125 MB/s → 0.125 × 86,400 = 10.8 GB per day → × 30 = 324 GB

Everything else is multiplication. Camera trailer data usage per month equals total uploaded bitrate × 324, where total bitrate is the sum of every stream actually leaving the site.

Continuous Upload, Per Stream

Per-stream bitrate	Per day	Per 30-day month	Four such streams, monthly
0.25 Mbps	2.7 GB	81 GB	324 GB
0.5 Mbps	5.4 GB	162 GB	648 GB
1 Mbps	10.8 GB	324 GB	1.30 TB
2 Mbps	21.6 GB	648 GB	2.59 TB
4 Mbps	43.2 GB	1.30 TB	5.18 TB

Read the right-hand column before quoting a monitored contract. A full-quality stream from each camera, uploaded around the clock, reaches terabytes per month on a mobile plan. That is why continuous upload at recording quality is rare on trailers, and why the sub-stream bitrate is the number to specify.

Event-Driven Upload, for Comparison

Alert-only architectures do not scale with time. They scale with event count.

Clip size (MB) ≈ bitrate (Mbps) × clip length (s) ÷ 8

A 10-second clip at 2 Mbps is about 2.5 MB. Two hundred events a day is roughly 500 MB per day, or about 15 GB per month. That is one to two orders of magnitude below continuous upload of the same stream.

The Crossover Rule

The decision reduces to one comparison:

Uploaded bitrate × 324 × (cost per GB) versus the cost of retrieving footage on request.

If the monthly figure exceeds the data allowance, the architecture is wrong for the site, not the plan. Reduce uploaded bitrate, reduce the number of streams that leave the trailer, or move to event-driven upload with retrieval on demand.

Architecture	Monthly volume driver	Typical order of magnitude	Behaviour when signal drops
On-board recording, alerts only	Events per day	Tens of GB	Records locally, alerts queue and deliver on reconnection
On-board recording, retrieval on request	Retrieval frequency	Tens to low hundreds of GB	Records locally, retrieval queues until reconnection
Continuous upload of sub-streams	Sub-stream bitrate × stream count	Hundreds of GB	Buffers, then risks gaps if the outage runs long
Continuous upload at recording quality	Full bitrate × stream count	Terabytes	Most exposed to outage and overage

Most sites need reliable local recording and fast access when something happens, not a permanent outbound feed. That choice sits alongside the wider storage decision, which the Optraffic team covers in cloud storage versus on-board recording for surveillance trailers.

Check Mobile Network Coverage for Surveillance Trailers Before the Unit Leaves

Coverage is the one variable a fleet can verify in advance and routinely does not.

Ofcom publishes a free mobile coverage checker covering all four UK networks, indoor and outdoor, for 4G and 5G. Entering the site postcode before dispatch takes a minute. Confirming mobile network coverage for surveillance trailers at the planning stage prevents the most avoidable callout in the category.

Why a 4G Fallback Still Matters on a 5G Router

Newer is not automatically better here. High-band 5G delivers large capacity in dense urban areas but travels shorter distances and penetrates obstacles less well. Lower-band 4G often reaches further into rural diversions, quarries and remote compounds.

A router that supports both simply uses whatever the site offers. On a remote site that usually means 4G, and the deployment still works.

The reverse case is now a real fleet problem. UK operators have effectively completed their 3G switch-off, and the Government published a voluntary 2G switch-off charter in March 2026, with Ofcom setting out its expectations of mobile providers through the transition. Older equipment that depended on those networks has no fallback left, and the failure is silent: the unit powers up, the cameras record, and nothing reaches the operator. Router generation is an asset-register field, not a site-survey field. The House of Commons Library briefing sets out the operator timetables. Fleets holding legacy units should audit router generation before the next season, not after a site goes silent.

What Happens When a Camera Trailer Loses Signal

This question decides whether an outage is an inconvenience or an evidence gap.

What happens when a camera trailer loses signal depends entirely on where recording happens. A unit recording on board keeps recording. Nothing is lost; remote viewing pauses and resumes. A unit dependent on continuous upload loses whatever it could not send.

Two practical consequences follow:

1. Evidence survives outages when recording is local. This is the stronger position for any site where footage may be needed later.
2. Alerts still queue. Notifications generated during an outage deliver once the connection returns, so the operator gets the history rather than silence.

Coverage gaps also interact with power, which is the part a connectivity vendor has no reason to model. A router hunting for a marginal signal transmits at higher power and retries more often, so it draws more than one resting on a solid connection. On a solar unit that draw comes out of the same battery the cameras use, and it bites hardest in the months when yield is already low. A weak-signal site is therefore a power problem as much as a bandwidth problem. That interaction runs through the sizing method in will a solar camera trailer run through winter.

SIM Management for a Camera Trailer Fleet Is a Cost Problem at Scale

One unit is a phone contract. Thirty units is a procurement decision.

SIM management for a camera trailer fleet carries three recurring costs that rarely appear in a first-year budget:

• Per-SIM line rental, multiplied by fleet size and paid whether the unit is on hire or in the yard.
• Overage charges when a site streams more than planned.
• Per-unit software licences, where the supplier charges monthly for remote access on top of the data plan.

The third is avoidable. Optraffic supplies its fleet platform with the equipment at no additional cost, so a hire company watching thirty units pays no more for software than one watching three. Data still costs what the carrier charges, but the licence layer disappears.

Pooled data plans handle the second cost better than per-SIM allowances, because utilisation varies wildly between deployments. Fleet-level visibility of which units are consuming most is what makes pooling work, and that view sits in the same platform as connection state. Hire fleets running units across scattered sites will find the operational side in camera trailer fleet management across multiple sites.

A Sixty-Second Check Before the Unit Leaves the Yard

Four steps, in order. They fit on a dispatch sheet.

1. Check coverage at the site postcode. Compare all four networks, outdoor, 4G and 5G. Record which network the SIM in that unit uses.
2. Confirm the router generation. Anything without 4G has no network left to fall back to.
3. Set the uploaded bitrate. Decide which streams leave the trailer, note the sub-stream bitrate, and multiply by 324 for the monthly figure.
4. Check that figure against the pool. Compare against remaining allowance across the fleet, not against a per-SIM allowance.

Steps three and four are the two that get skipped, and they are the two that produce the overage.

Conclusion

Network planning costs a minute per deployment and saves a callout. Check coverage at the postcode, confirm the router generation, multiply uploaded bitrate by 324 for the monthly figure, and pool data across the fleet rather than per unit.

Optraffic builds the trailer, cameras, recorder and 4G/5G router as one specified platform, so stream settings and connection behaviour are matched rather than assembled from separate vendors. Fleet software ships with the equipment, which keeps connection state and consumption visible at no extra cost. Broader deployment context sits in the guide to mobile solar surveillance for remote sites, and camera coverage sizing in how far a security camera trailer can see. To model connectivity for a specific contract, contact the Optraffic team with the site locations and camera plan.

FAQ

How much data does a camera trailer use in a typical month?

Multiply the total uploaded bitrate in Mbps by 324 to get GB per 30-day month. A single 1 Mbps sub-stream uses about 324 GB; an alert-only configuration typically uses tens of GB. Model camera trailer data usage per month from bitrate, not from camera count.

Does a camera trailer need 5G to work properly?

No. Most deployments run on 4G, and rural sites often receive better 4G than 5G. A router supporting both uses whichever the site provides.

Can a camera trailer work with no mobile signal at all?

It records locally and stores footage on site. Remote viewing and alerts pause until a connection returns. Some sites add external antennas to reach a usable signal.

How do I check coverage before dispatching a unit?

Use the Ofcom checker with the site postcode and compare all four networks. Verifying mobile network coverage for surveillance trailers in advance removes the most common avoidable callout.

What reduces data use on a weak site?

Lower the remote viewing stream resolution and frame rate, and reduce the number of permanent live feeds. Managing upload bandwidth for remote CCTV remotely avoids a site visit.