What it is
A script draws text in a few fonts and some shapes on an invisible canvas, reads the pixels back, and hashes them. The same code produces slightly different pixels on different combinations of GPU, driver, operating-system font rendering and anti-aliasing, so the hash separates devices.
It is stable: the same machine gives the same hash every time, which is why it is useful to a tracker and why it survives clearing cookies.
Why it matters
Two profiles on one machine produce the same canvas hash unless something changes it. Tools that add noise to the canvas make profiles differ, but noise that changes on every read is itself detectable: a hash that never repeats is unusual.
What to do
The noise has to be stable per profile and agree with the rest of the fingerprint. Random per-read noise and a graphics vendor that contradicts the operating system are the two common mistakes.
In Clout Browser
Canvas, WebGL image and audio noise are produced by the browser engine, so the same configuration run on a different engine reads differently. That is why a Clout Browser profile always opens with the engine it was made for.