From bf9f0a8f7d8b7de24590615311cd7cbd92b7f430 Mon Sep 17 00:00:00 2001
From: Agentlab <musnit+agentlab@gmail.com>
Date: Wed, 12 Aug 2026 02:52:35 +0000
Subject: [PATCH] Disable the Next image optimizer

Nothing in the app uses next/image (frame images are rendered by
frames.js/sharp), but wildcard remotePatterns exposed /_next/image as an
open image-transformation proxy for any URL on the internet - the likely
source of the Vercel image-transformation quota burn.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VMPaNZRGFuNaPm973D15vx
---
 next.config.mjs | 14 ++++----------
 1 file changed, 4 insertions(+), 10 deletions(-)

diff --git a/next.config.mjs b/next.config.mjs
index 8f885ae..ea6e346 100644
--- a/next.config.mjs
+++ b/next.config.mjs
@@ -2,17 +2,11 @@
 const nextConfig = {
   // prevent double render on dev mode, which causes 2 frames to exist
   reactStrictMode: false,
+  // The app renders frame images itself (frames.js/sharp) and never uses
+  // next/image; the previous wildcard remotePatterns left /_next/image open
+  // as a public image-transformation proxy, burning Vercel quota.
   images: {
-    remotePatterns: [
-      {
-        hostname: "*",
-        protocol: "http",
-      },
-      {
-        hostname: "*",
-        protocol: "https",
-      },
-    ],
+    unoptimized: true,
   },
 };