v4: a still is scaled from its first frame alone, a second image in its file made the copy flash — an avatar came out as a WebP of two frames looping at 40 ms each, the picture then a blank. A still's file may hold more than one image, a phone's JPEG carrying a gain map or a depth map after the photo, and ffmpeg reads each as a frame: only the JPEG and PNG copies were held to one, the WebP keeping them all as it does a GIF's. scalableImage (lib/upload.ts) now says whether the image is an animation, which a GIF alone is, and scaleImage (lib/ffmpeg.ts) writes one frame of anything else, in every format; the image proxy scales through the same call. The copies already made stay, a copy being current while it has its upload's date: uploads/scaled is to be deleted once on an instance that ran the previous version, everything in it being made again on first request.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

api/remote/image-proxy.ts

@@ -111,8 +111,7 @@ export async function fetchProxiedImage(
   const original = await fetchOriginal(url);
   if (!original) return null;
   const how = scalableImage(original.bytes);
-  const bytes = how &&
-    await scaleImageBytes(original.bytes, width, how.orientation);
+  const bytes = how && await scaleImageBytes(original.bytes, width, how);
   if (!bytes) return original;
   writeImageCache(key, bytes, "image/webp");
   return { bytes, contentType: "image/webp" };