coil-kt/coil

Image loading for Android and Compose Multiplatform.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 5th, 2026
Created on August 10th, 2019
Open Issues & Pull Requests: 74 (+0)
GitHub issues: Enabled
Number of forks: 788
Total Stargazers: 11,892 (+0)
Total Subscribers: 107 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.8 hours
Mean response time: 15.9 days
90th percentile: 12.9 days
Tracked items: 308

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 11% of issues opened in the past year have been closed. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 46
New in 7 days: 4
Closed in 7 days: 2
Avg open age: 610 days
Stale 30+ days: 37
Stale 90+ days: 31

Recent activity

Opened in 7 days: 4
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (88)
  • help wanted (43)
  • bug (8)

Detailed Description

Coil is an image loading library for Android and Compose Multiplatform that prioritizes simplicity and performance.

The library addresses the complexity of loading, caching, and displaying images in Android applications by providing a straightforward API built on Kotlin coroutines. It handles image fetching from various sources, decoding, caching at multiple levels, and rendering with minimal boilerplate. The approach leverages coroutines for non-blocking operations and integrates deeply with Compose's composable functions, allowing developers to load and display images with single-line expressions.

Coil suits projects targeting Android and Compose Multiplatform where developer experience and runtime efficiency matter. It works well for applications that need flexible image loading without extensive configuration, though teams already invested in alternative image loading solutions should evaluate whether migration provides sufficient benefit. The library's design emphasizes reducing common pain points like memory management, request cancellation, and cache invalidation through sensible defaults.

The project maintains active development with regular updates addressing both new platform capabilities and community feedback. The codebase shows consistent refinement of core functionality and expansion of Compose support. Documentation is comprehensive and kept current alongside feature additions. The maintainers respond to issues and pull requests with attention to architectural concerns and backward compatibility.