Quick answer: Plan night imaging from the recorded task, actual light, target movement and permitted illumination. IR, visible light and low-light imaging offer different options; WDR manages scene contrast rather than supplying light. Compare the exact SKU’s lens, output, lighting and published test conditions, then record moving targets on the real site. A small lux number or light-distance row does not guarantee usable color or identification.
On this page
Why “lux rating” is the wrong first question
Minimum-illumination figures need their stated measurement conditions and acceptance criterion before comparison. Do not assume every manufacturer uses the same test, or that no common test method could exist. Exposure, gain, optics, noise and movement affect the result; obtain the exact specification and test the required recorded scene rather than ranking cameras by one number.
Define the actual target detail, distance, angle, movement, lighting and acceptance criterion/edition. The familiar 25/62.5/125/250 px-per-metre DORI table belongs to the 2014 IEC 62676-4 approach; the 2025 edition changes the task/pixel-density framework. Neither a density label nor a lux rating alone guarantees faces, plates or color in the final recording. State and test the real task. Use the IEC 62676-4:2025 application guidelines when agreeing the task and acceptance edition for the project.
Avoid treating a generic moonlight/office lux table as proof of what a camera will deliver. Actual light at the target and camera, scene contrast, spectrum, weather, exposure and movement vary. A meter can document one aspect of the site, while representative recorded clips establish whether the agreed task is met.
- Record the required night task, target positions, movement and relevant site conditions.
- Agree permitted visible/IR illumination and any privacy, neighbour, traffic or local lighting constraints.
- Compare exact camera/lens/output, power and supported lighting/exposure modes, not a technology icon alone.
- Test representative moving targets and required events/recordings under actual night conditions; record settings, results and limits.
IR: a different illumination option, not a distance guarantee
Supported IR night modes commonly use monochrome imaging, but actual filter, illumination and switching behavior varies by model/settings. Some IR hardware can show a faint visible glow; do not promise that every installation is invisible to people. CS-I8WS SD-2.8mm lists IR 50 m and white light 15 m; CS-I8XQ II-2.8mm lists 50/30 m. These are published light-distance rows, not guarantees of recorded detail or analytics at those distances.
IR can lose visible color information and be affected by reflections, near objects, weather, contamination or exposure. The end of a published beam is not automatically a point where every camera only detects and cannot identify: optics, target size, light, angle and the actual task decide. Verify whether the exact design meets the site’s illumination constraints and recorded requirement. If the night image is blurry or washed out, follow the night-image troubleshooting guide before replacing the camera.
White light: color, deterrence, trade-offs
Visible illumination can support color imaging where the actual scene, exposure and optics permit it. CS-I4SV S-2.8mm lists white light 10 m; CS-I4UV S-4mm and CS-I8WS SD-2.8mm list 15 m; CS-I8XQ II-2.8mm lists 30 m. A distance row is neither a hard optical cutoff nor a guaranteed useful radius or evidence of a particular trigger mode.
Confirm which continuous, scheduled, event or other lighting modes the exact model/firmware supports and how they operate with exposure, IR and events. A speaker, red/blue light or EW label does not establish every automatic rule/action combination. EW/AEW availability and the actual permitted deterrence workflow need exact product/project confirmation and a recorded test; do not promise an incident-prevention outcome.
Assess light spill, glare, traffic, privacy, neighbours and applicable site/local lighting requirements before choosing visible illumination. Neither constant nor event lighting guarantees useful color or insect reduction. Agree the task and allowed mode for each position, including how vehicles and pedestrians move through parking areas. For a specific product reference, review CS-I4SV S-2.8mm and confirm permitted illumination and the actual recorded result.
Low-light sensors: PhotonX and NightBright
Another option is using the scene light with supported low-light settings, optics and imaging. Sensor/aperture details and technology names alone do not establish exposure behavior or usable moving-target color. Compare the exact revision’s documented conditions and actual recorded task.
The catalog lists 0.0001 Lux for CS-I4SV S-2.8mm and CS-I4UV S-4mm, and 0.0009 Lux for CS-I86V I-180. Use the exact SKU row and conditions rather than substitute one PhotonX value for every model. IR N/A on the two 4 MP models means no listed IR illuminator; it does not prove every monochrome mode is absent. Check that exact turret’s documented lighting modes against the task before choosing it.
PhotonX and NightBright names are not interchangeable performance specifications or universal minimum-lux values. Do not promote an unverified older model from a previous comparison. One letter can change the actual hardware rows: CS-I8WS S-2.8mm lists white light N/A, while CS-I8WS SD-2.8mm lists 15 m. Confirm actual modes and task performance instead of inferring them from a name or icon. Request the IP camera user manual for the exact model and firmware when a supported mode is unclear.
WDR: the other half of night footage
Mixed bright/dark scenes can be a major challenge, alongside low light, motion, focus, weather and other factors. WDR implementation and resulting motion/noise/artifacts vary. A published 120 dB row does not prove every headlight/plate task or a particular exposure algorithm; compare exact supported settings and actual moving-target recordings.
Compare supported WDR/exposure settings on the real scene, including required moving targets and changing headlights/doorway light. Do not prescribe always-on for every entrance or always-off for every dark scene. Choose the tested setting that meets the agreed task, and retain the conditions and any trade-offs.
Which CASE camera for which night?
| Exact catalog candidate | Minimum illumination / lighting rows | Task check |
|---|---|---|
| CS-I4SV S-2.8mm | 0.0001 Lux; IR N/A; white light 10 m | 2.8 mm fixed; actual color/motion, light policy and recorded task |
| CS-I4UV S-4mm | 0.0001 Lux; IR N/A; white light 15 m | Different 4 mm lens/output/environment; not an automatic substitute |
| CS-I8WS S-2.8mm | 0.002 Lux; IR 50 m; white light N/A | Actual supported night modes and required target detail |
| CS-I8WS SD-2.8mm | 0.002 Lux; IR 50 m; white light 15 m | Confirm supported light switching and recorded task |
| CS-I8XQ II-2.8mm | 0.002 Lux; IR 50 m; white light 30 m | ExactII revision, light/speaker/event controls, power and integration |
| CS-I86V I-180 | 0.0009 Lux; IR 30 m; white light 30 m | 4640×1728 at 25 fps stitched output; actual pixels/task across the required view |
General category policies are a starting point, not a warranty for every SKU. Confirm the term, exclusions and claim process for the exact model and revision in writing. Project Series items, intercoms, powered accessories and model-specific exceptions need their own confirmation; hard-drive claims follow the applicable drive-manufacturer terms. Confirm exact product/order terms rather than infer every component from the camera category. For a turret vs dome camera comparison, shortlist turret options in the shop and check the exact mounting specifications for both models. Approved demo purchases may have a 90-day test period under the approved demo return process and conditions; this is not a general return right or a guarantee the site test will pass.
What to tell your customer
We will agree what the night recording must show and the illumination your site allows, then compare supported camera/settings on representative moving targets. The final choice follows the recorded result and documented limits, not the smallest lux number or a universal door/perimeter housing rule.
FAQ
Is a full color night vision security camera better than infrared?
It depends on the required recorded task and permitted light. Useful color can add information, but low light, movement, exposure and glare still matter; IR has its own limitations. Compare the exact supported design and actual recordings rather than assign every door to color and every long view to IR.
What does 0.0001 Lux actually mean on a spec sheet?
It is the published minimum-illumination row under the applicable measurement/acceptance conditions, which must be obtained before making a fair comparison. CS-I4SV S-2.8mm and CS-I4UV S-4mm list it, but it is not a guaranteed moonless-night identification or moving-target color result. Test the actual camera and site.
Does white light on a camera count as a deterrent?
Visible or event lighting may be part of an agreed deterrence strategy, but no automatic crime-prevention or rule/action behavior follows from the label. Confirm actual supported lights, speaker, events and permissions for the exact SKU/firmware and project, then test the required image/control result. When illumination changes scene contrast, use Axis’s general WDR guide to structure the image comparison; confirm CASE settings separately.
Do I need WDR on a night camera?
Compare supported WDR settings against the real contrast, movement and recording task. A dB value does not prove every headlight/plate result or that WDR should always be enabled/disabled for a named scene. Retain the tested settings and limits.
References
- IP camera user manual
- Axis: general WDR performance and artifacts; confirm CASE implementation separately
- IEC 62676-4:2025 application guidelines
