Three Routes to Running Verse Today

1. Route One: Install UEFN — the Only Place Verse Genuinely Runs Today

Let’s be blunt: as of today, the only place that can genuinely compile and run a piece of Verse is UEFN (Unreal Editor for Fortnite, the creation environment for Fortnite). UE6 Early Access targets the end of 2027 and has not shipped; and in UE 5.8, the current stable production target, Verse is not yet used in production either. So if you want to see your own code come alive, today there is exactly one road.

To be clear about its role on this site: UEFN is a tool, not the subject. We are not teaching you to build Fortnite islands — we are borrowing its compiler and output log to run the Verse language in front of you.

The whole flow is roughly six steps:

1. Install the editor. Sign in to the Epic Games Launcher with an Epic account and install UEFN (Windows / macOS). It is a separate editor from UE5, not a UE5 plugin. First use requires accepting the relevant creator terms.
2. Create a project. The emptiest island template is plenty — what you want is a container that compiles, not a fun map.
3. Create a Verse file. Open the Verse Explorer panel, right-click the project to create a new Verse file, and pick the Verse Device template. What it generates is a close relative of the hello device from Lesson 1.
4. Edit the code. Epic’s recommended editor is VS Code, and the Verse extension installs alongside UEFN. This is where you first see syntax highlighting and completion.
5. Compile. Back in UEFN, hit Build Verse Code. On success, the device type you wrote shows up in the Content Browser and can be dragged into the level like any official device.
6. Launch a session. Hit Launch Session for a playtest. This step is “running” — only now does Print output appear in the Output Log.

The one thing to remember first: compiling is not running. A successful Build only means the code is legal; without launching a session, OnBegin is never called and of course the log stays empty. “Clicked Build, then stared at an empty log” is every newcomer’s initiation rite, and you get to skip it.

The costs, stated plainly: you need an internet connection, an Epic account, and a whole Fortnite creation environment on disk, which is not small and takes some patience to download the first time. If that is inconvenient right now, take route two below — you can still read this handbook cover to cover.

2. Route Two: Read-Only Practice — No Engine, Still the Whole Syntax

This route is underrated. The genuinely hard part of a programming language is the rules and the mental model — why = is not assignment, how indentation can replace wires, why failure is not an exception. None of that needs a compiler; it only needs you to be willing to run the code in your head.

Every lesson on this site is designed for exactly that use. Code blocks to read, a stepper to watch execution order line by line, fill-in-the-blanks and quizzes that force you to think before the answer is visible. The recommended reading method:

• ◇ Read the code block first and do not touch the stepper: mark out, in your head or on paper, the execution order and what each line does;
• △ Then click “Run Next Step” and check yourself step by step — wherever you were wrong is exactly your knowledge gap;
• ▢ Finally read the “Blueprint Comparison” section and hang the new knowledge onto Blueprint concepts you already own. What gets hung on something stays.

What this route gives you: the full syntax and rules of the language, the Blueprint-to-Verse vocabulary mapping, and the ability to read other people’s code. What it does not give you: feel — what a compile error looks like, how assets and files are organized, which pane the log lives in, which button to press after editing. The good news is that this layer is shallow: half an hour after you install UEFN or UE6 you will have it. The reverse is not true — no amount of button-pressing produces an understanding of the language.

3. Route Three: Wait for UE6 Early Access

A perfectly legitimate choice, especially if you have a live project on UE5. The facts first: UE6 Early Access targets the end of 2027 and has not shipped; Actors and Blueprints are fully supported in UE6 Early Access and early versions; deprecation waits for Scene Graph to be mature enough, with no date announced; Epic has committed to providing conversion tools before deprecation, but they have not shipped.

So waiting does not make you miss a bus. The one caveat: a waiting period is not a blank period. Conversion tools will move your assets for you one day; what they cannot move is judgment — somebody still has to read, edit, and review the screenful of Verse they produce. If that somebody is you, every lesson you read now is a head start.

One common misconception worth heading off: do not go looking for Verse in UE 5.8. UE 5.8 is the current stable production target, and Verse is not yet used in UE5 production. To run Verse today, go back to route one.

4. Whichever Route: You Are Learning a Language, Not an Editor

This is the sentence this page most wants you to take away. After the move to UE6, not a word of Verse syntax needs relearning; what changes is the framework it hangs on. The table below separates “changes” from “does not change”:

Read that table and you know where the time should go: the hours you put into the top two rows — syntax and type system — are money in the bank; the bottom three are API memory, which you look up anyway and which changes with versions regardless. That is also this site’s trade-off: the vast majority of the pages go to the language, the framework waits for Chapter 8’s Scene Graph, and we always flag which bits are specific to today’s UEFN.

5. Quick Check

Sources & Further Reading

This page draws on Epic’s official documentation and official news:

• Playtesting Your Island in UEFN (official documentation) ↗
• Verse Language Quick Reference (official documentation) ↗
• Epic official news: “The road to UE6” (unrealengine.com) ↗