Skip to content

Disable the Next image optimizer (open proxy burning Vercel quota) - #3

Open
musnit-agent wants to merge 1 commit into
spinamp:mainfrom
musnit-agent:fix/disable-image-optimizer
Open

Disable the Next image optimizer (open proxy burning Vercel quota)#3
musnit-agent wants to merge 1 commit into
spinamp:mainfrom
musnit-agent:fix/disable-image-optimizer

Conversation

@musnit-agent

Copy link
Copy Markdown

The wildcard remotePatterns config made this deployment's /_next/image?url=… endpoint transform any image on the internet — a scan-and-abuse target that's the likely source of the image-transformation usage on the Vercel bill. The app itself never uses next/image (frames.js renders frame images via sharp/satori), so the optimizer is disabled outright.

After merging + redeploying, the Usage graph for Image Optimization should flatline; if anything legitimately depended on the optimizer it would 400 with unoptimized: true — none found in the codebase.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VMPaNZRGFuNaPm973D15vx

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
@vercel

vercel Bot commented Aug 12, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Spinamp Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant