Fortnite Comes To Linux Once Epic Fixes Easy Anti-Cheat

By Indie Kings | October 14, 2026

Updated October 14, 2026: Fortnite is coming to Linux once Epic Games finishes rebuilding Easy Anti Cheat for Linux, per columnist Tyler Wilde in PC Gamer on October 14, 2026. The plan ties the Fortnite Linux release to EAC Linux v2 reaching a critical mass of distro maintainers, with delivery through the Epic Games Launcher and with the same improvements offered to other developers.

Image: Fortnite key art. Credit: PC Gamer.

What Epic Games actually announced

Per columnist Tyler Wilde, Epic Games intends to launch Fortnite on Linux. That sentence alone ends years of waiting for players who want native access without workarounds. The announcement does not promise immediate availability. It sets a clear order of operations. First comes the anti cheat rebuild. Then comes the game.

Per columnist account, the company described the work as rebuilding Easy Anti Cheat. That wording matters because it signals more than a small patch or a compatibility flag. A rebuild implies changes to how the anti cheat observes, verifies, and trusts a Linux session. Players should read that as structural work rather than a simple switch that someone forgot to flip.

The central condition uses precise language. Per columnist account, Epic Games said, Once EAC Linux v2 is working with a critical mass of distro maintainers, we will bring Fortnite to Linux via the Epic Games Launcher. Every clause in that sentence carries weight. The trigger is technical readiness. The readiness test involves distro maintainers. The delivery vehicle is the launcher. The audience is Linux players who have waited for a supported path.

Per columnist account, the company added a second promise with wider effects. The company said, We will also make these improvements available to other developers so they can bring their games to Linux players. That turns a single game port into possible platform progress. If the improved anti cheat can be reused, then other studios face a lower barrier when they evaluate Linux support.

Readers should keep the standing of this story in mind. Standing per columnist throughout means the details below come from columnist reporting rather than from hands on testing by this site. The announcement sets direction and conditions. It does not provide a release date, a supported distro list, a minimum specification, or a feature checklist. Those specifics remain unannounced in the reported material.

The practical takeaway is still large. A major shooter is pushing past the Linux anti cheat barrier, per columnist framing. That framing places Fortnite in a different category from smaller titles that already run through compatibility layers. When one of the largest live service games commits to a Linux path, it changes expectations for publishers, anti cheat vendors, distro maintainers, and players who track Linux gaming news.

This section answers the core query in plain terms. Is Fortnite coming to Linux. Yes, with a condition. What is the condition. EAC Linux v2 working with a critical mass of distro maintainers. How will it ship. Through the Epic Games Launcher. Who else benefits. Other developers who can use the same improvements. Those four points form the foundation for everything that follows.

Why EAC Linux v2 comes first

Per columnist account, Easy Anti Cheat is the gate. Fortnite cannot arrive in a supported form until the anti cheat trusts Linux sessions enough for competitive play. That order reflects how modern multiplayer security works. The game client, the server, and the anti cheat must agree that a session is legitimate. If any part lacks confidence, the whole match is at risk.

The name EAC Linux v2 signals a new generation of Linux support rather than a continuation of older approaches. Per columnist account, Epic Games is rebuilding Easy Anti Cheat to support the move. A rebuild suggests lessons learned from earlier Linux and Proton era problems. It also suggests coordination beyond Epic Games itself, because anti cheat on Linux touches kernel interfaces, distro differences, update cadence, and cheat developer behavior.

The phrase critical mass of distro maintainers deserves close attention. Linux is not one operating system with one update path. It is a family of distributions with different kernels, libraries, packaging choices, and release rhythms. An anti cheat solution that works on one distribution but breaks on others creates support load and uneven protection. Waiting for a critical mass means waiting until enough maintainers can carry the integration without leaving large parts of the player base behind.

That choice protects both players and matches. Players benefit when installation, updates, and verification behave consistently. Matches benefit when enforcement is uniform enough that cheaters cannot simply move to the least protected distribution. A fragmented rollout would invite exactly the kind of exploit shopping that anti cheat teams try to prevent. A coordinated rollout reduces that risk.

Per columnist framing, opening Linux access represents a security and cheating risk. That risk explains the caution. Competitive shooters attract cheat developers because rank, rewards, accounts, and audiences create strong incentives. Any new platform widens the attack surface. The rebuild must therefore balance access with assurance, giving legitimate players a path while denying cheat developers an easy new vector.

The promise to share improvements with other developers also starts here. If EAC Linux v2 solves distro coordination once, then other studios do not need to solve it alone. That shared benefit could matter more than any single release. Anti cheat vendors, engine providers, and publishers all watch the same problem. A credible reference implementation lowers cost and uncertainty for the next team that considers Linux.

Players should not read impatience into the sequencing. Security first is not a delay tactic in this context. It is the only order that preserves match integrity. A Linux release without trusted anti cheat would lead to rapid cheat development, emergency restrictions, and possible rollback. A Linux release after the anti cheat rebuild has a better chance of lasting. That durability matters more than being first through the door.

Why the launcher path matters

Per columnist account, Fortnite will come to Linux via the Epic Games Launcher. That detail answers the where question. Players will not need to guess which storefront or side channel carries the supported build. The launcher becomes the home for installation, updates, entitlements, and likely verification steps tied to the new anti cheat.

The launcher path also fits the related context in the same report. Per columnist account, Epic Games has released a new Epic Games Store client which includes a Linux version for the first time. That client progress and the Fortnite plan point in the same direction. The store and launcher stack is gaining Linux capability at the same time the flagship game prepares for Linux. Readers should treat those as parallel parts of one platform move rather than isolated news items.

A launcher based release helps with support boundaries. Linux fragmentation makes direct download support difficult because every distribution handles dependencies differently. A maintained launcher can centralize update logic, prerequisite checks, and error reporting. That centralization does not remove distro differences, but it gives Epic Games one place to fix common failures and one place to coordinate with distro maintainers.

The launcher also helps with account level protections. Fortnite accounts carry purchases, progression, competitive history, social connections, and creative content. Anti cheat is only one layer of trust. Installation integrity, update authenticity, and account security all matter. Delivering through the official launcher keeps those layers under one roof instead of spreading them across community packages and unofficial scripts.

Players who currently use unofficial methods should pay attention to this distinction. Community workarounds may launch parts of the ecosystem, but they do not carry official anti cheat trust. A supported launcher build changes that relationship. It tells players that the path they use is the path the security team tests, monitors, and defends. That assurance is especially important in ranked modes and limited time competitive events.

The launcher detail also clarifies what this announcement is not. It is not a Steam release announcement. It is not a Proton configuration guide. It is not a promise that every Linux distribution will work on day one. It is a statement that the official Epic Games route is the intended Linux route once EAC Linux v2 reaches the stated readiness point.

For now, the useful preparation is simple. Linux players should keep their distribution updated, follow official Epic Games channels for launcher news, and avoid treating unofficial packages as equivalent to the coming supported path. When the launcher build arrives with the new anti cheat, clean installation through the official route will matter more than early experimentation through unsupported routes.

Proton progress and the multiplayer holdout problem

Per columnist account, more PC games than ever are playable on Linux, thanks in part to Valve Proton emulation. Proton allows many Windows games to be played on SteamOS and has been essential to the Steam Deck success. That progress explains why Linux gaming feels transformed compared with earlier eras. Large parts of a Steam library now launch with little friction.

The same section draws a firm boundary. Some of the biggest multiplayer games have been holdouts, because opening the doors to Linux represents a security and cheating risk. That sentence captures the central tension. Compatibility layers can translate graphics calls, audio paths, input handling, and file access. They cannot by themselves create trust. Trust requires publisher approval, anti cheat cooperation, and ongoing maintenance.

This distinction helps new Linux players set correct expectations. A game can be technically launchable yet officially unsupported. A game can run well in single player yet remain blocked in multiplayer. A game can work today and break after an anti cheat update. Proton reduces porting cost, but it does not remove security policy. Publishers still decide whether Linux sessions are welcome in competitive queues.

This site has covered Steam Remote Play versus dual boot approaches for anti cheat games. That experience shows why players seek indirect access when direct support is absent. Streaming from a Windows host or rebooting into Windows preserves access, but neither route equals native support. Native support means local installation, local performance, local input, and official anti cheat trust on Linux itself.

The Fortnite plan matters because it targets the trust layer directly. Instead of asking players to accept indirect access forever, Epic Games is rebuilding the component that blocks direct access. If that rebuild succeeds, then Fortnite moves from the holdout category into the supported category. That move would demonstrate that large multiplayer games can solve the Linux security question rather than avoid it.

The table below restates the current split in simple terms so readers can see where Fortnite sits before and after the planned change.

That table makes the strategy visible. Proton already solved a large part of Linux gaming. The remaining problem is concentrated in high risk multiplayer titles. Fortnite aims to solve that concentrated problem with a shared anti cheat upgrade. Success would not just add one game. It would provide a pattern that other holdouts can follow.

The Rust precedent and the cheat vector argument

Per columnist account, Rust provides the clearest example of why publishers hesitate. Former Facepunch COO Alistair McFarlane said last year that Rust was unsupported on Linux because of cheating. That statement came from operational experience rather than theory. It described a live game with active cheat pressure and limited support resources.

The reported wording is direct. Per columnist account, McFarlane said, There are no plans to support Proton or Linux. The same passage gives two reasons. First, Linux is described as a vector for cheat developers. Second, that vector would be poorly maintained by both the studio and EAC due to the low user base. Those two reasons combine into a cost benefit judgment. More risk plus more maintenance for fewer players equals no support.

The report adds a striking operational detail. Per columnist account, McFarlane said, When we stopped support for Linux, we saw more cheat users exploiting Linux, than actual legitimate users. That observation explains why some studios view Linux as a net security loss. If cheaters use the platform more than legitimate players do, then continued support harms match quality without growing the audience.

Readers should treat that Rust history as context, not as a prediction for Fortnite. Rust and Fortnite differ in scale, resources, update cadence, anti cheat staffing, and platform leverage. Epic Games owns Easy Anti Cheat, which changes the maintenance calculation. A studio that rents anti cheat protection faces different incentives from a company that builds the protection itself. Ownership makes a rebuild more feasible.

Per columnist account, Epic Games move could potentially change that calculation for Rust and other games. That sentence is careful. It says could potentially change, not will change. The logic is still clear. If EAC Linux v2 makes Linux sessions easier to trust and easier to maintain, then the low user base argument weakens. Other studios can reconsider Linux without accepting the same open ended burden that Rust described.

The table below compares the two positions without adding facts beyond the report.

The comparison shows why coordination matters. Rust described a world where each studio bears Linux anti cheat cost alone for a small audience. Epic Games describes a world where the anti cheat owner absorbs the core rebuild cost and shares the result. The second world gives smaller teams a better starting point. It does not guarantee that every holdout will follow, but it removes one strong reason for refusing.

Players should also notice what is missing. The report does not say Rust will return to Linux. It does not quote current Facepunch leadership about EAC Linux v2. It does not promise that shared improvements fit every engine, every server model, or every threat profile. The reasonable reading is narrower. A successful Fortnite Linux launch would give other studios new evidence, not a new obligation.

The Steam Deck gap and the Valve talks

Per columnist account, one hurdle stands out because it affects how many players will actually use the Linux version. Most of the people the columnist knows who play games on Linux do so on a Steam Deck. That observation matches the visible shape of Linux gaming today. The handheld brought many new players into Linux without asking them to install or maintain a desktop distribution.

The problem is direct. Per columnist account, an Epic Games blog post with technical details says the Steam Deck does not currently support the new EAC Linux v2 solution. That means the most popular Linux gaming device sits outside the initial solution. Desktop Linux players may gain support while handheld players wait. That gap will shape early reaction no matter how strong the desktop implementation becomes.

Per columnist account, Epic Games says that it is actively talking with Valve about making Steam Deck support happen. Active talks indicate recognition of the problem, but talks are not the same as a tested implementation. Players should treat Steam Deck support as an open work item rather than a launch guarantee. The wording promises effort and communication, not a date.

This gap has practical consequences. A Fortnite Linux release without Steam Deck support would still matter for desktop players, competitive players with dedicated rigs, and Linux first households. It would matter less for handheld first players who expect their library to travel. Those players will rightly ask whether the Linux version includes the Linux device they actually own.

The technical relationship also matters. Steam Deck runs SteamOS, which is shaped by Valve choices around updates, immutability, drivers, and security posture. An anti cheat solution that needs distro maintainer cooperation must account for how SteamOS ships changes. Talks with Valve therefore make sense as a separate track from talks with desktop distribution maintainers. Each environment has its own constraints.

Players should avoid two easy mistakes here. The first mistake is assuming Steam Deck support will arrive automatically because SteamOS is Linux. The report says the opposite for now. The second mistake is assuming Steam Deck exclusion means the whole plan failed. The report frames desktop Linux through the launcher as the stated path, with handheld compatibility as a separate investigation. Both facts can be true at once.

The useful question for handheld owners is therefore narrow. Does EAC Linux v2 gain Steam Deck and SteamOS compatibility before or after the desktop Fortnite Linux release. The report does not answer that timing question. It only confirms that compatibility is under investigation and that Valve talks are active. Handheld players should watch official Epic Games and Valve channels rather than assume day one parity.

What security leadership said about player choice

Per columnist account, game security engineering director Rick Deist told PC Gamer on a call this week that Epic Games is investigating compatibility with Steam Deck and SteamOS devices. That statement puts a named security leader behind the handheld question. It matters because security leadership owns the tradeoff between access and protection. Investigation means the team is testing what handheld support would require, not merely wishing for it.

The same section connects the Fortnite plan to wider Linux client work. Per columnist account, Epic Games has released a new Epic Games Store client which includes a Linux version for the first time. A Linux capable store client plus a Linux bound launcher plan plus a Linux anti cheat rebuild form a coherent stack. Each layer removes one excuse for staying Windows only. Together they suggest sustained investment rather than a single experiment.

Per columnist account, Deist said, We want to let players play where they want to play as much as possible. That sentence states the player choice philosophy in plain words. It does not promise every device, every distribution, or every mode at launch. It states direction. The security team wants access to follow the player, subject to the trust work that makes access safe.

That philosophy helps explain the sequencing choices. A team that only cared about control would keep Fortnite Windows only and avoid new risk. A team that only cared about reach would ship Linux quickly and accept higher cheat pressure. The reported path tries to honor both goals. Expand where players can play, but only after the enforcement layer can protect those new places.

Readers should also note the source discipline here. The handheld investigation comes from a direct call with PC Gamer, per columnist account. The EAC Linux v2 technical details come from an Epic Games blog post referenced in the same report. The release condition and sharing promise come from the company announcement quoted in the report. Each layer has a named origin, which makes the story easier to verify than rumor based port speculation.

None of this removes the remaining unknowns. The report does not give a release window. It does not list supported distributions. It does not describe performance targets, input handling, voice chat behavior, competitive mode eligibility, or cross progression details for Linux. Those are normal launch questions, but they sit outside the reported facts. Responsible coverage should leave them open rather than fill them with guesses.

The durable point is simpler. Security leadership publicly ties Linux support to player choice, names handheld compatibility as an active investigation, and places the work inside a broader Linux client effort. That combination gives Linux players more reason for confidence than a vague statement of interest. It still leaves execution as the test. Announcements open the door. EAC Linux v2, distro maintainer readiness, launcher delivery, and Valve talks will decide who walks through it.

FAQ

Is Fortnite officially coming to Linux?
Yes, with a condition, per columnist Tyler Wilde. Epic Games intends to bring Fortnite to Linux via the Epic Games Launcher once EAC Linux v2 works with a critical mass of distro maintainers. There is no release date in the reported material.

What is EAC Linux v2?
Per columnist account, it is the rebuilt Easy Anti Cheat Linux solution that must support the Fortnite move. The rebuild aims to make Linux sessions trustworthy enough for large scale competitive play. Other developers are expected to receive the same improvements.

Why does Fortnite need distro maintainer support first?
Per columnist account, Linux distributions differ in kernels, libraries, packaging, and update cadence. Waiting for a critical mass helps the anti cheat work consistently instead of protecting some players while leaving others exposed. That coordination also reduces long term maintenance risk.

Will Fortnite Linux work on Steam Deck at launch?
Per columnist account, Steam Deck does not currently support the new EAC Linux v2 solution. Epic Games says it is actively talking with Valve, and Rick Deist says handheld and SteamOS compatibility is under investigation. Handheld owners should wait for explicit confirmation.

How does the Rust example relate to Fortnite?
Per columnist account, Rust remains the cautionary case because cheating concerns and low user base led Facepunch away from Linux support. Epic Games owns Easy Anti Cheat and plans to share EAC Linux v2 improvements, which could change the calculation for Rust and other games. No return by Rust is promised.

Where will the Linux version be available?
Per columnist account, the stated path is the Epic Games Launcher. That keeps installation, updates, entitlements, and verification under the official client. It is not described as a Steam release in the reported material.

Bottom Line

Per columnist reporting, Fortnite is coming to Linux once EAC Linux v2 earns trust across enough distributions, and that order is the story. Epic Games will ship through the Epic Games Launcher, share the anti cheat improvements with other developers, keep talking with Valve about Steam Deck support, and investigate SteamOS compatibility while security leadership points toward player choice. Desktop Linux players have a clear path to watch. Handheld players have an open question to track. Other publishers have a possible template if the rebuild holds under live cheat pressure. Watch distro maintainer readiness, launcher delivery, and Valve talks before expecting a date, and treat any Linux build outside the official launcher path as unsupported until Epic Games says otherwise.

Sources

Source: PC Gamer, Fortnite is coming to Linux once Epic improves Easy Anti Cheat, per columnist Tyler Wilde dated October 14, 2026. Standing per columnist throughout.