nextjs - 💡(How to fix) Fix `Image` component ignores explicitly set `quality` property [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#87913Fetched 2026-04-08 02:05:45
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2closed ×1issue_type_added ×1

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:09:56 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6041
  Available memory (MB): 49152
  Available CPU cores: 14
Binaries:
  Node: 24.12.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/patient-sun-pxydl6

To Reproduce

  1. Start the application
  2. Make sure the quality property of an image is different than 75
  3. Observe in devtools that image has a quality of 75 anyway, looking at URL and its q=75 query parameter

Current vs. Expected behavior

Instead of respecting the quality property value, the image remains loaded with q=75 query parameter, assuming that the quality is not explicitly set

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.2.0: Tue Nov 18 21:09:56 PST 2025; root:xnu-12377.61.12~1/RELEASE_ARM64_T6041
  Available memory (MB): 49152
  Available CPU cores: 14
Binaries:
  Node: 24.12.0
  npm: 11.6.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 16.1.1 // Latest available version is detected (16.1.1).
  eslint-config-next: N/A
  react: 19.2.3
  react-dom: 19.2.3
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Image (next/image)

Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Other (Deployed)

Additional context

No response

extent analysis

TL;DR

  • The issue can likely be resolved by explicitly setting the quality property in the next/image component or by checking the default quality setting in the Next.js configuration.

Guidance

  • Verify that the quality property is being passed correctly to the next/image component and that it is not being overridden by a default setting.
  • Check the Next.js configuration for any default quality settings that may be applied to images.
  • Review the next/image component documentation to ensure that the quality property is being used correctly.
  • Test the application with different quality property values to see if the issue persists.

Example

// Example of explicitly setting the quality property
import Image from 'next/image';

function MyImage() {
  return (
    <Image
      src="/image.jpg"
      width={500}
      height={300}
      quality={90} // Explicitly set the quality property
    />
  );
}

Notes

  • The issue may be specific to the next dev and next start commands, so testing with different commands may yield different results.
  • The lack of additional context makes it difficult to provide a more specific solution.

Recommendation

  • Apply workaround: Explicitly set the quality property in the next/image component to ensure that the desired quality is used.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix `Image` component ignores explicitly set `quality` property [2 comments, 2 participants]