vanilagy/mediabunny

Pure TypeScript media toolkit for reading, writing, and converting video and audio files, directly in the browser.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 9th, 2026
Created on September 1st, 2024
Open Issues & Pull Requests: 42 (-1)
GitHub issues: Enabled
Number of forks: 293
Total Stargazers: 7,118 (+0)
Total Subscribers: 22 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.2 hours
Mean response time: 2.5 days
90th percentile: 5.4 days
Tracked items: 299

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 37
New in 7 days: 6
Closed in 7 days: 7
Avg open age: 194 days
Stale 30+ days: 27
Stale 90+ days: 20

Recent activity

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

Top labels

No label distribution available yet.

Detailed Description

Mediabunny is a pure TypeScript media toolkit for reading, writing, and converting video and audio files directly in the browser.

The tool solves the problem of performing media operations on the web without requiring server-side processing or external dependencies. It handles demuxing and muxing of formats including MP4, WebM, MP3, OGG, WAV, and HLS, leveraging the browser's WebCodecs API where available. Built entirely from scratch in TypeScript with zero dependencies, it prioritizes performance and tree-shakeability so applications only bundle the functionality they actually use.

Developers should choose this tool when building browser-based media applications that need to avoid server round-trips for encoding, decoding, or format conversion. It suits projects where keeping media processing on the client side reduces latency and server load. The README positions it conceptually as FFmpeg reimagined for the web, though it does not make direct feature-by-feature comparisons to other libraries.

The project maintains active engagement with its community through a Discord channel and accepts sponsorship. Documentation and examples are published alongside the core library to support adoption.