Image optimization cache policy when hosting locally / via Docker #57833
Unanswered
anaisbetts
asked this question in
Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
While using the Next.js Image Optimization with dynamic URLs, I see that the optimized image gets saved in the
.next/cache/imagesdirectory. This is great!For projects hosted via Vercel, this gets sent through their optimization service and is part of the billing, but when running via
next serve, is there a cache policy for this folder? If your app loads lots and lots of images for users, will you eventually run out of disk space?Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions