A Krita pass-through group is useful when a blending mode on a layer inside the group must affect layers outside that group. However, Krita’s official Layers documentation states that pass-through does not currently work with masks; group-layer mask-related indicators are shown with a strike-through. Therefore, verify both the intended blend scope and the mask limitation before approving the group structure.
Concrete Decision and Steps
Use pass-through only when the design requirement is specifically that an internal blending mode participates in composition beyond the group boundary. A hypothetical overlay group may contain a Multiply paint layer, while the required result is for that layer to darken an external background layer.
- Identify the actual group and confirm its children by layer type and label. Do not use a color cue as proof of a layer’s function; rely on the layer information and visible hierarchy.
- Record the intended scope: should the internal
Multiplylayer affect only content in the group, or should it also affect the external background? - Inspect the group’s pass-through control in the Layers docker. With pass-through enabled, compare the group’s effect against the external background. This comparison is an editorial acceptance method, not a claim about an untested rendering result.
- Inspect the group and its masks for the documented strike-through indicator. If a required mask is marked as unsupported in pass-through mode, treat that as a compatibility warning rather than assuming the mask still controls the result.
- If the mask is essential, disable pass-through and reassess the composition as an ordinary group. Record the expected internal-only blend result separately from the cross-group result.
The Krita Layers documentation defines pass-through as allowing blending modes of layers inside a group to affect layers outside it. The same documentation states that it does not currently work with masks.
A New Acceptance Worksheet
The following is a hypothetical worksheet for a three-layer arrangement. Its observations are project-specific and are not guaranteed software behavior.
| Check | Assumed setup or observation | Decision |
|---|---|---|
| Internal blend | Multiply paint layer is inside Tone Group | Keep pass-through only if external influence is required |
| External target | Background layer sits below the group | Compare the background with pass-through on and off |
| Mask state | Group mask shows the documented strike-through in pass-through mode | Treat the mask requirement as incompatible until resolved |
| Non-pass-through comparison | Group is switched off from pass-through and internal result is reviewed | Approve this structure if the group can remain self-contained |
| Final requirement | Background must darken from the internal layer, and the mask must remain authoritative | Reconsider the group design; do not approve on appearance alone |
Limits and Next Steps After Failure
If pass-through produces the needed cross-group blend but the required mask is unavailable or marked as unsupported, there is no documented basis for promising that both behaviors will operate together. Keep the pass-through version as a comparison state, then build a non-pass-through alternative and define its expected internal composition. If that alternative cannot meet the visual brief, escalate the structure for a different layer arrangement or consult current Krita documentation before changing artwork.
Do not infer a specific mask algorithm, pixel count, or automatic correction from the strike-through icon. The icon is a documented compatibility signal, not proof of how every masked result is calculated.
Three Short Questions
When do I need pass-through?
When a blending mode on content inside the group must affect content outside the group.
Does pass-through guarantee that a group mask remains usable?
No. The official documentation explicitly records a current mask limitation and shows a strike-through indicator.
What is the practical fallback?
Turn pass-through off, review the group as an independently composited unit, and approve it only if that scope matches the brief.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.