ImageForge CLI documentation

Build the image pipeline. Verify it in CI.

Start with a non-destructive preview, generate WebP/AVIF derivatives and metadata, then enforce image freshness without runtime image transformation fees.

Safe first command

npx @imageforge/cli@0.1.10 ./public/images --dry-run

Guides

Getting started

Install, preview, generate, and verify your first image pipeline.

Next.js

Connect manifest output to next/image or a responsive picture element.

Static HTML

Complete a framework-free first integration using generated static assets.

CI and GitHub Actions

Make stale generated images fail pull-request checks before merge.

CLI reference

Choose and reproduce the options that define your generated image contract.

Configuration

Keep options reviewable and identical across developers and automation.

Manifest and responsive images

Turn generated files into reliable application image metadata.

Troubleshooting

Diagnose common failures without editing generated metadata by hand.

When to use ImageForge

Choose ImageForge for the workflows it actually serves well.

Build time vs runtime

Choose where image transformation belongs based on how your media changes and ships.

Vercel decision guide

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

Image service comparison

Use a scoped factual matrix without treating different product categories as interchangeable.

ImageForge and Sharp

Choose an adoption layer without presenting the underlying image library as a competitor.