Imageflow's four-method C ABI and the server it removed
High-performance image manipulation for web servers. Includes imageflow_server, imageflow_tool, and libimageflow
At a glance
- What is it?
- Imageflow is a Rust image processing engine split into a command line tool, an in-process C-compatible library and a separate .NET server product. Its own README now tells you the server binary is gone and points you elsewhere.
- Who is it for?
- Adopt Imageflow if you want image work in process through a narrow C ABI, or a command line that already speaks ImageResizer 4 querystrings, and stay on ImageMagick or libvips if you need a normally versioned pure-Rust crate or a server that does not add .NET to your stack.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 8 days ago.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.
Star history
- imazen/imageflow4,470 ★ · +55
| Repository | 2026-09-23 | 2026-11-14 |
|---|---|---|
| imazen/imageflow | 4.4k | 4.5k |
55 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Three deliverables, one Rust workspace, and a fourth that lives elsewhere
Imageflow exists because a web server that resizes images usually ends up calling ImageMagick, and calling ImageMagick per request is where memory ceilings and security advisories come from. The project answers that with two shipped pieces plus a server that lives in a different repository. imageflow_tool is the command line binary, meant for batch jobs, JSON graphs and process isolation. libimageflow is the in-process library you link from your own language. Imageflow.Server, the piece that answers a request such as /bucket/img.jpg?w=200, lives in a separate repository, imazen/imageflow-dotnet-server; the removed piece is the old imageflow_server.
That third piece matters because the README is precise about why it left. imageflow_server was built on the Rust web framework iron, and the README states the framework is abandoned and no longer secure, so the project recommends Imageflow.Server, a .NET server with hybrid disk caching and Azure and Amazon blob storage support. Two languages for one job is the tax you pay for that decision. Anyone arriving expecting a single self-hosted Rust service should read that note before anything else.
A four-method ABI is the whole integration story
The claim worth testing is how thin the foreign boundary really is. The README states that only 4 methods are needed to implement bindings, and that the C and C++ interface is stable, pointing at bindings/headers/imageflow_default.h. Existing bindings cover Node, Go, Scala, Elixir, .NET and Ruby, and for any other language you run an FFI binding generator over whichever header it picks.
The Rust side is where the stability stops. imageflow_core is the execution engine, and the README says its interfaces are not semver in line with the tagged versions, because those numbers track the C ABI rather than the Rust API. One recent tag, v2.2.0-rc01, commits to make the ABI thread-safe and add imageflow_context_request_cancellation, so even the fixed surface is still moving. The repository is not archived and the last push was on 2026-10-20, so nothing here is dormant, but the licence is AGPL-3.0 and the README sends commercial users to imageresizing.net for an exception, which is not a formality for anyone shipping a modified Imageflow over a network.
Querystrings and JSON graphs run through two different subcommands
imageflow_tool exposes two front ends. v1/querystring takes a single image and an ImageResizer 4 style command string, a syntax the README says ImageResizer brought to more than a thousand different CMSes and applications. v1/build takes a JSON job file, which can hold multiple inputs and outputs and any operation graph.
The single-image path is the shortest thing to try first:
imageflow_tool v1/querystring --in source.jpg --out thumb.jpg --command "width=50&height=50&mode=crop&format=jpg" You should see thumb.jpg written next to the input. The graph path is what you want when one source becomes four widths. The example pairs a job file with repeated --out arguments and a --response target:
imageflow_tool v1/build --json examples/export_4_sizes/export_4_sizes.json
--in waterhouse.jpg
--out 1 waterhouse_w1600.jpg
2 waterhouse_w1200.jpg
3 waterhouse_w800.jpg
4 waterhouse_w400.jpg
--response operation_result.jsonDefault behaviour is to print a JSON response to stdout, so --response is what turns that into a file you can read later. If you have no example jobs yet, imageflow_tool examples --generate writes an examples directory with JSON jobs and invocation scripts. When something misbehaves, --debug-package produces a zip that reproduces it under both subcommands, which is the fastest way to file a useful bug.
Building from source means living on git branches of forks
The build section says you need more than Rust because there are C dependencies, then gives you the same three steps everyone gets. On Windows, build commands only run inside the window created by win_enter_env.bat.
git clone [email protected]:imazen/imageflow.git && cd imageflow
cargo build --release --allBinaries land in the target directory. That part is ordinary. The part that should make you hesitate is in Cargo.toml, under [patch.crates-io]. libpng-sys points at imazen/rust-libpng-sys on git, lcms2-sys points at a fork branch called update-lcms2-2.18, zenjpeg and zenwebp both track the main branch of the maintainer's own repositories, and a commented-out rgb crate carries a TODO waiting for rgb 0.8.91 to reach crates.io. Those dependencies follow branch heads rather than crates.io releases, with the resolved commits recorded in the committed Cargo.lock.
The profiles reinforce the point: the shipped profile sets strip = true and lto = true, while the test profile sets opt-level = 2, and a comment records RIAPI tests dropping from 600ms each at level 0 to 26ms at level 3. What you test and what you ship are not the same binary.
Where Imageflow genuinely loses to ImageMagick
The performance claim is the README's own, not an independent measurement: up to 17x faster than ImageMagick, with smaller files at higher quality. Even granting it, imageflow_tool is a process. Each call pays startup, and for a server path it also pays serialization, which is why the project frames process isolation as a feature rather than an accident.
The harder limit is the Rust crate path. If your team wants image processing inside a Rust service through crates.io with ordinary semantic versioning, imageflow_core is the wrong door, because the README states plainly that the Rust interfaces are not semver in line with the C ABI. You pin to a commit and re-pin after upstream moves. The self-hosted story has the same shape of problem in a different place: imageflow_server is gone, so the remaining option puts .NET in your deployment.
A smaller catch worth knowing: c_components/tests is described as tests for the C components, and it is commented out of the workspace members list in Cargo.toml. A default cargo build --all does not build it.
The real alternative: libvips and ImageMagick as a library
ImageMagick is the thing the README positions against, and it is worth being concrete about the difference. ImageMagick is a general command line suite you shell out to, or embed through its C API, and its per-request process cost is what puts it under pressure in a serving path. Imageflow's bet is an in-process engine reached through four C ABI methods, so a language binding is a thin shim over a fixed surface rather than a port of a large library.
libvips is the quieter alternative, because it solves the same shape of problem, in process and fast, with a wide format surface and mature language bindings, but without candidate-suffixed version numbers, and without a dependency graph reaching git branches of forks. Imageflow's counterargument is ImageResizer 4 querystring compatibility, carried by the imageflow_riapi crate, which exists to parse and lay out exactly that vocabulary.
If you already own ImageResizer or a CMS that speaks its querystrings, that compatibility is the deciding factor, and it is not something a competitor hands you for free.
Checksum-gated tests decide whether a change is accepted
Imageflow is not tested by eye. The justfile wraps cargo nextest against the imageflow_core integration suite and adds a few escape hatches that say a lot about how the project catches regressions in an encoder. test-update and its alias test-replace run the suite with UPDATE_CHECKSUMS=1 so checksums within tolerance are auto-accepted rather than failed, and a comment states there is no separate replace mode, only the one toggle. Upload of reference images to S3 is gated on UPLOAD_REFERENCES=1 plus the sync_and_verify_uploads test, and verify-uploads checks that every reference image is recorded in uploaded.log without needing credentials.
Reading a change means judging whether a new checksum is an intended encoder change or a regression, and the justfile gives you two more ways to do it: backfill-diffs downloads images and fills in diff stats on auto-accepted entries, and accept-ci pulls the checksum list from the latest workflow run for a named platform.
That is the maintenance load nobody advertises. Every encoder upgrade arrives as a checksum diff you have to attribute. Alongside it sit imageflow_types for shared serialized types, imageflow_helpers for common utilities, append_only_set for its append-only structure, plus a benchmarks directory and a fuzz directory, so the crate layout explains how much of the effort sits around the engine rather than in it.
Editorial conclusion
Adopt Imageflow if you want image work in process through a narrow C ABI, or a command line that already speaks ImageResizer 4 querystrings, and stay on ImageMagick or libvips if you need a normally versioned pure-Rust crate or a server that does not add .NET to your stack. Before either path, build it once on your own platform and check that the git-branched zenjpeg, zenwebp, libpng-sys and lcms2-sys forks still compile, because those dependencies track branch heads rather than crates.io releases. Then confirm that c_components/tests, commented out of the workspace, is not something you were counting on.
Frequently asked questions
What is Imageflow used for?
Imageflow is a high-performance image manipulation library for web servers. It ships as the imageflow_tool command line binary and as libimageflow, an in-process library with a C-compatible ABI.
How do I install Imageflow?
Self-contained binaries are provided for Windows, Ubuntu and Mac, and Docker images exist for Linux. From source, clone the repository and run cargo build --release --all, which also needs platform prerequisites and C dependencies.
Can Imageflow still run as a web server?
No. The README states that imageflow_server was removed because its web framework, iron, is abandoned and no longer secure. The project points to Imageflow.Server, a separate .NET product, as the replacement.
Is the Imageflow Rust crate API stable?
The C and C++ interface is described as stable, and only 4 methods are needed for bindings. The README says the imageflow_core crate interfaces are not stable or semver in line with the tagged versions, because those numbers track the C ABI.
How do I resize an image with the Imageflow CLI?
Use the v1/querystring subcommand with an ImageResizer 4 compatible command string, or v1/build with a JSON job file for multi-input, multi-output operation graphs. Add --response to write the JSON result to a file instead of stdout.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/imazen-imageflow)Star history chart for your README
[](https://hysenlabs.com/projects/imazen-imageflow)Was this useful?