When people move to Linux, one of the first questions they ask is: “Where do I download software?” On Windows, the answer is often a website or the Microsoft Store. On Linux, there are several ways to install applications, and two common options on Fedora are DNF and Flatpak apps from Flathub.

These options are not simply two storefronts competing to do the same thing. They represent different approaches to software distribution. Understanding the difference helps you choose the right source, diagnose dependency issues, and avoid the mistaken idea that every Linux app must be installed in exactly the same way.

DNF: your distribution’s package manager

DNF is Fedora’s package manager for installing, updating, and removing system packages. It obtains packages from configured software repositories, checks their dependencies, and performs the required changes as a transaction. Fedora’s current releases use DNF5 by default, though some older documentation and systems may still refer to the earlier DNF implementation. Fedora’s DNF documentation describes the everyday workflow.

A typical command-line workflow looks like this:

# Search package metadata sudo dnf search package-name # Install a package sudo dnf install package-name # Update installed packages sudo dnf upgrade # Remove a package sudo dnf remove package-name 

DNF is not just a downloader. It resolves dependencies and considers the packages already installed on the system. If an application needs libraries or helper tools, DNF can install those from the repositories as part of the same transaction. That integration is useful for command-line tools, system components, development libraries, and software that should closely match the distribution’s supported environment.

The tradeoff is that a package is built and maintained for a particular distribution and release. A package available on one Fedora release may not exist in the same form on another distribution. The installed application also generally relies on libraries supplied by the host system. This is a feature when the package is intended to integrate with the OS; it can be an inconvenience when an application needs a newer library than the one in an older distribution.

DNF commands normally use administrator privileges for system-wide changes. Review the proposed transaction before confirming it, especially when removing packages or accepting a large set of changes. DNF makes dependency handling easier, but it does not make every system modification risk-free.

Flatpak and Flathub: application packaging across distributions

Flatpak is an application distribution and sandboxing technology. Flathub is a popular repository, or remote, from which users can install Flatpak applications. An application is identified by an application ID such as org.gimp.GIMP, rather than only by a package name that varies by distribution.

Many Flatpak apps use shared runtimes. A runtime supplies common libraries and platform components, while the application package supplies the app itself. Multiple apps can share a runtime, and different runtimes can coexist. This helps an app use a consistent set of libraries across distributions, although it can mean additional downloads and disk use compared with an app that uses libraries already present on the host.

On Fedora Workstation, Flatpak support is generally installed by default, and Flathub may already be enabled through Fedora’s third-party repository setup. If it is not enabled, Flathub provides Fedora setup instructions. The manual command is:

flatpak remote-add --if-not-exists flathub \ https://dl.flathub.org/repo/flathub.flatpakrepo 

Then search and install by application ID:

flatpak search gimp flatpak install flathub org.gimp.GIMP flatpak run org.gimp.GIMP flatpak update 

You can also use GNOME Software or KDE Discover, which can present Flatpak apps alongside other software sources. When the same app appears from multiple sources, check which source you are installing from.

What does the sandbox actually mean?

Flatpak applications run with restricted access to parts of the host system. An app may receive access to particular files, devices, or services that it needs. The exact permissions depend on the application’s packaging and configuration. Sandboxing can reduce unnecessary access, but it is not a guarantee that every Flatpak is perfectly isolated or that an app cannot access anything sensitive.

For example, a video editor may need access to folders containing media. A game launcher may need access to a library directory. Depending on how those permissions are configured, the app might not see a folder you can access in your regular desktop session. This can look like a broken installation when it is actually a permission boundary.

Inspect permissions with tools such as Flatseal, or from the command line with flatpak info --show-permissions APP_ID. Change permissions only when you understand why the application needs access. Granting broad access to the entire home directory can solve a short-term inconvenience while weakening the purpose of the sandbox.

Which option should I choose?

Use DNF when you are installing system tools, development packages, command-line utilities, drivers or components that need tight integration with Fedora. It is also the natural choice when Fedora’s repositories are the intended source and you want the distribution to manage updates with the rest of the OS.

Use Flatpak when the software is distributed on Flathub, you want a broadly compatible desktop application, or you need an application that can use a different runtime from the host. Flatpak is especially common for desktop apps such as media tools, chat clients, and creative software.

There is no universal rule that one format is safer or better. The package source and maintainer matter. Prefer official distribution repositories or the application publisher’s verified source. On Flathub, check the publisher information and app details. A package manager can deliver an outdated or poorly maintained app; a sandboxed app can still request powerful permissions.

Can both be installed at once?

Yes. A system can have both DNF packages and Flatpak apps. In some cases you may even find the same application in both places. That can be useful, but it can also be confusing: each copy may store settings differently, use a different version, and have separate update channels.

If you encounter duplicated launchers, check the app’s source in your software center or list installed apps using dnf list installed and flatpak list. If you choose to switch formats, remove the copy you no longer want and check whether you need to preserve or migrate its settings and data first.

The simplest mental model is this: DNF manages software packages as part of Fedora’s system environment; Flatpak distributes desktop apps with runtimes and permission boundaries that work across distributions; and Flathub is one important source of Flatpak applications. Once you know which layer you are using, choosing and troubleshooting Linux software becomes much less mysterious.

References