VIIRS Nightfire vs. commercial satellite flare counts: what's the difference

What VIIRS Nightfire measures

NOAA's VIIRS Nightfire product, built from the VIIRS sensor flying on Suomi NPP and NOAA-20, has been the default free source for flare detection for over a decade. It fits multiple infrared bands against a blackbody curve for each hot spot it finds, then reports an estimated temperature, radiant heat output, and source area for every flare pixel detected, every night, everywhere the satellites pass over. The World Bank's Global Gas Flaring Reduction Partnership leans on it for the country-level flaring estimates that end up in national rankings and ESG disclosures.

That's a genuine public good, produced and maintained for exactly that purpose. It's also a dataset built for a different job than the one most regulators and fund analysts need to do on a Tuesday afternoon.

Where the free data runs out

Nightfire ships as a global point file, and someone on your team has to turn that file into a usable tool before it's any good against one concession, one lease block, or one basin. That means pulling the files, filtering them spatially, deduplicating overlapping passes from two satellites, and reconciling detections that drop in and out because of cloud cover or saturation on very hot flares. None of that is hard exactly. It's work that has to happen every time you want a current read, and the output is a scatter of hot-spot records rather than a running log tied to named assets.

Commercial flare monitoring narrows the same thermal detection down to one job: a nightly count and size read on a defined monitoring area, formatted as a log instead of a raw point file. Instead of a global dump you filter yourself, entries come scoped to the fields or operators you regulate or hold positions in.

If you're building a national or global flaring trend line, Nightfire is the right starting point, and it's free. Researchers have used it that way for years, and there's no reason to pay for a global scan NOAA already publishes.

The gap shows up at the asset level. An ESG analyst checking an operator's self-reported flaring volumes against an independent read needs flare activity tied to that operator's fields specifically, on a schedule that lines up with reporting periods, not a global file that has to be re-filtered every quarter. A regulator cross-checking permits against actual flare activity needs the same thing: a log scoped to a jurisdiction, not a planet. That's the gap Flare Monitoring works from: a nightly count and size read on your monitoring area, drawn from night-time and SWIR imagery as a proxy for production activity, delivered as a log rather than a file you have to process yourself.

A few things to check before you rely on either

Neither a free global dataset nor a commercial flare log measures emissions directly. Flare counts and sizes are a proxy for production activity and flaring intensity, one input into an emissions estimate, not the estimate itself. Flare efficiency, gas composition, and venting that never gets lit don't show up in either kind of thermal detection. If your report needs emissions figures, the flare count feeds a model. It doesn't replace one.

Cloud cover and satellite revisit timing affect both sources the same way. A missed night in the log usually means the satellite's pass didn't catch the flare, while the flare kept burning underneath the clouds. When a known flare site shows a one-night gap, check the next night's pass before assuming anything changed at the field: the gap is almost always the orbit, not a shutdown.

So the choice isn't really free versus paid. A global baseline for trend analysis is one job. An asset-level record scoped to the sites you're accountable for, ready to hand to a compliance team or an investment committee, is another. If it's the second one you're after, that's what to ask for.