Learn ImageMagick - Modern Features & Roadmap

#Introduction

In episode 20 we brought ImageMagick into applications via APIs and bindings. To close the technical discussion, let's look out the window: what's happening with ImageMagick itself in 2026. The version you install today isn't the same product released five years ago — and understanding this journey helps you make the right installation and configuration decisions.

In this episode 21 we'll cover ImageMagick 7.x: the unified magick command, modern format support (WebP, JPEG XL, HEIC, AVIF), the coder and filter environment variable revamp, regular release cycles, an outline of the still-maintained 6.x legacy releases, and its official roadmap.

#ImageMagick 7.x: The Unified magick Command

Since version 7, ImageMagick introduced a single main binary: magick. All the old commands that used to be separate — convert, mogrify, identify, montage, compare — are now subcommands within it:

magick convert input.png output.jpg
magick identify -verbose image.webp
magick mogrify -resize 50% *.jpg

It's not just about simplifying naming. The unified command brings real improvements: a consistent command architecture, full support for all of ImageMagick's features, and more focused maintenance. For compatibility with old scripts, ImageMagick 7 still ships convert, identify, etc. symlinks — but new scripts should use magick directly.

#Modern Format Support

#WebP with Better Compression

WebP is Google's highly efficient format for the web. ImageMagick 7.x keeps improving its WebP coder: finer quality control, alpha support, and a lossless mode comparable to PNG:

magick input.png -quality 90 -define webp:lossless=true out.webp

The rule of thumb: use lossy WebP for photos (-quality 75–85 is usually indistinguishable from JPEG at half the size) and lossless WebP for logos and UI.

#JPEG XL (JXL)

JPEG XL is the next-generation format designed to replace JPEG: higher quality at the same size, lossless support, and a smooth transition from legacy JPEG. ImageMagick 7.x supports it through the JXL coder:

magick input.png -quality 85 out.jxl

JXL's most practical advantage: lossless transcoding from JPEG — you can convert JPEG to JXL and back without losing quality, something other formats can't do to already-compressed JPEG files.

#HEIC and AVIF via libheif

HEIC and AVIF are HEIF-based formats popular in the Apple and modern ecosystems. ImageMagick processes both through libheif — not rewritten from scratch, but delegated to the external library. This is the same delegation pattern as formats in episode 13: ImageMagick provides the API layer, the external library provides the codec:

magick input.png -quality 80 -define avif:quality=80 out.avif

AVIF offers remarkable compression for photos — often 30–50% smaller than WebP at comparable quality — at the cost of higher encoding speed. Good for archives and serving images that rarely change.

#The Coder & Filter Environment Variable Revamp

One of the less visible but important technical improvements is the revamp of how ImageMagick locates coder and filter modules. In version 7, the old path mechanism was replaced by two clearer environment variables:

• MAGICK_CODER_FILTER_PATH — the list of directories where ImageMagick looks for coder and filter modules (colon-separated on Linux).
• MAGICK_FILTER_MODULE_PATH — more specific to filter modules (for example the MODEL, CUSTOM, and similar filters).

The goal: separate module sources from configuration, so binaries can be moved without breaking module lookup, and multi-architecture installations (for example different architectures for delegate library arch) can use the right paths:

MAGICK_CODER_FILTER_PATH=/opt/im/modules/coders \
MAGICK_FILTER_MODULE_PATH=/opt/im/modules/filters \
magick convert input.png out.webp

#Security: Advisories and Policy

Since the ImageTragick incident in episode 14, ImageMagick has taken a far more disciplined security approach. In 2026, there are two things you should know:

1. Security advisories are released regularly. Found vulnerabilities — especially in coders for exotic formats like SVG, MVG, and MSL — are published and fixed quickly. This is the main reason why always using the latest version is part of the security strategy, not just about features.
2. policy.xml remains the primary defense wall. All the lessons from episodes 14 and 15 still apply: disable unused coders, limit resources, and never trust user input without validation.

#Release Cycles

ImageMagick's current release policy splits releases into two tracks running simultaneously:

The 7.1.2-x track is released very often — sometimes weekly — because the ImageMagick team follows a small-and-frequent release model. Don't be surprised to see many releases in a month; that's normal. Meanwhile, the 6.9.13-x releases are kept for organizations that can't migrate to 7 yet because of thousands of legacy scripts. If you're starting from scratch, choose 7.x without hesitation.

#Roadmap

Based on official announcements and the team's development direction, ImageMagick's roadmap centers on three axes:

1. Modern format improvements — continuous refinement of the JXL and AVIF/HEIC coders, including more granular effort/quality control and faster encoding.
2. Performance — continuously improving core speed (resize, filter, decode) and low memory usage, especially for multi-threaded operations and large batch pipelines.
3. Security policy — tightening policy.xml defaults, reducing coder attack surface, and responding quickly to emerging security advisories.

There's no "total rewrite" plan — the ImageMagick team chooses stable evolution over a mature architecture. For you as a user, that means: the skills you've learned across these 21 episodes remain relevant and only get better over time.

#Closing

In this episode 21 you've seen ImageMagick's state in 2026: the unified magick command, full WebP, JPEG XL, and HEIC/AVIF support via libheif, the coder and filter path variable revamp, a weekly-to-monthly release rhythm on the 7.1.2-x track (with 6.9.13-x still maintained), and a roadmap centered on modern formats, performance, and security policy. ImageMagick isn't a frozen project — it keeps moving, and the security and version decisions you make today determine tomorrow's pipeline stability.

Episode 22 will be the final episode of this series: Ecosystem, Alternatives & Final Reflections — comparing ImageMagick with GraphicsMagick, libvips, sharp, and ImageSharp, when to choose which, a recap of all episodes, a production checklist, and the closing of this 23-episode series.