This week, we made libvips the default image processing library in Discourse as part of our ongoing work to make processing user uploads more secure. DEV: Enable vips image processing by default (#44870) committed 07:09AM - 26 Oct 26 UTC (UTC) [imagem] tgxworld +8 -3 This commit enables libvips image processing by default. Operators can retain Im…ageMagick processing by setting `DISCOURSE_ENABLE_VIPS_IMAGE_PROCESSING=false`. The `enable_vips_image_processing` global setting is experimental and will be removed soon. Although this isn’t a direct port of the ImageMagick operations, we do not expect any noticeable changes in how images appear to end users. In the coming weeks, we plan to remove the ImageMagick dependency from the Discourse Docker images. Questions? Comments? Spotted something weird with images? Let me know!

Does the dev install steps need to change?

Which guide are you referring to? We did update the guides but might have missed one or two.

I was referring to Install Discourse on Ubuntu or Debian for Development. I don’t think that was updated.

It was updated which links to the installation instructions for libvips .

out of interest, what was the rationale for this change?

Right. Missed the link. Should the ImageMagick link be removed then?

[imagem] merefield: out of interest, what was the rationale for this change? This first was considered many years ago simply because libvips was faster and used less memory for the operations we do with images. But since it was a lot of work for no visible benefit we let it on the backlog. Nowadays, the LLM are finding bugs on every part of the stack, and image processing is the major surface area for that. This mean that libvips being more popular among WebApps handling images gives us a larger umbrella for this new challenge.

ImageMagick substituído por libvips para processamento de imagens

Dev

tgxworld (Alan Tan) Outubro 30, 2026, 6:26am 5

Ele foi atualizado para vincular às instruções de instalação para libvips.

Tópico		Respostas	Visualizações
Libvips instead of imagemagick7 Development	3	1029	4 de Julho de 2018
ImageMagick CVE-2016–3714 Bug	4	5086	3 de Maio de 2016
Libvips upgrade error Self-hosting unsupported-install	3	54	9 de Novembro de 2026
ImageMagick is not installed on my server (one more) Bug	5	1570	13 de Fevereiro de 2015
ImageMagick missing? Product Support	2	1566	6 de Fevereiro de 2015

ImageMagick substituído por libvips para processamento de imagens

Tópicos relacionados