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…

  • Media Applications
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

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

73/100 Good

Maintained
100last commit 10 days ago
Popular
621,232 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
81no serious findings, CI, tests, OpenSSF Scorecard 5.9/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
1,232
Open issues
2
Last commit
2026-11-11
Latest release
1.12.13
License
AGPL-3.0
Activity
steady

Checked yesterday - source: GitHub (flyimg/flyimg)

Resources & Compatibility

Requirements not published yet.

Checked yesterday - source: Docker Hub image tags and published docs

First-install notes

  • Install Flyimg runs as a Docker container: pull the ready-made Docker image and start it; copy parameters.yml to your current directory and mount it as a volume to customise settings. source
  • Docker deployment The README describes Flyimg as a Dockerized application; run one Docker container to self-host the image optimization service. source

Fetched yesterday - each note links to its source

Alternatives (8)

  • 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 & resize service.

Checked yesterday - source: AlternativeTo

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.

Answers sourced from docs.flyimg.io, github.com

Community

No community discussions collected yet.