Analogue / HD-over-coax camera vs IP camera.
An analogue or HD-over-coax camera sends video down coaxial cable and is digitised at the recorder; an IP camera encodes on board and sends a stream over structured cabling, with PoE carrying power and data on one run.
Quick answer — when to choose Analogue / HD-over-coax camera or IP camera
Quick answer
An analogue or HD-over-coax camera sends video down coaxial cable and is digitised at the recorder; an IP camera encodes on board and sends a stream over structured cabling, with PoE carrying power and data on one run. For new work an IP design is the usual answer, because resolution headroom, on-camera analytics, flexible placement and integration all follow the network. Analogue earns its place on retrofit, where sound coax already exists and re-cabling an occupied building is the genuine constraint. The deciding factors are the cabling you have, the resolution the scene actually needs, and whether the cameras are allowed on the network — not the camera type in the abstract.
When to use
You are setting the camera and transmission technology for a surveillance system and want it matched to existing cabling, resolution requirements and the site's network policy.
When not to use
The camera technology is already fixed and the open question is the recorder or the storage — that is a recorder-architecture or retention question instead.
Option A
Analogue / HD-over-coax camera
A camera that sends video as a signal down coaxial cable to a recorder that does the digitising and encoding, with power usually run as a separate pair.
Choose Analogue / HD-over-coax camera when
- Serviceable coaxial cabling already exists and re-cabling the building is the real cost
- The camera count is modest and the required resolution is bounded
- The site wants cameras kept entirely off the data network as a matter of policy
Option B
IP camera
A camera that digitises and encodes on board and sends a stream over structured cabling, taking power from the same run over PoE and appearing on the network as a device.
Choose IP camera when
- Structured cabling is being installed, or can be run to every camera position
- Higher resolution, wide dynamic range or on-camera analytics are part of the requirement
- The system has to grow, federate across sites, or integrate with access control and a control room
Side by side
The fields that decide it
| Dimension | Analogue / HD-over-coax | IP |
|---|---|---|
| Cabling | Coaxial, with power usually run separately | Structured cabling, with PoE carrying power and data |
| Where encoding happens | At the recorder | On the camera, before the network |
| Resolution headroom | Bounded by the transmission format in use | Scales with the camera and the available bandwidth |
| Typical run length | Long runs on coax without active equipment | Bounded by the structured-cabling channel limit; extenders or fibre beyond it |
| On-camera analytics | Limited; processing sits at the recorder | Available on capable models, running at the edge |
| Network exposure | Cameras are off the data network by construction | Cameras are network devices and need segmentation and hardening |
| Integration | Largely self-contained | Integrates with access control, analytics platforms and control-room systems |
| Typical fit | Retrofit onto serviceable existing coax | New build, fit-out, and systems expected to grow |
HD-over-coax formats carry high-definition video on existing coaxial cable and are the reason analogue remains a live option rather than a legacy one. What they do not carry is the on-camera processing and network integration an IP design brings.
Before the drawings freeze
What changes at design stage
What changes at design stage
- Survey the existing cabling before the camera technology is chosen. Sound, correctly routed coax is the strongest argument for staying analogue, and its absence usually settles the question toward IP.
- Set the resolution requirement per position from what the scene has to yield — recognition, identification or general observation — rather than picking a headline sensor figure and working backwards.
- Check the site's network policy early. Where cameras are not permitted on the corporate network, the design needs either a segregated network or a coax-based answer, and that is a design decision rather than a commissioning surprise.
Infrastructure implications
- An IP design makes the switch, the PoE budget, the uplinks and the network segmentation part of the surveillance package rather than someone else's problem.
- Structured-cabling channel-length limits apply to camera runs; positions beyond the limit need fibre or an extender designed in, not improvised.
- Recorders, switches and their storage are critical loads in both designs and need power protection planned with the rest of the security layer.
Getting it built
Coordination & integration
Coordination for architects & consultants
- Agree network ownership, addressing and segmentation with the client's IT function before commissioning; surveillance arriving unannounced on a corporate network is a predictable dispute.
- Coordinate camera positions with the containment and cabling design early, because positions settled after containment is fixed are the usual source of rework.
- Confirm retention requirements at design stage — they size storage regardless of which camera technology is chosen.
Integration considerations
- IP cameras are network devices, which is what makes them integrate readily with access control, analytics and a control-room view — and equally what makes segmentation, credential management and firmware discipline part of the design.
- Analogue cameras are self-contained, which limits integration but also removes an attack surface; on some sites that is the deciding factor rather than a limitation.
- Hybrid recorders that accept both exist, but the specific model's capability has to be confirmed rather than assumed from the product category.
Typical project fit
Where each is the right answer
Decision summary
- Occupied building with sound existing coaxial cabling and modest resolution needs
- Favours Analogue / HD-over-coax cameraStay with HD-over-coax — reusing serviceable coax avoids re-cabling an occupied building, and the resolution required is within what the format carries.
- New building or full fit-out with structured cabling being installed
- Favours IP cameraAn IP design — the cabling is going in anyway, and IP brings resolution headroom, PoE simplicity, on-camera analytics and a growth path.
- Phased estate upgrade with mixed cabling and a growing camera count
- Favours either optionUsually a staged migration: retain coax where it is sound, run IP on new and refurbished areas, and confirm the recording platform holds both during the transition rather than assuming it will.
From the field
Common mistakes
- Assuming IP automatically means better footage. Image quality comes from the sensor, the lens, the lighting and the configuration; a poorly lit scene is a poorly lit scene at any resolution.
- Putting IP cameras on the general corporate network without segmentation, and inheriting an avoidable security exposure along with the convenience.
- Specifying IP cameras for positions beyond the structured-cabling channel limit and resolving it on site rather than in the design.
- Discarding sound existing coax on principle, and spending the budget on re-cabling that the resolution requirement never justified.
- Leaving default credentials and shipped firmware in place on network cameras, which is the most common and most avoidable failure in an IP deployment.
TechnoGuru engineering perspective
How we specify it
We treat this as a cabling, lifespan and network-policy question rather than a preference. On new work the structured cabling is being installed anyway, so an IP design is normally the proportionate answer — resolution headroom, power and data on one run, on-camera analytics and a growth path. On retrofit the arithmetic changes: where existing coax is sound and the scene does not demand more resolution than HD-over-coax carries, reusing it is often the more responsible engineering decision than re-cabling an occupied building. What we will not do is treat an IP camera as a substitute for lighting, or put cameras on a client's network without agreeing segmentation and hardening first. Camera positions, coverage geometry and network topology stay off public surfaces.
Where this connects
Services, sectors, tools & proof
Relevant services
Relevant sectors
Relevant tools & calculators
Related comparisons
Further reading
Selected proof
- PM Ekta Mall, Guwahati
- Arunachal Pradesh Legislative Assembly
- Multi-Purpose Hall, Arunachal Pradesh Assembly Complex
- Cabinet Conference Room, Arunachal Pradesh Secretariat
Owner-approved, publicly-verifiable project references. No quantities, pricing, layouts or restricted detail are shown.
· How we approach this on a live brief
On a real security & surveillance brief the choice between Analogue / HD-over-coax camera and IP camera usually turns on a few of the fields above, not every row in the table. Share the drawings, the BOQ or the constraints and a project lead will name the one we would specify for the building — with the engineering reason set out in writing.
· Frequently asked
IP vs analogue camera — which surveillance camera type to specify —
what people ask first.
What is the difference between an IP camera and an analogue camera?
The difference is where the video is turned into a digital stream and what cable carries it. An analogue or HD-over-coax camera sends a signal down coaxial cable and the recorder digitises and encodes it. An IP camera encodes on board and sends a stream over structured cabling, taking power from the same cable over PoE and appearing on the network as a device.
Are IP cameras better than analogue cameras?
For new installations, usually — IP carries more resolution headroom, supports on-camera analytics, simplifies power with PoE and integrates with the wider security layer. It is not better in every case: where sound coaxial cabling already exists, the resolution requirement is bounded, or site policy keeps cameras off the network, an HD-over-coax design can be the more sensible choice.
Can I use IP cameras on my existing coax cable?
Sometimes, using transmission products designed to carry ethernet over coaxial cable. Whether that suits a given site depends on the cable's condition and type, the run lengths and the bandwidth the design needs, so it is a site-survey question rather than a general yes or no. Where the coax is sound and the resolution requirement is modest, staying with HD-over-coax is often the simpler answer.
Do IP cameras need the internet?
No. IP cameras need a local network to reach their recorder or management platform, and they record without any internet connection. Internet access is only required for remote viewing, remote notification or cloud services.
Are IP cameras a security risk?
They carry a real and manageable one. Because they are network devices, they need segmentation from the general network, changed credentials, current firmware and controlled remote access. Analogue cameras avoid that exposure by being off the network entirely, which on some sites is the deciding factor. The risk with IP is not inherent to the technology — it comes from deploying it with shipped defaults.
Is HD-over-coax the same as analogue?
It is the modern form of it. Traditional analogue CCTV was standard definition; HD-over-coax formats carry high-definition video over the same coaxial cable, which is why coax-based systems remain a live option on retrofit rather than a purely legacy one. The transmission is still analogue and still digitised at the recorder — what changed is the resolution it can carry.
Which camera type is cheaper?
It depends far more on the cabling than on the cameras. Where usable coax already exists, an HD-over-coax design avoids the cost and disruption of re-cabling an occupied building. Where cabling is being installed anyway, the structured cabling serves the whole building rather than only the cameras, and that changes the comparison entirely. Comparing camera unit costs alone will mislead you.
· Begin
Discuss a surveillance architecture
after a look at the drawings.
Share drawings, a BOQ, a project brief or site information and a project lead will return an engineering reading — not a sales pitch — within two working days.