Can eleventy-img recognize images it processed from another page and not process it again like a new image?

[GoOz]

Hello there,

I'm not sure if this is an actual issue, a behaviour by design or if I'm just doing it wrong but on my portfolio website my homepage is displaying a grid of my photos with a link on their dedicated page.

The picture in those pages is processed as intended and will end up in the folder of the page.

The thumbnail pictures though are processed again and stored in the img folder at the root of my website.

So basically every picture is processed twice.

There is the code I use for the grid:

<li class="post">
	<a href="{{ post.url }}">
		{% if post.data.photo %}
		<img src="/{{ post.url }}/{{ post.data.photo }}" alt="{{ post.data.photo_alt }}" sizes="(min-width: 50em) 50vw, 100vw">
		{% endif %}
		<h2 class="post-title">{{ post.data.title }}</h2>
		</a>
</li>

I'm guessing the plugin doesn't check if it processed the picture already.
And it would be harmless on a small website but mine is already 500+ pictures which, as you may expect, makes the image processing time twice longer than it should and… needs almost twice the disk space it should.

Is there a way to avoid that?

---

eleventy: v3.0.0
eleventy-img: v6.0.1

[GoOz]

I read the documentation again and saw that it's indeed by design. But still trying to find a workaround.

[GoOz]

I used a variation of the solution given in #278 but I'm still wondering if there could be a more reliable built-in solution for this kind of things.

[zeroby0]

Unless you're deleting the output folder, this processing should happen only the first time you run eleventy. Once images are processed and outputs are produced, they won't be processed again. So you don't need to worry about it as much, imo.

[GoOz]

Still, it's using way too much memory whether the images are already processed and in the output folder or not.
My hosting provider kills any process using more than 3Go of RAM which should be way enough for a static website imho.

Besides that, and to get back to the original issue, it's not really eco-friendly to process the same image twice with the same output options but at two different locations. It uses more space and energy than it should or even need.

[SunfireWeb]

Are the thumbnails a different source image or simply a resized version of the original?

You may consider the use of the eleventy:ignore attribute as listed here in the tag where the thumbnails are displayed...

[zachleat]

Why do you think it’s processing the image twice? I want to push back on that assertion first, so we can move forward from there!

[GoOz]

Well, as I said:

The picture in those pages is processed as intended and will end up in the folder of the page.

The thumbnail pictures though are processed again and stored in the img folder at the root of my website.

I get the same images and its size variantes, at two places, in the dist folder. In _site/img/ and in _site/page-b/.

Maybe I'm missing something or doing something wrong but it seems like when you're on a page A and calling an image from a page B, it just creates a new set of images (at different sizes as configured) when, I guess, a better way would be to use the ones already processed for the page B.