# Flyimg

Flyimg is an open-source, self-hosted, Docker-based image optimization service that resizes, crops, compresses, and converts images on the fly through a simple URL API with caching, so developers and homelab users can.

Canonical page: https://ourlocalhost.com/app/8466/flyimg

## Description

Flyimg is an open-source, self-hosted, Docker-based image optimization service that resizes, crops, compresses, and converts images on the fly through a simple URL API with caching, so developers and homelab users can run their own Cloudinary-style image pipeline using AV1 Image Format (AVIF), WebP, or MozJPEG-compressed JPEG.

## Platform availability

Available on 1 of 10 platforms: Any server.

## Health score

73/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 10 days ago)
- Popular: 62 (1,232 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 81 (no serious findings, CI, tests, OpenSSF Scorecard 5.9/10)

## Links

- Official website: https://flyimg.io
- GitHub: https://github.com/flyimg/flyimg
- Documentation: https://docs.flyimg.io/

## Common questions

### How do I apply custom Flyimg parameters when running Docker?

Copy the parameters.yml file into your current directory, edit it, and mount it into the container at /var/www/html/config/parameters.yml.

### Which output formats can Flyimg produce?

By default it generates AVIF when the browser supports it, and it also supports WebP, MozJPEG-compressed JPEG, PNG, and GIF. JPEG XL is available when enabled through ImageMagick and can be forced with o_jxl.

### How can I restrict access to the image optimization API?

Flyimg can restrict allowed image-source domains, including wildcard patterns, and can require encrypted signed URLs. These security settings are configured in parameters.yml.

### Are converted images cached after the first request?

Yes. Flyimg fetches and converts the requested image, stores the result, caches it, and serves that cached version for later requests.

### Which host port should I expose for the default Docker container?

The example docker run command exposes container port 80 by mapping it to host port 8080.

### What extra step is needed after cloning the repository to build locally?

After cloning for the first time, run composer install inside the container before starting it. If the Docker build fails with apt-get file-not-found errors, running the build command again may work.

## Alternatives

- Cantaloupe
- Cloudinary: Image and video API platform for developers, covering uploads, storage, AI-powered transformations, optimization, and delivery for web and…
- Rutba Media FileServer: Open-source, self-hosted image origin that keeps only master files and resizes on request, with an LRU cache and a Strapi upload provider.
- imageproxy
- imgix: Imagery is one of the most powerful tools you have to make a sale or get your message across.
- imgproxy: A fast and secure standalone server for resizing, processing, and converting images on the fly.
- picfit
- wsrv.nl: An image cache &amp; resize service.

---
Source: Our Local Host (https://ourlocalhost.com/app/8466/flyimg), the self-hosted and open-source app directory.
