Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 38 ยท Getting Started

Unreal Engine Versions, Licensing and Requirements

Understand Unreal Engine version numbers, which release to choose, how the license and royalties work in general, and the hardware that different features need.

Before you start a long project, it pays to understand three practical questions: which engine version to use, what the license means for money you earn, and what hardware your players need. This lesson gives general guidance. Epic changes details over time, so always read the current official license terms before shipping a commercial product.

Version numbers

Unreal Engine 5 releases are numbered 5.0, 5.1, 5.2 and so on. Each one is a "minor" release with new features, deprecations and sometimes breaking changes. Between them come hotfixes (5.4.1, 5.4.2). Early releases are marked as preview builds in the launcher.

Practical rules:

  • Start new projects on the newest stable release that all the plugins you need support.
  • Do not upgrade a project mid-production unless a feature or fix is worth the migration work.
  • Keep a copy (version control) before you open a project in a newer engine. Opening converts the project; going back is not supported.
  • A project records its engine version in its .uproject file as EngineAssociation.
Python Stand-in: reading a .uproject file

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A .uproject is plain JSON. A project with no Modules entry is Blueprint-only.

Licensing in general terms

Epic offers Unreal Engine for free to download and use. For games and most other products the general model has been:

  • No cost to learn and prototype.
  • A royalty on gross revenue from a product above a threshold (historically 5 percent after the first million US dollars per product), with exceptions, for example revenue from sales through the Epic Games Store, and different terms for some non-game uses.
  • Custom licenses for large companies or special needs.

Treat the list above as a map, not as legal advice. Thresholds, exemptions and the treatment of non-game industries such as film, architecture and education have changed before. Read the current EULA and pricing page on Epic's website, and ask a lawyer if real money is involved.

Third-party assets bring their own licenses. A marketplace asset may be allowed in your game but not in a competing asset pack. Always check each asset's terms.

Python Stand-in: a royalty calculator (illustration only)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Hardware requirements for features

Not every feature runs on every machine, and the minimum PC for your game depends on what you enable.

Feature Practical consequence
Lumen, Nanite, Virtual Shadow Maps Need a modern GPU with DirectX 12 / current Vulkan support
Hardware ray tracing Needs a ray-tracing-capable GPU
Mobile (Android, iOS) Use the mobile renderer and its limits (lighter materials, fewer lights)
Consoles Need a developer account and platform SDK from the console maker
Dedicated servers Need a source-built engine

The editor itself needs a stronger machine than a packaged game. You choose a scalability level (Low, Medium, High, Epic, Cinematic) to trade quality for speed; you will practise that in the performance chapter.

Choosing a project's target early

Decide these on day one, because they are hard to change later:

  1. Platforms: PC only, PC and console, mobile?
  2. Renderer features: do you need Lumen, or the cheaper forward/mobile path?
  3. Scale: small levels or one huge open world (World Partition)?
  4. Team: Blueprint-only artists, C++ programmers, or both?
flowchart TD
  A["New project"] --> B{"Mobile or low-end target?"}
  B -- "Yes" --> C["Mobile renderer, simple materials"]
  B -- "No" --> D{"Need dynamic lighting?"}
  D -- "Yes" --> E["Lumen + Nanite"]
  D -- "No" --> F["Baked lighting, fast on weak GPUs"]

Platform choices steer the renderer features.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What should you do before opening an old project in a newer engine version?

    Opening converts the project; downgrading is not supported, so keep a copy.
  2. 2. In which file is the project's engine version stored?

    The .uproject JSON has an EngineAssociation field.
  3. 3. Which statement about licensing is the safest?

    Terms and thresholds have changed over time, and assets carry their own licenses.
  4. 4. A .uproject file has no Modules entry. What does that mean?

    C++ modules are listed in Modules; none means Blueprint-only.

Summary

  • Use the newest stable 5.x for new projects and avoid upgrading mid-production without a backup.
  • The license is free to start; commercial products may owe royalties above a threshold. Always read the current terms.
  • Features like Lumen and Nanite need modern GPUs; choose platforms early.
  • The .uproject file is JSON and records the engine version, modules and plugins.

Next: Creating Your First Project