Glide puts fetching, decoding, and caching behind one Android call
Glide v5.0.9 loads URLs, files, Android resources, animated GIFs, and video stills into an ImageView through a short request chain. Under that call sit decoding, resizing, memory reuse, disk caching, placeholders, and cancellation. The default network path uses HttpUrlConnection, with integrations for OkHttp and Volley when an app already uses either client.
The commit we measured contained 1,174 files, about 117,435 source lines, and an 85.1 MB checkout. Glide includes the core library, annotation processing, samples, benchmarks, and optional integrations. That breadth helps teams needing more than thumbnail downloads, while contributors face a multi-module Android build rather than a small utility jar.
Four cache layers require an explicit invalidation rule
In v5.0.9, Glide checks 4 places before fetching an image again: an active resource, memory, transformed output on disk, and original data on disk. Cache keys include the model, dimensions, transformations, options, and an optional signature. The caching guide says there is no simple way to delete every derivative for one URL, so frequently replaced media needs a changed identifier or version signature.
What happened when we ran it
Our sandbox installed Glide in 116 seconds, then the build failed with exit 1 after 20 seconds. We ran commit c3df4d2 in an unprivileged container with 3 CPUs, 10 GB of RAM, no secrets, and lab-jvm:21. Gradle stopped while configuring the gallery sample because it could not find a Java 11 installation matching the requested toolchain.
The test command failed with exit 1 after 17 seconds on the same Java 11 lookup. Its log reported no test count, so we cannot say whether the tests pass. Our scan found 2 CI workflow files, no Dockerfile, and no directory named tests. These are layout signals; the failed command remains our only test result.
A fresh contributor machine needs Java 11 and Android tooling
Both the 20-second build and 17-second test attempt stopped before compilation completed. The README tells builders to install the Android SDK and Support Repository, then set ANDROID_HOME or add sdk.dir to local.properties. Its build section does not warn that Gradle may also request Java 11 when a newer JDK already runs the wrapper.
App developers consuming v5.0.9 do not have to build the 85.1 MB checkout. The README supplies Maven Central coordinates, and R8 rules ship in the Android archive. Normal use needs no Glide account or hosted service. An app choosing the OkHttp or Volley module must still add and configure that client.
Glide v5 needs API 23, while its Compose integration remains beta
The v5.0.8 release raised Glide's minimum Android version to API 23 and its compile SDK to 37. The root README still calls v4 stable and lists API 14 and compile API 26, although its dependency snippet points to 5.0.9. For a v5 compatibility decision, the release notes are safer than that stale block.
Glide's Compose page calls the integration beta, and the 5.0.9 release track names a 1.0.0-beta10 artifact. Issue 5739 reports an IllegalStateException during fast lazy-list scrolling. Pull request 5744 proposes an attachment check and a 20-item regression case, but remained open when researched. Compose apps should reproduce that behavior before choosing the loader.
Two documented edges affect cache correctness and huge-image viewers
In v5.0.9, open issue 5732 says passing a false option can produce a different cache key from leaving it unset, with unexpected misses and black flashes. One report does not establish a general cache defect. It gives apps that build request options dynamically a specific regression case, since a miss may look like a rendering fault.
The README sets another firm limit: Glide can downsample huge maps and comic strips, but it does not provide zooming, panning, or tiling. An 85.1 MB source tree and many decoder hooks do not change that boundary. Use a tiled-image component for the viewport, then decide whether Glide should handle previews elsewhere.
August 2026 work is active, despite a stale compatibility section
The repository was pushed on August 29, 2026, and open pull requests were updated on August 28. GitHub listed more than 35,000 stars and 658 combined issues and pull requests when fetched. That count combines proposed code with defect reports. The dates show current work on Android dependencies, decoders, and Compose fixes.
Release v5.0.9 arrived on July 11, 2026 and corrected an extra dot in the version name. The larger v5.0.8 notes moved the build to Gradle 9.4.1, raised platform requirements, and listed ImageDecoder fixes for the current line. Glide merits an upgrade test, while the v4 README text should not decide compatibility.
Three live alternatives serve different Android stacks
Glide v5.0.9 faces 3 live alternatives with different priorities. Coil supports Android and Compose Multiplatform, making it the first comparison for a Kotlin-first UI. Fresco uses its own Android image pipeline and display components. Picasso keeps URL-to-ImageView work narrow. Glide's 4 cache layers suit established View apps whose build machines provide the requested toolchains.