`next/image` optimizes images automatically: it serves the right size, supports modern formats, lazy-loads by default, and helps prevent layout shifts when you provide dimensions. It improves performance compared to shipping one huge image everywhere.
Expanding on the short answer — what usually matters in practice:
A tiny example (an explanation template):
// Example: discuss trade-offs for "what-does-`next/image`-do-for-you-(and-why-use-i"
function explain() {
// Start from the core idea:
// `next/image` optimizes images automatically: it serves the right size, supports modern for
}