Pattern 1
- hostname expected images.example.com, got cdn.example.com
Next.js image remotePatterns preflight
Paste one image URL and a sanitized config snippet. Get a static protocol, hostname, port, pathname, and query-string verdict without fetching the image or reading project files.
The image URL does not line up with the pasted Next.js remotePatterns config.
Next.js Image remotePatterns preflight Status: fail Summary: The image URL does not line up with the pasted Next.js remotePatterns config. Image URL parts: - https://cdn.example.com/account123/avatar.png Pattern checks: - Pattern 1: no match; protocol=https, hostname=images.example.com, pathname=/account123/**; hostname expected images.example.com, got cdn.example.com Warnings: - none Checklist: - Match protocol and hostname exactly unless you intentionally use a wildcard hostname. - Check pathname wildcards such as /account123/** before widening image access. - Review search params when the URL has a query string and the pattern includes search. - Run a real Next.js build because this page does not execute your project. Scope: static URL and config-name check only. This report does not fetch images, run Next.js, or upload project files.
It checks static URL matching against `images.remotePatterns`, including protocol, hostname wildcards, pathname wildcards, port, and exact search values.
It does not run Next.js, fetch remote images, validate CDN auth, optimize images, or prove that a deployment config is complete.