When to use ImageForge
When ImageForge CLI is the right fit
Choose ImageForge for the workflows it actually serves well.
Strong fit
- Static or moderately changing image catalogs
- Teams that want generated assets reviewed and committed
- Multiple frameworks consuming one manifest contract
- Controlled responsive widths and no runtime transformation service
- Air-gapped or predictable build environments
Consider another approach
- User-generated or rapidly changing media that cannot wait for builds
- Dynamic cropping, focal-point editing, or URL-based transformations
- A team that prefers a managed media library, delivery CDN, and analytics
- A small Next.js project already satisfied by static imports and its built-in optimizer
Cost language
ImageForge is open-source software and does not charge runtime transformation fees. Your build compute, repository/storage, CDN, and egress costs still depend on your hosting setup.