xiph/rav1e

The fastest and safest AV1 encoder.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on September 24th, 2017
Open Issues & Pull Requests: 255 (+0)
GitHub issues: Enabled
Number of forks: 292
Total Stargazers: 4,151 (+0)
Total Subscribers: 83 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 30.3 hours
Mean response time: 70.0 days
90th percentile: 125.7 days
Tracked items: 25

Most active contributors

Sign in to see contributor activity.

How this project is maintained

83% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 55% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 840 days
Stale 30+ days: 22
Stale 90+ days: 22

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 (15)
  • enhancement (2)
  • Chef's Choice (1)
  • invalid (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

rav1e is an AV1 video encoder written in Rust and Assembly that prioritizes speed and safety.

The project addresses the need for efficient AV1 video encoding by implementing the codec in Rust, a language that prevents entire classes of memory safety bugs at compile time. This approach eliminates undefined behavior vulnerabilities common in C-based encoders while maintaining performance through careful optimization and Assembly implementations of performance-critical paths. The encoder handles the complex task of converting video into the AV1 format, which offers superior compression compared to older codecs.

Developers should choose rav1e if they need an AV1 encoder with strong safety guarantees and good encoding speed. It suits projects where memory safety is a priority alongside performance, such as server-side transcoding infrastructure, cloud video services, or any application where encoder crashes or security vulnerabilities pose significant risks. The project is particularly valuable for teams that want to avoid the debugging burden and potential vulnerabilities associated with C-based encoders.

The project maintains steady development activity with regular commits across its codebase. Pull requests are reviewed and merged consistently, indicating active maintenance. The issue tracker shows ongoing engagement with bug reports and feature requests. Development appears distributed across multiple contributors who work on various aspects of the encoder, from algorithmic improvements to platform-specific optimizations.