Unreal Engine Download: How to Install UE5 on Windows, Mac, and Linux

Unreal Engine Download: The Complete 2026 Install Guide

Downloading Unreal Engine is the first real step for anyone serious about building games, cinematics, virtual production sets, or interactive simulations. Epic Games made the engine free for creators, and the install process is straightforward once you know where to click. Still, plenty of first-time users hit snags. Maybe the Epic Games Launcher refuses to open. Maybe the download stalls at 80 percent.

Maybe you're on a Mac and can't find the right build. This guide walks through every path: Windows, macOS, and Linux. You'll see system requirements, account setup, launcher install, engine version picks, and the common gotchas that derail new developers. By the end, you'll have UE5 running on your machine and know exactly which folder to open when you want to start your first project.

Before you click anything, a quick reality check. Unreal Engine is large. The download itself runs roughly 12 to 25 GB depending on version and platform options. After install and a few starter content packs, expect 40 to 80 GB of disk usage. On older drives that fills up fast, so plan storage before you start. And one more thing worth knowing upfront: you don't need a paid license to download or use the engine for learning, prototyping, or even shipping commercial games. Royalties only kick in past certain revenue thresholds, which we'll cover later.

What You Need Before You Download

Unreal Engine is demanding. Not impossibly so, but you can't run it on a budget laptop from 2014 and expect smooth editor performance. Epic publishes minimum specs, but in practice you want headroom above the minimum. Here's the realistic baseline. CPU: quad-core x86_64 at 2.5 GHz or better. Apple Silicon (M1, M2, M3, M4) is supported natively on macOS. RAM: 16 GB minimum, 32 GB strongly recommended.

The editor caches assets aggressively, and shader compilation alone will eat through 8 GB. Storage: a fast SSD with 100 GB free. Mechanical drives technically work, but project load times become brutal. GPU: a DirectX 12 or Vulkan capable card with at least 6 GB VRAM. Nvidia RTX 2060, AMD RX 5700, or better. For Apple Silicon Macs, the integrated GPU handles most editor work fine for indie projects.

OS versions matter too. Windows 10 64-bit version 21H2 or newer, with Windows 11 22H2 recommended. macOS 12.5 Monterey minimum, with Sonoma or Sequoia preferred. Linux support is community-maintained but officially endorsed; Ubuntu 22.04 LTS works reliably. You also need an Epic Games account. It's free, and you'll use it for the launcher, marketplace purchases, and any FAB asset downloads. Sign up at the Epic Games website before you start the launcher install. Two-factor authentication is encouraged, and Epic now requires it for marketplace purchases over a certain threshold.

Step-by-Step: Download on Windows

Windows is the most polished path, mostly because Epic builds the engine and launcher there first. Start by going to unrealengine.com and clicking Download in the top navigation. You'll land on the licensing page. Pick the Publishing License (the default) unless you specifically need the Creators License for non-game work like film or architecture. Both are free for the relevant use cases.

Next you'll download the Epic Games Launcher installer. It's a small EpicInstaller.msi file, usually under 100 MB. Run it. Accept the install location (default is fine for most users) and let it pull down its core files. Once installed, sign in with your Epic Games account. If you don't have one, the launcher will walk you through creation. After sign-in, look at the left sidebar. You'll see Store, Library, FAB, and Unreal Engine. Click Unreal Engine. This is the engine management hub.

Inside Unreal Engine you'll see three tabs: Library, Marketplace (now FAB), and Twinmotion (if you have that). In the Library tab there's a section called Engine Versions. Hit the plus icon to add a new version slot. Pick the version you want. UE 5.5 is the current stable as of late 2025, with 5.6 in active development. For most learners, grab the latest 5.x. Click Install.

You'll be prompted for an install path (default is C:\Program Files\Epic Games\UE_5.5) and a list of optional components. Engine source is needed only if you plan to compile from scratch. Target Platforms lets you skip mobile or console builds if you only target PC. Trimming components shaves gigabytes off the download.

Click Install and wait. On a fast broadband connection (200+ Mbps) and a modern SSD, the full download and install runs 20 to 45 minutes. The launcher shows progress in real time. Once done, you'll see a Launch button next to your engine version. That's it. Click Launch and the editor opens to the project browser.

Step-by-Step: Download on macOS

Mac install is nearly identical to Windows, but with a few platform quirks worth flagging. Apple Silicon Macs (M1 through M4) get native ARM64 builds, which run noticeably faster than older Intel-via-Rosetta builds. If you're on Intel Mac hardware from before 2020, you can still run Unreal, but performance is markedly worse and Epic may drop Intel support in future releases.

Go to unrealengine.com, click Download, accept the license, and you'll be offered a .dmg installer. Open the .dmg, drag the Epic Games Launcher icon to your Applications folder. First launch will trigger a Gatekeeper prompt. macOS asks if you really want to open an app from an identified developer. Click Open. Sign in with your Epic account. The interface mirrors Windows: Library tab, Engine Versions, plus icon, pick a version, install.

One Mac-specific note: full text shader compilation is slow on macOS because Metal differs from DirectX, and the editor has to recompile a lot of starter content on first launch. Expect 10 to 20 minutes of shader work the first time you open a new project. After that it's cached and much faster. Also, the default install path on Mac is /Users/Shared/Epic Games/UE_5.5. Keep this in mind if your Mac is space-constrained and you want to redirect to an external SSD.

Apple Silicon Performance Notes

The M1, M2, M3, and M4 chips run Unreal well for editor work and small to mid-size projects. AAA-scale scenes with Nanite and Lumen will push them harder. M3 Pro and M3 Max handle Unreal smoothly for solo and small-studio work. If you're targeting iOS or macOS as a build platform, Apple Silicon is the obvious choice because you can compile and test on the same hardware.

Linux Install: A Different Path

Linux users don't get the Epic Games Launcher. Epic publishes a binary build for Linux, but distribution happens through their website portal and GitHub source repository. The official binary release is a tarball you download, extract, and run directly. Go to unrealengine.com, sign in, and visit the Linux download page (find it under the Get Unreal section). You'll see a current binary release link, usually a .tar.gz around 12 GB compressed.

Extract it somewhere with plenty of space: tar -xvf Linux_Unreal_Engine_5.5.0.tar.gz -C ~/UnrealEngine. After extraction you'll have a directory roughly 50 GB on disk. To launch, cd into the Engine/Binaries/Linux directory and run ./UnrealEditor. The first launch builds shader caches and pulls a couple of needed runtime files. On Vulkan-capable hardware (which is most modern Nvidia and AMD cards), the editor runs well. Performance on AMD with Mesa drivers has improved significantly through 2024 and 2025.

The harder path: if you want engine source to modify or compile, link your Epic and GitHub accounts at unrealengine.com/account, then accept the EULA invite on github.com/EpicGames/UnrealEngine. Clone the repo. Be warned, the full source repository is hundreds of gigabytes after Setup.sh pulls down dependencies, and compilation takes several hours on a fast machine. Most Linux users stick with the binary release unless they need engine modifications.

Common Download and Install Problems

The Unreal Engine download is mostly painless on a healthy machine. But when things go wrong, the same handful of issues come up over and over. Knowing the fixes saves hours. The most common: the Epic Games Launcher won't launch after install. On Windows this is almost always permissions or a corrupted webcache. Right-click the launcher shortcut, pick Properties, head to Compatibility, and check Run as administrator. Or delete %localappdata%\EpicGamesLauncher\Saved\webcache and restart. That clears the launcher's internal browser cache, which trips up logins and the storefront.

Another frequent issue: download speed crawls to under 1 MB/s on a 200+ Mbps connection. Epic uses a content delivery network that occasionally routes you to a distant edge node. In the launcher settings, under Manage Games, look for Throttle Downloads and confirm it's off. Then try restarting your router. If speeds are still bad, set a manual DNS like Cloudflare 1.1.1.1 or Google 8.8.8.8 and retest.

Disk space errors are simpler: the launcher does check free space before starting, but if you fill the drive during install, it'll error out. Move temp directories or pick a different install drive in the Engine Versions settings. The launcher lets you change install location per version without re-downloading the launcher itself.

Verify Installation Integrity

If the editor crashes on launch or you suspect a corrupted install, run a verify operation. In the launcher, click the dropdown arrow next to your engine version and pick Verify. The launcher hashes every installed file against the manifest and re-downloads anything corrupted. This typically takes 10 to 30 minutes depending on disk speed but resolves the majority of post-install issues.

After the Download: First Project, First Open

Once Unreal Engine is installed and you've clicked Launch, the editor opens to the Project Browser. This is where most new users get a little lost. The browser has three sections: New Project, Recent Projects, and Sample Projects. Sample Projects pulls from Epic's free learn library, things like the Lyra starter, City Sample, and Stack-O-Bot.

These are massive downloads (Lyra is around 30 GB by itself) so don't grab them unless you have the disk space. For your first project, pick New Project. You'll see templates: First Person, Third Person, Top Down, Vehicle, and a handful of category-specific options like Architecture, Film, and Automotive.

Pick Third Person for a balanced starting point. It loads quickly, has a working character, and gives you something to fly around in. Set a project name, pick a location (separate from the engine install, your projects live in their own folder), and confirm Starter Content is checked if you want some default materials and props.

Hit Create. The editor builds the project and opens. First time, expect shader compilation in the bottom right corner. Anywhere from 30 seconds on a fast Windows rig to 10 minutes on a Mac. Once compilation finishes, hit Play in the toolbar and you're walking around a 3D world that you can edit in real time.

One thing worth saying clearly: don't try to learn Unreal by jumping straight into your dream game. The engine is huge. Materials, Blueprints, lighting, Niagara particles, Nanite, Lumen. Every system has its own depth. Spend a few weeks following Epic's official tutorials on the Unreal Online Learning portal. It's free, video-based, and structured from beginner to advanced. The Lyra Starter Game is also an excellent reference once you've grasped basics. Treat downloads and installs as the easy part. The actual learning curve is where most beginners need to be patient.

Licensing, Royalties, and Marketplace Considerations

One question that comes up constantly during download: am I going to owe Epic money? The short answer for most learners and indie developers is no. The Unreal Engine End User License Agreement is generous. You can download and use the engine free for any non-commercial purpose: learning, portfolios, internal tools, research, education. For commercial games, the royalty structure is a flat 5% on gross revenue exceeding $1 million per product over that product's lifetime, with the first $1M completely royalty-free. The Creators License (for non-game work like film, architecture, broadcast, and design visualization) is entirely royalty-free regardless of revenue.

The FAB marketplace (which replaced the old Unreal Marketplace and Quixel Bridge in 2024) is a separate consideration. Free assets are abundant and many are great quality. Megascans, audio packs, blueprints, and full template projects show up regularly. Paid assets range from a few dollars for single props to several hundred for entire game frameworks. None of these are required for download or basic use. You can build entire games using only the starter content and your own creations.

If you plan to ship a commercial product, two practical bits of advice. First, save the Custom License Agreement option for later. Epic offers per-title or per-studio custom deals that can reduce royalties for large publishers, but the default 5% is fine for most indies. Second, keep your project under royalty thresholds during development by tracking gross revenue from launch. Royalties are reported quarterly. There's no surprise audit if you're transparent.

Final Thoughts on Getting Started with Unreal Engine

Downloading Unreal Engine is the easy part. The hard part, and the rewarding part, is what comes after. The engine you've just installed powers titles like Fortnite, Senua's Saga: Hellblade II, the new Tomb Raider, and an enormous portion of the animated film and virtual production industry. Marvel, Disney, the BBC, and Lucasfilm all use Unreal for in-camera VFX on shows like The Mandalorian. The same toolset is sitting on your hard drive right now. That's wild to think about.

If you're new to game development, the next steps look something like this. Spend a week or two going through Epic's official Online Learning paths. The Blueprints introduction is essential, and the Lyra Starter Game tour gives you a real-world reference. Don't try to ship a finished game in your first month. Build small experiments: a working door, a working pickup item, a simple AI patrol. Each tiny mechanic teaches you a system. Once you've stacked enough small wins, the engine starts feeling familiar instead of overwhelming.

If you're coming to Unreal from another engine like Unity, Godot, or GameMaker, give yourself time to unlearn habits. Unreal's component system, Blueprint visual scripting, and asset pipeline work differently than what you're used to. Don't force C# patterns into a C++ codebase. Don't try to recreate Unity's prefab system one-to-one in Blueprint actors. Lean into Unreal's strengths: the rendering pipeline, the cinematic tools, the procedural content generation, the Niagara particle system. These are areas where Unreal genuinely outpaces competitors. Build the kind of project that takes advantage of them.

One last practical tip. Keep your engine install on a different drive from your project files, and back up your project folder regularly. Engine corruption is rare but recoverable; project corruption without backups is a nightmare. Git LFS or Perforce work well for version control on Unreal projects.

Both handle the large binary assets that crash standard Git. Even for solo work, run nightly local backups to a second drive. You'll thank yourself the first time a power outage corrupts your editor session. The download is just the start. Build the habits early and Unreal becomes one of the most productive creative environments you'll ever use.