<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Imagemagick on Khadirullah Mohammad</title><link>https://khadirullah.com/tags/imagemagick/</link><description>Recent content in Imagemagick on Khadirullah Mohammad</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>contact@khadirullah.com (Khadirullah Mohammad)</managingEditor><webMaster>contact@khadirullah.com (Khadirullah Mohammad)</webMaster><copyright>© 2026 Khadirullah Mohammad</copyright><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://khadirullah.com/tags/imagemagick/index.xml" rel="self" type="application/rss+xml"/><item><title>The Ultimate Guide to Automating SVG Rasterization: Inkscape vs ImageMagick vs Headless Chrome</title><link>https://khadirullah.com/blog/svg-rasterization-engine-showdown/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><author>contact@khadirullah.com (Khadirullah Mohammad)</author><guid>https://khadirullah.com/blog/svg-rasterization-engine-showdown/</guid><description>Automating social media preview images (Open Graph) using SVGs is incredibly powerful. But when I tried to automate SVG-to-WebP conversions on my Linux server, I discovered that standard command-line tools like Inkscape and ImageMagick handle browser-oriented SVGs very differently from Chrome.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://khadirullah.com/blog/svg-rasterization-engine-showdown/featured.svg"/></item></channel></rss>