Skip to content

Non-local means denoising

Algorithm atlasPhotography

Average pixels whose surrounding patches look similar, even when they are not immediate neighbours.

Try it on your image ↓

VISUAL WALKTHROUGHPhotography
REFERENCE INPUTNoisy or uneven image

The same scene stays here while the working view changes.

RESULTApply the rule at every pixel

The whole image has now been processed. The highlighted input value 156 becomes 156.2.

STEP 03 / 03

Average corresponding pixel values using those weights.

Computed teaching example on a 24 × 16 image. Small kernels and simplified settings keep each change visible; use the image laboratory for native OpenCV.

Try it on an image

YOUR IMAGE · REAL OPENCV

Experiment at pixel level

Open full lab ↗

Denoise the colour image by comparing similar patches.

The engine loads on your first run. Your images stay in this browser.

Input448 × 320
OutputWaiting for a result

Scroll over either image to zoom at the pointer. Use the scrollbars to pan both views over the same relative area. Zoom is relative to the input; pixel coordinates belong to each image. Warps can change scene correspondence.

Pixel inspector RGBA · native values · matched scale · 9 × 9 output pixels
Hover to inspect. Click to pin a pixel.
Input
Select a pixel

Output
Select a pixel

Sample models and licenses

When to use it

Reduce image noise while preserving recurring texture and structures.

How it works

  1. 01Compare the patch around a pixel with nearby candidate patches.
  2. 02Convert patch similarity into weights.
  3. 03Average corresponding pixel values using those weights.

weight depends on patch similarity, not only pixel distance

What to tune

h controls filtering strength; templateWindowSize sets patch size; searchWindowSize sets the candidate region.

Where it breaks down

Strong filtering can make textures waxy. Larger search windows cost more, and multi-frame variants depend on temporal consistency.

TypeScript API

Open an entry for its exact overloads, parameter descriptions, result ownership and pinned upstream source.

All of these calls execute on the CPU. Native objects need explicit disposal. See matrices and ownership and build compatibility.