next/image in dev does not update local image after file edit with same filename
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 142k
- Forks
- 32.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 351
Description
Link to the code that reproduces this issue
https://github.com/Austin1serb/next.js-minimal-build
To Reproduce
- Clone the reproduction repo.
- Install dependencies.
- Start the app in development mode with
next dev. - Open the page in the browser.
- The page renders the same local image twice, once with
next/imageand once with a plain<img>. - Edit the source image file used by both elements without changing its filename.
- Refresh the page.
- The plain
<img>shows the updated image, butnext/imagestill shows the old image. - Rename the image file or delete
.nextand restart the dev server. next/imagethen shows the updated image.
Current vs. Expected behavior
Expected:
Both next/image and plain <img> should reflect the updated local file in development after the image contents change.
Current:
Only the plain <img> updates. next/image continues to show a stale version when the file contents change but the filename stays the same.
Workarounds:
- rename the image file
- delete
.nextand restartnext dev
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 25.3.0: Wed Jan 28 20:54:22 PST 2026; root:xnu-12377.81.4~5/RELEASE_ARM64_T8112
Available memory (MB): 16384
Available CPU cores: 8
Binaries:
Node: 24.14.1
npm: 11.11.0
Yarn: 1.22.22
pnpm: 10.33.0
Relevant Packages:
next: 16.2.4 // Latest available version is detected (16.2.4).
eslint-config-next: N/A
react: 19.2.5
react-dom: 19.2.5
typescript: N/A
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
Image
Which stage(s) are affected? (Select all that apply)
next dev
Additional context
This is specifically about local development.
The reproduction shows a difference between next/image and plain <img> using the same local source image.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the linked minimal reproduction with next dev, compare next/image with the plain <img> after editing the same local file, and inspect the development image handling and .next behavior. Done means the next/image output reflects changed local image contents without renaming the file or deleting .next.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nextjs, react
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100