What “radiometric” actually means

In practical OEM work, radiometric capability means the camera has been calibrated so its output can be related to scene temperature. Depending on the module and software interface, the host may receive a temperature matrix, use spot and area measurements, set threshold alarms, or store temperature data for later analysis.

Some radiometric modules expose calibrated temperature information for every pixel. Others provide measurement functions through a dedicated SDK or data channel. The word on the product page is not enough; the exact output format still needs to be confirmed.

A useful radiometric system includes more than a detector. It needs calibration, a defined measurement range, appropriate optics, suitable software access and a way to handle the scene parameters that affect the result.

Non-radiometric does not mean low-quality

A non-radiometric module still detects long-wave infrared energy and turns the differences into a useful image. It can reveal a warm motor, a person in darkness, an overheated cable or a cold patch in a building surface. What it cannot do is report a calibrated absolute temperature that should be treated as a measurement.

For many products, that is perfectly acceptable. The operator may only need to find the warmer component. A robot may only need to locate a heat source. A monitoring system may only need to detect that the scene has changed. In these cases, image stability, field of view, latency, size and power can matter more than radiometry.

Removing a function that the product never uses is not a downgrade. It is often good engineering.

The difference at a glance

Two similar images can serve very different products

The difference becomes clearer when the same warm component is placed in two different product requirements.

The image may look nearly identical to the operator. The data behind it—and the responsibility placed on that data—is not identical.

Radiometric does not automatically mean accurate

A calibrated module gives the system a route to temperature measurement. The final reading still depends on how the target and the scene are handled.

Emissivity is the first problem. A painted motor housing and polished metal do not emit and reflect infrared energy in the same way. Enter the wrong emissivity and a precise-looking number can still be wrong. Reflected temperature also becomes important on low-emissivity surfaces because the camera may be reading more of the surroundings than the object itself.

Distance, atmospheric temperature, humidity and any external infrared window can add further error. At short range in a controlled setup, some of these corrections may be modest. At longer distances or through a protective window, they deserve proper attention.

NETD is not temperature accuracy

This mix-up appears constantly in thermal camera discussions. NETD describes sensitivity: how small a temperature difference the imaging system can separate from its own noise. Temperature accuracy describes how close a reported value is to the real temperature.

A lower NETD can preserve weaker thermal detail and produce a cleaner image in low-contrast scenes. It does not guarantee that the number printed beside the crosshair is closer to the truth. A non-radiometric module can have excellent NETD, and a radiometric module can still give a poor result when emissivity or scene settings are wrong.

For a closer look at sensitivity, read our guide to 25mK vs 40mK NETD.

A video stream is not the same as temperature data

Seeing a thermal image on a laptop does not prove that the host can read radiometric values. The picture may be a processed 8-bit or colorized video stream intended for display. Temperature data may travel through a different endpoint, a proprietary protocol or an SDK—or it may not be available at all.

For the video-side decision, see our comparison of PAL and UVC thermal camera interfaces.

Systems that need separate viewing, control and analysis paths may also benefit from multi-interface thermal camera modules.

Which one do you actually need?

Start with the product action, not the camera label. The following table is a starting point, not a substitute for testing the real scene.

Seven questions to settle before ordering a sample

1. Does the product need an actual temperature value, or only a thermal image?
2. Is temperature required at every pixel, at selected points, or only as a threshold alarm?
3. What measurement range and accuracy does the application genuinely require?
4. Will the host receive UVC video, raw data, radiometric data—or more than one of these?
5. Does the SDK support the target operating system and the production firmware?
6. Will the camera look through an external infrared window or operate at a meaningful distance?
7. Is the additional calibration and software work justified by the final product?

Radiometry is only one part of the final configuration. Lens, interface, connector and mechanical fit can also be reviewed as part of a custom OEM thermal camera module project.

Frequently asked questions