Guide · CCTV over Starlink or wireless
Rural CCTV: getting cameras working over Starlink or a wireless link.
Cameras on a rural property come down to two questions: how much do they use, and where does the footage go? This guide covers the bandwidth each camera needs, the upload and CGNAT catch that trips up remote viewing, why local recording beats cloud on a rural connection, and how a wireless bridge keeps the feed steady.
Last updated 4 July 2026 · by Alien IT Solutions
How much bandwidth each camera needs
The megapixels on the box are marketing. The number that matters is bitrate: how many megabits per second the camera pushes while it records. A typical 4MP camera at sensible settings streams around 4 to 6 Mbps on its main stream. An 8MP camera pushed hard might do 8 to 12. That is the whole load a camera puts on the link.
Cameras add up in a straight line. Four cameras at 6 Mbps each is 24 Mbps, steady, whenever they record. That is the figure the network between the cameras and the recorder has to carry, and it is a lot smaller than most people fear. Count your cameras at those numbers before you buy the gear, not after.
Where the footage goes changes everything
The bandwidth a camera uses on your own network is one thing. What it sends up the internet is a completely different, much smaller thing, and getting that split right is the whole game on a rural connection.
The numbers that matter
Local recording keeps it off your internet
Here is the part that surprises people. When your cameras record to a box on your own network, a small recorder or a computer at the house, that footage never touches the internet at all. It stays on the local network the whole time. Recording twelve cameras around the clock uses none of your Starlink or wireless data, because none of it goes up the pipe.
Cloud recording is the opposite. Every minute of footage from every camera has to climb your internet upload, the thin pipe on most rural connections, and it is a subscription per camera, forever. On a rural plan that is a double cost: you pay the monthly fee, and you spend upload you do not have to spare. A recorder on your own network is bought once and holds weeks of footage.
The rule is simple. Record locally, and use the internet only for the occasional remote look. Own the footage, do not rent it. The connection you already pay for, whether that is Starlink, NBN or a wireless link, stays free for everything else.
Watching from your phone: the upload and CGNAT catch
Live view when you are away is where rural connections throw their curveball. It is not about bandwidth, it is about how the connection is addressed.
Upload is the tight pipe
Remote viewing sends video up your internet upload, not down. Rural plans are lopsided, plenty of download and a fraction of the upload. One or two remote streams at a sensible bitrate fit, a dozen at full quality do not. Use a lower substream for the phone and keep the good footage local.
CGNAT blocks the old trick
Starlink and many 4G plans put you behind CGNAT, a shared address. It quietly kills the old habit of opening a port to your recorder, because there is no address of your own to open a port on. This is the number one reason a camera app that worked in town stops working in the bush.
The fix is a relay, not a port
Modern recorders and camera apps connect out to their own cloud relay, so your phone reaches them without any fixed address or port forwarding. Pick gear that works this way and CGNAT stops mattering for viewing. The Starlink Rural guide covers the CGNAT side in full.
Viewing and recording are separate
Losing remote view for an hour does not lose footage. The cameras keep recording to the local box the whole time, and the phone reconnects when the internet does. Never tie your evidence to your internet being up.
Why the bridge keeps the feed steady
A rural camera at the gate or a far shed is often too far to trench cable to. A point-to-point wireless bridge carries the camera streams back to the recorder at the house without a trench, over the trees rather than under the paddock. This link is on your own network, so the steady camera feed never touches the internet and never competes with it.
That separation is why the feed stays smooth. Latency over a point-to-point hop is a few milliseconds, nothing for live view or recording, and a properly built bridge over a clear path carries hundreds of megabits, so a handful of cameras barely dent it. The internet connection, Starlink or otherwise, does one job only: carrying remote viewing out when you ask for it. The two never fight over the same pipe.
A bridge lives or dies on the path. The two antennas need a clear line of sight and Fresnel clearance, solid mounts that do not flex in wind, and signal margin so a wet week costs nothing. Where trees or a hill block the way, a mast or relay clears it. A site survey works all this out before anything is quoted.
Putting it together on a rural property
Four decisions cover most camera jobs over Starlink or a wireless link.
Add up the camera bitrates
Total the main-stream Mbps of every camera. That is the load on the local network, and a sized bridge swallows it with room to spare. It is not the load on your internet.
Record to a local box
Put a recorder on the house network so footage stays off the internet entirely. Cameras with an SD card slot can buffer locally and backfill if a link blips.
Sort remote viewing around CGNAT
Choose a recorder or app that reaches out to its own relay, so a shared Starlink or 4G address does not block your phone. Keep the phone on a lower substream.
Carry the far cameras on a bridge
Link the gate or shed back to the house with a point-to-point bridge on a clear path, so the feed is steady and independent of the internet.
An honest word on limits
Wireless and Starlink are both good tools, and neither is magic. Heavy rain can shave signal off a long bridge, so we size in headroom. A link that drops for a minute in a violent storm and comes straight back is normal, and cameras with an SD card slot ride through it. Remote viewing depends on your internet being up, which is exactly why the recording sits local and does not.
CCTV is a safety and wellbeing aid, not a guarantee. No camera catches every event, no link is up every second of every year, and footage is only as useful as the path, the power and the recording behind it. Built with margin and recorded locally, a rural camera system runs for months untouched and keeps the footage you need. That is the honest promise, and it is a good one.
Who builds it
Long Range WiFi is the long-range wireless service of Alien IT Solutions, an Australian IT and networks company with more than 18 years running wireless links and camera systems in the places other installers will not drive to. Alien IT surveys the path, sizes the link, sets up local recording, and sorts remote viewing around CGNAT, and brings in licensed electrical and rigging trades where a job needs them.
For the connection itself, see Starlink Rural, which also covers CGNAT in detail. For property-scale rural networking across paddocks, gates and multiple buildings, see Paddock Networks; for remote sensing, Rural IoT. All are services of Alien IT Solutions.
Questions people ask
How much bandwidth does each CCTV camera need?
A typical 4MP camera at sensible settings streams around 4 to 6 megabits per second while it records, and an 8MP camera pushed hard might do 8 to 12. The megapixels on the box do not set the load, the bitrate setting does. Add your cameras up at those numbers and you have the real figure the network needs to carry between the cameras and the recorder.
Does recording CCTV use up my Starlink data?
Not if you record locally. When cameras record to a box on your own network, the footage never touches the internet at all, so it uses none of your Starlink or wireless plan. Only remote viewing and cloud recording send footage up the internet, and that is the part that leans on your upload speed. Record locally and watch remotely only when you need to.
Can I watch my cameras from my phone when I am away?
Usually yes, but rural connections add a catch. Starlink and many 4G plans put you behind CGNAT, a shared address that stops the old trick of opening a port to your recorder. The fix is a recorder or camera app that connects out to its own cloud relay, so your phone reaches it without a fixed address. Starlink Rural covers the CGNAT side in detail.
Should I record CCTV locally or to the cloud?
Record locally on a rural connection. A recorder on your own network holds weeks of footage, is bought once, and never fights your internet upload. Cloud recording is a subscription per camera and every minute of footage has to climb your uplink, the thin pipe on most rural plans. Keep the footage local and use the cloud only for the occasional remote look.
Is a wireless bridge or Starlink better for a stable camera feed?
They do different jobs. A point-to-point wireless bridge carries the camera streams from the gate or shed back to the recorder at the house, on your own network, with a few milliseconds of latency. Starlink or another connection is what carries remote viewing out to the internet. The steady feed between cameras and recorder rides the bridge, not the internet, which is why it stays smooth.
Who sets up CCTV over a rural link?
Long Range WiFi is the long-range wireless service of Alien IT Solutions, an Australian IT and networks company with more than 18 years of experience running wireless links and camera systems in rural Australia. Alien IT surveys the path, sizes the link, sets up local recording and sorts remote viewing around CGNAT, and brings in licensed trades where a job needs them.
Get your cameras working over the link you have.
Tell us how many cameras, where they need to go, and what connection is at the house. Alien IT will size the link, sort the recording and come back with a plan and a price.
Get a quote