Menu

INVALID_IMAGE_OPTIMIZE_REQUEST

Last updated March 4, 2025

The INVALID_IMAGE_OPTIMIZE_REQUEST error occurs when the query string is using an invalid value for q (quality) or w (width), or url returns a non-image response.

400

INVALID_IMAGE_OPTIMIZE_REQUEST:

Bad Request

Troubleshoot

I'm encountering an error and reviewing the docs at /flg~eyJhbGciOiJIUzI1NiJ9._v7-_v39.f3M12-KAPZCzcefUX_oPWq-I0u4iAhoJCQaxpxor_bI/docs/errors/INVALID_IMAGE_OPTIMIZE_REQUEST to understand what's happening. Please help me resolve this by: 1. **Suggest the fix**: Analyze my codebase context and propose what needs to be changed to resolve this error 2. **Explain the root cause**: Break down why this error occurred: - What was the code actually doing vs. what it needed to do? - What conditions triggered this specific error? - What misconception or oversight led to this? 3. **Teach the concept**: Help me understand the underlying principle: - Why does this error exist and what is it protecting me from? - What's the correct mental model for this concept? - How does this fit into the broader framework/language design? 4. **Show warning signs**: Help me recognize this pattern in the future: - What should I look out for that might cause this again? - Are there similar mistakes I might make in related scenarios? - What code smells or patterns indicate this issue? 5. **Discuss alternatives**: Explain if there are different valid approaches and their trade-offs My goal is to fix the immediate issue while building lasting understanding so I can avoid and resolve similar errors independently in the future.

To troubleshoot this error, follow these steps:

  1. Check for typos: Verify that there are no typos in the parameter names or values
  2. Review request format: Ensure that the request URL is correctly formatted and includes the required parameters
    • The q parameter controls the quality of the image and must follow these rules:
      • The q parameter must be an integer
      • The q integer must be greater than or equal to 1
      • The q integer must be less than or equal to 100
      • The q integer must be the same as one specified in qualities, if defined
    • The w parameter defines the width of the image and must follow these rules:
    • The url parameter specifies the image location and must follow these rules:
      • The url parameter must start with /, http://, or https://
      • The url parameter must match one of the configured remotePatterns or localPatterns in your next.config.js
      • The url parameter must have a Content-Type header that starts with image/
      • The url parameter must have a response body less than 300 MB (or less than 100 MB for hobby), otherwise the image won't be optimized

Run next dev locally to reproduce the error and get additional details.

Not what you were looking for?

Try filtering the errors by tag, code, or name on the Error Codes page.

Was this helpful?

supported.