Odds are one sentence pushed you here: "UE6 is deprecating Blueprints." This lesson won't comfort you and won't scare you. It does four things: define what "deprecate" actually means in engine land; lay the publicly known timeline out as a table with every row tagged as already happened, promised, or not yet announced; answer the three questions that actually matter to your project; and finally talk about the thing that doesn't have an official name yet — the one the community calls Visual Verse.
In everyday English, "deprecated" sounds like "thrown away". In engine development it's a technical move with a fixed meaning, made of three parts, none of them optional:
Unreal has run this play twice already. Matinee (the UE4-era cinematics system) was marked as no longer supported once Sequencer arrived, Epic shipped a Matinee to Level Sequence conversion plugin, and it only actually disappeared from the engine in UE5 — roughly five to six years from "replacement exists" to "gone". Cascade (the old particle system) is even starker: its replacement Niagara showed up around UE 4.20 as Early Access and became production-ready around 4.25; Cascade was marked deprecated around the UE5 mark and Epic shipped a Cascade to Niagara converter plugin — and to this day, in UE 5.x, Cascade is still sitting there, opening and running just fine.
So when you read "Actors and Blueprints will be deprecated", the correct translation is not "deleted tomorrow". It is: one day Epic will say "new projects should use Scene Graph", hand you conversion tools, and your existing Blueprints will keep working for a long time after that. As for when that day comes — that's the next section.
The reason UE6 discourse is such a mess is that most articles write three very different kinds of information in the same tone of voice: things that have already happened, things Epic has promised but not yet delivered, and things Epic hasn't announced at all. The table below keeps them apart. The status column is the whole point.
| Event | When | Status |
|---|---|---|
| Verse ships with UEFN and starts running in production on Fortnite islands | March 2023 to today | Already happened |
| State of Unreal 2026 (Chicago): Epic announces UE6, merging UE5 and UEFN into one engine | 2026 | Already happened |
| UE 5.8 ships and is positioned by Epic as the current stable production target | 2026 | Already happened |
| Scene Graph: UE6's new gameplay framework, built from scratch on Verse (entity + component) | Ongoing with UE6 | Announced, still in development |
| UE6 Early Access | Targeted for the end of 2027 | Promised (a target, not a ship date) |
| Actors and Blueprints fully supported in UE6 Early Access and the early releases | From UE6 EA | Promised |
| Conversion tools to move projects from the old framework to the new one | Before deprecation | Promised, but not yet released; coverage and form not yet announced |
| Actors and Blueprints get deprecated | Once Scene Graph is sufficiently mature | No date given |
| A visual scripting layer for Verse (the community calls it Visual Verse) | — | Form not yet announced, still under research |
| The UE6 full release (not Early Access) date | — | Not yet announced |
| Actors and Blueprints removed from the engine | — | Not yet announced; Epic has given no date at all |
Reading the table is simple: only the "already happened" rows can be used to plan, the "promised" rows can be used to set direction, and the "not yet announced" rows can only be used to stay curious. Any article that tells you the year Blueprints will disappear is, by that fact alone, telling you a year Epic never said. The full row-by-row breakdown with sources and confidence labels is in the first extra at the bottom of this page.
No. That answer has no "but", only reasons:
What should change isn't whether you build, it's how. There are five things that cost almost nothing, that you can start today, and that pay off whether or not UE6 ever arrives — that's the third extra on this page.
Yes — and no, you don't need to panic. Those two halves need separate explanations, because their reasons are completely different.
Why you should: Verse is not "a UE6 thing". It has been running in production in UEFN since March 2023 and hasn't stopped since. You can write it, compile it, and ship it to players today — this is not an experimental language waiting for launch day, it's a language already in service. More importantly: UE6's new gameplay framework, Scene Graph, is built from scratch on Verse. Learning Verse isn't "learning a language that might be useful someday" — it's learning the foundation your future gameplay sits on.
Why you needn't panic: you have plenty of time, and you already know the hard part. UE6 Early Access is still more than a year out, and the full release is further still. At a few hours a week you'll be comfortable long before it lands. And more than that — you're bringing more with you from Blueprints than you think: when an event should fire, which layer state belongs on, who owns which piece of logic, whether this reference is about to drag an entire asset chain into memory. That is gameplay logic design skill, and it belongs to no particular syntax. Changing languages changes how you write, not what you write.
Put bluntly: what expires is never the skill, only the muscle memory in your fingers. What you have to relearn is symbols and rules — a few weeks. What you don't have to relearn is judgement — the thing that took you years.
The facts first: Epic has committed to providing conversion tools before deprecation, but the tools have not been released, and their form and coverage have not been announced. Anyone claiming to know how much the conversion tools will cover is guessing today — including the passage below, which rests on history, not on a promise.
What history can tell us is that Epic really does ship conversion tools when it swaps a framework out, and that those tools really are useful. Matinee to Sequencer had an official conversion plugin; Cascade to Niagara had one too. What they could carry across was broadly the same category of thing:
| Automatic conversion carries this | Automatic conversion cannot carry this |
|---|---|
| Assets and file structure, variables and defaults, node topology, parameter values, naming | Why there's a 0.2-second delay here; why that reference is deliberately a soft one |
| Ordinary nodes whose counterpart is obvious at a glance | Constructs with no counterpart — you get a placeholder and a warning |
| A result that compiles and runs | A result that fits the new framework's idioms and that somebody is willing to maintain |
One sentence sums up the historical lesson: automatic conversion carries structure, not design intent. What comes out usually "runs", but it reads like machine translation — grammatically flawless, entirely soulless. In the last big migration, the time sink was never the conversion step; it was the read-through, the refactoring, and the judgement calls afterwards. Which is why what really determines your migration cost is not the tool's coverage — it's whether you can read what comes out of it.
So the right expectation is this: treat conversion tools as a way to skip the heavy lifting, not a way to skip the understanding. The more Verse you know, the more that generated code looks like a draft; the less you know, the more it looks like a black box you're afraid to touch. A full post-mortem of the last migration is in the second extra on this page.
Name first: "Visual Verse" is the community's label for "a visual scripting layer for Verse". It is not a confirmed product name. Only two things can be said today. Epic has indicated that Verse will get a visual scripting layer; and what that layer looks like — node-and-wire like Blueprints, or block-stacking like Scratch — has not been announced. Both descriptions have shown up as options in Epic's creator-facing research, which means Epic is still gathering opinions. The community has plenty to say about whether a block-based system would weaken professional workflows, but that is community opinion, not an Epic decision — don't relay it as a conclusion.
The thing actually worth thirty seconds of thought is a different one: even once a visual layer exists, understanding the underlying language remains the hard currency.
That isn't a pep talk, it's something you've already verified. Underneath Blueprints sits C++ — and the people around you who use Blueprints best are usually the ones who can read that C++. They know which node hides an expensive iteration, why this pin has to be that type, what the compiler is actually complaining about. A visual layer is always a front end for a language: it decides how you type, not what things mean. Behind the nodes there will still be Verse's types, Verse's failure contexts, Verse's concurrency rules. Without the layer underneath, all you can do in the visual editor is guess and retry. With it, you're the one calling the shots at either layer.
And one more practical reason: the visual layer hasn't shipped, and Verse can be written today. Rather than waiting for something whose shape is undecided, learn the language now — when it arrives, all that changes is your input method.
This lesson has no syntax to compare, but it has something more reassuring: a table of where each thing in your Content Browser ends up in the UE6 world. The "confirmed / undecided" labels in the last column are the point. Confirmed means the direction has been stated publicly by Epic, or the counterpart already exists in Verse today. Undecided means Epic has not announced the details — don't start work based on anybody's guess.
| The thing in Blueprints | Where it lands in UE6 | Difference and status |
|---|---|---|
| Blueprint Class (a Blueprint deriving from Actor) | A Verse class, plus an entity built from components in Scene Graph |
Confirmed: from "inherit down an Actor tree" to "attach components to an entity". Exact API undecided |
| Actor Component | A Scene Graph component | Confirmed: the name barely changes, the meaning does — components go from "an Actor's accessory" to the primary unit of organizing behavior |
| Level Blueprint | A Verse script attached to the level | Confirmed in direction; exact attachment form undecided. Note in passing: the old rule "don't put logic in the Level Blueprint" is about to be worth twice as much |
| Blueprint Interface | Verse's interface |
Confirmed: Verse has interfaces today, and the concepts map almost one to one |
| Blueprint Function Library | Free functions in a Verse module, pulled in with using |
Confirmed: no more inventing a fake class to hold utility functions — functions can just live in a module |
| Blueprint Macro Library | No one-to-one counterpart; split into ordinary functions | Confirmed: Verse has no Blueprint-style macros. This is the one common asset in this table with no counterpart |
| Variables panel + Instance Editable in the Details panel | Fields on a Verse class, plus @editable |
Confirmed: this is exactly how it's written in UEFN today; later lessons cover it in detail |
| Event Dispatcher / Bind Event | Verse events and subscription (Subscribe) |
Confirmed: Verse already has this today; Chapter 7 goes deep |
| Construction Script | No publicly announced counterpart | Undecided: Epic hasn't announced how edit-time construction is written in Scene Graph |
| Animation Blueprint, Widget Blueprint and other specialized Blueprints | Not yet announced | Undecided: these are separate subsystems and Epic hasn't spelled out their individual timelines |
| The node graph itself (dragging wires, right-click search) | Verse text, plus the future visual layer | Undecided: the visual layer's form has not been announced — see section 6 |
Where do these differences come from? From one root distinction: a Blueprint is "an asset plus a graph"; Verse is "a text file". A Blueprint class is a binary asset whose logic lives in the wires between its nodes. A Verse class is a passage of text in a .verse file — it diffs, it reviews, it greps, and an AI can read and write it. That distinction explains most of the "difference" column above: macros are gone because copying a function in text is cheaper than maintaining a macro asset; function libraries don't need a shell class because the text file is the module.
The second root distinction is the move from inheritance to composition. In the Blueprint world, what a thing is is determined by which Actor it inherits from. In the Scene Graph world, what a thing can do is determined by which components you attached to it. That worldview gets its own treatment in Chapter 8. For now, all you need to know is: every row above marked "Confirmed" is a mapping you can already carry into any piece of Verse code you read today.
Three questions, all about precision of wording — on this topic, saying it correctly matters more than knowing a lot. Retry as often as you like.
Epic says Actors and Blueprints "will be deprecated". Which reading is the most accurate?
Regarding conversion tools, which is the only statement that holds up today?
Suppose a visual editing layer for Verse really does arrive. Is there any point in learning text-form Verse today?
The timeline and commitments in this lesson come from Epic's public statements: The road to Unreal Engine 6 (Epic official) ↗ · State of Unreal 2026: Top news from the show (Epic official) ↗. The conversion plugin used in the historical comparison is documented in Cascade to Niagara Effects Converter Plugin (official docs) ↗. Anything marked "not yet announced" in this lesson means Epic had made no public statement as of the time of writing (August 2026) — always defer to Epic's latest announcements.
Deep Dive · EXTRA
Every publicly known date, commitment and open question in one detailed table, each row tagged with its source and confidence — check your wording here before repeating any of it to a colleague.
Open the extra →Advanced · EXTRA
A post-mortem of two framework replacements, Matinee→Sequencer and Cascade→Niagara: how long they coexisted, how far the conversion tools got, and what old projects actually did.
Open the extra →Technique · EXTRA
Five engineering practices you can start today. What they have in common: they're a net win for your current project whether or not UE6 ever shows up.
Open the extra →