Skip to navigation Skip to main content
11ty Logo Sustainability Fundraising
Eleventy
Eleventy Documentation
Stable
2.0.1
Canary
3.0.0-alpha.10
Toggle Menu
Eleventy 1.93s
Next.js 70.65s

Image

Contents

Low level utility to perform build-time image transformations for both vector and raster images. Output multiple sizes, save multiple formats, cache remote images locally.

You maintain full control of markup. Use with <picture>, <img>, CSS background-image, or others!

Installation Jump to heading

Published as @11ty/eleventy-img on npm.

npm install @11ty/eleventy-img

Usage Jump to heading

This example is the lowest-level use of Eleventy Image and returns a promise. This usage works independent of Eleventy.

View this example in: ESM CommonJS
Filename my-node-script.js
import Image from "@11ty/eleventy-img";

let src = "https://images.unsplash.com/photo-1608178398319-48f814d0750c";
let stats = await Image(src, {
widths: [300],
});

console.log(stats);
Filename my-node-script.js
const Image = require("@11ty/eleventy-img");

// ESM is required for top level async/await.
(async () => {
let src = "https://images.unsplash.com/photo-1608178398319-48f814d0750c";
let stats = await Image(src, {
widths: [300],
});

console.log(stats);
})();

Three things happen here:

  1. (Optional) If the first argument is a full URL (not a local file path), we download the remote image and cache it locally using the Fetch plugin. This cached original is then used for the cache duration to avoid a bunch of network requests.
  2. Images are then created for each format and width from the input source. In this example, two files are created: ./img/6dfd7ac6-300.webp and ./img/6dfd7ac6-300.jpeg.
  3. The promise resolves with a metadata object describing those newly created optimized images.
Expand to see a sample returned metadata object
{
webp: [
{
format: 'webp',
width: 300,
height: 300,
filename: '6dfd7ac6-300.webp',
outputPath: 'img/6dfd7ac6-300.webp',
url: '/img/6dfd7ac6-300.webp',
sourceType: 'image/webp',
srcset: '/img/6dfd7ac6-300.webp 300w',
size: 10184
}
],
jpeg: [
{
format: 'jpeg',
width: 300,
height: 300,
filename: '6dfd7ac6-300.jpeg',
outputPath: 'img/6dfd7ac6-300.jpeg',
url: '/img/6dfd7ac6-300.jpeg',
sourceType: 'image/jpeg',
srcset: '/img/6dfd7ac6-300.jpeg 300w',
size: 15616
}
]
}

Output Widths Jump to heading

Controls how many output images will be created for each image format. Aspect ratio is preserved.

Output Formats Jump to heading

Use almost any combination of these:

Output Locations Jump to heading

URL Path Jump to heading

A path-prefix-esque directory for the <img src> attribute. e.g. /img/ for <img src="/img/MY_IMAGE.jpeg">:

Output Directory Jump to heading

Where to write the new images to disk. Project-relative path to the output image directory. Maybe you want to write these to your output directory directly (e.g. ./_site/img/)?

Options for SVG Jump to heading

Skip raster formats for SVG Jump to heading

If using SVG output (the input format is SVG and svg is added to your formats array), we will skip all of the raster formats even if they’re in formats. This may be useful in a CMS-driven workflow when the input could be vector or raster.

Using svgShortCircuit: "size" means that raster image format entries will only be thrown out if the optimized raster size is larger than the SVG. This helps with large SVG images that compress to smaller raster sizes at smaller widths and will prefer the SVG over raster formats when the SVG file size is smaller.

To use Brotli compressed SVG sizes when making file size comparisons, use the svgCompressionSize: "br" option Added in Image v3.1.8.

Related:

Allow SVG to upscale Jump to heading

While we do prevent raster images from upscaling (and filter upscaling widths from the output), you can optionally enable SVG input to upscale to larger sizes when converting to raster format.

Use this in your templates Jump to heading

There are four different ways to use Eleventy Image in Eleventy projects:

  1. Eleventy Transform (Recommended. Easiest to configure, works with all template types)
  2. Asynchronous Shortcode (Nunjucks, Liquid, 11ty.js)
  3. WebC Component
  4. Synchronous Shortcode (Deprecated)

Eleventy Transform Jump to heading

Pre-release only: v3.0.0-alpha.5 Added in Image v4.0.1This is the easiest method to configure. You add a bit of code to your configuration file and we’ll transform any <img> tags in HTML files that exist in your output folder (probably _site/**/*.html).

Pre-release only: v3.0.0-alpha.7Added in Image v5.0.0During local development (when using --serve), images optimized via transform are not processed at build time and instead are optimized when requested in the browser. Read more about transformOnRequest.

View this example in: CommonJS ESM
Filename .eleventy.js
const { eleventyImageTransformPlugin } = require("@11ty/eleventy-img");

module.exports = function (eleventyConfig) {
eleventyConfig.addPlugin(eleventyImageTransformPlugin, {
// which file extensions to process
extensions: "html",

// Add any other Image utility options here:

// optional, output image formats
formats: ["webp", "jpeg"],
// formats: ["auto"],

// optional, output image widths
// widths: ["auto"],

// optional, attributes assigned on <img> override these values.
defaultAttributes: {
loading: "lazy",
decoding: "async",
},
});
};
Filename .eleventy.js
import { eleventyImageTransformPlugin } from "@11ty/eleventy-img";

export default function (eleventyConfig) {
eleventyConfig.addPlugin(eleventyImageTransformPlugin, {
// which file extensions to process
extensions: "html",

// Add any other Image utility options here:

// optional, output image formats
formats: ["webp", "jpeg"],
// formats: ["auto"],

// optional, output image widths
// widths: ["auto"],

// optional, attributes assigned on <img> override these values.
defaultAttributes: {
loading: "lazy",
decoding: "async",
},
});
}

Relative paths Jump to heading

If you do not specify the urlPath option:

  1. Relative image sources (<img src="./possum.png">) will be co-located in your output directory with the template they are used in. Note that if the same source image is used in multiple templates, it will be written to two different locations!
  2. Absolute image sources (<img src="/possum.png">) will be normalized relative to your input/content directory and written to your output directory with the default directory (e.g. _site/img/).

Attribute overrides Jump to heading

You can configure individual <img> elements with per-instance overrides:

INFO:
If you’re adding the transform method to a project that is already using an Image shortcode or the WebC component, make sure you add eleventy:ignore to the <img> attributes so the images aren’t optimized twice (e.g. Image.generateHTML(metadata, { "eleventy:ignore": "" });).

Nunjucks, Liquid, JavaScript (Asynchronous Shortcodes) Jump to heading

The examples below require an async-friendly shortcodes (works in Nunjucks, Liquid, JavaScript, and WebC).

Filename .eleventy.js
const Image = require("@11ty/eleventy-img");

// Only one module.exports per configuration file, please!
module.exports = function (eleventyConfig) {
eleventyConfig.addShortcode("image", async function (src, alt, sizes) {
let metadata = await Image(src, {
widths: [300, 600],
formats: ["avif", "jpeg"],
});

let imageAttributes = {
alt,
sizes,
loading: "lazy",
decoding: "async",
};

// You bet we throw an error on a missing alt (alt="" works okay)
return Image.generateHTML(metadata, imageAttributes);
});
};
Expand to see full options list for Image.generateHTML
Filename .eleventy.js
const Image = require("@11ty/eleventy-img");

// Only one module.exports per configuration file, please!
module.exports = function (eleventyConfig) {
eleventyConfig.addShortcode("image", async function (src, alt, sizes) {
let metadata = await Image(src, {
// omitted for brevity
});

let imageAttributes = {
// omitted for brevity
};

let options = {
// HTML attributes added to `<picture>` (left out if <img> is used)
// Added in v4.0.0
pictureAttributes: {},

// Condense HTML output to one line (no new lines)
// Added in v0.7.3
whitespaceMode: "inline", // or: "block"
};

// You bet we throw an error on a missing alt (alt="" works okay)
// Note that `options` are *optional*
return Image.generateHTML(metadata, imageAttributes, options);
});
};

The addShortcode method is async-friendly in Eleventy 2.0+. Use addAsyncShortcode in older versions of Eleventy. You can also add these shortcodes to individual template engines, if you’d like!

INFO:
Note that Nunjucks macros cannot use async shortcodes. If you use macros, use synchronous shortcodes described below.

If you want to use Eleventy Image in WebC, take note that it is possible to wire up the method below in WebC. However it is recommended to use the provided <eleventy-image> WebC component instead.

Now you can use the image shortcode in your templates and the appropriate HTML will be generated for you (based on your specified Image options).

View this example in: Liquid Nunjucks 11ty.js Handlebars
Syntax Liquid
{% image "cat.jpg", "photo of my tabby cat" %}
{% image "cat.jpg", "photo of my tabby cat", "(min-width: 30em) 50vw, 100vw" %}

The comma between arguments is optional in Liquid templates.

Syntax Nunjucks
{% image "cat.jpg", "photo of my tabby cat" %}
{% image "cat.jpg", "photo of my tabby cat", "(min-width: 30em) 50vw, 100vw" %}

The comma between arguments is required in Nunjucks templates.

Syntax JavaScript
module.exports = function() {
let img1 = await this.image("cat.jpg", "photo of my tabby cat");
let img2 = await this.image("cat.jpg", "photo of my tabby cat", "(min-width: 30em) 50vw, 100vw");

return `${img1}

${img2}`
;
};

This image shortcode example requires an async-friendly template language and is not available in Handlebars.

Synchronous Shortcode Jump to heading

INFO:
The new Eleventy Transform is now preferred for situations that are not asynchronous-friendly (Handlebars, macros in Nunjucks, et al). For asynchronous-friendly templates (e.g. Nunjucks, Liquid, JavaScript), the Asynchronous Shortcode is another option. If you’re using WebC, use the provided WebC component.
Expand to see an example of Synchronous usage.
WARNING:
Deprecated in Eleventy Image v4.0.0.

Use Image.statsSync to get the metadata of a source even if the image generation is not finished yet:

Filename .eleventy.js
const Image = require("@11ty/eleventy-img");
function imageShortcode(src, cls, alt, sizes, widths) {
let options = {
widths: widths,
formats: ["jpeg"],
};

// generate images, while this is async we don’t wait
Image(src, options);

let imageAttributes = {
class: cls,
alt,
sizes,
loading: "lazy",
decoding: "async",
};
// get metadata even if the images are not fully generated yet
let metadata = Image.statsSync(src, options);
return Image.generateHTML(metadata, imageAttributes);
}

module.exports = function (eleventyConfig) {
eleventyConfig.addShortcode("myImage", imageShortcode);
};

WebC Jump to heading

Added in Image v3.1.0 Eleventy Image now provides a built-in <eleventy-image> WebC component for use in your Eleventy project.

Using Eleventy Image in WebC offers all the same great benefits you’re used to from Eleventy Image with an intuitive declarative HTML-only developer experience. WebC components work in *.webc files. For similar functionality in other template formats, use the the Liquid/Nunjucks/JavaScript shortcodes above (or even <eleventy-image> with the Render plugin).

First, add the following to your project’s configuration file:

Filename .eleventy.js
const eleventyWebcPlugin = require("@11ty/eleventy-plugin-webc");
const { eleventyImagePlugin } = require("@11ty/eleventy-img");

// Only one module.exports per configuration file, please!
module.exports = function (eleventyConfig) {
// WebC
eleventyConfig.addPlugin(eleventyWebcPlugin, {
components: [
// …
// Add as a global WebC component
"npm:@11ty/eleventy-img/*.webc",
],
});

// Image plugin
eleventyConfig.addPlugin(eleventyImagePlugin, {
// Set global default options
formats: ["webp", "jpeg"],
urlPath: "/img/",

// Notably `outputDir` is resolved automatically
// to the project output directory

defaultAttributes: {
loading: "lazy",
decoding: "async",
},
});
};

Pre-release only: v3.0.0-alpha.7Added in Image v5.0.0During local development (when using --serve), <eleventy-image> images are not processed at build time and instead are optimized when requested in the browser. Read more about transformOnRequest.

Now you can use the <eleventy-image> WebC component in your templates.

Expand to see Eleventy Image WebC component Examples
<img webc:is="eleventy-image" src="cat.jpg" alt="photo of my tabby cat" />
<eleventy-image src="cat.jpg" alt="photo of my tabby cat"></eleventy-image>

<!-- Specify widths: -->
<img
webc:is="eleventy-image"
width="100, 200"
src="cat.jpg"
alt="photo of my tabby cat"
/>

<img
webc:is="eleventy-image"
:width="[100, 200]"
src="cat.jpg"
alt="photo of my tabby cat"
/>


<!-- Specify formats (overriding defaults set via the configuration) -->
<img
webc:is="eleventy-image"
formats="avif, png"
src="cat.jpg"
alt="photo of my tabby cat"
/>

<img
webc:is="eleventy-image"
:formats="['avif', 'png']"
src="cat.jpg"
alt="photo of my tabby cat"
/>


<!-- Change the url path or output dir (overriding defaults set via the configuration above) -->
<img
webc:is="eleventy-image"
url-path="/some-dir/"
output-dir="_site/some-dir/"
src="cat.jpg"
alt="photo of my tabby cat"
/>

Build Cost 🧰 Jump to heading

Image optimization is likely one of the costlier pieces of your Eleventy build. The total build cost of this utility is dependent on a few things:

  1. Number of unique images optimized (not number of pages)
  2. Number of widths you generate for each source image.
  3. Number of formats you generate for each source image.
    • avif is more costly than other image formats. +1 Build Cost
  4. File size of images being optimized (larger source images are more expensive).
  5. Optimizing a lot of remote images (image content must be fetched from a remote server and is subsequently cached via eleventy-fetch).

Optimize Images on Request Jump to heading

Pre-release only: v3.0.0-alpha.7Added in Image v5.0.0When using the transform method or the WebC component, image processing is removed from the build for extra performance. Instead, they are processed when requested by the browser using a special middleware built-in to the Eleventy Dev Server. This is enabled or disabled using the transformOnRequest option.

Optimize On Request with Shortcodes Jump to heading

Pre-release only: v3.0.0-alpha.7Added in Image v5.0.0You can use this with the Eleventy Shortcode directly too, with a little bit more configuration:

Filename .eleventy.js
const Image = require("@11ty/eleventy-img");
const { eleventyImageOnRequestDuringServePlugin } = Image;

// Only one module.exports per configuration file, please!
module.exports = function (eleventyConfig) {
eleventyConfig.addShortcode("image", async function (src, alt) {
let metadata = await Image(src, {
transformOnRequest: process.env.ELEVENTY_RUN_MODE === "serve"
});

// You bet we throw an error on a missing alt (alt="" works okay)
return Image.generateHTML(metadata, imageAttributes);
});

// Add the dev server middleware manually
eleventyConfig.addPlugin(eleventyImageOnRequestDuringServePlugin);
};

In-Memory Cache Jump to heading

To prevent duplicate work and improve build performance, repeated calls to the same source image (remote or local) with the same options will return a cached results object. If a request in-progress, the pending promise will be returned. This in-memory cache is maintained across builds in watch/serve mode. If you quit Eleventy, the in-memory cache will be lost.

Images will be regenerated (and the cache ignored) if:

You can disable this behavior by using the useCache boolean option:

Examples
Example of in-memory cache reuse (returns the same promise)
Filename .eleventy.js
const Image = require("@11ty/eleventy-img");

(async () => {
let stats1 = Image("./test/bio-2017.jpg");
let stats2 = Image("./test/bio-2017.jpg");

console.assert(stats1 === stats2, "The same promise");
})();
Example of in-memory cache (returns a new promise with different options)
Filename .eleventy.js
const Image = require("@11ty/eleventy-img");

(async () => {
let stats1 = Image("./test/bio-2017.jpg");
let stats2 = Image("./test/bio-2017.jpg", { widths: [300] });

console.assert(stats1 !== stats2, "A different promise");
})();

Disk Cache Jump to heading

Added in Image v1.0.0 Eleventy will skip processing files that are unchanged and already exist in the output directory. This requires the built-in hashing algorithm and is not yet supported with custom filenames. More background at Issue #51.

You can use this to speed up builds on your build server.

Advanced Usage Jump to heading

Fix Orientation Jump to heading

Added in Image v4.0.0Rotates the image to enforce the correct orientation set in EXIF metadata.

Custom Filenames Jump to heading

Don’t like those hash ids? Make your own!

{
// Define custom filenames for generated images
filenameFormat: function (id, src, width, format, options) {
// id: hash of the original image
// src: original image path
// width: current width in px
// format: current file format
// options: set of options passed to the Image call

return `${id}-${width}.${format}`;
}
}
Custom Filename Example: Use the original file slug
const path = require("path");
const Image = require("@11ty/eleventy-img");

await Image("./test/bio-2017.jpg", {
widths: [300],
formats: ["auto"],
filenameFormat: function (id, src, width, format, options) {
const extension = path.extname(src);
const name = path.basename(src, extension);

return `${name}-${width}w.${format}`;
},
});

// Writes: "test/img/bio-2017-300w.jpeg"

Dry-Run Jump to heading

If you want to try the utility out and not write any files (useful for testing), use the dryRun option.

Make your own Markup Jump to heading

If you have an advanced use case and don’t want to use our methods to generate the image markup, you can do it yourself!

Choose one: Do it yourself: <img> Do it yourself: <picture>
Filename .eleventy.js
const Image = require("@11ty/eleventy-img");

// Only one module.exports per configuration file, please!
module.exports = function (eleventyConfig) {
eleventyConfig.addShortcode("image", async function (src, alt) {
if (alt === undefined) {
// You bet we throw an error on missing alt (alt="" works okay)
throw new Error(`Missing \`alt\` on myImage from: ${src}`);
}

let metadata = await Image(src, {
widths: [600],
formats: ["jpeg"],
});

let data = metadata.jpeg[metadata.jpeg.length - 1];
return `<img src="${data.url}" width="${data.width}" height="${data.height}" alt="${alt}" loading="lazy" decoding="async">`;
});
};
Filename .eleventy.js
const Image = require("@11ty/eleventy-img");

// Only one module.exports per configuration file, please!
module.exports = function (eleventyConfig) {
eleventyConfig.addShortcode(
"image",
async function (src, alt, sizes = "100vw") {
if (alt === undefined) {
// You bet we throw an error on missing alt (alt="" works okay)
throw new Error(`Missing \`alt\` on responsiveimage from: ${src}`);
}

let metadata = await Image(src, {
widths: [300, 600],
formats: ["webp", "jpeg"],
});

let lowsrc = metadata.jpeg[0];
let highsrc = metadata.jpeg[metadata.jpeg.length - 1];

return `<picture>
${Object.values(metadata)
.map((imageFormat) => {
return ` <source type="${
imageFormat[0].sourceType
}
" srcset="${imageFormat
.map((entry) => entry.srcset)
.join(", ")}
" sizes="${sizes}">`
;
})
.join("\n")}

<img
src="
${lowsrc.url}"
width="
${highsrc.width}"
height="
${highsrc.height}"
alt="
${alt}"
loading="lazy"
decoding="async">
</picture>
`
;
}
);
};

Process images as a Custom Template Jump to heading

Use Eleventy’s Custom Template Language feature to process images. This one is not yet available on the docs: do you want to contribute it?

Process images as Data Files Jump to heading

Added in v2.0.0 Nontraditional use case. Eleventy’s Custom Data File Formats features an example of processing Images as data files to feed EXIF data into the Data Cascade. You can use the same feature to add the metadata stats returned from the Image utility directly to the Data Cascade for use in your templates.

Show the code
Filename .eleventy.js
const Image = require("@11ty/eleventy-img");
const path = require("path");

module.exports = function (eleventyConfig) {
eleventyConfig.addDataExtension("png,jpeg", {
read: false, // Don’t read the input file, argument is now a file path
parser: async (imagePath) => {
let stats = await Image(imagePath, {
widths: ["auto"],
formats: ["avif", "webp", "jpeg"],
outputDir: path.join(eleventyConfig.dir.output, "img", "built"),
});

return {
image: {
stats,
},
};
},
});

// This works sync or async: images were processed ahead of time in the data cascade
eleventyConfig.addShortcode("dataCascadeImage", (stats, alt, sizes) => {
let imageAttributes = {
alt,
sizes,
loading: "lazy",
decoding: "async",
};
return Image.generateHTML(stats, imageAttributes);
});
};

With a template my-blog-post.md and an image file my-blog-post.jpeg, you could use the above configuration code in your template like this:

Filename my-blog-post.md
{% dataCascadeImage image.stats, "My alt text" %}

Note this also means that folder/folder.jpeg would be processed for all templates in folder/* and any images stored in your global _data would also be populated into the data cascade based on their folder structure.

Change Global Plugin Concurrency Jump to heading

const Image = require("@11ty/eleventy-img");
Image.concurrency = 4; // default is 10

Advanced control of Sharp image processor Jump to heading

Extra options to pass to the Sharp constructor or the Sharp image format converter for webp, png, jpeg, or avif.

Output Animated GIF or WebP Jump to heading

Added in Image v1.1.0 To process and output animated gif or webp images, use the animated option for the Sharp constructor.

const Image = require("@11ty/eleventy-img");

await Image("./test/bio-2017.jpg", {
formats: ["webp", "gif"],

sharpOptions: {
animated: true,
},
});

Change the default Hash length Jump to heading

Added in v1.0.0 You can customize the length of the default filename format hash by using the hashLength property.

const Image = require("@11ty/eleventy-img");

await Image("./test/bio-2017.jpg", {
hashLength: 8, // careful, don’t make it _too_ short!
});

Advanced Caching Options for Remote Images Jump to heading

For any full URL first argument to this plugin, the full-size remote image will be downloaded and cached locally. See all relevant eleventy-fetch options.

{
cacheOptions: {
// if a remote image URL, this is the amount of time before it fetches a fresh copy
duration: "1d",

// project-relative path to the cache directory
directory: ".cache",

removeUrlQueryParams: false,
},
}

When caching remote images, you may want to check the processed image output into your git (et al) repository to avoid refetches in the future. If remote images are not checked in, they may be refetched every time on your CI server unless you preserve the .cache folder between builds.

Using a Hosted Image Service Jump to heading

Custom URLs Jump to heading

Want to use a hosted image service instead? You can override the entire URL. Takes precedence over filenameFormat option. Useful with statsSync or statsByDimensionsSync.

The metadata object returned will not include filename or outputPath properties.

{
urlFormat: function ({
hash, // not included for `statsOnly` images
src,
width,
format,
}) {
return `https://example.com/${encodeURIComponent(src)}/${width}/${format}/`;
}
}

Stats Only Jump to heading

Added in Image v1.1.0 Skips all image processing to return metadata. Doesn’t read files, doesn’t write files. Use this as an alternative to the separate statsSync* functionsβ€”this will use in-memory cache and de-duplicate requests.

For versions prior to Image 5.0, you need to supply the dimensions when using statsOnly via remoteImageMetadata:

{
statsOnly: true,
// Not required in Image 5.0+
remoteImageMetadata: {
width,
height,
format, // optional
}
}

From the Community Jump to heading

Γ—69 resources courtesy of 11tybundle.dev curated by IndieWeb Avatar for https://www.bobmonsour.com/Bob Monsour

Expand to see 64 more resources.

Other pages in Official Plugins: