The moment someone says “let’s put up a PTZ, it’ll see everywhere” in a survey meeting, the project’s first mistake has been made. A PTZ (pan-tilt-zoom) camera sees only where it’s looking at any given moment, and only that frame goes into the recording. If an event happened in another direction, that event isn’t on disk. Below, from the field, we explain which tasks a PTZ really serves, how to position it together with fixed cameras, how to design zoom and preset tours, and how to manage mechanical wear in operation.
PTZ strengths and weaknesses
A PTZ’s strength is getting high detail over a wide area on demand from a single point. A PTZ with 30× or more optical zoom can bring a vehicle or person hundreds of meters away to recognition level. Achieving the same flexibility with fixed cameras requires many narrow-angle cameras.
Its weakness comes from the same place. When a PTZ zooms to one point, the rest of the area is neither watched nor recorded. When the recording is opened the next morning, the camera was most likely looking in another direction at that moment. That’s why a PTZ isn’t a tool for retrospective evidence; it’s a tool for live response and verification. Make the distinction clear from the outset.
| Feature | PTZ | Fixed camera |
|---|---|---|
| Coverage | Narrow at any moment, very wide in total | Continuous and fixed |
| Retrospective review | Only the direction viewed at that moment | The entire defined area |
| Detail on a distant target | High (optical zoom) | Limited by the lens |
| Need for an operator | High | Low |
| Mechanical parts | Motors, gears, slip ring | None, or only a motorized lens |
| Video analytics compatibility | Limited (the scene keeps changing) | Good |
Don’t underestimate the analytics row. Most rule-based or AI-assisted analytics assume the camera is looking at a fixed scene; as the PTZ turns, virtual lines and zones lose their meaning. Some manufacturers offer the option of running analytics only on certain presets: analytics turns on while the camera waits at that preset and off when movement starts. Without this option, writing a line-crossing rule for a PTZ is wasted effort.
PTZ and fixed cameras together
In enterprise camera systems, the right architecture has two layers. Fixed cameras are the base layer that always records; they record the scene continuously at detection and observation level. The PTZ is the detail and verification layer; it turns to the target on an event or at operator request and gives an image at recognition or identification level. In this arrangement, even if the PTZ fails or looks the wrong way, the scene’s recording isn’t lost.
The rules we apply on site for placement:
- Line of sight: The PTZ must have an unobstructed view of every preset it’s expected to watch. A pole, tree, building corner or light fitting permanently cuts off part of the frame. In the survey, verify the line of sight for each preset direction separately; trees look different in summer and winter.
- Height: Height opens up the line of sight but makes it harder to see directly under the camera and its immediate surroundings. Cover the base of the pole with a fixed camera; otherwise a person approaching the pole isn’t seen.
- Fixed camera triggering: A line-crossing or area intrusion event on a fixed camera can send the PTZ to the relevant preset via a VMS rule. If you build the link at VMS level rather than inside the camera, cameras from different manufacturers work together.
- One PTZ, many events: If two events arrive at once, which one will the PTZ turn to? If no priority order is defined in the rules engine, the camera shuttles between two presets and misses both.
The fixed layer’s coverage plan and blind spot analysis should be finished, following the steps in the IP camera system design guide, before PTZ placement. A PTZ isn’t put in to patch gaps in the coverage plan. It adds detail on top of that plan.
Choosing optical zoom and range
On datasheets, the zoom ratio (25×, 32×, 40×) and the focal length range are given side by side. The ratio is what stands out in sales presentations; what determines range is the longest focal length and the sensor width. The field width at a given distance is calculated with the rectilinear lens approximation as follows:
Field width (m) = Distance (m) × Sensor width (mm) / Focal length (mm)
Pixel density (px/m) = Horizontal resolution (px) / Field width (m)
Worked example: Take a PTZ with a 1/2.8-inch sensor (effective width about 5.6 mm), 1920-pixel horizontal resolution and a 4.8–120 mm (25×) lens. At full zoom, the field width at 200 m is 200 × 5.6 / 120 ≈ 9.3 m; pixel density is 1920 / 9.3 ≈ 206 px/m. Enough for recognition, not enough for identification. At 100 m, the same camera gives a width of about 4.7 m and a density of around 410 px/m. Details of the formula and how to read sensor sizes are in the camera lens and focal length calculation article.
Common misconceptions in choosing range:
- Digital zoom isn’t range. “16× digital zoom” doesn’t create new pixels; it enlarges existing ones. It doesn’t enter recording or identification calculations.
- Atmosphere and vibration: At very long focal lengths, heat shimmer, fog, dust and pole sway degrade the image. At 120 mm, a pole sway of a few millimeters moves the frame by meters. For long-range PTZs, assess the pole’s stiffness and any image stabilization feature.
- Night range: The range of the integrated IR illuminator often falls short of the optical range. If there’s a night recognition target, verify the IR range separately or plan external lighting.
- Focusing speed: When zooming to a distant target, the image stays blurred for a few moments until autofocus locks again. If the focus value can be stored in the preset, use fixed focus.
Preset and tour design
A preset is a stored pan, tilt and zoom (and on most models, focus) position of the camera. A tour (patrol/tour) is visiting presets in sequence with set dwell times. The preset list isn’t filled in at random; it comes from the risk analysis. Every preset should have a purpose, a target level and a priority order.
A preset plan for an example logistics yard:
| Preset | Target | Purpose | Dwell |
|---|---|---|---|
| 1 – Main gate | Vehicle and driver | Recognition | 20 s |
| 2 – Docks 1–4 | Truck bed | Observation | 15 s |
| 3 – North fence line | Movement along the fence | Detection | 10 s |
| 4 – Scrap area | Material movement | Observation | 10 s |
| Home position | General yard | Observation | When the operator releases control |
In tour design, calculate two measures together: the total cycle time and each area’s unwatched time. In the example above, the dwell times add up to 55 seconds; with transitions between presets, the cycle comes to about a minute. So the docks are seen for only 15 seconds every minute. The other 45 seconds are blind.
If this ratio isn’t acceptable, the solution isn’t compressing the tour. A fixed camera is added for that area.
Design rules:
- Always define the home position and the time to return home after the operator releases control (park action). If they aren’t defined, the last position the operator zoomed to stays that way for days; this is a common complaint.
- Give presets descriptive names. Writing “Docks 1–4” instead of “Preset 7” in the VMS saves the operator seconds during an incident.
- Separate tours can be planned for night and day. Remove presets outside the IR range from the night tour; a preset looking into darkness only produces wear.
- On a PTZ, privacy masks must work position-dependently. Test one by one for each preset whether the mask stays in the right place when the camera moves.
Auto-tracking and operator workload
Auto-tracking is the camera following a detected target with pan/tilt/zoom. On a quiet site, it’s useful for tracking a single person crossing the fence line at night. On a site with multiple targets and moving branches and shadows, however, the camera locks onto the wrong target or shuttles between two targets. A PTZ tracking a flagpole on a windy night is a common sight at commissioning. Don’t accept auto-tracking without testing it in real scene conditions, day and night separately.
What needs to be clarified on the operator side:
- Control priority: In VMSs, PTZ priority can be defined per user or role. The operator in the control center should be able to override a move made by a guard on site from the mobile app.
- Lock time: While the operator uses the PTZ, tours and auto-tracking should pause and resume where they left off after a set time.
- Control interface: In centers managing many PTZs, a joystick is noticeably faster than a mouse during an incident. Verify before ordering that the VMS supports the joystick model to be used.
- Audit trail: Who made PTZ movements should be logged. For cameras that can turn toward privacy-sensitive areas, this log is the first record that will be asked for.
On the protocol side, current IP PTZs are usually controlled through the ONVIF PTZ service. In Profile S and Profile T, PTZ is a conditional feature; a device conforming to these profiles doesn’t on its own show that it supports PTZ commands, and this must be verified per model. Older analog PTZs mostly work with Pelco-D or Pelco-P over RS-485. When these devices are brought onto IP via an encoder, test that PTZ commands are supported by the encoder and VMS; reversed A/B wiring on the RS-485 line and mismatched addresses and baud rates are known causes of the “there’s video, but the camera won’t move” fault. For supported features, check the ONVIF conformance page together with the manufacturer’s declaration of conformance.
Mechanical wear, power and maintenance
A PTZ’s motors, gears or belts, and the slip ring that allows continuous rotation, wear with every movement. A PTZ running a 24/7 tour makes thousands of movements a day. Manufacturers generally support continuous tour use, but they specify maintenance intervals and continuous operating conditions in their own documentation. Read this document before the tour plan.
- Reduce unnecessary movement: Stopping the tour and waiting at the home position during night hours with no traffic reduces wear.
- Watch for preset drift: Presets drifting a few degrees over time is the first sign of a mechanical problem. In periodic maintenance, compare each preset image with a reference screenshot.
- Power budget: Outdoor PTZs with heaters, IR illuminators and wipers draw high power. Some models need 802.3bt PoE, others 24 V AC or a manufacturer-specific high-power PoE injector. A PTZ that restarts in winter when the heater kicks in is a typical sign of an inadequate port class; check separately in the PoE power budget calculation whether the switch port meets this class.
- Access: A PTZ at the top of a pole needs a platform or bucket truck for maintenance. Make maintenance access a criterion when choosing the mounting point.
Decision table
The table below shows the PTZ’s role in common scenarios. Using a PTZ as a verification tool together with radar or thermal cameras in perimeter security is covered separately in the critical infrastructure perimeter security article.
| Scenario | Is a PTZ suitable? | Recommended setup |
|---|---|---|
| Large open yard with a control center | Yes | Fixed layer + event-triggered PTZ |
| Large yard with no operator watching | Limited | Fixed cameras; PTZ only with tours and analytics presets |
| Door or turnstile identification | No | Narrow-angle fixed camera |
| Plate reading | No | Fixed LPR camera |
| Changing areas such as ports, construction sites, car parks | Yes | PTZ on a tall pole + panoramic or fixed cameras |
| Enclosed area, narrow corridor | Usually not | Fixed or panoramic camera |
Before applying the table, ask one question: “Who will operate this PTZ during an incident?” If the answer isn’t clear, putting most of the budget into fixed cameras gives more reliable results. An unwatched PTZ is an expensive fixed camera. In our PTZ and long-range camera systems and camera positioning and blind spot analysis services, we verify these decisions for long-range optics and pole design by measuring on site.
Frequently asked questions
Can one PTZ camera replace several fixed cameras?
No. A PTZ records only the direction it’s looking at any given moment; if an event happened in another direction, there’s no recording. PTZs are used to add a layer of detail and verification to a scene that fixed cameras record continuously.
When choosing a PTZ, should I look at zoom ratio or focal length?
Focal length. Range is determined by the longest focal length, sensor width and horizontal resolution. Two cameras with the same zoom ratio can give very different ranges with different focal ranges. Digital zoom doesn’t enter the range calculation.
How often should a preset tour cycle?
There’s no single right value; what matters is whether the time each area goes unwatched is acceptable. The longer the cycle, the less each area is seen. If an area must be seen continuously, add a fixed camera for it instead of speeding up the tour.
Can auto-tracking be used on every site?
No. It works on quiet, controlled sites; in crowded, tree-lined or shadowy scenes, it can lock onto the wrong target. Don’t put it into service without testing it in real conditions, day and night, and defining operator priority.