Loading...


Related Products


Date Published: September 19, 2025

Drupal Watchdog Logs Show Errors for Missing AVIF Support in GD Library

Issue 

After reviewing Drupal's watchdog logs (Admin > Reports > Recent log messages) or in Drupal's Status Report (Admin > Reports > Status Report), you may observe warnings or errors related to the AVIF image format. These log entries often mention that the imagecreatefromavif() function is unavailable or that "AVIF support is not available in your GD library."

Example error message:

 Unsupported image file format: AVIF.

These errors can be confusing, especially if you are not using AVIF images on your site. They can appear frequently, creating unnecessary "noise" in your logs and making it difficult to identify legitimate issues. This typically does not impact the functionality of your website or prevent other image formats (like JPEG, PNG, or WebP) from being processed correctly.

Cause

This issue is caused by a bug in certain versions of Drupal core. The bug causes Drupal's GD toolkit to check for the server's support of the AVIF image format during image processing operations, even when the image being handled is not an AVIF file.

If the version of the GD library installed on the server is not compiled with support for AVIF, this check fails and Drupal logs an error. Because this check occurs for many different image operations, it may result in a large volume of log entries. The resolution is to patch or upgrade Drupal core so that it no longer performs this unnecessary check.

Resolution

  1. Investigate to find out your Drupal core version. This issue is known to affect specific versions of Drupal 10 and 11.

  2. Navigate to the official Drupal page for more information about this error https://www.drupal.org/project/drupal/issues/3532792
  3. Examine the issue thread to determine which versions of Drupal are affected and the latest status.

  4. To stop the errors from being logged, do one of the following:

    • Apply the latest community-provided patch from the Drupal.org issue thread.
    • Upgrade your site's Drupal core to a version that includes the official fix for this issue.

Did not find what you were looking for?

If this content did not answer your questions, try searching or contacting our support team for further assistance.

Back to Section navigation