ImageForge and Sharp
ImageForge CLI vs direct Sharp scripts
Choose an adoption layer without presenting the underlying image library as a competitor.
ImageForge uses Sharp
Sharp is the image-processing dependency behind ImageForge's decoding and encoding. ImageForge adds a directory-oriented CLI contract: discovery, collision checks, responsive width sets, cache ownership, blur placeholders, a manifest, structured reports, dry-run, and CI freshness checks.
Use ImageForge for a standard pipeline
- The source-to-output contract should be shared across projects or frameworks
- You want manifest dimensions, hashes, blur data, and output paths
- Generated state belongs in review and must be checked in CI
- Responsive WebP/AVIF conversion covers the required transformations
Use Sharp directly for custom transforms
A direct Sharp script is the better layer when the pipeline needs custom compositing, metadata handling, colorspace work, dynamic crops, unusual formats, storage integration, or application-specific orchestration. ImageForge is intentionally not a replacement for Sharp's full API.