Fix · Vercel and deploying
Next.js images fail on the live site (invalid host or 400)
Not checked against the vendor's current screens
What you may see
- Images work locally but show broken online
- Error says hostname is not configured under images
Most likely cause
The image comes from an outside address that the framework was not told to trust, or the image address is wrong online.
Check first (about two minutes)
- Open the broken image address directly in a tab: does it load?
- Check the error text for the host name it complains about.
The fix prompt
What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.
Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.
Prompt language
Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.
After you tried it, did it work?
Steps
- Find the image component and the source address of each broken image.
- Add the trusted host to the framework's image settings (remote patterns), with the narrowest rule that works.
- Check the image address is correct and public online; redeploy; test.
Do not do this
- Do not allow every host with a wildcard.
- Do not turn image optimization off for the whole site.