facebook/igl

Intermediate Graphics Library (IGL) is a cross-platform library that commands the GPU. It provides a single low-level cross-platform interface on top of...

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 21st, 2026
Created on July 7th, 2023
Open Issues & Pull Requests: 1 (+1)
GitHub issues: Enabled
Number of forks: 221
Total Stargazers: 3,238 (+0)
Total Subscribers: 51 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.4 hours
Mean response time: 8.6 days
90th percentile: 12.9 days
Tracked items: 37

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • bug (12)
  • enhancement (6)
  • documentation (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Intermediate Graphics Library (IGL) is a cross-platform graphics abstraction layer that provides a unified low-level interface to command the GPU across different graphics APIs.

IGL solves the problem of writing graphics code that must run on multiple platforms with different underlying graphics APIs. Rather than forcing developers to write separate code paths for OpenGL, Metal, Vulkan, and other APIs, IGL presents a single consistent interface that abstracts away the differences between them. Applications built on IGL can target multiple platforms and graphics backends without duplicating rendering logic.

Developers should choose IGL when building graphics applications that need to run across multiple platforms and graphics APIs without maintaining separate rendering implementations for each. It suits projects where cross-platform compatibility is a requirement and where the overhead of an abstraction layer is acceptable. The library is particularly valuable for teams that want to write graphics code once and deploy it across desktop, mobile, and other platforms that support different graphics APIs.

The project shows active development with regular commits addressing bug fixes, feature additions, and API refinements. Work spans multiple areas including renderer implementations, shader compilation infrastructure, and platform-specific optimizations. The codebase receives updates that improve both the core abstraction layer and support for individual graphics backends. Development activity indicates ongoing maintenance and expansion of the library's capabilities across its supported platforms and APIs.