System
GStreamer Cache
GStreamer keeps a binary plugin registry in ~/.cache/gstreamer-1.0 so it can skip rescanning every multimedia plugin and element on each start. That cache stores discovered plugin metadata such as element factories, supported caps, feature ranks, and library paths, which speeds up media players, browsers, editors, and other apps built on GStreamer. Kudu removes the cached registry files so GStreamer can rebuild them from the currently installed plugins without touching media files, accounts, settings, or saved projects.
Why clean GStreamer Cache?
- A stale plugin registry after package upgrades can leave newly installed codecs or sinks invisible, so a player suddenly cannot open formats that should now be supported
- Cached library paths can point to removed or replaced plugin .so files, which shows up as missing decoder errors, failed playback, or apps hanging while probing media
- Version mismatches between the registry and updated plugin packages can cause repeated rescans at startup, leading to noticeably slower launch times in GStreamer-based apps
- Incorrect cached feature ranks may make GStreamer choose the wrong decoder or video sink, causing choppy playback, no audio, or unexpected fallback behavior
- If the cache records plugins from an older system state, cameras, microphones, or hardware-accelerated encoders may disappear from app device lists until the registry is rebuilt
- Corrupted registry files in ~/.cache/gstreamer-1.0 can trigger plugin loader warnings and pipeline creation failures, which users notice as media apps refusing to play or export
- Leftover entries from removed third-party plugins can produce noisy startup errors and capability probing failures, especially after distro upgrades or manual codec changes
What gets cleaned
Cache paths Kudu targets
Linux
~/.cache/gstreamer-1.0 |
Frequently asked
Common questions about GStreamer 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.