#images
11 messages · Page 1 of 1 (latest)
Hi @spice pawn. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Astro's image optimization process used to include the original images in the output directory (dist/ folder) along with the optimized versions. This was reported as an issue by users, as it increased storage consumption and deployment times, especially for projects with a large number of images (source (https://github.com/withastro/astro/issues/4896), source (https://github.com/withastro/astro/issues/8143)).
However, starting from Astro version 3.5, this behavior has been improved. Now, original images that are not used outside of the optimization pipeline are deleted from the final build. This change should help reduce storage consumption and deployment times (source (https://astro.build/blog/astro-350#image-optimization-improvements)).
If you're still experiencing this issue, ensure that you're using Astro version 3.5 or later. If the problem persists, it might be worth raising an issue on the Astro GitHub page.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@spice pawn kapa.ai is still learning and improving, please let us know how it did by reacting below
@full nacelle I am using astro 4.2 but have my jpg with optimised webp images
Let me check the knowledge base for you. One moment! :books:
Astro's image optimization process generates optimized versions of your images in formats like WebP, but it also keeps the original images in the output directory. This is a design choice, as it allows for features like "Click to see original" or showing the original as a fallback in case the optimized version fails to load. This is mentioned in a GitHub issue comment (https://github.com/withastro/astro/issues/8143).
However, this can lead to increased storage consumption and longer deployment times, especially if you have a large number of images. Some users have expressed a desire for an optional feature to delete the original images from the output directory if an optimized version exists.
If you're finding that the presence of original images in the output directory is causing issues for your project, you might want to consider raising an issue on the Astro GitHub page to discuss potential solutions.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@spice pawn kapa.ai is still learning and improving, please let us know how it did by reacting below
@full nacelle tell about the image.removeOriginals: true
Let me check the knowledge base for you. One moment! :books:
I'm sorry, but the information extracts provided do not contain any details about an image.removeOriginals: true configuration or feature in Astro. It's possible that such a feature or configuration option exists, but based on the information available, I can't provide a confident answer.