What is an IP camera? A 2026 guide to IP vs analog, resolution, PoE, ONVIF, codecs, bandwidth, security, and how a VMS connects the cameras.
An IP camera captures, compresses, and sends video as network data, not as an analog signal, so it can be addressed, managed, and analyzed with software.
The specifications that matter most are resolution, low light performance, lens and field of view, codec and bitrate, and the environmental rating of the housing.
Power over Ethernet delivers data and power on a single cable and is the biggest installation advantage of IP over analog.
ONVIF conformance lets cameras and VMS software from different brands work together, but firmware quality varies, so always test the specific camera against your platform.
Because IP cameras are networked computers, security is not optional: change default passwords, patch firmware, isolate the network, and prefer on premise where you can. Visylix ingests standards based IP cameras over ONVIF and RTSP, runs 22 built in AI analytics across them, and keeps video on the customer’s own infrastructure with no per camera fees.
An IP camera is a networked digital camera that produces a video stream and delivers it over an IP network, the same kind of network your computers and phones use. IP stands for Internet Protocol, the addressing and routing system that moves data across networks.
Where a traditional analog camera sends a continuous video signal down a dedicated coaxial cable to a recorder, an IP camera does three things on board before anything leaves the device. It captures light through a lens onto an image sensor, it encodes the image into a compressed digital video stream, commonly H.264 or H.265, and it transmits that stream as network packets to a recorder, a VMS, or a viewer using standard protocols.
Because the output is data rather than a signal, an IP camera can be reached from anywhere on the network, addressed by an IP address, and managed with software. That single shift, from signal to data, is what gives IP cameras their flexibility and is the reason they have become the default for new deployments.
Analog CCTV is not dead, but IP has become the standard choice for new systems, and the differences are practical rather than cosmetic.
An analog camera sends a continuous analog signal over coax to a Digital Video Recorder, typically at up to about two megapixels even with HD over coax, and it needs a separate power run to each camera. An IP camera sends a compressed digital stream over a network cable to a Network Video Recorder or a software VMS, commonly at two to eight megapixels or more, and it can draw its power from the same network cable.
The interoperability difference is just as important. Analog systems were often locked to a vendor, whereas IP cameras that follow open standards such as ONVIF and RTSP can be mixed across brands in a single platform. Analytics also move: analog analysis, where it existed at all, lived at the recorder, while IP cameras can run analytics on the camera itself and in the VMS across every feed. If you want the recorder side of this comparison in depth, our guide to NVR versus DVR covers it, and the resolution question is handled in our SD, HD, and 4K guide.
Light passes through the lens and lands on an image sensor, usually a CMOS sensor. The sensor size, its pixel count, and its light sensitivity set the ceiling on image quality, and a larger sensor with larger pixels generally sees better in low light.
An onboard image processor then handles exposure, white balance, wide dynamic range for high contrast scenes, noise reduction, and day to night switching. Raw video is far too large to send uncompressed, so the camera encodes it. The dominant codecs are H.264, also called AVC, and the newer, more efficient H.265, also called HEVC, both standardized by the ITU-T and ISO/IEC. H.265 can roughly halve the bitrate of H.264 at similar quality, which directly reduces bandwidth and storage.
The compressed stream is then packaged and sent using a transport protocol. Real Time Streaming Protocol, or RTSP, is the classic control protocol in surveillance, and many cameras also support HTTP based streaming and, increasingly, low latency options. A recorder or a software VMS receives the stream, stores it, and makes it available for live view, playback, search, and analytics.
Camera datasheets are long, but a handful of fields deserve most of your attention.
Resolution, measured in megapixels, is the headline. Two megapixels, or 1080p, is the practical minimum, while four and eight megapixels give more detail and more room to digitally zoom, at the cost of more bandwidth and storage. Low light performance is set by the sensor and stated as a minimum illumination figure in lux, where a lower number means the camera sees in darker conditions. For genuine darkness you move to infrared or thermal imaging.
The lens and field of view are a coverage decision. A wider lens covers more area with less detail, and a narrower lens covers less area with more detail, while a varifocal lens lets you adjust and a pan tilt zoom camera changes its view on demand. Frame rate of fifteen to twenty five frames per second is typical for surveillance, with higher rates smoothing fast motion at the cost of bitrate.
Codec and bitrate settings, especially H.265 with smart bitrate that only spends bits when something moves, are the biggest lever on storage. Wide dynamic range balances bright and dark areas in the same frame and is essential at entrances and windows. Finally, the housing carries an ingress protection rating defined by IEC 60529, where a figure such as IP66 or IP67 indicates dust and water resistance, and vandal resistance is a separate IK rating.
One of the biggest practical advantages of IP cameras is Power over Ethernet, standardized by the IEEE 802.3 working group. A single Ethernet cable carries both the video data and the electrical power, so there is no separate power run to each camera, which is the single largest installation saving of IP over analog.
The common standards are IEEE 802.3af, usually called PoE, which delivers around thirteen watts to the device and suits fixed cameras; IEEE 802.3at, called PoE+, which delivers around twenty five watts and suits pan tilt zoom cameras, heaters, and infrared illuminators; and IEEE 802.3bt, called PoE++, which delivers roughly fifty watts or more for high power and multisensor cameras.
A PoE switch or a midspan injector supplies the power. A standard Ethernet run reaches about one hundred meters before you need a switch or a fiber link to go further, so distance is planned around switch placement rather than around each camera.
Historically, cameras and recorders from different vendors did not talk to each other. ONVIF, the Open Network Video Interface Forum, fixed that by defining a common standard so that conformant cameras and VMS software interoperate regardless of brand.
The profiles you will see most often are Profile S for video streaming and pan tilt zoom control, Profile G for edge recording and retrieval, and Profile T for advanced streaming that includes H.265 and analytics metadata. When a camera lists ONVIF Profile S or T conformance, a standards based VMS can typically discover it, pull its stream, and control it without a proprietary integration.
One honest caveat matters here. ONVIF conformance is a strong signal, not a guarantee that every advanced feature is exposed, because firmware quality varies between vendors and even between firmware versions. Always test the specific camera and firmware against your VMS before you standardize on it at scale.
Choosing a camera form factor is a coverage and lighting exercise, not a brand exercise.
Bullet cameras are visible and directional, which suits perimeters and long corridors. Dome and turret cameras are discreet and harder to tamper with, which suits indoor spaces. Pan tilt zoom cameras use motorized movement and optical zoom to actively monitor large areas. Fisheye and multisensor cameras cover a very wide or full 360 degree area from one device. Thermal cameras detect heat rather than light, for total darkness, smoke, or long range perimeter detection.
Most estates mix several of these. The right approach is to map each viewpoint to the coverage, detail, and lighting it needs, then pick the form factor that meets it.
Every IP camera consumes network bandwidth and storage, and a short calculation avoids expensive surprises.
First, estimate the per camera bitrate. A four megapixel H.265 camera at fifteen frames per second might average two to four megabits per second depending on scene complexity and smart bitrate settings. Next, multiply by the number of cameras to find the network load. Fifty cameras at three megabits per second is about one hundred and fifty megabits per second of sustained traffic, which is why surveillance is usually placed on its own switch or VLAN.
For storage, the rough rule is that storage in gigabytes is roughly the bitrate in megabits per second divided by eight, times the seconds of retention you need, times the number of cameras. Retention requirements, often thirty to ninety days, tend to dominate the total. H.265, smart bitrate, and motion based recording are the biggest levers on both the network and the storage figures.
Because IP cameras are networked computers, they are attack surface, and the Mirai botnet of 2016, which recruited hundreds of thousands of poorly secured cameras and recorders, is the standing lesson.
Sensible hardening starts with changing default credentials and using strong, unique passwords, because default passwords remain the single most exploited weakness. Update firmware on a schedule, since unpatched cameras are the easy way in, and isolate the camera network on its own VLAN with no direct internet access. Disable services you do not use, such as universal plug and play, unnecessary open ports, and cloud relays you did not ask for.
Procurement rules also apply. United States federal buyers and many enterprises must comply with NDAA Section 889, which restricts certain named vendors, so check the current list before you standardize on a camera. Above all, prefer on premise where you can. Keeping video and analytics inside your own network removes an entire class of cloud exposure, which is why air gapped and on premise deployments remain the strongest posture for sensitive sites.
Individual IP cameras are only as useful as the software that unifies them. A video management system, or VMS, discovers cameras, ingests their streams, records them, provides live view and playback, and increasingly runs AI analytics across every feed at once.
This is where Visylix fits. Visylix is an enterprise VMS delivered as a Docker image that runs on your own infrastructure, so video never has to leave the building. In the context of IP cameras specifically, it connects to standards based cameras using ONVIF for control and RTSP for streaming, alongside a first party engine that supports thirteen or more protocols, so mixed brand estates work together. It does not charge per camera: paid plans carry unlimited streams, which changes the economics of large deployments. It runs twenty two built in AI analytics across those camera feeds without per stream AI fees or third party plugins. And it deploys on premise, at the edge, hybrid, or air gapped, matching the security posture described above.
The takeaway is not that you need one specific product. It is that the camera you buy and the VMS you run are one system. Choose cameras with genuine ONVIF conformance and open streaming, and you keep your software options open rather than locking yourself to a single vendor.
A good specification comes down to matching each camera honestly to its job. Choose the right resolution for the scene, so you neither overspend on 4K where two megapixels will do, nor underspend where you need to read a plate or a face. Match the lens and field of view to the coverage you actually need, and verify low light or infrared performance if the site is dark.
On the technical side, prefer H.265 with smart bitrate to control storage, confirm ONVIF Profile S or T conformance and test it against your VMS, and check that the ingress protection and vandal ratings suit the environment. Make sure the PoE class matches both the camera and your switch budget, and choose a vendor that ships firmware updates and meets your procurement rules.
Finally, choose a VMS that ingests the camera over open standards and does not tax you per device. Get those choices right and an IP camera estate scales cleanly from a handful of cameras to thousands without locking you in.
IP stands for Internet Protocol, the standard for sending data across networks. An IP camera sends its video as network data rather than as an analog signal. Note that the same letters mean something different in a weather rating such as IP66 or IP67, where IP stands for Ingress Protection, a dust and water resistance scale defined by IEC 60529.
CCTV traditionally refers to analog cameras that send a continuous video signal over coaxial cable to a DVR. An IP camera is digital: it compresses the video on board and sends it over a network to an NVR or a software VMS. IP cameras generally offer higher resolution, single cable power and data over PoE, and open standard interoperability across brands.
No. IP cameras need a network, not the internet. Many secure deployments keep cameras entirely offline on an isolated network with the VMS running on premise. Internet access is only required if you deliberately want remote viewing or a cloud service.
ONVIF is an open standard that lets network cameras and video management software from different manufacturers work together. A camera that is ONVIF Profile S or T conformant can usually be added to a standards based VMS without a proprietary integration, which is what lets you mix camera brands in one system.
It depends on resolution, frame rate, codec, and how much is happening in the scene. A 4MP camera using H.265 at 15 frames per second commonly averages between 2 and 4 Mbps. Multiply by the number of cameras to size the network, and place surveillance on its own switch or VLAN.
Yes, if they support open standards. ONVIF and RTSP allow a mixed brand estate to be recorded and viewed in one video management system. A platform such as Visylix connects standards based cameras this way and does not charge per camera, which matters when the estate is large.
You need something to record and manage the video, but it does not have to be a hardware NVR. A software VMS running on standard servers, or as a container on your own infrastructure, can replace a fixed NVR and add analytics across every camera at once.