Microsoft Edge is a Chromium-based web browser known for its speed, security, and cross-platform synchronization capabilities. The browser offers multiple release channels that let you choose between production stability and early access to experimental features, making it valuable for web developers testing cross-browser compatibility, enterprise users requiring Microsoft 365 integration, and privacy-focused users exploring tracking prevention options.
On Fedora, Microsoft Edge can be installed using two main methods. First, the Microsoft RPM repository provides access to the latest stable, beta, and developer builds with updates delivered directly from Microsoft. Alternatively, Flatpak from Flathub isolates Edge in a containerized sandbox with restricted filesystem access and controlled system permissions, reducing potential security exposure from browser vulnerabilities while maintaining full functionality. This guide walks you through both installation methods with practical examples, helping you choose the approach that fits your workflow and security requirements. For alternative browsers, see our guides on installing Chromium, Vivaldi, or Firefox Nightly on Fedora.
Choose Your Microsoft Edge Installation Method
Both installation methods deliver fully functional Microsoft Edge browsers, but they differ in package management, update delivery, and system integration. Understanding these trade-offs helps you select the method that aligns with your priorities.
| Method | Channel | Release Channels | Updates | Best For |
|---|---|---|---|---|
| Microsoft RPM Repository | Microsoft Repos | Stable, Beta, Dev | Automatic via dnf upgrade | Users who want native DNF integration, all three release channels, and traditional system package management |
| Flatpak from Flathub | Flathub | Stable, Dev only | Automatic via flatpak update | Users prioritizing application sandboxing, system isolation, and simplified permission management |
The RPM repository method integrates Microsoft Edge directly into your system package management, making it behave like any other Fedora package with standard update workflows. Flatpak isolates Edge in a sandbox with controlled filesystem and system access, reducing potential security exposure but adding a layer between the browser and your system. For most users, the RPM method offers the most straightforward experience with access to all three release channels, while Flatpak appeals to those who value application isolation and don’t need the beta channel.
Method 1: Install Microsoft Edge via Microsoft RPM
Microsoft removed official RPM installation instructions from their website but continues to provide and update all three release channels (stable, beta, and dev) in RPM format through their package repository. The method below remains fully supported and delivers the latest Microsoft Edge builds directly from Microsoft’s servers.
Update the Fedora Packages Before the Microsoft Edge Installation
Before jumping in, ensuring your system is up-to-date is good practice. This step avoids potential conflicts and ensures a smooth installation process. To begin, open your terminal and execute the following command:
sudo dnf upgrade --refreshImport Microsoft GPG Key
Before installing Microsoft Edge, you need to import the GPG key that verifies the authenticity and integrity of the RPM packages. This key ensures the packages are genuine and haven’t been tampered with:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.ascThe command completes silently when successful, with no output indicating the key import succeeded.
Add Microsoft Edge Repository
With the GPG key imported, you can now add the Microsoft RPM repository to your system:
sudo dnf config-manager addrepo --from-repofile=https://packages.microsoft.com/yumrepos/edge/config.repoOnce executed, the repository addition completes with a brief progress indicator showing the download:
https://packages.microsoft.com/yumrepo 100% | 945.0 B/s | 192.0 B | 00m00s
Install Microsoft Edge from the RPM Repository
Microsoft Edge offers three release channels, each serving different needs. First, the stable version provides a well-tested and reliable browsing experience with features that have passed thorough quality assurance. Next, the beta version lets you preview upcoming features before they reach stable, though you may encounter occasional bugs. Finally, the developer version delivers the newest features and changes as soon as they are ready, accepting higher instability in exchange for early access.
Option 1: Install Microsoft Edge Stable Build (Recommended)
For most users, the stable version offers the best balance of features, performance, and reliability. To install it, use this command:
sudo dnf install microsoft-edge-stableOnce installation completes, verify the version and build:
microsoft-edge --versionExpected output showing the installed version:
Microsoft Edge 131.0.2903.86
Option 2: Install Microsoft Edge Beta or Dev Builds
If you want to preview upcoming features or test web applications against pre-release versions, you can install the beta or developer channels instead. However, these versions receive less testing and may contain bugs that affect stability, making them unsuitable for critical daily browsing tasks.
Microsoft Edge Beta:
sudo dnf install microsoft-edge-betaMicrosoft Edge Dev:
sudo dnf install microsoft-edge-devNotably, these versions install as separate applications alongside any existing Microsoft Edge installation, allowing you to run stable, beta, and dev builds simultaneously without conflicts.
Verify the installed versions with these commands:
microsoft-edge-beta --versionMicrosoft Edge 132.0.2957.18 beta
microsoft-edge-dev --versionMicrosoft Edge 133.0.3014.0 dev
Method 2: Install Microsoft Edge via Flatpak from Flathub
Flatpak offers an alternative installation method that isolates Microsoft Edge in a sandboxed environment with controlled access to your system resources. As a result, this approach enhances security by limiting what the browser can access and modify, while Flathub serves as the centralized repository hosting the Edge packages. Additionally, Flatpak installations include all necessary dependencies bundled with the application, reducing conflicts with system libraries and simplifying cross-distribution compatibility.
Enable the Flathub Repository
Before installing Microsoft Edge through Flatpak, first ensure your system has access to the Flathub repository, which hosts thousands of applications including Microsoft Edge. To do this, run this command to add Flathub as a Flatpak remote:
sudo flatpak remote-add --system --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepoThe --if-not-exists flag prevents errors if Flathub is already configured on your system, making this command safe to run multiple times. This step establishes the connection between your Flatpak installation and Flathub’s application repository, enabling you to install and update Microsoft Edge through Flatpak’s package management system.
Install Microsoft Edge with Flatpak
With Flathub configured, you can now install Microsoft Edge through Flatpak. However, note that Flathub only provides stable and developer versions of Microsoft Edge, not the beta channel. Despite this limitation, both versions install as separate applications, allowing you to run them simultaneously if needed.
To install the stable version of Microsoft Edge:
sudo flatpak install --system flathub com.microsoft.Edge -yFor the developer version with the latest experimental features:
sudo flatpak install --system flathub com.microsoft.EdgeDev -yIf you encounter an error stating “Unable to load summary from remote flathub: Can’t fetch summary from disabled remote ‘flathub’,” then the Flathub repository is disabled on your system. To resolve this, enable it with this command:
sudo flatpak remote-modify --system --enable flathubAfter enabling Flathub, retry the installation command above for your desired Microsoft Edge version.
Launch Microsoft Edge Browser
Launch Microsoft Edge from the Command Line
Terminal commands provide direct control over application launching and can be useful for scripting, automation, or when you prefer keyboard-driven workflows. However, the launch command depends on which installation method you used.
Launch RPM-Installed Microsoft Edge
To launch the stable version of Microsoft Edge from your terminal, simply execute this command:
microsoft-edgeIf you installed the beta or developer versions, use their respective commands:
microsoft-edge-betamicrosoft-edge-devLaunch Flatpak-Installed Microsoft Edge
For Flatpak installations, use the flatpak run command with the application ID to launch Microsoft Edge:
flatpak run com.microsoft.Edgeflatpak run com.microsoft.EdgeDevLaunch Microsoft Edge from the Desktop
Most users prefer launching applications through the graphical interface. Fedora’s GNOME desktop environment provides an application menu where Microsoft Edge appears alongside your other installed software.
To launch Microsoft Edge from the desktop:
- Click on Activities in the top left corner of your desktop.
- Click on Show Applications, represented by a grid of dots at the bottom of the sidebar.
- Locate the Microsoft Edge icon, or type “Microsoft Edge” in the search bar for quick access.
- Click the Microsoft Edge icon to launch the browser. If you installed multiple versions (stable, beta, or dev), each appears as a separate icon with its channel label.
Configure Microsoft Edge on First Launch
When you launch Microsoft Edge for the first time, an introductory setup wizard walks you through basic configuration options. Fortunately, this process takes only a few minutes and helps customize the browser to match your preferences and workflow requirements.
Navigate the Welcome Screen
The welcome screen introduces key Microsoft Edge features and guides you through initial configuration choices, including privacy settings, new tab page layout, and bookmark importing from other browsers.
Available options typically include privacy settings customization, new tab page layout selection, and bookmark importing from other browsers installed on your system.
Sign In and Sync Settings (Optional)
Microsoft Edge offers synchronization across devices when you sign in with a Microsoft account, keeping your browsing history, bookmarks, passwords, extensions, and settings consistent across all your computers and mobile devices. As a result, this proves valuable when you work on multiple machines and want seamless access to your browser data.
During setup, Edge displays layout options for your new tab page:
The wizard prompts you to sign in with your Microsoft account to enable synchronization. If you lack an account, you can create one during this step, or alternatively skip sign-in entirely to use Edge without sync functionality.
To skip sign-in and use Microsoft Edge without synchronization, simply click the X button in the upper right corner of the sign-in dialog. As a result, this keeps your browsing data local to your Fedora system only.
Complete Initial Configuration
After navigating the welcome screens and choosing your synchronization preferences, Microsoft Edge completes its initial setup and displays the main browser window. The browser is now ready for daily use with your selected configuration.
With setup complete, Microsoft Edge opens to your chosen start page and is ready for browsing, web development, or testing web applications on Fedora.
Update and Remove Microsoft Edge
Update Microsoft Edge
Microsoft Edge receives regular updates that deliver security patches, performance improvements, and new features. However, the update method depends on your installation approach.
For RPM installations:
sudo dnf upgrade microsoft-edge-stableReplace microsoft-edge-stable with microsoft-edge-beta or microsoft-edge-dev for those channels.
For Flatpak installations:
sudo flatpak update --system com.microsoft.EdgeOr update all installed Flatpak applications at once:
sudo flatpak update --systemRemove RPM-Installed Microsoft Edge
If you installed Microsoft Edge through the DNF package manager, simply use DNF to remove it cleanly from your system:
Remove stable version:
sudo dnf remove microsoft-edge-stableRemove beta version:
sudo dnf remove microsoft-edge-betaRemove developer version:
sudo dnf remove microsoft-edge-devIf you plan to permanently remove Microsoft Edge and do not intend to reinstall it later, you should also remove the Microsoft Edge repository to keep your system clean. To begin, verify the repository name:
dnf repolist | grep edgeedge-yum edge-yum
Next, disable the repository using the confirmed repository ID:
sudo dnf config-manager setopt edge-yum.enabled=0After disabling the repository, remove the repository configuration file:
sudo rm /etc/yum.repos.d/config.repoFinally, verify the repository removal by checking that edge-yum no longer appears in the repository list:
dnf repolist --all | grep edgeedge-yum edge-yum disabled
Remove Flatpak-Installed Microsoft Edge
For Flatpak installations, use the flatpak uninstall command to remove Microsoft Edge cleanly from your system:
Remove stable version:
sudo flatpak uninstall --system com.microsoft.EdgeRemove developer version:
sudo flatpak uninstall --system com.microsoft.EdgeDevNotably, Flatpak automatically removes unused dependencies and runtime libraries when you uninstall applications, keeping your system clean without manual intervention.
Troubleshoot Common Issues
Repository GPG Key Verification Failures
If DNF reports GPG signature verification errors when installing Microsoft Edge, you may see an error like this:
Error: GPG check FAILED Public key for microsoft-edge-stable-131.0.2903.86-1.x86_64.rpm is not installed
This error indicates the GPG key import failed or became corrupted. To resolve this, re-import the Microsoft signing key:
sudo rpm --import https://packages.microsoft.com/keys/microsoft.ascThe command completes silently when successful. Retry the installation command, which should now proceed without GPG errors.
Microsoft Edge Does Not Launch
If Microsoft Edge fails to start after installation, first launch from the terminal to see diagnostic messages:
microsoft-edge 2>&1 | head -20Common causes include missing dependencies, conflicting libraries, or graphics driver issues. For RPM installations, verify the package installed correctly:
rpm -V microsoft-edge-stableIdeally, the command produces no output if all files verify correctly. However, any output indicates modified or missing files that may need reinstallation.
For Flatpak installations, check application permissions and access rights:
flatpak info com.microsoft.EdgeFlatpak Sandbox Limitations
Flatpak sandboxing may restrict Microsoft Edge’s access to certain directories or system resources. For example, if Edge cannot save downloads to a specific folder outside the default Downloads directory, or if file picker dialogs cannot browse certain locations, then you may need to grant additional filesystem permissions.
Check current permissions to understand existing restrictions:
flatpak info --show-permissions com.microsoft.Edge | grep filesystemGrant additional filesystem access if needed:
sudo flatpak override --system com.microsoft.Edge --filesystem=homeThis command grants Microsoft Edge access to your entire home directory, which may be necessary for downloading files or accessing documents outside the default sandbox restrictions. After applying permission changes, restart Edge for them to take effect.
Conclusion
Installing Microsoft Edge on Fedora through the RPM repository or Flatpak delivers a Chromium-based browser with Microsoft service integration and cross-platform sync capabilities. Specifically, the RPM method provides native system integration with access to stable, beta, and dev channels through DNF, while Flatpak offers application sandboxing with stable and dev builds. Regardless of which method you choose, both approaches keep Edge updated automatically, ensuring you receive security patches and new features as Microsoft releases them. With Edge installed, consider importing bookmarks from your previous browser, configuring tracking prevention settings in edge://settings/privacy, or testing web applications across different release channels to catch compatibility issues early.
On Fedora 41, with dnf5, the commands have changed a bit:
“`
sudo rpm –import https://packages.microsoft.com/keys/microsoft.asc
sudo dnf config-manager addrepo –from-repofile=https://packages.microsoft.com/yumrepos/edge/config.repo
sudo dnf install microsoft-edge-stable
“`
Thanks Steve, I need to update most of my Fedora guides with DNF 5 now released. Cheers for the message.