ffmpeg-static Cache
Node packages that depend on ffmpeg-static keep a local download cache under %LocalAppData%/ffmpeg-static-nodejs/Cache so they do not fetch FFmpeg binaries on every install or first run. That cache typically contains downloaded ffmpeg.exe archives, extracted binary copies, temporary partial downloads, and HTTP response metadata used to decide whether a cached build can be reused. Kudu removes these cached binaries and metadata so stale, corrupted, or abandoned ffmpeg-static downloads can be fetched again without affecting your projects, accounts, settings, or source media files.
Why clean ffmpeg-static Cache?
- A truncated or interrupted ffmpeg.exe download leaves a bad cached binary behind, so apps fail with spawn errors or "ffmpeg not found" until the package re-downloads it
- Cached response metadata can point to an outdated release URL, causing repeated download failures or install loops when the upstream binary location changes
- Old ffmpeg-static binaries accumulate after dependency upgrades, wasting space in LocalAppData even though only one current binary is needed
- Antivirus or endpoint protection sometimes quarantines part of the cached executable, leaving checksum mismatches and visible build or startup failures in tools that bundle ffmpeg-static
- Partial archives and temporary files from canceled npm or yarn installs remain in the cache, leading to unnecessary disk use and confusing retries on the next install
- Version mismatches between a newly updated wrapper package and an older cached FFmpeg binary can surface as unexpected codec support errors or failed media conversions until the binary is refreshed
Cache paths Kudu targets
Windows
%LocalAppData%/ffmpeg-static-nodejs/Cache |
Common questions about ffmpeg-static Cache
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.