What the Epic Games Launcher Preview Changed for Indies - 2026
![]()
If you searched epic games launcher preview on October 14, 2026, you landed in the middle of three different announcements that share one date. Epic opened a new launcher in preview for Windows, macOS, and Linux. The same morning Epic published a plan to rebuild Easy Anti-Cheat for Linux and pilot it in Fortnite later. And the store post opened with a joke about vibe coding that The Verge treated as a real statement about how the company builds software.
Those three threads are easy to mash into one Slack message. “The launcher is faster, it is on Linux, Fortnite is on Linux, and they vibe-coded it.” Each clause is either incomplete or false if you ship a game, install Unreal, or open Unreal Editor for Fortnite from the machine you use every day.
This page is the what-changed read for a small studio. It follows the Epic Games Store post and the preview site, then separates the install behavior from the Fortnite plan and from the speed numbers Epic commissioned.
Why this matters now
The launcher is how most Unreal and UEFN teams still get the editor onto a disk. A stuck-percent install is already a Monday problem on the legacy app. The preview adds a new one. The preview site says, in the install step, that trying the new Epic Games Launcher automatically uninstalls the legacy version. Your account, purchases, installed games, cloud saves, and progress are tied to the account and are supposed to carry over. The application on that computer is replaced.
That is the change that hits a shipping PC before any Linux headline does. A producer who clicks Download on the only workstation that opens UEFN has just swapped the tool that lesson one of a Fortnite course still assumes is the ordinary launcher. The UEFN setup lesson still says install the Epic Games Launcher, then Unreal Engine, then Fortnite, then UEFN. The Creative 2.0 overview still points at the store download. Both remain correct for the legacy path. Both become a different procedure the moment the preview has uninstalled that path.
Direct answer: On October 14, 2026 Epic shipped a preview launcher for Windows 10 or 11, Apple silicon Macs on macOS 12 or newer, and three named Linux families. It is lighter on features than the legacy app, it uninstalls the legacy app when you try it, and it does not ship Fortnite on Linux. Fortnite on Linux waits on a rebuilt anti-cheat, a critical mass of distro maintainers, and a live pilot. There is no date.
Who this read is for
| Audience | Use it to… |
|---|---|
| Beginners | Tell a preview download from a finished store app before you replace the launcher you already have |
| Developers | See which OS builds are supported, which speed numbers have a footnote, and what EAC Linux v2 still requires |
| Creators | Explain the Linux launcher and the Fortnite plan in a devlog without calling Fortnite shipped |
| Companies | Separate a commissioned startup benchmark from a migration date, and keep a legacy install on the machine that must open the editor tomorrow |
Time: about 35 minutes to read. Installing the preview is a separate sitting, and it belongs on a machine you can reinstall.
Prerequisites: an Epic account you already use for the store, Unreal, or UEFN. You do not need a new engine version to understand the announcement. You do need to know which computer is the only one that can open your project tonight.
What changed, in one table
| Before October 14, 2026 | After the preview opened |
|---|---|
| The Epic Games Launcher people installed for Unreal and the store was the legacy app | A preview app exists for Windows, macOS, and Linux, and trying it uninstalls the legacy app on that computer |
| Linux players used workarounds for the store client | Epic says the new launcher runs natively on Ubuntu 22.04 LTS or newer, Fedora 43 or newer, and Debian 12 or newer |
| macOS support followed the machines studios already had, including many Intel Macs | The preview supports Apple silicon only. Intel Macs are not supported |
| Fortnite on Linux was not a current Epic plan with a public anti-cheat rebuild | Epic is rebuilding Easy Anti-Cheat as EAC Linux v2 and plans to pilot it in Fortnite first. No ship date |
| “Faster launcher” was a wish | Epic published cold-start, store, and library timings from a Keywords Studios test, with a footnote that drops the three lowest-end machines |
| Feature parity with the legacy launcher was the baseline | Epic says this first release is light on features, and the FAQ says some social features and account-management options are missing |
The store post calls the preview a speedboat and not a yacht, then jokes that it does include a shopping cart. Read that as Epic’s own description of scope. A shopping cart and a faster library view are in. A promise that every legacy screen has a replacement is not.
The opening lines, and what a briefing added
The store post starts like this. Programming is hard. So, instead of doing that, Epic vibe coded a new Epic Games Launcher that is way faster and more responsive than the current one, and has a new look. The next paragraph says this first release is light on features. Think of it as a speedboat and not a yacht, though it does have a shopping cart.
The Verge asked Epic about that wording. Martin Keely, VP and GM of the Epic Games Store and Epic Online Services, told The Verge that Epic used AI as a tool, that it helped with testing and with replicating core functionality from the existing launcher, and that it is part of why Epic can offer the launcher on Linux. He also said agents wrote and reviewed the code, the team managed that process and supervised it, and the launcher team has not adopted a “no more hand-written code” rule. The Verge places that rule in a separate Bloomberg report about a different Epic project. Do not paste the Bloomberg line onto this launcher team. Keely told The Verge the launcher work has been underway for most of this year, that there is no date when everyone must move, and that the full launch waits until the update feels stable and has parity in the places Epic says it needs.
A comment thread on GamingOnLinux argued about whether the vibe-coded sentence is a joke, because the shopping-cart sentence next to it is obviously a joke. Both readings can be true at once. The shopping cart is a joke about a thin feature list. The AI claim is a briefing The Verge published the same day, with a named executive. For a studio ticket, quote the briefing when you mean “how was this built,” and quote the speedboat line when you mean “what is missing.”
What you should not do is treat either sentence as a test plan. “Agents wrote it” does not tell you whether cloud saves survived. “Way faster” does not tell you whether your Unreal install button is on the screen you expect. Those answers are in the install note, the FAQ, and a spare machine.
Install steps, and the line that replaces your app
Epic’s how-to on the store post is short.
- Download the launcher. Check the system requirements on the preview site, then grab the installer for your device.
- Install and sign in. Your Epic Games account, purchased games, installed games, cloud saves, and progress are tied to your account, so they carry over to the preview and to the full release.
- Explore the library, manage downloads, customize the launcher, and use Send Feedback to report an issue.
The preview site splits the same path into download, install and explore, and feedback. Step 2 on that site adds one sentence the store post does not put in the numbered list. Trying the new Epic Games Launcher will automatically uninstall the legacy version.
Hold that next to two other official lines.
The preview FAQ says your purchases, installed games, cloud saves, and progress carry over, and that switching between the legacy launcher and the preview should not affect your data. If something looks missing, use Send Feedback.
The Verge, citing Keely, says the old version will remain available, and that Epic has no specific timeline for when everyone has to move.
Read those three lines as three different scopes.
| Line | What it governs |
|---|---|
| Preview site, install step | The copy of the legacy app on the computer where you run the preview installer. That copy is uninstalled. |
| FAQ, carry-over and switching | Account data. Purchases and cloud saves are supposed to survive a switch. The FAQ does not say both apps stay installed side by side. |
| The Verge, Keely | The legacy product stays available as something Epic still offers. It is not a promise that your current PC keeps its current install after you click through the preview. |
A studio with one PC cannot satisfy “keep today’s Unreal install path” and “try the preview” in the same hour. A studio with a spare PC, or a spare user account on a machine nobody ships from, can. If the only disk that has your engine cache is the disk you are about to point at the preview installer, stop at the download link and send that link to the other computer. The preview site even has a “share download link” control for that.
The store post’s updated note covers play, not the installer. The preview can have issues. Once you are in a game or a developer tool, nothing in that note prevents development or casual and competitive play. The FAQ answers “Can I play competitive games like Fortnite?” with yes, once you are in the game. Services are supposed to work, and Epic says nothing there would prevent casual or competitive play. That note is about the session after launch. It does not restore the legacy shortcut the installer removed.
What is supposed to come with you
Write this down before anyone clicks install, because “carry over” is an account claim, and account claims fail in specific ways.
- Purchases stay on the Epic account. A game you own should still be owned after you sign into the preview.
- Installed games are supposed to carry over. “Installed” here means Epic still knows the install, not that every file path on a new disk is magically filled. If you moved the preview onto a different computer, expect downloads.
- Cloud saves and progress are supposed to carry over for games that use them. A local-only save in a folder the legacy launcher never synced is still a local folder. Confirm the game’s own save path if that title matters tonight.
- Unreal and UEFN are developer tools the store note groups with “once you are in a game or developer tool.” The note says the preview should not block development after the tool is open. It does not say the preview’s Library and Develop screens already match every legacy install button. The FAQ says some account-management options are missing. If your Monday task is “change the payment method” or “recover a seat,” do that on a legacy install you still have.
If a library row is empty after sign-in, the FAQ’s remedy is Send Feedback inside the launcher, plus Discord, the Epic Developer Community forums, or Player Support. Those are Epic’s channels. File the missing row there with the account and the machine, and keep the legacy installer available for the machine that has to keep working.
Windows, Mac, and Linux requirements
Epic says the new launcher is designed to run on the same hardware as the legacy one, with one Mac exception that matters. You need an internet connection for setup, updates, and online features. Offline mode exists for supported installed games.
| Spec | Windows | macOS | Linux |
|---|---|---|---|
| OS | Windows 10 or 11, 64-bit | macOS 12 Monterey or newer | Ubuntu 22.04 LTS or newer, Fedora 43 or newer, or Debian 12 or newer |
| CPU | Intel Core i3 or AMD Ryzen 3 | Apple M1 or newer | 64-bit x86-64, 2 GHz dual-core or newer |
| RAM | 4 GB | 4 GB | 4 GB |
| Storage | 700 MB | 200 MB | 2 GB |
| Mac CPUs | n/a | Apple silicon only. Intel Macs are not supported | n/a |
| Other distros | n/a | n/a | May work. Epic says they are not officially tested or supported |
Four gigabytes of RAM is a launcher floor, not a floor for Unreal, UEFN, or a cooked game. If the editor already struggles on the machine, the preview will not fix that. The storage numbers are for the launcher itself. Linux asking for 2 GB, against 700 MB on Windows and 200 MB on macOS, is a hint that the Linux build is carrying more than a thin UI. It is still not your game’s install size.
Apple silicon only
If the studio Mac is an Intel machine, the preview is a no. Epic states that on one FAQ line. Intel Macs are not supported. An M1 or newer on macOS 12 or newer is the Mac that can try it. Do not spend the afternoon collecting crash logs from a 2019 Intel MacBook and calling it a preview bug. Call it an unsupported CPU and keep that Mac on the legacy launcher if the legacy launcher still runs there.
Linux families Epic named
Ubuntu 22.04 LTS or newer, Fedora 43 or newer, and Debian 12 or newer are the supported set. Arch, SteamOS, and a long list of gaming distros can still launch something. Epic’s sentence is that other distributions may work and are not officially tested or supported. For a studio, “it happened to open” is a personal experiment. “We support Linux players of our store build” is a claim you can only make after you have read the game’s own Linux story, which is the next section.
A native launcher is not a native game
The preview FAQ is explicit. The new Epic Games Launcher runs natively on Linux, but many games are Windows-only builds and may need a compatibility layer. Check each game’s Linux compatibility before installing.
That splits the October 14 Linux news into two products.
| Product | What October 14 actually did |
|---|---|
| Launcher | Native Linux client for the named distros |
| A Windows store game | May still be a Windows build. The launcher can ask for a compatibility layer |
| Fortnite | Not available on Linux yet. Epic says it is coming after EAC Linux v2 |
| Your Unreal game | Unchanged until you ship a Linux build or opt into whatever compatibility path you intend to support |
GamingOnLinux reported a quick test of a Windows game. The launcher asked for a one-time download to support it, and the writer identified GE-Proton under /.local/share/com.epicgames.eglv2/compat/runtime/. Treat that path as one journalist’s install on October 14, not as an Epic support contract. If you need to debug a player’s prefix, look on their machine. Do not promise in a patch note that Epic’s prefix path will stay at that string.
For your own title, the checklist is the one you already use for any store. Do you ship a native Linux client? If you ship a Windows client only, are you willing to let a compatibility layer be the player’s path, and have you opted into the anti-cheat behavior that layer requires? The launcher preview does not answer those questions for you. It gives Linux players a first-party store client in which those questions show up.
What the preview is trying to be
The store post and the preview site describe a thinner, faster client. Use the list as a feature inventory for the preview build, and check it on the spare machine before you tell the team it is true on yours.
Cold start and navigation. Epic wants faster cold starts, snappier movement between library and store, and less load while the launcher sits in the background.
One frame for Store, Library, and Develop. The preview site calls this a cleaner framework, with more room for games.
A page per game. Select a game and see status, activity, details, and play controls on a dedicated page. The preview site adds add-ons, an activity feed for playtime and updates since you last played, and update status on the game page and in downloads.
Library layout. Collections sit alongside the library. You can switch grid and list, or the preview site’s Details view and Grid view. Details keeps games on the left and the selected game on the right. Grid uses tiles, and selecting one opens the game page over the grid. You can hide games you do not play and bring them back. Search and filter run as you type. Sort, then narrow by platform, genre, and more.
Top bar. Pin favorite games and apps, or pick a ready-made layout. Recent games are meant to be one click away from anywhere in the launcher.
Downloads. One place for active, queued, scheduled, and failed downloads, with download, read, and write speeds.
Social. The store post says you can party up and voice chat with friends across Fortnite, the Epic Games Store, and the Epic Games app. The preview site says you can start parties and chat in the new launcher. The FAQ then says some features from the legacy launcher are not available yet, including certain social features and account-management options. Both can be current. A party button can exist while a specific legacy social screen does not. Test the action you care about. Do not assume the word “social” means the old overlay, the old friends list, and voice all survived with the same names.
Other PC libraries. The store post says you can connect your PC libraries and see everything you own together. It does not, in that paragraph, name every other store. Confirm the connectors you need inside the preview before you drop a spreadsheet that says “our Epic library now includes the other stores.”
Feedback. Send Feedback inside the launcher is the path Epic repeats. Discord and the Epic Developer Community forums are the public rooms the store post links for the road to the full release.
What is still missing
Epic’s own FAQ heading is “known limitations.” Some legacy features are absent, including certain social features and account-management options. Epic says it is working toward feature parity and will update the FAQ as features land.
That is the speedboat line in operational form. Parity is the exit criterion Keely described to The Verge for the full launch, not a property of the October 14 build. If your studio runbook says “open the launcher, then the account page, then the organization seats,” run that runbook on the preview before you retire the legacy install. A missing account page is a known class of gap, not a surprise outage.
Also missing, because Epic said so in a different post the same day, is Fortnite on Linux. The launcher can be on Linux while the game is not. Those are different ship gates.
How to read the speed numbers
The preview site publishes timings and a footnote. Use both.
| Claim on the preview site | Numbers Epic printed | Footnote |
|---|---|---|
| Cold start | New launcher 5.47 s, Steam 10.07 s, called 1.8x faster startup than Steam | Average of 5 tests on each of 13 machines, excluding the 3 lowest-end machines. October 2026. Keywords Studios, commissioned by Epic. Individual results vary. |
| Opening the store | Called 3x faster than Steam | Same footnote |
| Background to library | New launcher 0.36 s, Steam 0.42 s, called 1.2x faster | Same footnote |
| Library browse | Headline “30x faster” | The page does not attach a second methodology block to that headline beyond the starred startup tests |
Keywords Studios is an independent studio Epic paid to run the test. That is a real third-party measurement, and it is still Epic’s commissioned number. The exclusion of the three lowest-end machines means the average is not “every PC we tried,” and “individual results will vary” is Epic’s sentence, not a reviewer hedge you have to invent.
Use the numbers in a devlog only with that footnote in the same breath. A producer comparing the preview with the legacy Epic launcher on a five-year-old laptop should time that laptop. The published average dropped the slowest machines and compared the preview with Steam, not with a line that says “5.47 seconds versus our own previous launcher on the same hardware.” If you need the legacy-versus-preview number for your own fleet, measure your fleet.
A 30x library claim is the one to be most careful with in a pitch deck. The cold-start pair at least shows two clocks. The library headline, on the page fetched for this article, does not show the two clocks next to the words “30x.” Quote the cold start if you quote anything, and let someone on the spare machine scroll a large library with a stopwatch before you quote 30x.
Fortnite on Linux is a plan
The store post’s section title is “Fortnite is coming to Linux on the Launcher.” Coming is the verb. Epic says it is rebuilding Easy Anti-Cheat and working with distro maintainers on security requirements. Once that works with a critical mass of maintainers, Epic will bring Fortnite to Linux through the Epic Games Launcher. The same improvements are meant to become available to other developers so they can bring their games to Linux players. There is no date in that section.
The technical post is Introducing Easy Anti-Cheat Linux v2, published the same day. It is the right primary source when someone asks what “rebuilding EAC” means. The short version, in Epic’s words, is that EAC has supported native Linux clients since 2014 and Windows builds through Wine and Proton since 2021, that the Proton path is opt-in per game, and that many games have not opted in because the Linux implementation did not match Windows protection. Epic says that is why Fortnite is not on Linux yet.
EAC Linux v2 is the rebuild. Epic plans to pilot it in Fortnite first, learn from that live environment, and only then offer it to more developers. A panel with Jef Spaleta, Fedora Project Leader, is planned for later this year. Distro maintainers who have not already been contacted are pointed at [email protected] so their signing keys can be considered for a well-known list Epic intends to open source.
The Verge’s Fortnite piece adds a briefing detail the store post does not. Engineering director Rick Deist told The Verge there is no timeline for a Fortnite Linux version. The Verge also reports that Epic is investigating SteamOS compatibility and does not plan to put Fortnite on Steam’s store. Quote The Verge for the “no timeline” sentence. Quote Epic’s own post for the pilot order.
What EAC Linux v2 asks of a machine
Epic says EAC Linux v2 does not install or load an anti-cheat kernel module. A systemd service is installed the first time a player launches a protected game. The service starts with the game and stops when the game exits. Protection is supposed to come from platform features plus Epic’s eBPF logic. Epic expects the requirement list to change. As published on October 14, the eight areas are:
| # | Requirement | What Epic is trying to guarantee |
|---|---|---|
| 1 | Signed kernel and signed kernel modules | The running kernel, and out-of-tree modules such as NVIDIA’s, are signed with a well-known key |
| 2 | TPM 2.0, enabled in the BIOS | A tamper-resistant boot log the anti-cheat can read without running at boot |
| 3 | Secure Boot with well-known keys | The firmware only boots a boot manager it trusts, and that manager checks the kernel |
| 4 | Measured boot | systemd-boot and GRUB typically record the next stage. Other boot managers might not |
| 5 | IOMMU on, passthrough off, for non-handheld devices | DMA devices cannot freely read a protected process |
| 6 | Kernel lockdown integrity mode, enabled at boot | Root cannot do a list of operations Epic treats as cheat primitives |
| 7 | kexec disabled at boot | A replacement kernel cannot skip the measured boot log |
| 8 | BPF LSM loaded and active | eBPF programs can restrict access to the game process without a kernel module |
Well-known keys named in that post include Canonical, Fedora, Universal Blue, Debian, openSUSE, SUSE, Rocky Linux, the Microsoft UEFI CA used by the shim, and AlmaLinux. Epic says you can keep a second boot entry with your own keys for everything that is not a protected game. If you boot through shim and want custom keys for those other entries, Epic says to enroll them in the Secure Boot db, not as Machine Owner Keys, because enrolled MOKs are trusted broadly for module verification and EAC Linux v2 wants every MOK to be well-known.
Failing the check is an error message, not an account ban, according to Epic’s FAQ on that post. A cheat that works against v2 does not, in Epic’s telling, mean the system is abandoned. Anti-cheat still needs updates. The goal they state is a higher cost for cheat authors.
Steam Deck
Epic’s sentence is narrow. The Steam Deck does not support the required features for EAC Linux v2. Epic is talking with Valve and hopes to support it in the future. The same post says the Easy Anti-Cheat team keeps an open line with Valve about Steam hardware generally. Hope and a conversation are not a Deck build of Fortnite. If your community is mostly Deck players, the October 14 posts are a reason to watch, and they are not a patch-note line that says Fortnite now runs on the Deck.
What this means if your game uses Easy Anti-Cheat
Developers who already turned on the older Linux EAC path will be able to choose. Epic says they can stay on the older implementation for compatibility or move to EAC Linux v2 for stronger protection, after Epic has validated v2. Validation is the Fortnite pilot. Your opt-in does not flip on October 14 because a launcher preview exists.
If your game has never opted into Linux EAC, nothing in the launcher preview opts you in. Players may still try a Windows build through the compatibility download GamingOnLinux observed. That is a player-side experiment until you support it. Write the store page accordingly. “The Epic launcher has a Linux client” and “our competitive mode is supported on Linux” are different sentences, and only the first one became true for Epic’s own client on October 14.
What to do on Monday
Pick one machine role before anyone installs anything.
| Machine role | Action this week | Stop when |
|---|---|---|
| The PC that must open Unreal or UEFN tomorrow | Leave the legacy launcher in place. Do account work there. | Someone needs the legacy app and it is already gone |
| A spare PC, or a spare OS install, that can be wiped | Download from launcher.epicgames.com, sign in, and write down what is missing | You are about to use it as the only install |
| An Intel Mac | Do not install the preview. It is unsupported | The FAQ changes |
| A Linux box on Ubuntu 22.04, Fedora 43, or Debian 12 | You may try the native launcher. Check each game before you install it | You are about to tell players Fortnite or your EAC game is supported |
| Anything else | Read the distro line again. Untested can still be interesting. It is not a support promise | A customer ticket assumes you tested it |
On the spare machine, run this pass once and keep the notes.
- Confirm the OS is on the supported list, including Apple silicon if it is a Mac.
- Install, sign in, and see whether purchases and installed games appear.
- Open one game you already trust, or open the editor if this spare box has it, and confirm the store post’s “once you are in the tool” claim on that box.
- Open the download panel and see whether active, queued, scheduled, and failed rows match the post.
- Try the social action you actually use. If it is missing, that matches the known-limitations line. File it with Send Feedback.
- If the box is Linux, install one Windows-only store game only if you are willing to accept a compatibility layer, and record whether a one-time runtime download appeared.
- Do not publish a player-facing “we are on the new launcher” note from this pass. The full release is still gated on stability and parity, per The Verge’s briefing.
If the spare pass fails in a way that blocks play, you still have the shipping PC on the legacy app. That is the whole point of the split. The preview site tells you the try replaces the legacy install. Believe that sentence on the first machine you choose.
Teams who already fight the legacy installer can keep using the cache, permissions, and antivirus pass in the stuck-percent help page. That page is about the launcher you have. It does not become a preview migration guide because the buttons moved.
Common mistakes
Calling the preview the full release. Epic’s own page puts you at “Preview,” with “Stable release” still ahead, polished with feedback. Keely’s briefing matches that. There is no forced cutover date in the sources above.
Equating the Linux launcher with Fortnite on Linux. The launcher is in preview on three distro families. Fortnite waits on EAC Linux v2, maintainers, and a pilot. The store post uses “coming.” The EAC post says Fortnite is not available on Linux yet.
Quoting 5.47 seconds as your laptop. Those seconds are an average that excluded the three lowest-end machines in a 13-machine Keywords Studios set, compared with Steam, in October 2026. Time your own cold start if the number is going into a deck.
Installing on the only editor machine. The uninstall line is on the install step. Account data is supposed to survive. The shortcut your runbook clicks may not.
Testing the preview on an Intel Mac and filing it as a bug. Epic already marked Intel Macs unsupported.
Telling Deck players Fortnite is next week’s patch. Epic says the Deck does not support the EAC v2 feature set and that talks with Valve are underway.
Pasting “vibe coded” as your test report. It is Epic’s opening line, and The Verge has a briefing about AI assistance. Neither one is a result from your spare machine.
Assuming every Windows store game is now a Linux build. Many remain Windows builds. The FAQ tells you to check each game and to expect a compatibility layer where that is true.
What this page is for
Use it when someone asks what the October 14 preview changed. The answer is a new client, a real Linux launcher on a short distro list, an installer that removes the legacy app, a thinner feature set, commissioned speed numbers, and a separate anti-cheat plan whose Fortnite pilot has not shipped.
The refusal for a machine you still ship from is Stop Replacing Your Only Epic Games Launcher with the Preview. A spare-machine worksheet is Epic Games Launcher Preview First Indie Lab Worksheet 2026. This URL stops at the facts those sittings need. The Unreal guide and the UEFN course remain the right next step when the task is learning the engine, on whichever launcher still opens it.
Key takeaways
- On October 14, 2026 Epic opened an Epic Games Launcher Preview for Windows, Apple silicon Macs, and Linux.
- The preview site says trying it automatically uninstalls the legacy launcher on that computer.
- Purchases, installed games, cloud saves, and progress are supposed to carry over with the account. The FAQ says switching should not damage that data.
- The Verge reports that the old launcher remains available as a product and that Epic has no date for a forced move.
- Intel Macs are unsupported. macOS 12 or newer on Apple M1 or newer is the Mac preview.
- Supported Linux families are Ubuntu 22.04 LTS or newer, Fedora 43 or newer, and Debian 12 or newer. Other distros are untested.
- The launcher is native on Linux. Many games are still Windows builds and may need a compatibility layer.
- Fortnite on Linux is not shipped. EAC Linux v2 is a pilot plan with eight published requirement areas and no date.
- The Steam Deck does not meet those EAC v2 requirements, according to Epic, while Epic talks with Valve.
- Cold-start figures of 5.47 s versus Steam’s 10.07 s come from a Keywords Studios test Epic commissioned, excluding the three lowest-end machines.
- Once a game or developer tool is open, Epic says the preview should not block development or casual and competitive play. That says nothing about the uninstalled legacy shortcut.
- Send Feedback inside the launcher is the bug path Epic repeats.
FAQ
Is the Epic Games Launcher Preview the new required launcher?
No. Epic is calling the October 14 build a preview and showing a stable release as a later step. The Verge quotes Martin Keely saying there is no specific timeline for a forced move, and that the full launch waits on stability and feature parity. You can keep shipping on the legacy launcher.
Does installing the preview remove the old launcher?
On the computer where you install it, yes. The preview site says trying the new launcher automatically uninstalls the legacy version. The Verge’s report that the old version remains available describes the product Epic still offers, not a side-by-side install on that PC.
Will my games and cloud saves disappear?
Epic says purchases, installed games, cloud saves, and progress carry over because they are tied to the account, and that switching between the legacy launcher and the preview should not affect your data. If a row is missing, use Send Feedback. Local saves that never synced are still local files.
Can I play Fortnite on Linux with this preview?
Not as a shipped Fortnite Linux client. Epic says Fortnite is coming to Linux after EAC Linux v2 works with enough distro maintainers. The EAC post says Fortnite is not on Linux yet and that Fortnite will be the first pilot. The Verge reports no timeline.
Which Linux distros does Epic support for the launcher?
Ubuntu 22.04 LTS or newer, Fedora 43 or newer, and Debian 12 or newer. Other distributions may work and are not officially tested or supported. The launcher’s support list is separate from the longer EAC Linux v2 requirement list.
Does the preview run on Intel Macs?
No. Epic says the macOS preview supports Apple silicon only and that Intel Macs are not supported. The OS floor is macOS 12 Monterey or newer, on an Apple M1 or newer.
Are Epic’s startup numbers a promise for my PC?
They are Epic’s published average. Keywords Studios ran five tests on each of 13 machines in October 2026, Epic commissioned the test, and the average excludes the three lowest-end machines. Epic says individual results vary. The 5.47-second cold start is versus Steam’s 10.07 seconds in that test, not a measurement of your legacy install.
Can I still develop in Unreal or UEFN if I do try the preview?
Epic’s updated store note says that once you are in a game or developer tool, nothing there would prevent development or casual and competitive play. Confirm that on a spare machine. The note does not restore a legacy install the preview uninstalled, and the FAQ says some account-management options are still missing.
Where to leave it
The preview is worth a spare machine and a written list of missing buttons. It is a poor candidate for the only launcher on a PC that has to open the editor tomorrow. Linux players got a native store client on a short distro list, and a public anti-cheat plan that still has to pass a Fortnite pilot before other EAC games get the new path. Quote the store post, the preview site, and the EAC Linux v2 post when the claim is Epic’s. Quote The Verge when the claim is the briefing. Then time your own cold start if the number is going to leave the building.