Apps
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 the FFmpeg executable on every install or run. That cache typically contains downloaded ffmpeg-static binary archives or extracted executables plus response metadata used to track which build was fetched for Windows. Kudu removes only those cached download artifacts and metadata so the package can fetch a fresh copy when needed, without touching your media files, project data, app settings, accounts, or passwords.
Why clean ffmpeg-static Cache?
- A partially downloaded or truncated FFmpeg archive in the cache causes ENOENT, unzip, or spawn errors when an app tries to start video conversion, and the job fails immediately
- Stale response metadata can point a package to an older cached Windows build, leading to 'ffmpeg exited with code 1' or unsupported codec behavior until a fresh binary is downloaded
- Interrupted updates can leave mismatched executable files and metadata in the cache, which shows up as apps hanging on 'preparing export' or repeatedly retrying the FFmpeg download
- Old cached ffmpeg-static binaries accumulate across package updates and consume hundreds of megabytes in %LocalAppData%, even though only one current download is needed
- Permission or antivirus interference can leave a cached executable present but unusable, causing 'Access is denied' or 'not a valid Win32 application' when media processing starts
- Corrupt cache contents can make Electron or Node apps repeatedly revalidate and redownload FFmpeg on launch, which users notice as long startup delays before recording, transcoding, or waveform generation begins
What gets cleaned
Cache paths Kudu targets
Windows
%LocalAppData%/ffmpeg-static-nodejs/Cache |
Frequently asked
Common questions about ffmpeg-static Cache
Related cleaners
Free & open source
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.