Linux Apps and Browsers
Linux apps are the software programs that run on a Linux operating system, and the everyday set covers roughly 6 core categories: web browsers, office suites, file managers, media players, code editors and terminal tools.
A Linux desktop install ships with a working browser, a file manager and a text editor from the first boot, and everything else is a package-manager install away. The stack underneath those apps is the Linux Kernel, the Linux Commands you type in a terminal, and the package repositories that deliver the builds. This page surveys the apps a typical user actually installs and the browsers worth putting on a Linux box.
The everyday apps a Linux desktop ships with
The apps that make a Linux desktop usable from minute 1 are the ones bundled in the base install. A standard Ubuntu 24.04 or Fedora 41 desktop includes a file manager (Nautilus or Files, respectively), a text editor (gedit or Text Editor), a terminal emulator, and the default web browser. The file manager handles the 2 main daily tasks: browsing directories and moving files between them. The terminal gives access to the package manager, where you install the rest of the software with a single command such as sudo apt install libreoffice on a Debian-based system or sudo dnf install libreoffice on Fedora.
Beyond the bundled set, 5 categories of apps round out a working Linux desktop:
- Office suite: LibreOffice 24.8 covers Writer, Calc, Impress and Base, and the file format is ODF, though it opens and saves .docx, .xlsx and .pptx without loss.
- Media player: VLC 3.0 plays virtually every video and audio container, including MKV, FLV and AVI, with no codec pack required.
- Image editor: GIMP 2.10 handles layer-based editing and batch processing; PhotoGIMP adds a Photoshop-style layout if the default GIMP UI feels dense.
- Code editor: VS Code 1.95 runs natively on Linux via the .deb or .rpm package, and the extension marketplace is identical to the Windows and macOS builds.
- Terminal and scripting: the shell (bash 5.2 on most current distros) plus tools like grep, awk and sed cover text processing, and a command reference for Find Files on Linux keeps the daily lookups short.
Browsers on Linux: what actually runs
The browsers you can install on Linux fall into 4 engine families, and the 3 that matter for daily use are Chromium-based, Gecko-based and WebKit-based. The table below lists the current mainstream options, their engine, and the minimum disk space a fresh install needs.
| Browser | Engine | Min disk (fresh install) | Package format |
|---|---|---|---|
| Firefox 139 | Gecko | 420 MB | .deb, .rpm, AppImage, Snap |
| Chromium 139 | Blink | 280 MB | .deb, .rpm, flatpak |
| Microsoft Edge 139 | Blink | 310 MB | .deb, .rpm, Snap |
| Brave 1.76 | Blink | 260 MB | .deb, .rpm, flatpak |
| LibreWolf 139 | Gecko | 440 MB | .deb, AppImage |
| Epiphany (GNOME Web) | WebKitGTK | 95 MB | .deb, .rpm (built into GNOME) |
Firefox is the default on most Linux desktop distros and the 1 browser that ships with the least tracking in its stock configuration. Chromium is the reference implementation for the Blink engine; if a site breaks in a Chromium-based browser, it will almost certainly break in Edge and Brave on the same engine. Edge adds a built-in PDF reader and a taskbar-style tab grouping that some users prefer. Brave layers an ad and tracker block on top of Blink, which saves roughly 30% of the network requests on a typical news page. LibreWolf is a Firefox fork that strips telemetry and forces a stricter privacy policy out of the box.
How to install a browser that is not in the base repo
To install a browser that the distro repository does not carry, the 2 paths that work on every major distribution are the native package and the flatpak. The native package gives the best integration with the desktop environment (correct icon, MIME type associations, and a unified update cycle), while flatpak gives a version that is independent of the distro release and typically 2 to 4 weeks newer than the repo build.
- Open a terminal and check whether the package exists: run
apt search firefoxordnf search firefoxto see what the repo offers. - If the repo version is current enough, install it directly:
sudo apt install firefox-esrorsudo dnf install firefox. - If you need a newer build, download the .deb or .rpm from the vendor site and install with
sudo apt install ./firefox-139.0.1-1.x86_64.deborsudo dnf install ./firefox-139.0.1-1.x86_64.rpm. - If you prefer a sandboxed build, install flatpak once with
sudo apt install flatpak, then add the Flathub repository withflatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo, and finally runflatpak install flathub org.mozilla.firefox.
The flatpak route keeps the browser out of the system directories, so a broken install is a single flatpak uninstall away from a clean state. The native package route updates through the same apt upgrade or dnf upgrade cycle as the rest of the system, which means 1 update pass covers the browser and every other installed app.
File managers and the terminal: the apps you open most
The file manager and the terminal are the 2 apps that get the most daily use on a Linux desktop, and choosing the right pair shapes how quickly routine tasks finish. Nautilus (GNOME), Dolphin (KDE) and Thunar (XFCE) are the 3 main file managers, and each is tuned to its desktop environment. Nautilus favours a clean, icon-based layout with a built-in trash and a shortcut bar; Dolphin adds a dual-panel view and built-in FTP and SFTP access; Thunar is the lightest at roughly 45 MB of RAM at idle and opens in under 0.5 seconds on a 256 GB SSD.
For the terminal, the default shell on Ubuntu, Debian, Fedora and RHEL is bash 5.2, and the terminal emulator (GNOME Terminal, Konsole or xfce4-terminal) is a thin layer on top. The commands that cover 80% of daily file work are ls, cd, cp, mv, rm, find, grep and chmod. A user who memorises those 8 commands and the 2 flags they take most often (recursive for find, case-insensitive for grep) handles the bulk of navigation and search without leaving the terminal.
Keeping the app stack current on a rolling-release schedule
Keeping the app stack current on Linux follows 2 different rhythms depending on the distro. A rolling-release distro such as Arch Linux or openSUSE Tumbleweed applies security and feature updates to the base system and every installed app in the same weekly or bi-weekly cycle, so 1 sudo pacman -Syu or sudo zypper dup pass updates the kernel, the desktop, Firefox and the file manager together. A fixed-release distro such as Ubuntu 24.04 LTS or Fedora 41 holds the base system to a 6-month (Fedora) or 5-year (Ubuntu LTS) cycle and delivers app updates through the repository, which means the browser and office suite get monthly security patches while the kernel and desktop environment stay on the release version.
For a server-side or sysadmin workflow, the practical split is to pin the distro to a fixed release for the 3 core services (web server, database, reverse proxy) and let the desktop app stack float on whatever the repo offers. That keeps the production kernel and the 2 userland packages it depends on stable while the browser, editor and media player on the same box track the latest builds without a separate maintenance window.