Skip to main content
Browse documentation

Vercel decision guide

ImageForge and Vercel Image Optimization

Evaluate a migration without implying that every Vercel or Next.js workload should move.

Keep Vercel optimization when it fits

Vercel transforms and caches images through framework image components. Keep that workflow when sources or required dimensions are dynamic, managed delivery is valuable, or the current usage and operational model already fits your application.

Evaluate ImageForge for stable assets

ImageForge is a candidate when the assets ship with the repository, the team wants generated files in pull-request review, and a fixed responsive set is sufficient. ImageForge itself has no runtime transformation fee; build compute, storage, CDN, requests, and transfer still belong to your hosting stack.

npx @imageforge/cli@0.1.10 ./public/images --formats webp,avif --widths 320,640,960,1280 --dry-run

Migrate one bounded directory

Start with a stable directory rather than changing the whole application. Generate and inspect derivatives, switch markup to generated paths, preserve intrinsic dimensions, add responsive srcsets, and bypass a second runtime transformation with unoptimized or an equivalent loader. Compare bytes, visual quality, build time, cache behavior, and delivery cost before expanding.

  • Keep the original route available during the evaluation
  • Test the exact production layout and sizes values
  • Add the same ImageForge options to build and CI check scripts
  • Review imageforge.json with the generated files; check mode validates both as one generated-state contract
  • Retain Vercel optimization for dynamic or remote media when it remains the better fit