ffmpegwasm/ffmpeg.wasm

FFmpeg for browser, powered by WebAssembly

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 3rd, 2026
Created on October 16th, 2019
Open Issues & Pull Requests: 422 (+0)
GitHub issues: Enabled
Number of forks: 1,105
Total Stargazers: 17,788 (+0)
Total Subscribers: 119 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 9.4 days
Mean response time: 81.7 days
90th percentile: 168.8 days
Tracked items: 127

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 1% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 117
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 854 days
Stale 30+ days: 115
Stale 90+ days: 109

Recent activity

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

Top labels

  • help wanted (2)
  • bug (1)
  • enhancement (1)
  • triage (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

ffmpeg.wasm is a WebAssembly port of FFmpeg that enables video and audio processing directly in web browsers.

The tool solves the problem of performing media transcoding and conversion without requiring server-side processing. By compiling FFmpeg to WebAssembly, it allows developers to handle video and audio recording, conversion, and streaming entirely on the client side, keeping processing local to the user's browser and reducing server load.

Developers should adopt ffmpeg.wasm when building browser-based applications that need to manipulate media files without backend infrastructure. It suits projects where client-side encoding, transcoding, or format conversion is required, or where users need to process media before upload. The tool is particularly valuable for applications prioritizing privacy or reduced server costs, since processing happens in the browser rather than on remote servers.

The project maintains a substantial base of active adopters who report issues from real-world use cases. Response times to issues and pull requests typically range from one to two weeks. Development activity centers on bug fixes and feature enhancements, with the issue tracker dominated by these categories of work.