How to optimize images and fonts
Learn how to optimize images and fonts.
Next.js comes with automatic image and font optimization for better performance and user experience. This page will guide you through how to start using them.
Handling static assets
You can store static files, like images and fonts, under a folder called public in the root directory. Files inside public can then be referenced by your code starting from the base URL (/).

Optimizing images
The Next.js <Image> component extends the HTML <img> element to provide:
- Size optimization: Automatically serving correctly sized images for each device, using modern image formats like WebP and AVIF.
- Visual stability: Preventing layout shift automatically when images are loading.
- Faster page loads: Only loading images when they enter the viewport using native browser lazy loading, with optional blur-up placeholders.
- Asset flexibility: Resizing images on-demand, even images stored on remote servers.
To start using <Image>, import it from next/image and render it within your component.
The src property can be a local or remote image.
Local images
To use a local image, import your .jpg, .png, or .webp image files from your public folder.
Next.js will automatically determine the intrinsic width and height of your image based on the imported file. These values are used to determine the image ratio and prevent Cumulative Layout Shift while your image is loading.
Remote images
To use a remote image, you can provide a URL string for the src property.
Since Next.js does not have access to remote files during the build process, you'll need to provide the width, height and optional blurDataURL props manually. The width and height attributes are used to infer the correct aspect ratio of image and avoid layout shift from the image loading in.
Then, to safely allow images from remote servers, you need to define a list of supported URL patterns in next.config.js. Be as specific as possible to prevent malicious usage. For example, the following configuration will only allow images from a specific AWS S3 bucket:
Optimizing fonts
The next/font module automatically optimizes your fonts and removes external network requests for improved privacy and performance.
It includes built-in automatic self-hosting for any font file. This means you can optimally load web fonts with no layout shift.
To start using next/font, import it from next/font/local or next/font/google, call it as a function with the appropriate options, and set the className of the element you want to apply the font to. For example:
Google fonts
You can automatically self-host any Google Font. Fonts are included in the deployment and served from the same domain as your deployment, meaning no requests are sent to Google by the browser when the user visits your site.
To start using a Google Font, import your chosen font from next/font/google:
We recommend using variable fonts for the best performance and flexibility. But if you can't use a variable font, you will need to specify a weight:
Local fonts
To use a local font, import your font from next/font/local and specify the src of your local font file in the public folder.
If you want to use multiple files for a single font family, src can be an array:
