
next/image Optimization on a Self-Hosted VPS (1 GiB Container)
On Vercel, next/image is somebody else's problem. The optimizer runs on their infrastructure, scales on their bill, and you never see it fall over. Move the same app to a self-hosted VPS in a 1 GiB container — which is exactly where this site runs, on a Coolify-managed Docker host — and the optimizer becomes the single most likely thing to get your process OOM-killed. It is not a bug. next/image does real work: it decodes the source image, resizes it to the requested width, re-encodes it to WebP
















