Connect the existing MASK to FeatherMask and set left, top, right, and bottom for the corresponding canvas edges you want to feather. The documentation defines each input as an integer distance from its corresponding edge within which feathering is applied, but does not specify what a value of zero does. Treat zero as a setting to verify, not as a documented guarantee that an edge will remain unchanged: check the current node’s control information and compare its output mask with the input before relying on that behavior. No universal distance or visual result is prescribed.
Identify the edges that need a transition
Start with the mask connected to FeatherMask, not with guessed values. View the input mask and mark which of its four canvas boundaries needs to blend into the surrounding area. For example, a mask touching only the left boundary may need a left-side transition while the other three boundaries should remain as intended. Verify the result in the output mask rather than inferring unchanged edges from their parameter values. A boundary that does not reach the canvas edge is a different case: the documented controls refer to distances from the canvas edges, so do not assume they are per-object-edge feather controls.
FeatherMask changes the mask’s edge opacity over the specified distances. That is distinct from GrowMask, whose role is to change the mask boundary’s extent. If the selected region is too narrow or too wide, changing feather distances is not the same operation as correcting its extent.
Set the four values in order
- Connect the current
MASKoutput to FeatherMask’smaskinput. Keep the node’s output connected to the downstream mask input you intend to use. - Decide which canvas edges should soften. Record those edges before editing; do not infer the desired sides from the node’s left-to-right control order alone.
- Set
leftfor the left canvas boundary,topfor the top,rightfor the right, andbottomfor the bottom. For sides you do not intend to feather, check the current node’s control information for the appropriate setting; the cited documentation does not define zero’s behavior. Verify those sides in the output mask rather than treating any parameter value as proof that they stayed unchanged. - If several sides need feathering, adjust one side at a time while viewing the output mask. This makes it easier to associate a visible change with its control. Treat the entered distances as test values, not as a guaranteed pixel-to-appearance recipe; the documentation identifies them as integer distances but gives no universal recommended range.
- Compare the input and output masks at the same view scale. Check both the intended edge and the edges whose controls are zero. Confirm that the output still represents the region you meant to use.
Diagnose with a hypothetical mask
The figures below are hypothetical setup values, not measured recommendations. Suppose a 1024-by-768 canvas has a mask that reaches the left boundary, while the other three boundaries should stay unchanged. As an author-suggested comparison experiment, record the current output, set left = 24, and use the current node’s control information to choose settings for the other sides; do not assume that zero leaves them unchanged. Compare the resulting output mask with the input and the recorded baseline, checking all four edges. The value 24 and this test setup are hypothetical, not an official recommendation or measured result.
| Observation in the output mask | What to check next | Decision |
|---|---|---|
| Left boundary now has a gradual transition | Compare it with the input and check whether the transition reaches farther than intended | Keep or reduce left based on the visible mask |
| Another boundary appears softened | Compare the actual FeatherMask output mask with the input first; then check that side’s parameter, the input mask, and the node connection | Judge the observed output rather than inferring behavior from a zero value |
| No visible change at the expected side | Verify the correct mask is connected and that the mask actually reaches that canvas edge | Recheck the setup before increasing values |
| Region size seems different, not just softer | Compare the mask boundary with the input | Consider whether the problem is mask extent rather than feathering; FeatherMask is documented as an edge-feathering node |
If the result is not what you intended
First confirm that you are inspecting FeatherMask’s output, not only its input or a downstream image preview. Then recheck the four side-to-control mappings and whether the input mask touches the edge you intend to soften. Change one distance at a time so the next comparison identifies which setting affected the output. If the issue is that the mask covers too much or too little area, correct the mask’s extent with an appropriate workflow rather than treating FeatherMask distances as a substitute for boundary growth or shrinkage.
The documentation does not specify how a chosen distance will look for every mask, provide a universal numeric preset, or explain additional controls for feathering arbitrary interior contours. Judge the actual output mask in your graph. A downstream image can make a mask transition harder to assess, so use the mask view when available.
Common questions
Does zero mean that an edge will not be feathered? The cited documentation does not specify the behavior of a zero distance. Check the current node’s control information and verify the output mask against the input before relying on zero to leave an edge unchanged. Node behavior should be confirmed for the version in use, not inferred from this documentation.
Does FeatherMask enlarge the selected area? Its documented function is to soften mask edges by changing opacity across specified distances. The documentation does not describe it as a mask-growth control. Use a boundary-size operation when the region itself needs to expand or contract.
What distance should I start with? There is no universal value in the cited documentation. Start with a modest test value suited to your canvas and inspect the output, then adjust the relevant side based on the visible transition.
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.