:sunrise: next-optimized-images

:bulb: Version 3 is coming! It introduces a complete rewrite with many new features and bugfixes. If you want to help developing and testing the upcoming major version, please check out the canary branch for installation instructions and more information about the new features. (RFC issue)

---

Automatically optimize images used in next.js projects (jpeg, png, svg, webp and gif).

Image sizes can often get reduced between 20-60%, but this is not the only thing next-optimized-images does:

• Reduces image size by optimizing images during build
• Improves loading speed by providing progressive images (for formats that support it)
• Inlines small images to save HTTP requests and additional roundtrips
• Adds a content hash to the file name so images can get cached on CDN level and in the browser for a long time
• Same image URLs over multiple builds for long time caching
• Provides query params for file-specific handling/settings
• jpeg/png images can be converted to webp on the fly for an even smaller size
• Provides the possibility to use SVG sprites for a better performance when using the same icons multiple times (e.g. in a list)
• Can resize images or generate different placeholders while lazy loading images: low quality images, dominant colors or image outlines

Table of contents

• Installation
• Optimization Packages
• Usage
  • Query Params
• Configuration
• Example
• See also
• License

Installation

npm install next-optimized-images

Node >= 8 is required for version 2. If you need to support older node versions, you can still use version 1 of next-optimized-images.

Enable the plugin in your Next.js configuration file:

1// next.config.js
2const withPlugins = require('next-compose-plugins');
3const optimizedImages = require('next-optimized-images');
4
5module.exports = withPlugins([
6  [optimizedImages, {
7    /* config for next-optimized-images */
8  }],
9
10  // your other plugins here
11
12]);

See the configuration section for all available options.

:warning: From version 2 on, images won't get optimized out of the box anymore. You have to install the optimization packages you really need in addition to this plugin. This doesn't force you to download big optimization libraries you don't even use. Please check out the table of all optional optimization packages.

The example above uses next-compose-plugins for a cleaner API when using many plugins, see its readme for a more detailed example. next-optimized-images also works with the standard plugin api:

1// next.config.js
2const withOptimizedImages = require('next-optimized-images');
3
4module.exports = withOptimizedImages({
5  /* config for next-optimized-images */
6
7  // your config for other plugins or the general next.js here...
8});

Optimization Packages

Starting from version 2, you have to install the optimization packages you need in your project in addition to this plugin. next-optimized-images then detects all the supported packages and uses them.

So you only have to install these packages with npm, there is no additional step needed after that.

The following optimization packages are available and supported:

Optimization Package	Description	Project Link
imagemin-mozjpeg	Optimizes JPEG images.	Link
imagemin-optipng	Optimizes PNG images.	Link
imagemin-pngquant	Alternative for optimizing PNG images.	Link
imagemin-gifsicle	Optimizes GIF images.	Link
imagemin-svgo	Optimizes SVG images and icons.	Link
svg-sprite-loader	Adds the possibility to use svg sprites for a better performance. Read the sprite section for more information.	Link
webp-loader	Optimizes WebP images and can convert JPEG/PNG images to WebP on the fly (webp resource query).	Link
lqip-loader	Generates low quality image placeholders and can extract the dominant colors of an image (lqip resource query)	Link
responsive-loader	Can resize images on the fly and create multiple versions of it for a srcset. Important: You need to additionally install either jimp (node implementation, slower) or sharp (binary, faster)	Link
image-trace-loader	Generates SVG image outlines which can be used as a placeholder while loading the original image (trace resource query).	Link

Example: If you have JPG, PNG, and SVG images in your project, you would then need to run

1npm install imagemin-mozjpeg imagemin-optipng imagemin-svgo

To install all optional packages, run:

1npm install imagemin-mozjpeg imagemin-optipng imagemin-gifsicle imagemin-svgo svg-sprite-loader webp-loader lqip-loader responsive-loader jimp image-trace-loader

:warning: Please note that by default, images are only optimized for production builds, not development builds. However, this can get changed with the optimizeImagesInDev config.

:bulb: Depending on your build/deployment setup, it is also possibile to install these as devDependencies. Just make sure that the packages are available when you build your project.

:information_source: Since version 2.5, ico files are also optionally supported but need to be enabled in the handleImages config.

Usage

You can now import or require your images directly in your react components:

1import React from 'react';
2
3export default () => (
4  <div>
5    <img src={require('./images/my-image.jpg')} />
6    <img src={require('./images/my-small-image.png')} />
7    <img src={require('./images/my-icon.svg')} />
8  </div>
9);
10
11/**
12 * Results in:
13 *
14 * <div>
15 *   <img src="/_next/static/images/my-image-5216de428a8e8bd01a4aa3673d2d1391.jpg" />
16 *   <img src="data:image/png;base64,..." />
17 *   <img src="/_next/static/images/my-icon-572812a2b04ed76f93f05bf57563c35d.svg" />
18 * </div>
19 */

Please be aware that images only get optimized in production by default to reduce the build time in your development environment.

If you are using CSS modules, this package also detects images and optimized them in url() values in your css/sass/less files:

1.Header {
2  background-image: url('./images/my-image.jpg');
3}
4
5/**
6 * Results in:
7 *
8 * .Header {
9 *   background-image: url('/_next/static/images/my-image-5216de428a8e8bd01a4aa3673d2d1391.jpg');
10 * }
11 */

If the file is below the limit for inlining images, the require(...) will return a base64 data-uri (data:image/jpeg;base64,...).

Otherwise, next-optimized-images will copy your image into the static folder of next.js and the require(...) returns the path to your image in this case (/_next/static/images/my-image-5216de428a8e8bd01a4aa3673d2d1391.jpg).

You can use both variants directly on an image in the src attribute or in your CSS file inside an url() value.

Query params

If you are using flow or eslint-plugin-import and are experiencing some issues with query params, check out the solution posted by @eleith.

There are some cases where you don't want to reference a file or get a base64 data-uri but you actually want to include the raw file directly into your HTML. Especially for SVGs because you can't style them with CSS if they are in an src attribute on an image.

So there are additional options you can specify as query params when you import the images.

• ?include: Include the raw file directly (useful for SVG icons)
• ?webp: Convert a JPEG/PNG image to WebP on the fly
• ?inline: Force inlining an image (data-uri)
• ?url: Force an URL for a small image (instead of data-uri)
• ?original: Use the original image and do not optimize it
• ?lqip: Generate a low quality image placeholder
• ?lqip-colors: Extract the dominant colors of an image
• ?trace: Use traced outlines as loading placeholder
• ?resize: Resize an image
• ?sprite: Use SVG sprites

?include

The image will now directly be included in your HTML without a data-uri or a reference to your file.

As described above, this is useful for SVGs so you can style them with CSS.

1import React from 'react';
2
3export default () => (
4  <div dangerouslySetInnerHTML={{__html: require('./images/my-icon.svg?include')}} />
5);
6
7/**
8 * Results in:
9 *
10 * <div>
11 *   <svg width="16" height="16" xmlns="http://www.w3.org/2000/svg">
12 *     <path d="M8 0C3.589 0 0 3.589 0 8s3.589 ..." style="filled-opacity:1" fill-rule="evenodd">
13 *     </path>
14 *   </svg>
15 * </div>
16 */

The image will still get optimized, even if it is directly included in your content (but by default only in production).

?webp

Requires the optional optimization package webp-loader (npm install webp-loader)

WebP is an even better and smaller image format but it is still not that common yet and developers often only receive jpeg/png images.

If this ?webp query parameter is specified, next-optimized-images automatically converts a JPEG/PNG image to the new WebP format.

For browsers that don't yet support WebP, you can also provide a fallback using the <picture> tag:

1import React from 'react';
2
3export default () => (
4  <picture>
5    <source srcSet={require('./images/my-image.jpg?webp')} type="image/webp" />
6    <source srcSet={require('./images/my-image.jpg')} type="image/jpeg" />
7    <img src={require('./images/my-image.jpg')} />
8  </picture>
9);
10
11/**
12 * Results in:
13 * <picture>
14 *   <source srcset="/_next/static/images/my-image-d6816ecc28862cf6f725b29b1d6aab5e.jpg.webp" type="image/webp" />
15 *   <source srcset="/_next/static/images/my-image-5216de428a8e8bd01a4aa3673d2d1391.jpg" type="image/jpeg" />
16 *   <img src="/_next/static/images/my-image-5216de428a8e8bd01a4aa3673d2d1391.jpg" />
17 * </picture>
18 */

?inline

You can specify a limit for inlining images which will include it as a data-uri directly in your content instead of referencing a file if the file size is below that limit.

You usually don't want to specify a too high limit but there may be cases where you still want to inline larger images.

In this case, you don't have to set the global limit to a higher value but you can add an exception for a single image using the ?inline query options.

1import React from 'react';
2
3export default () => (
4  <img src={require('./images/my-image.jpg?inline')} />
5);
6
7/**
8 * Results in:
9 *
10 * <img src="data:image/png;base64,..." />
11 *
12 * Even if the image size is above the defined limit.
13 */

The inlining will only get applied to exactly this import, so if you import the image a second time without the ?inline option, it will then get normally referenced as a file if it is above your limit.

?url

When you have an image smaller than your defined limit for inlining, it normally gets inlined automatically. If you don't want a specific small file to get inlined, you can use the ?url query param to always get back an image URL, regardless of the inline limit.

If you are using this option a lot, it could also make sense to disable the inlining completely and use the ?inline param for single files.

1import React from 'react';
2
3export default () => (
4  <img src={require('./images/my-image.jpg?url')} />
5);
6
7/**
8 * Results in:
9 *
10 * <img src="/_next/static/images/my-image-5216de428a8e8bd01a4aa3673d2d1391.jpg" />
11 *
12 * Even if the image size is below the defined inlining limit.
13 */

The inlining will only get disabled for exactly this import, so if you import the image a second time without the ?url option, it will then get inlined again if it is below your limit.

?original

The image won't get optimized and used as it is. It makes sense to use this query param if you know an image already got optimized (e.g. during export) so it doesn't get optimized again a second time.

1import React from 'react';
2
3export default () => (
4  <img src={require('./images/my-image.jpg?original')} />
5);

This can also be combined with the ?url or ?inline resource query (e.g. ?original&inline).

?lqip

Requires the optional package lqip-loader (npm install lqip-loader)

When using this resource query, a very small (about 10x7 pixel) image gets created. You can then display this image as a placeholder until the real (big) image has loaded.

You will normally stretch this tiny image to the same size as the real image is, like medium.com does. To make the stretched image look better in chrome, check out this solution and add a blur filter to your image.

1import React from 'react';
2
3export default () => (
4  <img src={require('./images/my-image.jpg?lqip')} />
5);
6
7/**
8 * Replaces the src with a tiny image in base64.
9 */

?lqip-colors

Requires the optional package lqip-loader (npm install lqip-loader)

This resource query returns you an array with hex values of the dominant colors of an image. You can also use this as a placeholder until the real image has loaded (e.g. as a background) like the Google Picture Search does.

The number of colors returned can vary and depends on how many different colors your image has.

1import React from 'react';
2
3export default () => (
4  <div style={{ backgroundColor: require('./images/my-image.jpg?lqip-colors')[0] }}>...</div>
5);
6
7/**
8 * require('./images/my-image.jpg?lqip-colors')
9 *
10 * returns for example
11 *
12 * ['#0e648d', '#5f94b5', '#a7bbcb', '#223240', '#a4c3dc', '#1b6c9c']
13 */

?trace

Requires the optional package image-trace-loader (npm install image-trace-loader)

With the ?trace resource query, you can generate SVG image outlines which can be used as a placeholder while loading the original image.

1import React from 'react';
2import MyImage from './images/my-image.jpg?trace';
3
4export default () => (
5  <div>
6    <img src={MyImage.trace} />   {/* <-- SVG trace */}
7    <img src={MyImage.src} />     {/* <-- Normal image which you want to lazy load */}
8  </div>
9);
10
11/**
12 * Results in:
13 *
14 * <div>
15 *  <img src="data:image/svg+xml,...">
16 *  <img src="/_next/static/images/image-trace-85bf5c58ce3d91fbbf54aa03c44ab747.jpg">
17 * </div>
18 */

require('./images/my-image.jpg?trace') returns an object containing the trace (trace) as an inlined SVG and the normal image (src) which also gets optimized.

The trace will have exactly the same width and height as your normal image.

Options for the loader can be set in the plugin configuration.

?resize

Requires the optional package responsive-loader (npm install responsive-loader) and either jimp (node implementation, slower) or sharp (binary, faster)

After the ?resize resource query, you can add any other query of the responsive-loader which allows you to resize images and create whole source sets.

1import React from 'react';
2
3const oneSize = require('./images/my-image.jpg?resize&size=300');
4const multipleSizes = require('./images/my-image.jpg?resize&sizes[]=300&sizes[]=600&sizes[]=1000');
5
6export default () => (
7  <div>
8    {/* Single image: */}
9    <img src={oneSize.src} />
10
11    {/* Source set with multiple sizes: */}
12    <img srcSet={multipleSizes.srcSet} src={multipleSizes.src} />
13  </div>
14);

If only the size or sizes param is used, the ?resize param can also be omitted (e.g. my-image.jpg?size=300). But it is required for all other parameters of responsive-loader.

You can also set global configs in the responsive property (in the next.config.js file) and define, for example, default sizes which will get generated when you don't specify one for an image (e.g. only my-image.jpg?resize).

?sprite

Requires the optional optimization packages imagemin-svgo and svg-sprite-loader (npm install imagemin-svgo svg-sprite-loader)

If you need to style or animate your SVGs ?include might be the wrong option, because that ends up in a lot of DOM elements, especially when using the SVG in list-items etc. In that case, you can use ?sprite which uses svg-sprite-loader to render and inject an SVG sprite in the page automatically.

1import React from 'react';
2import MyIcon from './icons/my-icon.svg?sprite';
3
4export default () => (
5  <div>
6    my page..
7    <MyIcon />
8  </div>
9);

All props passed to the imported sprite will get applied to the <svg> element, so you can add a class normally with <MyIcon className="icon-class" />.

The svg-sprite-loader object also gets exposed if you want to build your own component:

1import React from 'react';
2import icon from './icons/icon.svg?sprite';
3
4export default () => (
5  <div>
6    my page..
7    <svg viewBox={icon.viewBox}>
8      <use xlinkHref={`#${icon.id}`} />
9    </svg>
10  </div>
11);

To also make this work for server-side rendering, you need to add these changes to your _document.jsx file (read here if you don't have this file yet):

1// ./pages/_document.js
2import Document, { Head, Main, NextScript } from 'next/document';
3import sprite from 'svg-sprite-loader/runtime/sprite.build';
4
5export default class MyDocument extends Document {
6  static async getInitialProps(ctx) {
7    const initialProps = await Document.getInitialProps(ctx);
8    const spriteContent = sprite.stringify();
9
10    return {
11      spriteContent,
12      ...initialProps,
13    };
14  }
15
16  render() {
17    return (
18      <html>
19        <Head>{/* your head if needed */}</Head>
20        <body>
21          <div dangerouslySetInnerHTML={{ __html: this.props.spriteContent }} />
22          <Main />
23          <NextScript />
24        </body>
25      </html>
26    );
27  }
28}

Configuration

This plugin uses img-loader under the hood which is based on mozjpeg, optipng, gifsicle and svgo.

The default options for these optimizers should be enough in most cases, but you can overwrite every available option if you want to.

handleImages

Type: string[]
Default: ['jpeg', 'png', 'svg', 'webp', 'gif']

next-optimized-images registers the webpack loader for all these file types. If you don't want one of these handled by next-optimized-images because you, for example, have another plugin or custom loader rule, simply remove it from the array.

Please note that an image being handled does not mean it also gets automatically optimized. The required optimization package for that image also has to be installed. Please read the optimization packages section for more information.

If an image gets handled but not optimized, it means that the original image will get used and copied for the build.

:information_source: Since version 2.5, ico files are also supported but for backwards compatibility, they need to be manually enabled. By adding 'ico' to the handleImages array, the plugin will also handle ico files.

inlineImageLimit

Type: number
Default: 8192

Smaller files will get inlined with a data-uri by url-loader. This number defines the maximum file size (in bytes) for images to get inlined. If an image is bigger, it will get copied to the static folder of next.

Images will get optimized in both cases.

To completely disable image inlining, set this value to -1. You will then always get back an image URL.

imagesFolder

Type: string
Default: 'images'

Folder name inside /static/ in which the images will get copied to during build.

imagesPublicPath

Type: string
Default: `/_next/static/${imagesFolder}/`

The public path that should be used for image URLs. This can be used to serve the optimized image from a cloud storage service like S3.

From version 2 on, next-optimized-images uses the assetPrefx config of next.js by default, but you can overwrite it with imagesPublicPath specially for images.

imagesOutputPath

Type: string
Default: `static/${imagesFolder}/`

The output path that should be used for images. This can be used to have a custom output folder.

imagesName

Type: string
Default: '[name]-[hash].[ext]'

The filename of the optimized images. Make sure you keep the [hash] part so they receive a new filename if the content changes.

removeOriginalExtension

Type: boolean
Default: false

When images converted to WebP on the fly, .webp was append to the filename. For example, test.png became test.png.webp. If you want to have only one filename extension like test.webp, you can set this option to true.

optimizeImagesInDev

Type: boolean
Default: false

For faster development builds and HMR, images will not get optimized by default when running in development mode. In production, images will always get optimized, regardless of this setting.

mozjpeg

Requires the optional optimization package imagemin-mozjpeg (npm install imagemin-mozjpeg)

Type: object
Default: {}

mozjpeg is used for optimizing jpeg images. You can specify the options for it here. The default options of mozjpeg are used if you omit this option.

optipng

Requires the optional optimization package imagemin-optipng (npm install imagemin-optipng)

Type: object
Default: {}

optipng is used for optimizing png images by default. You can specify the options for it here. The default options of optipng are used if you omit this option.

pngquant

Requires the optional optimization package imagemin-pngquant (npm install imagemin-pngquant)

Type: object
Default: {}

pngquant is an alternative way for optimizing png images. The default options of pngquant are used if you omit this option.

gifsicle

Requires the optional optimization package imagemin-gifsicle (npm install imagemin-gifsicle)

Type: object
Default:

1{
2    interlaced: true,
3    optimizationLevel: 3,
4}

gifsicle is used for optimizing gif images. You can specify the options for it here. The default options of gifsicle are used if you omit this option.

svgo

Requires the optional optimization package imagemin-svgo (npm install imagemin-svgo)

Type: object
Default: {}

svgo is used for optimizing svg images and icons. You can specify the options for it here. The default options of svgo are used if you omit this option.

Single svgo plugins can get disabled/enabled in the plugins array:

1{
2  svgo: {
3    plugins: [
4      { removeComments: false }
5    ]
6  }
7}

svgSpriteLoader

Requires the optional optimization packages imagemin-svgo and svg-sprite-loader (npm install imagemin-svgo svg-sprite-loader)

Type: object
Default:

1{
2  runtimeGenerator: require.resolve(path.resolve('node_modules', 'next-optimized-images', 'svg-runtime-generator.js')),
3}

When using the svg sprite option, svg-sprite-loader gets used internally. You can overwrite the configuration passed to this loader here.

webp

Requires the optional optimization package webp-loader (npm install webp-loader)

Type: object
Default: {}

imagemin-webp is used for optimizing webp images and converting other formats to webp. You can specify the options for it here. The default options of imagemin-webp are used if you omit this option.

imageTrace

Requires the optional package image-trace-loader (npm install image-trace-loader)

Type: object
Default: {}

When using image-trace-loader for the ?trace resource query, you can define all options for the image trace loader in this object. The default options of image-trace-loader are used if you omit this option.

responsive

Requires the optional optimization package responsive-loader (npm install responsive-loader)

Type: object
Default: {}

The configuration for the responsive-loader can be defined here.

defaultImageLoader

Requires the optional optimization package responsive-loader (npm install responsive-loader)

Type: string
Default: 'img-loader'

By default, img-loader handles most of the requests. However, if you use the responsive-loader a lot and don't want to add the ?resize query param to every require, you can set this value to 'responsive-loader'.

After that, responsive-loader will handle all JPEG and PNG images per default, even without an additional query param. Just be aware that you can't use any of the query params next-optimized-images provides anymore on these images because the request just gets forwarded and not modified anymore. All other formats (SVG, WEBP and GIF) still work as before with the img-loader and so have all query params available.

optimizeImages

Type: boolean
Default: true

If you don't have any optimization package installed, no image will get optimized. In this case, a warning gets written to the console during build to inform you about a possible misconfiguration. If this config is intended and you indeed don't want the images to be optimized, you can set this value to false and you won't get the warning anymore.

Example

The options specified here are the default values.

So if they are good enough for your use-case, you don't have to specify them to have a shorter and cleaner next.config.js file.

1// next.config.js
2const withPlugins = require('next-compose-plugins');
3const optimizedImages = require('next-optimized-images');
4
5module.exports = withPlugins([
6  [optimizedImages, {
7    // these are the default values so you don't have to provide them if they are good enough for your use-case.
8    // but you can overwrite them here with any valid value you want.
9    inlineImageLimit: 8192,
10    imagesFolder: 'images',
11    imagesName: '[name]-[hash].[ext]',
12    handleImages: ['jpeg', 'png', 'svg', 'webp', 'gif'],
13    removeOriginalExtension: false,
14    optimizeImages: true,
15    optimizeImagesInDev: false,
16    mozjpeg: {
17      quality: 80,
18    },
19    optipng: {
20      optimizationLevel: 3,
21    },
22    pngquant: false,
23    gifsicle: {
24      interlaced: true,
25      optimizationLevel: 3,
26    },
27    svgo: {
28      // enable/disable svgo plugins here
29    },
30    webp: {
31      preset: 'default',
32      quality: 75,
33    },
34  }],
35]);

See also

• next-images if you just want images and not optimize them
• next-compose-plugins for a cleaner plugins API when you have many plugins in your next.config.js file
• next-plugins for a list of official and community made plugins

License

MIT © Cyril Wanner