Background pairing

A nocap element is a rectangle of moving noise. On a flat ground that reads as a rendering fault. Put it on something with texture and the same rectangle reads as a deliberate treatment, without a single change to the split.

This is free, and that is the point. The masking constraint applies to what the split has to carry, and the page is not that. Measured on a pattern inside the element background: 0.197 raw when flat, 0.200 at 6 levels, and 0.285 raw with 0.380 blurred at 34 levels, because the split reproduces the pattern as content and its dark parts leave those pixels less headroom. Outside the canvas none of that applies, so put the texture on the page and keep the element background flat.

Texture strength 1.00 Element strength Ground Texture layer Texture in the element 16 levels

masking … one frame … texture costs nothing

Pick a pairing

What actually helps, and why

Match the scale, avoid the frequency. The single rule worth following. A texture near the noise block beats against it and produces moiré that looks far worse than either alone. Blocks in normal use run 4 to 16px, so a page texture wants to be either much finer, like grain, or much coarser, like a 46px grid. Nothing in between.

Texture beats colour. Changing the ground colour does not help, because the element already matches it. What makes the rectangle disappear is the page having a surface at all: the eye stops treating a patch of static as anomalous when the whole page has grain.

Regular against irregular reads as intentional. A dot grid or a line grid is obviously deliberate, so a viewer files the element's irregular texture as another deliberate thing. Grain does the opposite and hides it by similarity. Both work, and they are different design languages rather than better and worse.

Hero shapes work on the edges rather than the surface. Large soft blobs and rings do not disguise the noise up close, but they stop the page reading as a void with one lit rectangle in it, which is most of why the element looks stark. Pair one with grain if you want both.

What does not work

Judging the in-element texture from a screenshot. It survives into the perceived mean at full strength, but one captured frame spans about 117 levels and buries a 20-level texture completely. A screenshot shows no texture at any setting, and that is not a bug. Look at it running.
Pushing the in-element texture past about 26 levels. By 34 it has spent a third of the protection on something the page could have done for free outside the canvas.
A busy photographic background. Its own high-frequency detail competes with the noise, and the element ends up harder to read rather than better hidden.
Anything animated. The element is already moving at refresh rate. A second moving thing next to it is exhausting.
High contrast in the texture. Not because it costs masking outside the canvas, but because the element boundary becomes visible again wherever a strong pattern edge stops at it.