Ajax TurretCam Blurry Faces — How to Fix Image Quality (Complete 2026 Guide)
You installed four Ajax TurretCam 8MP cameras and the footage looks great — until someone walks past and their face is an unrecognisable blur. This is the most common complaint from Ajax camera installers right now. This guide covers every cause and every fix, from lens selection to NVR bitrate settings to mounting angle. If you’d rather have a Sipko Security technician diagnose and fix it on-site, call us on 0406 432 691 — we service all of Melbourne and the Mornington Peninsula.
🔍 Quick Diagnosis: Match Your Blur Symptom
Faces are soft regardless of how close the subject is to the camera?
Daytime footage is fine but night footage loses all face detail?
Close subjects are sharp but faces blur as distance increases?
Live view looks sharp but recorded footage is noticeably worse?
Faces appear as bright white blobs, especially at night or near lights?
Image quality drops randomly or during motion, then recovers?
2. The Lens Factor — 2.8mm vs 4mm for Face Clarity
The Ajax TurretCam 8MP is available in two fixed lens options: 2.8mm and 4mm. This is the single most impactful decision you make for face clarity — and it’s one you cannot change after installation without replacing the camera. Most installers default to 2.8mm because it gives a wider field of view, but for face capture, 4mm is almost always the better choice.
Here is the practical difference: a 2.8mm lens on the TurretCam gives approximately 103° horizontal field of view. A 4mm lens gives approximately 78°. The narrower field of view of the 4mm means each person in the frame occupies more pixels — which directly translates to more face detail. At Sipko Security, we specify the 4mm lens as standard for any installation where face capture at entry points is a client requirement.
Wide View, Weaker Face Detail
- ~103° horizontal field of view
- Best for: corridors, small rooms, tight entry points under 4m
- Face clarity at 5m: borderline recognition
- Face clarity at 8m: poor — faces typically unidentifiable
- Face clarity at 10m+: not suitable for face capture
- Use when: you need wide coverage and face capture is secondary
Narrower View, Much Better Face Detail
- ~78° horizontal field of view
- Best for: driveways, front paths, entry points 4–10m
- Face clarity at 5m: good recognition quality
- Face clarity at 8m: acceptable recognition quality
- Face clarity at 10m: borderline — better than 2.8mm at same distance
- Use when: face identification is a priority requirement
💡 The Practical Rule for Lens Selection
If the primary purpose of the camera is to capture faces — at a front door, driveway entry, or pedestrian gate — choose the 4mm lens. If the primary purpose is wide-area coverage (a large car park, a long corridor, a backyard overview) and face capture is secondary, the 2.8mm is acceptable. Never install a 2.8mm lens camera pointing down a 10-metre driveway and expect identifiable faces at the far end. It will not deliver them regardless of how you configure the settings. See our Ajax TurretCam 2.8mm product page and compare with the 4mm variant before specifying your installation.
What About Motorised / Varifocal Lenses?
The Ajax TurretCam 8MP is a fixed lens camera — there is no varifocal or motorised zoom option in the current Ajax HL camera range. This means lens selection at the time of purchase is final. If you have already installed a 2.8mm camera in a location that requires face capture at 8+ metres, your options are: (1) replace the camera with a 4mm unit, (2) reposition the camera closer to the subject, or (3) accept that face capture at that distance is not achievable with this camera and adjust client expectations accordingly.
4. Camera Mounting Height and Angle — How It Destroys Face Clarity
Even with the right lens and the right distance, mounting the camera at the wrong height or angle is one of the most common reasons faces come out blurry, distorted, or simply showing the top of someone’s head. The geometry of face capture is unforgiving — a few degrees of tilt or an extra metre of height can be the difference between a usable face image and a useless one.
The Ajax TurretCam is a turret-style camera, which means it can be tilted and panned within its housing after mounting. This gives you more flexibility than a fixed dome — but it also means installers sometimes mount it at a convenient height and then try to compensate with tilt angle, which rarely works as well as getting the height right in the first place. When Sipko Security installs Ajax cameras, we always assess the mounting position before drilling — repositioning after the fact costs time and money that is easily avoided upfront.
The “Top of Head” Problem
When the camera is mounted too high, the steep downward angle means you capture the crown of the head and shoulders — not the face. Even if you tilt the camera to compensate, the perspective distortion compresses the face vertically, making it harder to identify. At 4m+ height, a person at 5m distance will have their face occupying a very small portion of the frame at an unflattering angle.
Result: Footage shows hair and shoulders. Face is angled away from the lens. Useless for identification.
The Face Capture Sweet Spot
At 2.4–3.0m height with a 15–25° downward tilt, the camera captures faces at a natural angle — slightly above eye level, which is how CCTV face capture is designed to work. The face is presented toward the lens rather than away from it, and the perspective distortion is minimal. This is the height range used in professional face capture installations worldwide.
Result: Face is clearly visible, well-lit, and occupies maximum pixels in the frame.
The Chin-Up Problem
Cameras mounted below eye level capture faces from below — showing nostrils and chin rather than the full face. This is less common in residential installations but occurs when cameras are mounted on low walls, gate posts, or intercom panels. The upward angle also means the camera is looking into bright sky or ceiling lights, causing backlight issues.
Result: Unflattering angle, backlight issues, face partially obscured by chin and jaw.
🛠️ The Tilt Angle Rule
For face capture, the camera should be tilted so that the centre of the frame points at face height (approximately 1.7m from the ground) at the primary capture distance. If your camera is at 2.8m height and your capture zone is 5m away, the required downward tilt is approximately 12–15°. If your camera is at 2.8m and your capture zone is 3m away, the tilt increases to approximately 20–25°. The Ajax TurretCam housing allows tilt adjustment without tools — use this to fine-tune after mounting rather than accepting the default angle.
Practical Mounting Guide for Common Scenarios
- Front door (subject at 2–3m): Mount at 2.4–2.6m height, tilt 20–25° downward, 4mm lens. Camera should be beside or above the door frame, not directly above it.
- Driveway entry (subject at 4–6m): Mount at 2.6–3.0m height, tilt 15–20° downward, 4mm lens. Position camera to capture faces as subjects approach, not as they pass beneath.
- Pedestrian gate (subject at 3–5m): Mount at 2.4–2.8m on gate post or adjacent wall, tilt 15–20° downward, 4mm lens. Ensure camera faces the approach path, not the gate itself.
- Retail entrance (subject at 2–4m): Mount at 2.4–2.8m above door frame, tilt 20° downward, 4mm lens. Aim to capture faces as customers enter, not as they browse inside.
- Car park / large area: Accept that face capture at 10m+ is not achievable with this camera. Use for vehicle detection and general overview; add a dedicated face capture camera at the entry point.
5. IR Night Mode and Face Blur — Why Faces Go White at Night
Night footage is where most Ajax TurretCam face clarity complaints originate. A camera that produces perfectly sharp faces in daylight can deliver completely washed-out, unidentifiable faces at night — and the cause is almost always the infrared (IR) illumination system, not the camera sensor itself.
The Ajax TurretCam 8MP uses built-in IR LEDs to illuminate scenes in darkness. When a person is close to the camera at night, the IR illumination can be so intense that it overexposes the face — turning it into a bright white blob with no detail. This is called IR overexposure or IR washout, and it is one of the most common causes of blurry, unidentifiable faces in night footage. Sipko Security encounters this on roughly one in three Ajax camera service calls — and it is almost always fixable without replacing any hardware.
IR Overexposure at Close Range
The Ajax TurretCam’s IR LEDs are designed to illuminate subjects at distances of up to 30m. When a subject is only 2–3m from the camera, the IR intensity is far too high for that distance — the camera’s automatic exposure control cannot compensate fast enough, and the face is blown out. The result is a bright white oval where the face should be, with no discernible features.
This is particularly severe at front doors and entry points where subjects approach closely — exactly the scenarios where face capture matters most.
How to Reduce IR Overexposure
- Increase mounting distance — move the camera further from the capture zone so IR intensity is lower at face level
- Reduce IR intensity in settings — check the Ajax app / NVR for IR intensity controls (available on some firmware versions)
- Add external white-light illumination — a separate LED floodlight on the approach path provides even, non-overexposing illumination that the camera handles much better than IR
- Use the hybrid illumination model — the newer Ajax cameras with hybrid (white light + IR) illumination handle close-range face capture significantly better
⚠️ IR Mode vs Colour Night Mode
The Ajax TurretCam switches to black-and-white IR mode in low light. In IR mode, the camera loses all colour information — which means it also loses one of the key cues used for face recognition (skin tone, hair colour, clothing colour). If your installation requires colour night footage for face identification, you need either: (1) sufficient external white-light illumination to keep the camera in colour mode, or (2) the newer Ajax hybrid illumination camera models that use white light for close-range colour capture. Standard IR-only night mode is not suitable for forensic face identification.
Diagnosing Your Night Blur — Step by Step
- Review a night clip where the face is blurry. Is the face bright white / overexposed, or is it dark and noisy?
- If bright white: IR overexposure. Fix by increasing camera-to-subject distance, reducing IR intensity, or adding external white-light illumination.
- If dark and noisy: insufficient illumination. Fix by adding external lighting or checking that IR LEDs are functioning correctly.
- If blurry but correctly exposed: motion blur from slow shutter speed. Fix by increasing the minimum shutter speed in the camera’s exposure settings (if available), or by ensuring the subject is moving slowly through the capture zone.
- Check whether the blur is consistent across all night clips or only when subjects are close. Consistent blur = settings issue. Close-range only = IR overexposure.
6. Bitrate and Compression — The Hidden Face Destroyer
This is the fix most installers overlook. You can have the perfect lens, perfect mounting height, perfect lighting — and still get blurry faces if the camera or NVR is compressing the video too aggressively. Bitrate is the amount of data used to encode each second of video. Low bitrate = high compression = lost detail. And face detail is exactly the kind of fine, high-frequency information that H.265 compression discards first.
The Ajax TurretCam 8MP records at up to 8MP (3840×2160) resolution, but the actual image quality you see depends heavily on the bitrate setting. A camera recording at 8MP with a 1 Mbps bitrate will look significantly worse than the same camera at 4 Mbps — even though both are technically “8MP”. The resolution tells you the maximum possible detail; the bitrate tells you how much of that detail actually survives the compression process. This is one of the first things Sipko Security checks when attending a site where clients report blurry footage — and it is the fix in roughly 30% of cases.
What Happens to Faces
At low bitrates, H.265 compression aggressively discards fine detail to meet the data budget. Faces — which contain high-frequency detail like skin texture, eye definition, and hair strands — are among the first casualties. The result is a face that looks like it has been smeared with a soft brush: the general shape is there, but no identifying features remain. This is often mistaken for a focus or lens problem when it is actually a compression problem.
What You Should Be Using
For 8MP face capture, a minimum of 4 Mbps is recommended for acceptable face detail. For forensic-quality face capture, 6–8 Mbps is the professional standard. Yes, this uses more storage — but if face identification is a requirement, there is no way around it. A 4 Mbps stream at 8MP uses approximately 43 GB per day per camera. Factor this into your NVR storage planning. See our guide on how many days of CCTV storage you actually need.
How to Check and Adjust Bitrate on Ajax NVR
- Open the Ajax app → tap your NVR → tap Settings
- Navigate to Camera Settings → select the TurretCam you want to adjust
- Find Video Encoding or Stream Settings
- Check the current Bitrate value — if it is set to “Auto” or under 3000 kbps, increase it
- Set Bitrate Type to CBR (Constant Bit Rate) for consistent face quality — VBR (Variable) can drop quality during motion, exactly when you need it most
- Set Bitrate to a minimum of 4000 kbps (4 Mbps) for face capture use cases
- Save and allow the NVR to apply the new settings — check a live view clip to confirm improvement
💡 H.265 vs H.264 — Which to Use?
The Ajax NVR supports both H.265 and H.264 encoding. H.265 achieves the same visual quality as H.264 at roughly half the bitrate — meaning you can get equivalent face detail at 4 Mbps H.265 vs 8 Mbps H.264. Always use H.265 if your NVR and cameras support it. However, be aware that H.265 at very low bitrates (under 2 Mbps) can produce more visible compression artefacts on faces than H.264 at the same bitrate. The recommendation: H.265 at 4–6 Mbps for 8MP face capture.
7. NVR Recording Quality vs Live View — Why Playback Looks Worse
A common complaint from Ajax camera users is that the live view looks sharp but recorded playback looks noticeably worse. This is not a bug — it is a deliberate design choice that many installers are unaware of. Understanding it is essential for getting the best face quality from your recordings.
Most IP camera systems — including Ajax — use two separate video streams: a main stream (high resolution, high bitrate, used for recording) and a sub stream (lower resolution, lower bitrate, used for remote live viewing). The sub stream exists to reduce bandwidth when viewing remotely over a mobile connection. The problem arises when the NVR is configured to record the sub stream instead of the main stream, or when the app defaults to sub stream for playback. If you’re unsure how to check this, Sipko Security’s maintenance service includes a full NVR settings audit as standard.
What You Want for Recording
- Full 8MP (3840×2160) resolution
- High bitrate (4–8 Mbps)
- Used for NVR local recording
- Best face detail in playback
- Uses more storage — plan accordingly
What Causes Blurry Playback
- Reduced resolution (typically 1080p or lower)
- Low bitrate (often under 1 Mbps)
- Designed for remote mobile viewing
- Faces lose significant detail
- If NVR records sub stream, all footage is low quality
How to Confirm Your NVR Is Recording Main Stream
- Open the Ajax app → tap your NVR → tap Settings
- Navigate to Recording Settings or Storage Settings
- Confirm that the recording stream is set to Main Stream — not Sub Stream or Auto
- Check the recorded resolution shown — it should display 3840×2160 or 8MP for the TurretCam 8MP
- If it shows 1080p or 2MP, the NVR is recording the sub stream — change this immediately
- Also check the playback stream setting in the app — some apps default to sub stream for playback even when the NVR recorded main stream. Switch to main stream for playback to see the full quality footage
⚠️ The Ajax NVR “Only One Camera in High Quality” Issue
A widely reported issue in the Ajax installer community: the Ajax NVR only allows one camera to display in high quality on the TV/monitor at a time, with the rest defaulting to low quality. This is a display bandwidth limitation of the NVR’s HDMI output — it does not affect the recording quality. All cameras continue to record at full main stream quality regardless of what the display shows. The fix for display quality is to select individual cameras for full-screen view rather than relying on the multi-camera grid view. This is a known limitation that Ajax is expected to address in future NVR firmware updates.
8. PoE Switch Quality — The Cause of Intermittent Blur and Pixelation
If your Ajax TurretCam footage is sharp most of the time but occasionally drops to a pixelated, blocky mess — particularly during motion — the PoE switch is a prime suspect. This symptom is distinct from the consistent blur caused by lens or compression issues: intermittent pixelation that appears and disappears is almost always a network problem, not a camera problem.
The Ajax TurretCam 8MP at 4–8 Mbps requires a stable, consistent network connection to deliver smooth, high-quality footage. A cheap or overloaded PoE switch that drops packets, introduces latency, or delivers inconsistent power will cause the camera’s video stream to degrade — manifesting as pixelation, freezing, or sudden quality drops that look like blur. Sipko Security uses managed Gigabit PoE switches on all installations — it is a small cost difference that eliminates an entire category of post-installation complaints. See our best CCTV systems for Melbourne homes guide for our full hardware recommendations.
What to Look For
- Intermittent pixelation or blocking artefacts during motion
- Camera goes offline briefly then reconnects
- Image quality drops at certain times of day (when network load is higher)
- One camera on the switch is fine but others are blurry
- Footage freezes for 1–2 seconds then resumes
- NVR shows camera as “offline” intermittently despite cable being connected
PoE Switch Recommendations
- Use a managed PoE switch — unmanaged switches cannot prioritise video traffic and are more prone to congestion
- Check total PoE budget — the Ajax TurretCam 8MP draws approximately 7–10W. Ensure your switch’s total PoE budget is not exceeded
- Use Gigabit ports — 100Mbps ports can bottleneck multiple 8MP cameras simultaneously
- Avoid daisy-chaining switches — each hop adds latency and potential packet loss
- Use quality brands — TP-Link, Netgear, or Ubiquiti for reliable PoE delivery
🔧 Quick PoE Switch Diagnostic
To confirm whether your PoE switch is causing the blur: temporarily connect the affected camera directly to the NVR’s built-in PoE port (bypassing the external switch entirely). If the image quality improves immediately, the external switch is the problem. If quality remains the same, the issue is elsewhere — lens, settings, or cable.
9. Cable Quality and Run Length — When the Wire Is the Problem
Long cable runs and poor-quality cable are a frequently overlooked cause of image degradation in Ajax camera installations. Unlike analogue CCTV where cable quality directly affects image quality, IP cameras transmit digital data — so the effect is different but equally damaging. Instead of a gradual quality reduction, poor cable causes packet loss, which manifests as intermittent pixelation, freezing, or complete camera dropouts.
The Ajax TurretCam uses standard Cat5e/Cat6 Ethernet cable for both data and PoE power. The maximum recommended run length for PoE is 100 metres (328 feet). Beyond this, both data reliability and power delivery degrade — and the camera may receive insufficient power to operate its IR LEDs at full intensity, directly affecting night image quality. If you’re unsure about your cable runs, Sipko Security can perform a full cable audit as part of a system maintenance visit.
How to Test Your Cable
- Use a cable tester — a basic RJ45 cable tester (under $30) will confirm all 8 pairs are connected correctly and identify wiring faults
- Check link speed in NVR — the NVR should show a 1000 Mbps (Gigabit) link for each camera. A 100 Mbps link on a Gigabit switch indicates a cable or termination issue
- Swap the cable temporarily — run a known-good patch cable as a temporary replacement. If quality improves, the original cable is the problem
- Check for physical damage — inspect the full cable run for kinks, staple damage, pinch points, and UV degradation on outdoor sections
- Measure the run length — if you don’t know the exact length, use a cable length tester or measure the physical route. Any run approaching 80m should be treated as potentially problematic
10. Lens Cleaning — The 5-Minute Fix Nobody Tries First
Before adjusting any settings or replacing any hardware, clean the lens. It sounds obvious, but a dirty lens is one of the most common causes of soft, hazy, or low-contrast footage — and it is the easiest fix of all. The Ajax TurretCam’s lens dome accumulates dust, condensation residue, insect deposits, and spider webs over time. Even a thin film of dust can reduce contrast and sharpness significantly, making faces appear soft even when everything else is correctly configured.
Spider webs are a particular problem for outdoor cameras. A spider building a web across the lens dome creates a persistent soft-focus effect that appears and disappears as the web moves in the wind. This is covered in detail in our guide to minimising spider webs on security cameras. Sipko Security includes lens cleaning and inspection as part of every annual maintenance visit — it takes 5 minutes and often produces an immediate, visible improvement in footage quality.
Step-by-Step Cleaning Guide
- Use a soft, lint-free microfibre cloth — never paper towel or tissue
- For dust: gently wipe the dome in a circular motion from centre outward
- For stubborn deposits: use a small amount of isopropyl alcohol (70%) on the cloth — never spray directly on the camera
- For spider webs: use a soft brush or compressed air to remove the web before wiping
- Check the result in live view — the improvement in contrast and sharpness is usually immediate
- Repeat every 3–6 months as part of routine security system maintenance
Common Cleaning Mistakes
- Never use paper towel — it scratches the dome surface permanently
- Never spray water or cleaner directly — liquid can enter the housing and damage electronics
- Never use abrasive cloths — even a slightly rough cloth will micro-scratch the dome
- Never use acetone or strong solvents — they will cloud the polycarbonate dome permanently
- Don’t ignore the housing — clean the area around the dome too; dirt on the housing can fall onto the lens
✅ Prevention: Reducing Spider Web Buildup
Apply a thin layer of insect deterrent spray (citronella-based) around — not on — the camera housing every 3–6 months. Spiders are attracted to the warmth of the IR LEDs. Reducing their access to the housing significantly reduces web buildup on the lens. See our full guide on minimising IR attraction and spider webs for more prevention strategies.
11. WDR Settings — Fixing Washed-Out Faces in Backlit Scenes
Wide Dynamic Range (WDR) is a camera feature designed to handle scenes with extreme contrast — bright backgrounds and dark foregrounds simultaneously. A classic example: a person standing in a doorway with bright sunlight behind them. Without WDR, the camera exposes for the bright background and the person’s face becomes a dark silhouette. With WDR enabled, the camera processes multiple exposures to reveal detail in both the bright and dark areas.
For Ajax TurretCam installations facing east or west — or any camera pointed toward a bright sky, window, or reflective surface — WDR is essential for face clarity. Without it, faces in backlit conditions will appear as dark, featureless shapes regardless of how well everything else is configured. Our CCTV camera placement guide covers how to avoid backlit positions in the first place.
The Backlight Problem
Camera exposes for the bright background. The person’s face is underexposed — appearing as a dark silhouette with no visible features. This is most severe at dawn and dusk when the sun is low and directly behind subjects approaching the camera. Even at 8MP with perfect lens selection, a backlit face without WDR is completely unidentifiable.
The Fix
Camera processes multiple exposures simultaneously, revealing detail in both bright and dark areas. The face is correctly exposed even against a bright background. WDR does introduce a slight reduction in overall sharpness but this trade-off is always worth it when backlight is present. A slightly softer but visible face is infinitely more useful than a perfectly sharp silhouette.
How to Enable and Configure WDR on Ajax TurretCam
- Open the Ajax app → tap your NVR → tap Camera Settings → select the TurretCam
- Navigate to Image Settings or Display Settings
- Find WDR or BLC (Backlight Compensation) — enable it
- Set WDR level to Medium as a starting point — High WDR can introduce haloing artefacts around edges
- Review a live view clip in the backlit condition to confirm face detail has improved
- If WDR is not available in the app, access the camera’s web interface directly via its IP address for more advanced image controls
💡 WDR vs BLC vs HLC — What’s the Difference?
WDR (Wide Dynamic Range) — processes multiple exposures for the best overall image in high-contrast scenes. Best for general backlight situations. BLC (Backlight Compensation) — exposes specifically for the dark foreground area, brightening faces at the expense of overexposing the background. Simpler than WDR but less sophisticated. HLC (Highlight Compensation) — reduces bright spots like headlights or spotlights to prevent them from washing out nearby faces. Useful for car park and driveway cameras at night. For face capture in backlit conditions, WDR is the recommended setting. For night-time face capture near bright lights, HLC is the better choice.
12. Firmware Updates and Image Processing Improvements
Ajax ships image quality improvements — including noise reduction, colour accuracy, and low-light processing — embedded in camera firmware updates. Running outdated firmware means running an older image processing pipeline that may produce softer, noisier, or less colour-accurate footage than the current version. This is particularly relevant for night image quality, where Ajax has made significant improvements in recent firmware cycles.
Unlike the AI detection improvements (which are also firmware-based), image quality improvements are less publicised but equally impactful. If your TurretCam footage looked acceptable when first installed but has not improved despite other fixes, checking the firmware version should be one of your first steps.
How to Update Ajax TurretCam Firmware
- Open the Ajax app → go to Devices → tap the TurretCam → tap the gear icon
- Scroll to Firmware — the current version is displayed. If an update is available, an “Update” button appears
- Tap Update — keep the camera powered throughout. The update takes approximately 5–10 minutes
- The camera will reboot automatically after the update completes
- Also update your NVR firmware — go to NVR → Settings → Firmware. NVR firmware updates can affect how video is processed and stored
- Also update your Hub firmware — Hub OS (Malevich) updates can affect how camera events are processed
- After updating all three, review a live view clip and a night clip to assess any quality improvement
Image Quality Improvements
- Improved noise reduction in low-light conditions
- Better colour accuracy and white balance
- Improved IR cut filter switching (day/night transition)
- Reduced compression artefacts at standard bitrates
- Better automatic exposure control in high-contrast scenes
- Improved AI detection accuracy (fewer false positives)
Hardware Limitations
- Wrong lens focal length for the detection distance
- Camera mounted at wrong height or angle
- Physical lens damage or permanent scratching
- Insufficient pixels-on-face at the required distance
- Fundamental sensor size limitations vs dedicated face cameras
💡 Check Ajax Release Notes After Each Update
Ajax publishes firmware release notes on their official blog and support site. After each update, check the notes for mentions of “image quality improvements”, “low-light enhancements”, or “colour accuracy fixes”. These confirm whether the update is likely to improve your specific issue. See our guide on what makes Ajax systems so powerful for the broader picture of how Ajax continues to improve its platform.
13. Ajax TurretCam vs Hikvision AcuSense vs Dahua WizMind — Honest Face Clarity Comparison
The Ajax TurretCam 8MP is a strong all-round camera for an integrated Ajax system — but it is not a dedicated face capture camera, and it is not yet at the same level as Hikvision’s AcuSense or Dahua’s WizMind platforms for face detail in challenging conditions. Understanding where it sits in the market helps you set realistic expectations and make the right recommendation to clients.
This comparison is based on real-world installer experience, not manufacturer specifications. Specifications tell you what a camera can do under ideal conditions; this comparison tells you what you can expect in a typical Melbourne residential or commercial installation. Sipko Security installs all three platforms and can advise which is most appropriate for your specific site requirements — call us on 0406 432 691 for an honest assessment. See also our Ajax vs Hikvision AX Pro comparison and our Hikvision vs Dahua comparison for the broader picture.
💡 The Hybrid Approach for Demanding Sites
For sites where face capture quality is critical — commercial properties, high-value homes, or any site where footage may be used as evidence — many professional installers use a hybrid approach: Ajax cameras for general coverage and alarm integration, with a dedicated Hikvision or Dahua face capture camera positioned specifically at the primary entry point. This gives you the best of both worlds: Ajax’s seamless alarm integration and the superior face detail of a mature CCTV platform. See our Ajax vs Hikvision AX Pro comparison and our guide to Ajax video surveillance for Melbourne homes for more on this approach.
14. BulletCam vs TurretCam — Which Ajax Camera Is Better for Face Capture?
Ajax currently offers three camera form factors in the HL range: TurretCam, BulletCam, and MiniDomeCam. Each has different strengths for face capture, and choosing the wrong form factor for a face capture application is a common installation mistake that no amount of settings adjustment can fix.
Best For: Entry Points, Driveways
- Ball-and-socket mount allows precise tilt and pan adjustment after installation
- Compact housing — less obtrusive on residential properties
- Available in 2.8mm and 4mm — choose 4mm for face capture
- Good for under-eave mounting at 2.5–3m height
- IR range up to 30m — more than sufficient for residential face capture distances
- Limitation: Fixed lens — cannot adjust focal length after purchase
Best For: Long-Range, Perimeter
- Longer body allows for a longer focal length lens — better for distant subjects
- Typically used for perimeter monitoring and long driveway coverage
- More visible deterrent effect due to larger housing
- Better suited for mounting on walls and poles at greater heights
- Same fixed lens limitation as TurretCam
- For face capture: use at 4–8m with 4mm lens — similar performance to TurretCam at equivalent distances
Best For: Indoor, Ceiling Mount
- Ceiling-mount design — ideal for indoor retail, reception areas, corridors
- Vandal-resistant housing — suitable for public-facing indoor locations
- Wide-angle lens captures more of the room but at lower face detail per subject
- Best for indoor face capture at 2–4m ceiling height
- Not recommended for outdoor face capture — housing not optimised for external mounting
💡 The Verdict for Face Capture
For outdoor residential face capture at entry points and driveways, the TurretCam with 4mm lens is the correct choice in most cases. Its adjustable ball-and-socket mount gives you the flexibility to fine-tune the angle after installation — critical for face capture geometry. The BulletCam is better suited for longer-range perimeter coverage where face capture is secondary. The MiniDomeCam is the right choice for indoor ceiling-mount applications.
15. Using Ajax NVR Smart Search — Making the Most of What You Have
Even with imperfect face clarity, the Ajax NVR’s smart search features can significantly improve your ability to find and identify subjects in recorded footage. Rather than scrubbing through hours of continuous recording, smart search lets you filter footage by detection type — human, vehicle, or motion — and jump directly to relevant clips.
This is particularly useful when face clarity is marginal: instead of reviewing every frame, you can quickly isolate the specific moments when a human was detected and review only those clips. Combined with the best possible image quality settings, smart search makes the Ajax NVR a genuinely useful investigative tool even when face detail is not forensic-grade.
How to Use Ajax NVR Smart Search
- Open the Ajax app → tap your NVR → tap Playback
- Select the camera and date/time range you want to search
- Tap the Smart Search or Event Search filter
- Select Human Detection to show only clips where a person was detected
- The timeline will highlight only the relevant segments — tap each to review
- For each clip, use the full-screen mode and zoom in on the face area to assess detail
- Export clips of interest using the NVR’s export function for sharing with police or insurance
Getting More From Your Footage
- Use Vehicle Detection filter to find footage of specific vehicles — often more identifiable than faces
- Cross-reference timestamps across multiple cameras to track a subject’s movement through the property
- Review footage at 0.5x speed for clips where the subject is moving quickly — faces are clearer in slower playback
- Use the digital zoom in playback to enlarge the face area — even at 2–3x zoom, 8MP footage retains useful detail
- Export at the highest available quality setting — some export options compress the footage further
What Police Need From Your Footage
- Export the original file — not a screen recording or screenshot
- Include the timestamp overlay — police need to verify when the footage was recorded
- Provide footage from multiple cameras if available — different angles help identification
- Export a longer clip than you think is needed — context before and after the incident matters
- Note the camera model, resolution, and bitrate — this helps forensic analysts assess the footage quality
16. Positioning for Doorway and Entry Point Face Capture
The front door is the most important face capture location on any residential or commercial property — and it is also the most commonly misconfigured. Most installers mount the camera directly above the door frame pointing straight down, which produces footage of the top of people’s heads. The correct approach requires thinking about where subjects will be when their face is most visible, and positioning the camera to capture that moment.
The key insight: faces are most visible when a person is approaching the door, not when they are standing directly beneath the camera. A person standing at the door is typically 0.5–1m from the camera — too close for most cameras to focus correctly, and at an angle that shows the top of the head. A person approaching from 3–5m away is at the ideal distance and angle for face capture.
The Ideal Front Door Camera Setup
Mount beside or above the door frame at 2.4–2.8m height. Angle the camera to face the approach path — the footpath, driveway, or gate — not the door itself. The camera should be looking outward, not downward.
The primary capture zone should be 3–5m from the camera — where subjects are walking toward the door. At this distance with a 4mm lens at 2.6m height, face detail is at its best. The door itself is secondary.
Add a porch light or external LED on the approach path — not just above the door. Illuminating the 3–5m capture zone ensures colour footage at night. A well-lit approach path is more valuable than a well-lit doorstep.
Mounting directly above the door pointing straight down. This captures the top of heads and shoulders — useless for face identification. The camera is in the right location but pointing in the wrong direction.
💡 The Two-Camera Front Door Setup
For high-value properties where front door face capture is critical, the professional standard is two cameras: one positioned for face capture on the approach path (4mm lens, 2.6m height, facing outward), and one positioned for wide-area coverage of the door and immediate surroundings (2.8mm lens, higher mount, facing downward). The face capture camera catches identifiable faces; the wide-angle camera provides context and coverage. This is the setup used in commercial retail and high-security residential installations. See our CCTV camera placement guide for the full principles behind multi-camera entry point design.
17. Ajax Hybrid Illumination Cameras — Do They Fix the Face Blur Problem?
Ajax released their hybrid illumination camera range in late 2024 — cameras that combine traditional IR illumination with white LED illumination. When motion is detected, the camera switches from IR (black and white) to white light (full colour), providing colour footage at night without requiring a separate external light source. This directly addresses one of the most common face clarity complaints: black-and-white IR footage that loses colour cues needed for identification.
The hybrid illumination models are available in TurretCam and BulletCam form factors, with 5MP and 8MP sensor options and 2.8mm or 4mm fixed lenses. They represent a meaningful improvement for night face capture compared to the standard IR-only models — but they are not a complete solution to all the face clarity issues covered in this guide.
Genuine Improvements
- Colour at night — white light activation provides full-colour footage when motion is detected, preserving clothing colour, hair colour, and skin tone
- Reduced IR washout — white light illumination is more even than IR, reducing the overexposure problem at close range
- Better contrast — white light produces better facial contrast than IR in most conditions
- Deterrent effect — the visible white light flash when motion is detected can deter intruders
- Up to 50m illumination — significantly longer range than standard IR models
Remaining Limitations
- Fixed lens — still available in 2.8mm and 4mm only; no varifocal option
- Distance limitations — pixels-on-face at 10m+ remains insufficient for forensic identification
- Bitrate and compression — same settings issues apply; must still be configured correctly
- Mounting height and angle — same placement principles apply
- White light can disturb — the flash of white light when motion is detected may be unwanted in some residential contexts (bedrooms, neighbour-facing positions)
💡 Should You Upgrade to Hybrid Illumination?
If your primary complaint is blurry or black-and-white faces at night, and your camera is correctly positioned and configured, upgrading to a hybrid illumination model is likely to produce a noticeable improvement. If your primary complaint is blurry faces in daylight, or faces that are unidentifiable at distances beyond 8m, the hybrid illumination model will not solve the problem — the root cause is lens selection, mounting, or bitrate, not illumination. Fix those first before considering a hardware upgrade. See the full Ajax professional catalogue for the current hybrid illumination range and pricing.
18. Melbourne-Specific Face Capture Challenges
Melbourne’s residential environment creates specific face capture challenges that are worth addressing directly. Properties in the suburbs Sipko Security services most frequently — Brighton, Kew, Toorak, Camberwell, Hampton — share common architectural and environmental characteristics that affect camera performance in predictable ways.
Melbourne’s Latitude Problem
Melbourne’s latitude (37.8°S) means sunrise and sunset create extended periods of low-angle, high-contrast backlighting — particularly severe in summer when the sun rises and sets at extreme angles. East-facing cameras in Brighton and Hampton face the worst morning backlight conditions in Australia. The fix: WDR enabled, or reposition to face north where possible. Properties on east-west oriented streets are most affected.
Kew, Camberwell, Hawthorn
Heritage homes in Kew, Camberwell, and Hawthorn often have deep verandahs, ornate eaves, and heritage overlay restrictions that limit where cameras can be mounted. The ideal 2.6m eave-height position may not be available, forcing cameras higher or lower than optimal. In these cases, the TurretCam’s adjustable ball-and-socket mount is particularly valuable — it allows maximum angle compensation within the available mounting position.
Brighton, Toorak, Malvern
Melbourne’s temperate climate supports dense garden vegetation — large established trees, hedges, and climbing plants are common in Toorak, Malvern, and Brighton. Vegetation in the background of the capture zone creates complex, high-contrast scenes that challenge the camera’s auto-exposure. Vegetation movement also triggers motion detection constantly, generating large numbers of clips to review. The fix: position cameras to use a plain wall or fence as the background rather than a garden.
Portsea, Sorrento, Mount Martha
Holiday homes on the Mornington Peninsula — particularly in Portsea and Sorrento — face accelerated lens dome degradation from salt air and UV exposure. Lenses that are clear in year one can develop a hazy film by year three. Regular cleaning and inspection is essential. Consider UV-resistant dome covers for cameras in direct sun exposure on coastal properties.
💡 The Safety Ratings Context
Face capture quality matters most in suburbs with higher burglary rates. Read our suburb safety ratings near Brighton and our guide to security threats facing Brighton homeowners to understand where face capture investment is most justified. In higher-risk suburbs, the cost of upgrading to a 4mm lens or adding a dedicated face capture camera is easily justified by the potential evidentiary value.
19. Managing Client Expectations — What to Tell Your Client About Face Clarity
One of the most common sources of post-installation complaints is a mismatch between what the client expected from their CCTV system and what it actually delivers. Clients who have seen high-quality face capture footage on TV crime shows or in news reports often expect their residential CCTV to deliver the same quality — which is unrealistic for a standard residential installation at typical distances.
Setting accurate expectations before installation — not after — is the professional approach. A client who understands what their system can and cannot do is a satisfied client. A client who discovers limitations after installation is a complaint waiting to happen. At Sipko Security, we show every client a live view clip from the proposed camera position before finalising the installation — this single step eliminates the vast majority of post-installation image quality disputes. If you’re planning a new Ajax camera installation in Melbourne, contact us first for a site assessment and honest capability briefing.
What to Tell Clients Before Installation
- Be specific about face capture distance: “This camera will give you clear, recognisable faces at up to 5–6 metres with the 4mm lens. Beyond that, faces will be visible but may not be identifiable.”
- Set night expectations: “At night, the camera switches to black-and-white IR mode. Faces will be visible but colour information is lost. If colour night footage is important, we can add external lighting or upgrade to a hybrid illumination model.”
- Explain the difference between recognition and identification: “This system will let you recognise someone you know. For forensic identification by police, the footage may or may not be sufficient depending on the distance and conditions.”
- Discuss the primary purpose: “CCTV is primarily a deterrent and an investigative tool — not a guarantee of identification. The presence of visible cameras reduces the likelihood of an incident occurring in the first place.”
- Show them a sample clip: Before finalising the installation, show the client a live view clip from the proposed camera position. Let them assess the face detail themselves rather than discovering it after the fact.
What Ajax TurretCam Delivers Well
- Clear, recognisable faces at 3–6m in good lighting
- Vehicle registration plates at 5–8m in daylight
- General activity overview of the property
- Deterrent effect — visible cameras reduce incident likelihood
- Timestamped evidence of presence and activity
- Seamless integration with Ajax alarm for video verification
What It Cannot Reliably Deliver
- Forensic-quality face identification at 10m+
- Colour face footage at night without external lighting
- Zoom capability to enlarge distant faces (fixed lens)
- “TV quality” face capture in all conditions
- Guaranteed police-admissible face identification evidence
20. The Complete Fix Checklist — Apply in This Order
Work through this checklist in order. Each step is ranked from easiest/cheapest to hardest/most expensive. Stop when the face clarity reaches an acceptable level for your use case. If you’ve worked through the full list and still have blurry faces, call Sipko Security on 0406 432 691 — we’ll diagnose the remaining issue on-site.
- Clean the lens dome — microfibre cloth, isopropyl alcohol if needed. Takes 5 minutes. Do this first, always.
- Update firmware — camera, NVR, and Hub. Check all three. Image quality improvements ship with firmware updates.
- Check bitrate settings — confirm main stream is selected for recording, bitrate is minimum 4 Mbps, CBR mode enabled.
- Check stream settings — confirm NVR is recording main stream (8MP), not sub stream. Check playback is also set to main stream.
- Enable WDR — if camera faces east, west, or any bright background. Set to Medium as starting point.
- Check PoE switch — bypass the switch temporarily by connecting directly to NVR PoE port. If quality improves, replace the switch.
- Check cable — test with a cable tester, check link speed (should be 1000 Mbps), inspect for physical damage.
- Adjust tilt angle — ensure camera is tilted 15–25° downward, not horizontal. Adjust the TurretCam ball-and-socket mount.
- Check mounting height — confirm camera is at 2.4–3.0m. If higher, consider adding a wall bracket to bring it down. Our camera specialist technicians can remount and reconfigure in a single visit.
- Check lens focal length — if capture zone is beyond 5m and camera has 2.8mm lens, replace with 4mm lens model.
- Reposition camera — angle toward the approach path, not the door. Ensure capture zone is 3–6m from lens. See our camera placement guide for optimal angles.
- Add external lighting — for night face capture, add a white LED on the approach path to keep camera in colour mode.
- Upgrade to hybrid illumination model — if night colour footage is required and external lighting is not practical. Browse the Ajax professional catalogue for current models.
- Add a dedicated face capture camera — if forensic-quality identification at 8m+ is required, Sipko Security can specify and install a Hikvision or Dahua varifocal camera alongside your Ajax system. Call us to discuss.
Frequently Asked Questions
Why are faces blurry on my Ajax TurretCam 8MP?
The most common causes are: wrong lens focal length for the detection distance (use 4mm, not 2.8mm, for face capture beyond 4m), camera mounted too high or at the wrong angle, low bitrate settings on the NVR, IR overexposure at night, or a dirty lens dome. Work through the checklist above in order — most cases are resolved by fixing the lens selection, mounting angle, and bitrate settings.
Does 8MP mean I’ll get sharp faces?
Not automatically. 8MP is the sensor resolution — the maximum possible detail. The actual face detail you get depends on how many of those pixels are covering the face at the detection distance, how much the H.265 compression discards, and how well the illumination renders the face. A correctly configured 8MP camera at 4m with a 4mm lens delivers excellent face detail. The same camera at 10m with a 2.8mm lens delivers poor face detail regardless of the megapixel count.
Why do faces look sharp in live view but blurry in playback?
The NVR is likely recording the sub stream (lower resolution) rather than the main stream (full 8MP). Check your NVR recording settings and confirm main stream is selected. Also check that the playback stream in the app is set to main stream — some apps default to sub stream for playback even when the NVR recorded main stream.
Why are faces washed out white at night?
This is IR overexposure — the camera’s IR LEDs are too intense for the close-range subject. The fix is to increase the camera-to-subject distance, reduce IR intensity in settings (if available), or add external white-light illumination which the camera handles much better than IR at close range. The new Ajax hybrid illumination cameras also address this by using white light instead of IR when motion is detected.
What is the maximum distance for face recognition on the Ajax TurretCam?
With a 4mm lens at 2.8m mounting height: approximately 6–8m for recognition quality (enough to identify someone you know), and approximately 4–5m for forensic identification quality (250+ pixels across the face). With a 2.8mm lens, these distances drop to approximately 4–5m for recognition and 2–3m for forensic quality. Beyond these distances, faces are visible but not reliably identifiable.
Should I use 2.8mm or 4mm lens for face capture?
For face capture at entry points, driveways, and gates where the subject is 3–8m from the camera, always use the 4mm lens. The 2.8mm lens is appropriate for wide-area coverage where face capture is secondary, or for very close-range applications (under 3m). The 4mm lens cannot be retrofitted — it must be specified at the time of purchase. If you have already installed a 2.8mm camera in a face capture location, the most effective fix is to replace it with a 4mm model.
Can I use Ajax cameras as evidence in a police investigation?
Yes — Ajax NVR footage is admissible as evidence. Export the original file (not a screen recording), include the timestamp overlay, and provide footage from multiple cameras if available. The quality of the footage as evidence depends on the face detail captured — which is why correct installation and settings matter. For guidance on CCTV compliance in Victoria, see our guide on CCTV permits and compliance in Victoria.
Where We Service in Melbourne
Sipko Security provides Ajax camera installation, configuration, and face capture optimisation across Melbourne and the Mornington Peninsula. If you want your system assessed or reconfigured for better face clarity, we cover:
Still Getting Blurry Faces After All This?
A site visit resolves what settings alone cannot.
Sipko Security’s licensed technicians will assess your camera positions, lens selection, mounting angles, NVR settings, and network infrastructure in a single visit — and fix every contributing factor. We service Brighton, Kew, Hampton, Mornington Peninsula and all Greater Melbourne.
sipkosecure@gmail.com
📞 Call Now
0406 432 691
Sources and References
- Ajax Systems — TurretCam User Manual — Official documentation for TurretCam setup, lens specifications, and image settings.
- Sipko Security — Ajax TurretCam 8MP Melbourne — Product page and installation service for the Ajax TurretCam 8MP in Melbourne.
- Sipko Security — CCTV Camera Placement Guide — Comprehensive guide to camera positioning for maximum coverage and face capture quality.
- Victoria Police — Home Security — Government guidance on residential CCTV best practices and evidence requirements.
- Sipko Security — Ajax Installation Melbourne — Professional Ajax camera and alarm installation services across Melbourne and Mornington Peninsula.
