{"id":154,"hash":"1a4fb4f8626c03059090312eae4c367aeadeb2e0662d550ab066d5a502ab16cf","pattern":"Error: Image Optimization using Next.js default loader is not compatible with `next export`","full_message":"I got this error when deploying Next.js to Netlify.\n\nError: Image Optimization using Next.js default loader is not compatible with `next export`.\n\nPossible solutions:\n\n6:47:15 AM:   - Use `next start`, which starts the Image Optimization API.\n6:47:15 AM:   - Use Vercel to deploy, which supports Image Optimization.\n6:47:15 AM:   - Configure a third-party loader in `next.config.js`.\n6:47:15 AM:  -  Read more: https://err.sh/next.js/export-image-api.\n6:47:15 AM:   at exportApp (/opt/build/repo/node_modules/next/dist/export/index.js:14:712)\n\nThe problem does not occur when deploying to Vercel.","ecosystem":"npm","package_name":"next.js","package_version":null,"solution":"From Next.js 12.3, you can completely disable next/image Image Optimization using the unoptimized configuration in next.config.js. This avoids having to use a third-party provider to optimize the image when using next/export.\n\nFrom the next/image documentation:\n\nunoptimized - When true, the source image will be served as-is\ninstead of changing quality, size, or format. Defaults to false.\n\nmodule.exports = {\n    images: {\n        unoptimized: true\n    }\n}\n\nBefore Next.js 12.3 and from 12.2, the unoptimized configuration was still experimental and could be enabled under the experimental flag.\n\nmodule.exports = {\n    experimental: {\n        images: {\n            unoptimized: true\n        }\n    }\n}","confidence":0.95,"source":"stackoverflow","source_url":"https://stackoverflow.com/questions/65487914/error-image-optimization-using-next-js-default-loader-is-not-compatible-with-n","votes":90,"created_at":"2026-04-19T04:41:25.072577+00:00","updated_at":"2026-04-19T04:51:06.844124+00:00"}