// troubleshooting guide · vercel

Vercel Images Not Loading: Image Optimization 400/500/502 Error

Status
Workaround available
platforms:
Web (Next.js on Vercel)
updated:
November 21, 2026
reports:
3
Method
how we research
Share

RUNBOOK · vercel/images-not-loading-image-optimization4 FIXES

// quick answer

Images that work locally but fail on Vercel usually hit the Next.js image optimizer: the remote host is not allowed in next.config, the source URL is unreachable, or the optimization quota is used up. Check the failing /_next/image response and the runtime logs.

Most likely fix: Allow the remote host

How to fix it

// try these in order, the most common fix is first

  1. FIX 1Allow the remote host

    1. 01Add the host to images.remotePatterns in next.config
    2. 02Redeploy
    3. 03Open the /_next/image URL directly to see the status code
    Did this fix it?
  2. FIX 2Check the source and file names

    1. 01Open the original image URL in a private window
    2. 02Match file name case exactly
    3. 03Put static images in /public and reference them from root
    Did this fix it?
  3. FIX 3Check usage limits

    1. 01Team dashboard > Usage > Image Optimization
    2. 02On Hobby, wait for reset or upgrade
    3. 03Reduce variants with fewer sizes/qualities
    Did this fix it?
  4. FIX 4Bypass optimization where needed

    1. 01Set unoptimized on the Image component for static exports
    2. 02Or provide a custom loader
    3. 03Keep optimization for big photos
    Did this fix it?

SANDBOX · vercel RUNS IN YOUR BROWSER

Try it: push, build and ship on a Vercel-style dashboard

A hands-on Vercel-style sandbox, including the spots where users get stuck. See where problems like this one start. 1-2 minutes, nothing is saved.

Symptoms

Broken images on the deployed site; /_next/image returns 400, 500 or 502; INVALID_IMAGE_OPTIMIZE_REQUEST or INTERNAL_OPTIMIZED_IMAGE_REQUEST_FAILED in logs.

Why it happens

  • C-01Remote hostname missing from images.remotePatterns
  • C-02Source image URL returns an error or is blocked for Vercel's servers
  • C-03Image path differs in case between local and Linux build
  • C-04output: 'export' with the default image loader
  • C-05Image transformation limit reached (5,000/month on Hobby)

// this guide also covers

  • vercel images not loading
  • next/image not working vercel
  • INTERNAL_OPTIMIZED_IMAGE_REQUEST_FAILED
  • _next/image 500 vercel

Still not working?

If Vercel keeps failing, you're not alone. See every Vercel problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us

Watch Vercel Get an email when its price changes, it has an outage, or we publish a new fix. No spam.

Fixed it? Share this guide

Other Vercel errors

All 16 Vercel errors and fixes →