Enabling RPM Fusion on Fedora is what lets you play the H.264 and HEVC videos a stock install refuses, or plays with no picture. Fedora cannot ship those patent-encumbered codecs, so its ffmpeg-free build has them compiled out. By the end you’ll have the RPM Fusion free and nonfree repos, the full ffmpeg, the RPM Fusion multimedia group for GStreamer apps, and GPU video decoding on Intel, AMD or NVIDIA.
The same commands work on Fedora 45, 44 and 43. You will also see what changed on Fedora 45, where a plain rpm -Uvh of the release package now fails, and how to check, disable or fully remove RPM Fusion later. I went through every step again in November 2026 on fresh Fedora 45, 44 and 43 machines, and they still hold.
Run the whole setup in five commands
If you just want the RPM Fusion codecs working and you’re on Fedora Workstation, this is the short version. Each line is explained in its own section below, so come back to those when something prints an error or you want hardware decoding too:
sudo dnf upgrade --refresh
sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
sudo dnf install rpmfusion-free-appstream-data rpmfusion-nonfree-appstream-data
sudo dnf swap ffmpeg-free ffmpeg --allowerasing
sudo dnf install @multimedia --setopt=install_weak_deps=False --exclude=PackageKit-gstreamer-plugin
After the last command finishes, check these before you move on:
- You see four
rpmfusionentries when you rundnf repo list | grep rpmfusion(more if you also turned on Workstation’s third-party NVIDIA or Steam repos). - You get
libx264andlibx265back fromffmpeg -encoders. - You can open an HEVC file in GNOME Videos, VLC or mpv without a “missing codec” prompt.
On Server, Cloud or a minimal install the same five lines work too. With no ffmpeg-free to remove, the swap simply installs ffmpeg, which on a Fedora 45 test machine with no ffmpeg of either kind installed meant 73 packages and 52 MiB of downloads. The line people get wrong there is the last one, and the multimedia section explains why install and not update is the form to use.
Know what RPM Fusion free, nonfree and tainted hold
RPM Fusion is a community repository that packages software Fedora will not ship, either because of software patents or because the licence is not free. It’s split into repos by that reason, and you only enable what you need:
| Repo | What it holds | Examples you’ll use here | Needed for codecs? |
|---|---|---|---|
| rpmfusion-free | Open source software Fedora can’t ship (patents) | ffmpeg, x264-libs, x265-libs, gstreamer1-plugins-bad-freeworld, mesa-va-drivers-freeworld | Yes |
| rpmfusion-nonfree | Redistributable but not open source | intel-media-driver, akmod-nvidia, Steam | Intel and NVIDIA GPUs |
| rpmfusion-free-tainted | Legally unclear in some countries | libdvdcss for encrypted DVDs | Only for DVDs |
| rpmfusion-nonfree-tainted | Firmware without a clear redistribution licence | Assorted *-firmware packages | No |
The part that trips people up is the “Enable Third-Party Repositories” switch that Fedora Workstation offers on first boot and in GNOME Software. That switch controls the repos from the fedora-workstation-repositories package, and on the Fedora 45 test machine that package added only three repo definitions, all disabled until you flip it:
- You get
google-chrome, which carries only Google Chrome. - You get
rpmfusion-nonfree-nvidia-driver, which carries the NVIDIA driver packages such asakmod-nvidiaand nothing else. - You get
rpmfusion-nonfree-steam, which carries Steam.
None of those hold a codec. So if you flipped that switch and your video still won’t play, that’s normal: you still need the full repos from this guide.
Check what ships on Fedora 45, 44 and 43
Every URL and repo file keys off $(rpm -E %fedora) and $releasever, so the commands don’t change between releases. What does change is the version each release gets. These are the builds the repos served to the three test machines in November 2026, and every rpmfusion Fedora 45 build in the first column carries the .fc45 suffix:
| Package | Fedora 45 | Fedora 44 | Fedora 43 | Repo |
|---|---|---|---|---|
| rpmfusion-free-release | 45-2 | 44-3 | 43-1 | mirrors.rpmfusion.org |
| ffmpeg (full) | 9.0.2 | 8.1.3 | 7.1.5 | rpmfusion-free |
| gstreamer1-plugins-bad-freeworld | 1.28.8 | 1.28.8 | 1.26.11 | rpmfusion-free |
| x265-libs | 4.3 | 4.1 | 4.1 | rpmfusion-free |
| intel-media-driver | 26.3.5 | 26.1.5 | 26.1.5 | rpmfusion-nonfree |
| libva-intel-media-driver (Fedora’s build) | 26.3.5 | 26.3.5 | 26.2.4 | Fedora |
| mesa-va-drivers-freeworld | 26.2.6 | 26.2.6 | 25.3.6 | rpmfusion-free |
| akmod-nvidia | 620.70.06 | 620.70.06 | 580.178.04 | rpmfusion-nonfree |
| libva-nvidia-driver | 0.0.18 | 0.0.18 | 0.0.18 | Fedora |
| lame | 4.0 | 3.100 | 3.100 | Fedora |
| mozilla-openh264 | 2.6.0 | 2.6.0 | 2.6.0 | fedora-cisco-openh264 |
Two rows deserve a second look. LAME and the NVIDIA VA-API bridge come from Fedora’s own repos now, so you don’t need RPM Fusion for MP3 encoding at all. And on Fedora 44 and 43 the RPM Fusion Intel driver is older than Fedora’s own build, which changes the advice in the Intel section below. The ffmpeg row matters if you build scripts around ffmpeg options: Fedora 45 gets the 9.0 series, 44 gets 8.1 and 43 stays on 7.1, so a filter or flag added in a newer FFmpeg may not exist on an older Fedora even though the package name is the same.
Update Fedora before you add the repos
Start from a fully updated system. RPM Fusion builds against the current Fedora libraries, and a half-updated machine is the usual cause of “conflicting requests” errors during the ffmpeg swap later on:
sudo dnf upgrade --refresh
If a new kernel landed, reboot before you continue so the running kernel matches the installed one:
sudo systemctl reboot
You can skip the reboot if dnf didn’t touch the kernel, since nothing in the next steps needs it. If you’re not sure, compare uname -r with the newest entry from rpm -q kernel: when they match, you’re already running the latest kernel.
Enable RPM Fusion on Fedora 45, 44 and 43
RPM Fusion ships two small release packages that drop the repo definitions and signing keys onto your system. Install both straight from the mirror with dnf. The $(rpm -E %fedora) part expands to your release number, so this one line covers 43, 44 and 45:
sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
You’ll see both packages install from @commandline, followed by a warning that dnf skipped the OpenPGP check. That warning is expected, because the key that signs these two packages ships inside them, so there is nothing on your system to check against yet:

Don’t swap this for the older rpm -Uvh method you’ll still find in a lot of guides. On Fedora 45, rpm enforces package signatures by default, and it stops on the RPM Fusion release package with a NOKEY error (the exact output is in the troubleshooting section). Fedora 44 and 43 only print a warning for the same file, which is why the old method seems to work right up until you upgrade.
Now confirm the repos are registered. The release package version tells you which build you got, and on RPM Fusion Fedora 45 setups it should read 45-2, the current build:
dnf repo list | grep -i rpmfusion
rpm -q rpmfusion-free-release rpmfusion-nonfree-release
All three releases now enable the same four repos: rpmfusion-free, rpmfusion-free-updates, rpmfusion-nonfree and rpmfusion-nonfree-updates. The updates-testing repos are defined but disabled. If your list shows updates-testing entries instead, rpm -q will show you a release package older than 45-1, because the early 45-0.x builds of it enabled the testing repos:

That capture also shows where the repo files went. On Fedora 45 the RPM Fusion .repo files sit in /usr/share/dnf5/repos.d/ next to Fedora’s own, and /etc/yum.repos.d/ is empty. On Fedora 44 and 43 they’re still in /etc/yum.repos.d/. If you audit enabled repos by listing a directory, check the right one for your release, or just trust dnf repo list, which reads both.
Accept the RPM Fusion signing keys
GNOME Software and KDE Discover only list RPM Fusion apps such as Steam once the AppStream metadata is installed. It’s also the first package you pull from the new repos, so this is where dnf asks you to trust the RPM Fusion keys:
sudo dnf install rpmfusion-free-appstream-data rpmfusion-nonfree-appstream-data
Compare the fingerprints with the RPM Fusion keys page before you answer yes. These are the two keys the Fedora 45 machine imported:
Importing OpenPGP key 0xD651FF2E:
UserID : "RPM Fusion free repository for Fedora (2020) <[email protected]>"
Fingerprint: E9A491A3DE247814E7E067EAE06F8ECDD651FF2E
From : file:///usr/share/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-45
The key was successfully imported.
Importing OpenPGP key 0x94843C65:
UserID : "RPM Fusion nonfree repository for Fedora (2020) <[email protected]>"
Fingerprint: 79BDB88F9BBF73910FD4095B6A2AF96194843C65
From : file:///usr/share/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-45
The key was successfully imported.
The keys are the same 2020 keys on all three releases, so you compare against the same two fingerprints whichever one you run. Only the path differs: Fedora 45 reads them from /usr/share/pki/rpm-gpg/, while 44 and 43 use /etc/pki/rpm-gpg/. If a fingerprint doesn’t match the keys page, answer no and stop, because every package you’d install afterwards would be trusted on that key.
Swap ffmpeg-free for the full ffmpeg
This is the swap that actually fixes playback for most apps. Before it, ffmpeg -decoders on the Fedora 45 machine had AV1 and AAC but no native h264 or hevc line at all; the only H.264 entry was the Cisco libopenh264 wrapper. RPM Fusion’s ffmpeg is built with x264, x265 and the rest, and --allowerasing lets dnf remove the -free libraries in the same transaction:
sudo dnf swap ffmpeg-free ffmpeg --allowerasing
On Fedora 45 dnf removes eight -free packages and installs eight in their place, a 16 MiB download that grows the install by 30 MiB. Watch the Repository column: ffmpeg, ffmpeg-libs, x264-libs, x265-libs and vvenc-libs come from rpmfusion-free, and that’s where the patented encoders live:

Next, confirm the encoders and decoders are there. You’re looking for libx264 and libx265 on the encoder side and plain h264 and hevc on the decoder side:
ffmpeg -hide_banner -encoders 2>/dev/null | grep -E 'libx264|libx265|aac'
ffmpeg -hide_banner -decoders 2>/dev/null | grep -E ' (h264|hevc) '
Both now show up. The VFS..D flags on the decoders mean frame and slice threading, so they can spread work across cores when there’s no GPU help:

If the ffmpeg command line tool is all you’re after, the FFmpeg install guide for Fedora goes further into build options and everyday usage.
Install the RPM Fusion multimedia group
The ffmpeg swap covers apps that link libavcodec directly, like mpv, VLC and OBS. GStreamer apps (GNOME Videos, Rhythmbox, the GNOME thumbnailer) need the freeworld GStreamer plugins, and those come from Fedora’s hidden multimedia group once RPM Fusion is enabled. Use install, which is also what the rpmfusion multimedia howto shows:
sudo dnf install @multimedia --setopt=install_weak_deps=False --exclude=PackageKit-gstreamer-plugin
Skip this distinction and you can lose ten minutes on it. The older form, sudo dnf update @multimedia, only works when the group is already installed. Workstation and KDE Plasma include it, so it works there, but on Server, Cloud or a minimal install dnf5 refuses with “No match for argument: multimedia”. The capture shows both on the same Fedora 45 machine:

Sixteen packages came in, eight of them from RPM Fusion. The two flags kept the transaction small and stopped PackageKit’s codec installer from coming back. Once it finishes, you can tick these off:
- You have
gstreamer1-plugins-bad-freeworldandgstreamer1-plugins-ugly, so GStreamer apps can play H.264, HEVC and MP3. - You have
libde265, an HEVC decoder GStreamer can use. - You have
libheif-freeworld, the HEIC build that iPhone photos need in apps that use libheif. - You have
pipewire-codec-aptx, so your aptX Bluetooth headphones can use aptX.
If any of those are missing from your own transaction, they were already installed, and dnf lists them as “already installed” at the top of its output.
You may have seen dnf group install sound-and-video in older guides. On all three releases that group has optional packages only, no mandatory or default ones, so installing it adds nothing useful. Install the apps you want by name instead. LAME for MP3 encoding is a normal Fedora package now:
sudo dnf install lame
On Fedora 45 that pulls LAME 4.0 from the main fedora repo, while 44 and 43 still get 3.100.
Add OpenH264 for Firefox and WebRTC
Firefox plays normal web video through the system ffmpeg libraries, so the swap above already covers YouTube and most streaming sites. WebRTC calls are the exception: Firefox handles H.264 there through Cisco’s OpenH264 plugin, which comes from Fedora’s fedora-cisco-openh264 repo because Cisco pays the H.264 royalty per download. Install the codec, the GStreamer plugin and the Mozilla plugin:
sudo dnf install openh264 gstreamer1-plugin-openh264 mozilla-openh264
The Cisco repo is enabled by default on 43, 44 and 45, so on most machines the first two are already installed and dnf only adds mozilla-openh264 and its mozilla-filesystem dependency:
Package "openh264-2.6.0-3.fc45.x86_64" is already installed.
Package "gstreamer1-plugin-openh264-1.28.9-1.fc45.x86_64" is already installed.
Package Arch Version Repository Size
Installing:
mozilla-openh264 x86_64 0:2.6.0-3.fc45 fedora-cisco-openh264 1.1 MiB
Installing dependencies:
mozilla-filesystem x86_64 0:1.9-39.fc45 fedora 0.0 B
If dnf says it can’t find mozilla-openh264, someone disabled the Cisco repo. Turn it back on with the dnf5 config-manager syntax, which writes an override to /etc/dnf/repos.override.d/99-config_manager.repo rather than editing the repo file. The dnf5-plugins package provides config-manager; it was already present on every test machine, and installing it again is harmless:
sudo dnf install dnf5-plugins
sudo dnf config-manager setopt fedora-cisco-openh264.enabled=1
Run the Mozilla plugin install again after that and it should resolve. Because the override lives in /etc/dnf/repos.override.d/ and not in the repo file itself, you can see exactly what was changed with cat, and deleting that file puts every repo back to its packaged default.
Turn on hardware video decoding (VA-API)
Software decoding works after the multimedia group, but a 4K HEVC file will still pin a laptop CPU and drain the battery. VA-API hands decoding to the GPU, and the driver package depends on your vendor. Install libva-utils first so you have vainfo to check the result:
sudo dnf install libva-utils
Then follow only the subsection for the GPU in your machine. Installing a driver for a GPU you don’t have won’t break anything, but you’d carry those packages through every upgrade for no benefit. On a laptop with Intel graphics plus an NVIDIA card, you do both the Intel and NVIDIA parts.
Intel (Broadwell and newer)
Fedora ships its own libva-intel-media-driver, and the multimedia group installs it for you. RPM Fusion nonfree carries intel-media-driver, which is the build RPM Fusion’s howto points Intel users to. Run the swap after the multimedia group, because the group installs Fedora’s build itself (it did on all three test machines), and swapping first leaves nothing for it to replace:
sudo dnf swap libva-intel-media-driver intel-media-driver --allowerasing
On Fedora 45 both builds are 26.3.5, so the swap is a straight trade. On Fedora 44 and 43 it isn’t: the RPM Fusion build was 26.1.5 while Fedora’s was 26.3.5 on 44 and 26.2.4 on 43, so the swap installs an older driver. The RPM Fusion package also declares that it provides libva-intel-media-driver, and dnf check-upgrade stayed quiet afterwards on every machine, so later upgrades did not flip it back:

On 44 or 43 I’d keep Fedora’s build first and run the vainfo check below. If it already lists the H.264 and HEVC profiles you need, you’re done; swap only if a profile is missing. Going the other way is just as easy if the swap disappoints you, because the same dnf swap with the two names reversed puts Fedora’s build back, which is exactly what the removal section later does. For pre-Broadwell chips, install libva-intel-driver from rpmfusion-free instead.
AMD Radeon
Fedora’s Mesa has the H.264 and HEVC VA-API entry points disabled, and the freeworld build restores them. On the Fedora 44 and 45 machines mesa-va-drivers was not installed at all, only mesa-dri-drivers, while Fedora 43 still had mesa-va-drivers as its own package. Either way, mesa-va-drivers-freeworld installs alongside with no swap:
sudo dnf install mesa-va-drivers-freeworld
RPM Fusion also recommends the freeworld Vulkan driver for Vulkan Video decoding, which recent mpv builds and some browsers use. On Fedora 45 this swap replaced a 174 MiB package with a 174 MiB package, so it costs you nothing in disk space:
sudo dnf swap mesa-vulkan-drivers mesa-vulkan-drivers-freeworld
If you run Steam or other 32-bit apps, repeat both commands with the .i686 suffix on the package names, which is what RPM Fusion’s howto shows for that case. You can skip them on a machine with no 32-bit libraries at all, and rpm -qa '*.i686' tells you which kind of machine you have: an empty result means there’s nothing 32-bit to match.
NVIDIA
The proprietary NVIDIA driver has no native VA-API support. libva-nvidia-driver bridges VA-API to NVDEC, and it’s in Fedora’s own repos on all three releases. It only works with the proprietary akmod-nvidia driver from RPM Fusion nonfree loaded, not with nouveau, so set that up first with the NVIDIA driver guide for Fedora:
sudo dnf install libva-nvidia-driver
The repos offered akmod-nvidia 620.70.06 on Fedora 45 and 44, and the 580 series on 43, so check that your card is still supported by the branch your release gets.
Check the driver with vainfo
Run vainfo on the real machine as a user who can open /dev/dri/renderD128, which your desktop login can:
vainfo | grep -E 'Driver version|VAProfileH264|VAProfileHEVC'
A working setup names the driver (iHD for Intel, Mesa Gallium for AMD, NVDEC for NVIDIA) and lists VAProfileH264 and VAProfileHEVC entries. My test machines were cloud VMs with no GPU, so they could only prove that every package installs and resolves cleanly. There, vainfo printed “failed to initialize display” because there’s no /dev/dri device, which is also exactly what you’ll see on real hardware when the kernel driver didn’t load.
Add DVD playback and extra firmware
Encrypted DVDs need libdvdcss, which lives in RPM Fusion’s separate tainted repo because its legal status varies by country. Enable the tainted release packages and install it:
sudo dnf install rpmfusion-free-release-tainted rpmfusion-nonfree-release-tainted
sudo dnf install libdvdcss
The nonfree tainted repo also carries firmware without a clear redistribution licence. Only pull it if a device on your machine actually needs it, because it installs every matching firmware package at once:
sudo dnf --repo=rpmfusion-nonfree-tainted install "*-firmware"
You can stop here if you don’t own a DVD drive, because nothing else in this guide depends on the tainted repos. If you add them anyway, they’re two more repo definitions that dnf refreshes with the rest, and you can switch them off later with the same config-manager setopt command shown in the next section.
Test the Fedora video codecs with a sample clip
You don’t need to download a test video, and the Big Buck Bunny link most codec guides use now returns a 404 page anyway. Generate your own H.264 clip, transcode it to HEVC, then read it back. This runs both encoders and both decoders you just installed:
ffmpeg -y -hide_banner -v error -f lavfi -i testsrc2=size=1280x720:rate=30 -f lavfi -i sine=frequency=440 -t 10 -c:v libx264 -pix_fmt yuv420p -c:a aac sample.mp4
ffmpeg -y -hide_banner -v error -i sample.mp4 -c:v libx265 -preset ultrafast -c:a copy sample-hevc.mkv
ffprobe -hide_banner sample-hevc.mkv 2>&1 | grep Stream
Then push the HEVC file through GStreamer, which is what GNOME Videos uses. A missing decoder makes it print an error and exit non-zero:
gst-launch-1.0 -q filesrc location=sample-hevc.mkv ! decodebin ! fakesink; echo "exit: $?"
ffprobe reports an HEVC video stream and an AAC audio stream, the 10 second clip shrinks from 3.9 MB to 2.2 MB as HEVC, and GStreamer exits with 0:

After that, ffplay sample.mp4, mpv or VLC on Fedora play both files without prompts. Kodi picks up the same libraries, so the Kodi media center setup works straight after this guide.
Check, disable or remove RPM Fusion
To see whether RPM Fusion is already enabled on a machine you didn’t set up yourself, ask rpm for the release packages and count the enabled repos. On the finished Fedora 45 machine that printed both release packages at 45-2 and six enabled repos (four main ones plus the two tainted ones; Workstation’s third-party NVIDIA and Steam repos add to that count when enabled):
rpm -q rpmfusion-free-release rpmfusion-nonfree-release
dnf repo list --enabled | grep -c rpmfusion
Want to switch off just the nonfree side, for example on a machine that should only carry open source code? Disable those repos without uninstalling anything. dnf5 records the change in /etc/dnf/repos.override.d/99-config_manager.repo, and setting the values back to 1 re-enables them:
sudo dnf config-manager setopt rpmfusion-nonfree.enabled=0 rpmfusion-nonfree-updates.enabled=0
Removing RPM Fusion completely takes more than uninstalling the release packages, and that’s the step people get wrong. Start by removing the two main release packages. If you installed the tainted ones, dnf removes them too as dependent packages, so you don’t need to name them:
sudo dnf remove rpmfusion-free-release rpmfusion-nonfree-release
On the Fedora 44 machine that removed four release packages, yet ffmpeg, x264-libs and the other codec packages stayed installed: 22 entries still carried the RPM Fusion packager tag, the two signing keys among them. Those packages would never get another update. One rpmfusion repo also survived, rpmfusion-nonfree-nvidia-driver, because it belongs to Fedora’s fedora-workstation-repositories package and I had switched it on earlier. You’ll see the same on Workstation if you enabled third-party repositories, and sudo dnf config-manager setopt rpmfusion-nonfree-nvidia-driver.enabled=0 turns it off if you don’t use the NVIDIA driver:

To finish the job, swap each RPM Fusion package that replaced a Fedora one back to the Fedora build first, so nothing your desktop depends on disappears. Skip any line for a package you never installed:
sudo dnf swap ffmpeg ffmpeg-free --allowerasing
sudo dnf swap intel-media-driver libva-intel-media-driver --allowerasing
sudo dnf swap mesa-vulkan-drivers-freeworld mesa-vulkan-drivers --allowerasing
Then remove everything still packaged by RPM Fusion. If you run the NVIDIA driver or Steam from Workstation’s third-party repos, those packages match this filter too, so delete their names (akmod-nvidia, the xorg-x11-drv-nvidia packages, steam) from the list before you remove, or you’ll lose the driver your desktop runs on. The awk filter keeps the signing keys out of the list, so run the first command on its own and read what it prints before you remove anything:
rpm -qa --qf '%{name} %{packager}\n' | awk '/RPM Fusion/ && $1 != "gpg-pubkey" {print $1}'
sudo dnf remove $(rpm -qa --qf '%{name} %{packager}\n' | awk '/RPM Fusion/ && $1 != "gpg-pubkey" {print $1}')
I ran this cleanup on the Fedora 43 machine, and it removed 16 packages plus the now unused OpenCL-ICD-Loader. When you’re done, check that you end up where the test machine did:
- You still have Fedora’s own
gstreamer1-plugins-bad-freeandgstreamer1-plugins-ugly-free. - You still have
libva-intel-media-driverandmesa-vulkan-driversfrom Fedora. - You see only the two
gpg-pubkeyentries when you runrpm -qa --qf '%{name} %{packager}\n' | grep "RPM Fusion".
Those two keys only verify packages that RPM Fusion signed, and with no RPM Fusion repo left nothing will ask for them.
Troubleshooting the errors I actually hit
These are the errors I hit across this round of testing and the earlier one on Fedora 45, with the fix that cleared each one.
Error: “No match for argument: multimedia”
You ran dnf update @multimedia (or dnf upgrade @multimedia) on a system where the group was never installed, which is every Server, Cloud and minimal install. dnf5 only upgrades groups that are already installed. Run sudo dnf install @multimedia with the same flags instead. The group is hidden, so dnf group list does not show it, but dnf group list --hidden does.
Error: “package rpmfusion-free-release-45-2.noarch does not verify: … NOKEY”
This is Fedora 45’s rpm refusing a package whose signing key isn’t in the keyring yet. You will only see it when you install the downloaded release package with rpm directly. This dry run with --test on Fedora 45 shows the whole message:

Fedora 44 and 43 ran the same command with only the NOKEY warning and exit code 0, because Fedora 44 and 43 do not enforce package signatures by default. The clean fix on every release is sudo dnf install ./rpmfusion-free-release-*.noarch.rpm or the URL form from the enable step. dnf accepts the local package and imports the key on the first repo transaction. rpm -Uvh --nosignature also gets past it, but it skips the very check you want.
Error: “moov atom not found” / “Invalid data found when processing input”
The file isn’t a video. In my case curl -L -o sample.mp4 had saved a 146 byte 404 page from the dead Blender mirror. Check with ls -la and file sample.mp4 before blaming the codecs, or generate a local clip as shown in the test section.
Do I still need libavcodec-freeworld?
No, not after the ffmpeg swap. libavcodec-freeworld exists only to add the missing codecs on top of ffmpeg-free, and the multimedia group lists it as a conditional package that installs only when libavcodec-free is present. Once the swap removes that library, it stays out of the way, which is why it never showed up in any of the three test transactions.
Browser video still stutters or uses the CPU
Codecs and hardware decoding are separate problems. If playback works but CPU usage is high, run the vainfo check first. No profiles listed means the VA-API driver is wrong or missing for your GPU; profiles listed but high CPU means the browser isn’t using VA-API, which is a browser setting and not a codec issue. Test with mpv first, because it tells you plainly which decoder it picked when you run it with --hwdec=vaapi, and that separates a driver problem from a browser one in a few seconds.
With codecs sorted, the rest of a new desktop setup is in things to do after installing Fedora 45 Workstation, and apps that aren’t packaged as RPMs come from Flathub on Fedora. Flatpak apps bundle their own codec runtimes, so nothing in this guide affects them. If you’re still on an older release, install Fedora 45 fresh or read what changed in Fedora 45 first, and keep the dnf5 cheat sheet open for the swap, group and config-manager syntax used throughout.
I appreciate the guide. It helped me where Claude and Gemini couldn’t.
Glad it helped. RPM Fusion plus the codec swap is the one step a fresh Fedora install always needs and never ships with by default.
Fedora is really hypocritical on this. They defend not shipping patented codecs because of their US jurisdiction and “copyright” yet they happily accept copyright violating GenAI slop code into the project.