Question 1

Is gm still maintained for Node.js in 2025?

Accepted Answer

No, gm is officially not maintained as of February 2025. The author recommends migrating to alternatives like cross-spawn with ImageMagick binaries or other npm libraries. Using it now poses security and compatibility risks.

Question 2

How to crop an image with gm?

Accepted Answer

Use the .crop(width, height, x, y) method on a gm instance. For example, gm('image.jpg').crop(300,300,150,130).write('cropped.jpg', callback) extracts a 300x300 region starting at coordinates (150,130).

Question 3

gm vs sharp for Node.js image processing – which should I use?

Accepted Answer

Sharp is actively maintained, faster, and supports modern formats like WebP, while gm is abandoned but was valued for its direct GraphicsMagick/ImageMagick integration. For new projects, Sharp is the safer and more performant choice.

Question 4

Does gm work with ImageMagick 7?

Accepted Answer

Yes, but it requires manual configuration using .subClass({ imageMagick: '7+' }), and support may be incomplete since the project is no longer updated. You might encounter edge cases with new ImageMagick features.

Question 5

How to handle errors with gm streams?

Accepted Answer

Check the callback in .write() or .stream() for errors. Common issues include missing binaries or stream buffering problems; the README warns about using {bufferStream: true} for identify operations to avoid crashes.

Question 6

What are good alternatives to gm?

Accepted Answer

Consider Sharp for high-performance processing, Jimp for pure JavaScript manipulation without binaries, or using cross-spawn to run ImageMagick commands directly for more control. Each has trade-offs in ease of use and features.

Gm

What is Gm?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions