Reading fNIRS Outputs

fNIRS output is fundamentally different from a static image like an MRI or CT scan — it's a continuous stream of data showing how oxygenated and deoxygenated blood levels shift in the cortex over time. That real-time character is what makes fNIRS a promising tool for applications like neurofeedback and brain-computer interfaces, and its combination of spatial specificity and mobility makes it attractive for clinical use both at the bedside and in a patient's home.

What the output shows

The banana-shaped signal path

Every fNIRS reading depends on how light physically travels between a source and detector. Light entering the scalp at a source doesn't travel in a straight line — it scatters repeatedly through skin, skull, and brain tissue, following a curved path that dips down into the cortex before rising back up to a nearby detector. Because this path resembles a banana shape, it only samples the outer 5–8 mm of the cortex — the superficial layers of the brain — rather than reaching deeper structures.

This has a direct effect on how fNIRS output should be interpreted. Because the signal is confined to that curved, near-surface path, a given source-detector pair reports on a fairly small and specific patch of cortex directly beneath it. That gives fNIRS good local spatial specificity, but it also means results depend heavily on precisely where each optode sits — small variations in cap placement between sessions, combined with limited information about each person's exact brain anatomy under the cap, can shift which patch of cortex a given channel is actually reporting on, which is a particular challenge in studies that rely on repeated measurements over multiple sessions.

How often signals are captured

fNIRS systems generate their readings by repeatedly firing each light source and listening for the returning signal, a cycle that can repeat several million times per second at the level of individual photon detection. At the level of a full reading per channel, many systems use time-multiplexing — firing sources one at a time in sequence rather than all together — which lets a single detector distinguish which source a given signal came from. Depending on the number of optodes in use and how they're arranged, this multiplexing allows overall sampling rates of roughly 3 to 25 Hz for a full montage, though the underlying hardware can acquire and transmit data at rates up to 240 Hz. In practice, there's a trade-off between how fast a system samples and how much of the head it can cover at once — a larger field of view or higher source density typically means a slower effective sampling rate across the full montage.

Why speed alone isn't the full picture

There's an important difference between how fast the hardware can sample and how fast the underlying biology actually changes. fNIRS measures blood oxygenation, not the electrical firing of neurons directly, and blood flow takes time to respond to neural activity — a hemodynamic response typically peaks about 4 to 6 seconds after the triggering brain activity. So while the hardware can stream data instantly and continuously, the physiological signal it's tracking is inherently slower than the sampling rate itself.

Maintaining signal quality

Because fNIRS is often used in real-time settings, it's important that what's being measured genuinely reflects brain activity rather than noise. fNIRS signals are susceptible to contamination from both cerebral and extracerebral systemic noise — such as blood flow changes in the scalp rather than the brain — as well as motion artifacts from head or body movement. Without adequate real-time preprocessing to filter these out, a system can end up responding to noise instead of true cortical activity, which is a particular concern for live applications like brain-computer interfaces, where the output needs to be trustworthy moment to moment rather than only after offline analysis.

Practical advantages

← Back to Overview