#Why does Directus create huge PNG files for uploaded images?

3 messages · Page 1 of 1 (latest)

candid elk
#

Hello, sorry if this has been discussed before.

I'm trying out Directus (self hosted using docker) and mostly loving it.

However, most of the images I upload have derivatives created that are many times the original filesize.

In the screenshot example, I uploaded a 14K webp image. A png copy was made immediately that was about 10x the size. A bit later, another png copy was made that was 70x the size.

I have image transformations restricted to output webp with enlargement disabled so I don't think it's caused by transformation requests.

Maybe they're generated for use in the studio app, but surely this can be done more efficiently. The current behavior massively increases requirements and cost for storage and backups.

hollow ingotBOT
#

Thanks for posting! This is a community powered server, so you may or may not get an answer based on available help and expertise. To increase your chances of somebody being able to help you, please help us help you making sure you:

  • Adding an explanation of exactly what you're trying to achieve.
  • Adding any and all related code or previous attempts.
  • Describing the exact issue or error you are facing.
  • Posting any screenshots if applicable.
  • Reading through https://stackoverflow.com/help/how-to-ask.

When you're done with this thread, please close it. Thanks! ✨

(If you have a support agreement and need help, please contact the core team via email.)

gusty obsidian
#

.webp is a much more compressed and modern format so it makes sense that a large image would be a lot smaller than its counterpart in .png