Next.js Image Loader and Component

Optimize images with Uploadcare on the fly by using the UploadcareImage component or the uploadcareLoader custom image loader for Next.js.

The built-in Next.js Image component does a great job in optimizing images but the number of optimizations is limited. It allows setting a custom image loader to process images externally. This is where the @uploadcare/nextjs-loader package comes in handy.


Here is a demo app and its source code.



yarn add @uploadcare/nextjs-loader


Get your public key from the Dashboard and add it to your environment variables through .env file or your hosting UI.

# .env

If you're using a proxy, provide your application's base URL (also whitelisted), which is required to process local images properly.

# .env

Image transformation settings example:

# .env
NEXT_PUBLIC_UPLOADCARE_TRANSFORMATION_PARAMETERS="format/auto, quality/smart_retina, stretch/off, progressive/yes"javascript

The default image transformation parameters are format/auto, stretch/off, progressive/yes. If quality isn't explicitly specified, the plugin will use quality/smart by default.

Find additional settings, such as custom CDN domain, and custom proxy domain, in the developer documentation on Github.


Allow custom image loaders through next.config.js:

// next.config.js
module.exports = {
  images: {
    loader: "custom"

The easiest and the most straightforward way of utilizing the power of Uploadcare is to use the UploadcareImage component for all images on your site the same way as the built-in Image component.

import UploadcareImage from '@uploadcare/nextjs-loader';

  alt="A test image"

If you still need to use the built-in Image component with the uploadcareLoader:

import Image from 'next/image';
import { uploadcareLoader } from '@uploadcare/nextjs-loader';

  alt="A test image"

Note that if you pass a local image URL, the loader returns it AS IS if the app is run in the development mode or if the NEXT_PUBLIC_UPLOADCARE_APP_BASE_URL is not set.

Full documentation

Read the full documentation on GitHub.