Connect the source MASK to GrowMask and use a positive expand value to expand the mask or a negative value to contract it. Check the receiving node’s actual input requirements and confirm the connection works in your current workflow; matching port labels or colors alone do not establish compatibility. Compare the output with the input, then decide whether tapered_corners should be enabled. This changes mask extent, not edge softness.
Choose a direction before tuning
Start with the visible mismatch: does the mask stop short of the intended region, or extend beyond it? A mask that is too small suggests testing a positive value. A mask that includes unwanted area suggests testing a negative value. The documentation specifies these directions, but does not prescribe a universal amount or a unit-to-pixel conversion. Treat the value as a control to tune in your workflow, not as a guaranteed measurement of boundary movement.
Keep the input and output available for comparison. If the downstream result changes, inspect the mask boundary itself before attributing the difference to another node. The GrowMask documentation describes the node as modifying mask size through expand and optionally applying tapered corners.
Adjust it in a controlled sequence
- Connect the source
MASKto themaskinput. Check the receiving node’s actual input requirements and confirm the connection works in your current workflow; port labels or colors alone are not proof of compatibility. Confirm that the connected mask is the region you mean to modify. - Set
expandto a positive value if the boundary needs to extend outward, or a negative value if it needs to move inward. Start with a modest test value; the documentation gives no universal amount or pixel conversion. - Compare the output mask with the input in the same relevant area. Check the target boundary and nearby regions you need to protect.
- Change
tapered_cornersseparately. As an author-recommended comparison, holdexpandconstant and inspect both settings; this is a suggested workflow check, not an official test result. - Keep the version that best meets the target and protection-boundary criteria. If one edge improves while another worsens, do not assume a single
expandvalue can satisfy both. Revisit the source mask or use another workflow operation whose behavior and compatibility you have confirmed.
Separate boundary size from edge softness
GrowMask is relevant when the mask’s footprint is too narrow or too broad. Feathering addresses a different question: how gradually the mask transitions at its edge. A boundary can be in the right place and still look too abrupt; expanding or contracting it does not, by itself, establish that the transition has become softer. Conversely, softening an edge is not a substitute for removing a clearly unwanted region from the mask.
Use this distinction when troubleshooting: first decide whether the wrong area is included, then decide whether the edge transition is too hard. Adjust the GrowMask boundary for the first problem. Assess any separate softening control in the workflow for the second; the cited GrowMask documentation does not identify such a control on this node.
Example acceptance check
The figures below are hypothetical observations, not tested results or a promised pixel conversion. Suppose a creator’s mask is short of the intended object boundary on one side and includes a narrow strip of background on another. They compare a small positive test with a small negative test, then inspect both tapered_corners settings.
| Hypothetical trial | Observation to record | Decision |
|---|---|---|
Positive expand; corners off | The short side improves, but more background is included on the opposing side | Record both edges; do not treat one improved edge as an overall pass |
Negative expand; corners off | The background strip recedes, but part of the intended region is lost | Record the target-versus-protection tradeoff; reduce the adjustment or reject it |
| Same value; corners on | Corner shape differs from the off setting | Choose by the corner boundary needed; do not assume this feathers the full edge |
| Smaller adjustment; compare both corner states | The target and protection boundaries are closer to their criteria, or a conflict remains | Accept only if both criteria are met; otherwise revisit the source mask or use another confirmed workflow operation |
For an actual task, record the sign, chosen value, corner setting, and the specific edge you checked. This makes it possible to explain why a setting was kept without claiming a numeric effect the documentation does not guarantee.
If the result is wrong
If the intended region gets smaller when you need it larger, check the sign of expand. If the output is still too broad or narrow, change the value incrementally and recheck the same boundary. If only the corners are problematic, hold the value fixed and compare tapered_corners on and off. If the mask has the desired footprint but an unsatisfactory transition, treat that as an edge-softness issue and look for a separate workflow control rather than expecting GrowMask to feather it.
The documentation does not state the node’s numeric limits, exact expansion distance, implementation details, or whether a particular setting will preserve fine structures. Do not infer those properties from the parameter names alone. Inspect the output for narrow features and nearby regions that matter to your image, and use a different supported mask operation if GrowMask cannot meet the boundary requirement.
Does a positive value always make the mask better?
No. It expands the mask, which may include areas you did not intend. Use it only when the boundary needs to extend outward.
Does `tapered_corners` feather the mask edge?
The documentation describes a tapered effect at corners. It does not say that this setting feathers the whole edge, so compare the corner shape separately from edge softness.
Does `expand` specify a pixel distance or have a documented universal range?
No. The cited GrowMask documentation identifies expand as an INT that determines the magnitude and direction of modification, but gives neither a pixel conversion nor a universal numeric range. Tune it against the output in your workflow; do not infer an exact boundary distance from the value.
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.