
With ImageMagick morphology, a list of kernels can run sequentially or produce separate results that are composited. Under composition None, each kernel consumes the previous kernel's result. An explicit method such as Lighten instead combines results computed from the original input. Two directional kernels therefore need not produce the same shape under both policies.
Describe the dependency you intend
For a controlled example, imagine one bright point on black with ample surrounding space. A horizontal blur followed by a vertical blur produces a different dependency from independently blurring that point in both directions and taking their lighter contributions.
That distinction concerns intermediate pixel data, not the order in which two filenames appear in a handoff. The independent-variant guide addresses creative outputs with different relationships, rather than this kernel execution graph.
Select the combination policy explicitly
The official multiple-kernel example uses Blur:0x1> to create rotated kernels. Proposed POSIX-shell comparisons are:
magick single-pixel.png -define morphology:compose=None -morphology Convolve 'Blur:0x1>' sequential.png
magick single-pixel.png -define morphology:compose=Lighten -morphology Convolve 'Blur:0x1>' independent-lighten.png
These commands have not been executed. Confirm the installed ImageMagick 7 kernel syntax and preserve the controlled input. The historical usage examples describe the mechanism; they do not supply a benchmark for your build.
Inspect the intermediate interpretation
For the sequential result, the second kernel acts on a result already changed by the first. For the Lighten result, each kernel begins with the original source, then its contribution joins the composite.
Inspect the center, horizontal extension, vertical extension and diagonal region. A different appearance is not necessarily a malformed kernel; it may be the selected dependency policy.
If display enhancement is needed, create separately identified viewing derivatives. Do not mix auto-leveling one candidate with leaving the other unscaled and then interpret the contrast difference as the kernel-combination effect.
Choose a compositor for its actual mathematics
Lighten is the documented example, not a universal replacement for sequential convolution. Other compose choices have different meanings. The layer-blend guide addresses another compositor's appearance decisions; it does not define ImageMagick morphology's input dependency.
Accept the candidate when the declared kernel list and combination policy produce the intended inspected structure. No filter comparison, measured speedup or claim that one policy is inherently better is reported.
Related tasks
- Do Four Generated Images Mean Four Alternatives or a Four-Part Story?
- Which Kdenlive Blend Mode Fits a Darker, Lighter, Contrast, or Color-Only Composite?
Sources and scope
- ImageMagick morphology examples: kernel_compose: None re-iterates kernel results sequentially; an explicit compose such as Lighten combines independent results from the original input.
- ImageMagick 7 morphology operator: Current command-line reference links to the official morphology examples; confirm installed methods and kernels.
The official ImageMagick morphology usage page was captured with HTTP 200 on October 23, 2026. It includes historical examples and explicit legacy version notes. Commands, calculations and acceptance exercises here are proposed, not executed; verify the installed ImageMagick 7 methods, kernel behavior, quantum precision and shell syntax.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.