Issue Feature Closed

#93981 Google webp and Apple heic/heif support for TYPO3 - Make default targetfileextensions for processed images configurable

Sven Wiener 04/24/21, 16:04 updated 12/02/25, 14:33

Description

Actually the core defines hardcoded which target file-extensions are mapped, if nothing is defined via configuration-array.

In the function “determineTargetFileExtension” in file “sysext/core/Classes/Resource/Processing/AbstractGraphicalTask.php” it is defined that:

1) jpg, jpeg, png and gif will stay the same
2) uncropped svg will stay svg
3) unprocessable files with disabled option $GLOBALS[‘TYPO3_CONF_VARS’][‘GFX’][‘thumbnails_png’] will be gif
4) all other files will be converted to png

This disables the possibility to render all or specific image types to a default type. This is usally needed, if the use of the new file types heic/heif or webp is needed (suggested for better performance, Google!)
The usage of heic/heif files (Default on Apple Devices) oder webp is still configurable, but must be implemented by an integrator to every element. This could be a fluid template with the image viewhelper and the attribute fileExtension.

New configuration options in $GLOBALS[‘TYPO3_CONF_VARS’][‘GFX’] would make it possible to set the target file type. Optimum would be the possibility to add a mapping for each configured type.
A default example list could be something like that:

jpg -> webp
jpeg -> webp
webp -> webp
heic -> webp
png -> png
gif -> gif
svg -> svg

Maybe a default file extension option if no mapping exists.

There are a couple of other configurations we should have an eye on.
The options
$GLOBALS[‘TYPO3_CONF_VARS’][GFX][gif_compress]
$GLOBALS[‘TYPO3_CONF_VARS’][GFX][jpg_quality]
for example should maybe extended by new features for webp optimiazation

Either the “Image Processing” module in the backend could be extended with heic/heif and webp file format.

Last point. We could rethink to get better performance using the modern image formats in the backend.

Reviews 8

History 929

Show 34 earlier messages
  1. Martin Kutschker commented <span data-processor="relativetime" data-value="2021-05-13T18:33:18+00:00" > 05/13/21, 18:33 </span>

    No WebP support on macOS 10. I have no idea if that system is supported for the upcoming v11.

    Another contender is the AVIF format which has no macOS/iOS support (with FF support in the near future).

    OTOH HEIC/HEIF is currently support by no browser.

    Sidenote:
    Not every WebP file is smaller than its JPEG counterpart. The TYPO3 extension “webp” makes sure that WebP is only used if it smaller.

  1. Benni Mack commented and changed status Under Review Needs Feedback <span data-processor="relativetime" data-value="2024-12-10T14:21:29+00:00" > 12/10/24, 14:21 </span>

    webp support was added in v13, I’m not sure if we really should add HEIC/HEIF support as Apple / Safari is still the only one to use due to licensing issues. https://caniuse.com/heif

    AVIF support is almost there https://caniuse.com/avif

    The only part is missing is to configure explicit targetfileextensions, don’t know if we should do this in general.

  2. Gerrit Code Review pushed patch set 5 for main to change 87582 status Needs Feedback Under Review <span data-processor="relativetime" data-value="2025-01-03T20:24:02+00:00" > 01/03/25, 20:24 </span>

  3. Garvin Hicking commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-10-20T19:00:09+00:00" > 10/20/25, 19:00 </span>

    Applied in changeset commit:649ea85171c232cb17df3b4914f0d78cdc49e40b.