How does caching work for my website?
Fingerprinted build output — hashed JavaScript, CSS, and media — is cached aggressively and safely, because filenames change whenever content does. Server-rendered pages follow the Cache-Control header your app sets: no header means every request renders fresh, while a shared lifetime like s-maxage caches the response at the CDN for every visitor. Time-based revalidation (Next.js "export const revalidate") is honored.