Every time WordPress resizes, compresses, or converts an image — whether that happens when you upload a photo or when a plugin creates a smaller variant for mobile visitors — it hands the job to one of two underlying PHP libraries: Imagick or GD. You’ve probably never chosen either one on purpose. WordPress just uses whatever your hosting server has installed, and most people never think about it again.

But the library your host uses quietly affects how good your images look and how small your files are. If you care about page speed or image quality (and if you’re reading this, you probably do), it’s worth five minutes to understand the difference.

What Imagick and GD actually are

Both are PHP extensions — pieces of software installed on your web server that WordPress calls on to do the actual pixel-pushing work of image processing. Neither is a WordPress plugin; they live at the server level, and WordPress simply detects which one is available.

• GD is the older, simpler, more universally available option. Almost every PHP hosting environment ships with it by default.
• Imagick is a PHP wrapper around ImageMagick, a much more powerful, general-purpose image-processing toolkit used well beyond WordPress. It’s not always installed by default, but most quality WordPress hosts include it.

WordPress core has supported both for years, and it automatically prefers Imagick when it’s present — unless a plugin or your hosting configuration says otherwise.

How they compare

Image quality

This is the big one. Imagick generally produces better visual quality at a given file size than GD, especially for modern, efficient formats like AVIF and WebP. Its compression algorithms and color handling tend to be more refined, so photos and complex images come out looking sharper with less visible compression artifacting.

GD can still produce perfectly usable images, but at the same “quality” setting, it sometimes needs a slightly larger file to achieve comparable clarity — or produces a visibly softer result at the same file size.

Format support

Imagick supports a wider range of image formats and operations. It has more mature support for AVIF — the newest, most space-efficient image format most browsers now support — and generally handles WebP conversion more reliably too. GD’s format support has improved over the years but still lags behind, and on older server setups it may not support AVIF or WebP encoding at all.

Speed and resource use

GD’s advantage is efficiency. It’s a lighter library with a smaller memory footprint, and for simple resize jobs it can process images faster than Imagick, particularly on modest hosting plans. If your server is resource-constrained (common on cheaper shared hosting), GD’s lower overhead can matter.

Summary table

Neither library is strictly “wrong.” The right choice depends on what your hosting environment actually offers — which is why checking is the useful next step.

How to check which library your host has

You don’t need to be a developer to find out. A few simple options:

• Ask your host’s support team. They can confirm in seconds whether Imagick is installed on your plan.
• Check your hosting control panel. Many panels (cPanel, Plesk, or your host’s custom dashboard) list installed PHP extensions somewhere under PHP settings.
• Use a site health or diagnostics tool. WordPress’s own Site Health screen (under Tools → Site Health → Info → Media Handling) shows which image editing library is active and which ones are available on your server.
• Let a plugin detect it for you. This is the easiest route for non-technical users — a plugin can check server capabilities automatically and simply tell you what’s available, without you needing to dig through hosting settings at all.

The recommendation: let it decide automatically

If you’re not a developer and just want the best possible result, don’t try to force one library or the other. The safest, simplest approach is a setting often labeled “Auto (Prefer Imagick)”: the site uses Imagick whenever it’s available on your server, because it typically produces the better-looking, more efficient output — and it automatically falls back to GD on servers where Imagick isn’t installed, so image processing never breaks.

This gives you the best outcome your hosting environment can support, without requiring you to know anything about PHP extensions, server configuration, or command-line tools.

How AWP handles this

AWP — Accelerate Website Pages includes an Images module that converts images to modern formats like AVIF locally, on your own server, at upload time. As part of that process, AWP detects which image libraries your host has installed and lets you choose how it should behave — including the “Auto (Prefer Imagick)” option described above, so the plugin always uses the best available library without any manual guesswork.

This matters because AWP’s broader job is making sure visitors get right-sized, modern-format images without you having to manage the technical details yourself. Whether your host runs Imagick or GD, AWP works with what’s available and quietly picks the better path — one less decision for you to make, and one more reason your images load fast and look sharp.