Fortnite Is Coming to Linux. But What Will Linux Have to Give Up?

Epic Games is finally bringing Fortnite to Linux, a major win for Linux gaming. But its new anti-cheat requirements raise an uncomfortable question: how much control over our own computers should we surrender to play a game?

For years, Fortnite has been one of the biggest names missing from Linux gaming. While Valve's Proton compatibility layer has made thousands of Windows games playable on Linux, Fortnite remained out of reach because of its anti-cheat requirements.

That could finally change.

On 14 October 2026, Epic Games announced that it is rebuilding Easy Anti-Cheat (EAC) for Linux, with the intention of bringing Fortnite to the platform through its newly announced Epic Games Launcher for Linux.

The catch is that getting the game running will require more than installing a launcher and clicking Play. Epic wants Linux systems to meet a specific set of security requirements, including Secure Boot, TPM 2.0, signed kernels and verified boot measurements.

For competitive gaming, these measures have a purpose. For the Linux community, they also raise questions about what openness and freedom mean when commercial software starts dictating how your operating system must work.

A major win for Linux gaming

Credit where it is due. Epic's announcement is significant.

Linux gaming has made enormous progress thanks to SteamOS, the Steam Deck, Proton and the efforts of developers who have worked to make Windows games run outside Windows. Yet anti-cheat software has remained one of the biggest obstacles.

Some multiplayer games refuse to support Linux because their developers believe the platform makes cheating harder to detect or prevent. Fortnite has been a prominent example.

Epic is now developing EAC Linux v2 to bring Linux anti-cheat protection closer to the level it provides on Windows. The company plans to test the new system with Fortnite before making it available to other developers.

If successful, this work could benefit more than Fortnite players. Other studios could adopt the improved anti-cheat implementation, potentially opening the door to additional multiplayer games that have historically excluded Linux.

That is a meaningful step towards making Linux a more practical gaming platform.

There is, however, no confirmed release date for Fortnite on Linux yet. Epic says it will launch the game once the new anti-cheat system works with a sufficiently broad range of Linux distributions.

The price of admission: Secure Boot, TPM 2.0 and more

Epic's proposed EAC Linux v2 requirements go beyond simply running a supported Linux distribution.

The system must provide several layers of security that allow the anti-cheat software to establish confidence in the environment where the game is running.

These include:

• Secure Boot: UEFI firmware verifies the signatures of components in the boot process.
• TPM 2.0: A hardware security component helps record and verify information about the system's boot process.
• Signed kernels and kernel modules: The operating system components loaded for protected gameplay must meet Epic's signing requirements.
• Measured boot: The boot process records measurements of the components loaded, allowing the system to check what ran.
• IOMMU support: Hardware-assisted memory access controls help prevent unauthorised devices from accessing protected game memory.

These technologies have legitimate security applications. They can make certain forms of tampering more difficult and help anti-cheat software detect environments that have been modified to facilitate cheating.

Epic's approach also differs from its Windows implementation. EAC Linux v2 will not install its own anti-cheat kernel module. Instead, it will use existing Linux security features, a systemd service and eBPF-based mechanisms. The service is intended to run only while a protected game is running.

That is an important distinction. Epic is not proposing to run a Windows-style anti-cheat kernel driver permanently in the background on Linux.

However, the system still needs considerable control over the environment in which the game runs.

And that is where the philosophical debate begins.

Linux is supposed to be about freedom

One of Linux's greatest strengths is that users can choose how their computers operate.

You can run a distribution with a custom kernel. You can compile your own software, change system components, experiment with alternative bootloaders and configure your machine to suit your needs.

You can also decide that you do not want certain security mechanisms enabled.

That flexibility is not necessarily a security flaw. For many users, developers and enthusiasts, it is the whole point.

Epic's requirements introduce a different model. To play a protected game, your computer must satisfy the publisher's conditions for a trusted system. A kernel that works perfectly well for your purposes may be rejected if it is not signed with a key Epic recognises. A customised boot configuration may prevent the game from launching.

The concern is not that Secure Boot exists. The concern is that a commercial game can effectively dictate which system configurations are acceptable.

Consider a Linux enthusiast who compiles a custom kernel to improve performance, experiment with scheduling, or support specialised hardware. That user may have perfectly legitimate reasons for modifying the operating system. Yet those modifications could make the system incompatible with EAC Linux v2.

Linux still allows the user to make those changes. Epic simply does not have to let the game run under those conditions.

That distinction matters. The freedom to configure your computer remains, but access to particular commercial games becomes conditional on how you configure it.

Does Secure Boot mean surrendering control?

Not necessarily.

Secure Boot is a mechanism for verifying the software loaded during startup. It does not inherently require Windows, proprietary software or a locked-down Linux installation. Users can manage their own signing keys, and Linux distributions already use Secure Boot-compatible boot processes.

TPM 2.0 is also not a proprietary Windows feature. Linux supports TPM hardware, and it can be used to strengthen system security without giving a game publisher unrestricted control over the computer.

The issue is Epic's trust model.

For EAC Linux v2, Epic intends to recognise an approved set of signing keys and require a verifiable boot process. This gives its anti-cheat system greater confidence that the kernel and other components have not been altered to enable cheating.

Epic says it plans to make its list of recognised keys open source and welcomes contributions from the community. It is also working with Linux distribution maintainers to broaden compatibility.

Those are constructive steps, but they do not eliminate the trade-off.

A user who controls their own keys may still need to use a separate, approved boot configuration to play a protected game. Epic explicitly says players can maintain one boot entry for compatible games and another that they control themselves.

That is better than forcing every Linux installation to use the same configuration all the time. It also shows that this is a conditional requirement for protected gameplay, not a general restriction imposed on Linux itself.

Nevertheless, the publisher decides what counts as a sufficiently trusted environment for its game.

What about the Steam Deck?

The announcement is particularly interesting for Steam Deck owners.

Valve's handheld runs SteamOS, a Linux-based operating system, and has helped demonstrate that Linux can provide a mainstream gaming experience. But Epic says the Steam Deck does not currently support the features required by its proposed EAC Linux v2 solution.

Epic is discussing the matter with Valve and investigating compatibility with SteamOS devices. For now, however, Fortnite's arrival on Linux does not mean the Steam Deck will automatically be supported.

That is an important limitation. The device many people associate most closely with the recent Linux gaming boom could be left waiting while Epic and Valve work through the technical requirements.

There is also no promise that every Linux distribution will work. Epic is collaborating with distribution maintainers and wants the system to support a critical mass of distributions before launching Fortnite.

For players, the practical question will be whether their chosen distribution and hardware are supported without extensive manual configuration.

Is this the beginning of a wider problem?

It could establish a precedent worth watching.

Epic's reasoning is understandable: cheating damages competitive games, and sophisticated cheats can operate below the level where ordinary software can reliably detect them. Developers need effective ways to protect fair play.

But stronger anti-cheat measures can also increase the amount of control a publisher demands over a player's environment.

If more publishers adopt similar requirements, Linux users could face a growing divide between systems that are fully under their control and systems configured to satisfy commercial anti-cheat software.

That would not make Linux closed source or remove the ability to modify it. The kernel would remain open, distributions could continue to experiment, and users could still choose their own configurations.

The problem would be more subtle. The freedom to modify your system would remain, but the freedom to play certain games could depend on giving up some of that flexibility.

This is not an entirely new debate. Windows has already seen games impose Secure Boot and TPM requirements in certain competitive environments. Epic itself expanded security requirements for Fortnite tournaments in 2026.

Linux is now facing a version of the same tension.

The question is how far these requirements will spread, how transparent the approval process will be, and whether publishers will work with the community rather than treating every non-standard configuration as inherently untrustworthy.

Progress, with conditions

Epic deserves recognition for making a serious effort to bring Fortnite to Linux. Rebuilding its anti-cheat system instead of simply declaring Linux unsupported is a positive development. Sharing improvements with other developers could make the benefits much wider.

But Linux users should not have to ignore the implications simply because a popular game is finally arriving.

Security and freedom are not mutually exclusive. Secure Boot can be used with user-controlled keys. TPM hardware can protect system integrity without dictating which operating system you must use. Anti-cheat software can also be designed with clear limits on what it accesses and when it runs.

The challenge is finding an approach that protects competitive play without turning a user's choice of operating system into a list of publisher-approved configurations.

For now, Fortnite on Linux remains a work in progress. The launcher is available in preview, the new anti-cheat is being developed, and the game itself has no confirmed Linux release date.

The outcome will matter beyond one battle royale game. If Epic can make this work while respecting the diversity of Linux systems, it could help bring more major games to the platform.

If compatibility instead depends on increasingly restrictive assumptions about how a computer should boot and operate, Linux users will have to decide whether access to those games is worth the compromise.

Linux gaming needs more support from major publishers. But the goal should be to make games work on Linux, not to make Linux work only on a publisher's terms.