UE5 Sequencer: bindings, camera cuts, and playing it in game
By the Cosindra team · Updated August 7, 2026
Sequencer is Unreal’s timeline: cutscenes, camera moves, scripted events, trailer shots. The editing part is familiar to anyone who has used a video editor. The part that is not familiar is bindings, and that is where the first cutscene usually goes wrong.
This guide covers what a binding is and the Possessable/Spawnable choice behind it, how camera cuts work, and why a sequence that plays perfectly in the editor does nothing in a packaged game.
Nothing happens until an actor is bound
A Level Sequence does not animate actors directly. It animates bindings — named references it holds to actors — and a track can only exist on something already bound. Add the binding first, then the Transform track, then the keyframes.
This ordering is not a style preference; a track has nothing to attach to without it. If you are wondering why a track will not add, this is almost always why.
Possessable or Spawnable
A Possessable binds an actor that already exists in the level. The sequence takes control while it plays and hands it back afterwards. This is what you want for the player character, an existing door, or anything the rest of the game also cares about.
A Spawnable is owned by the sequence: it is created when playback starts and destroyed when it ends. This is what you want for a cutscene-only camera or a one-off prop that should not exist in the level at all.
The practical difference shows up when someone deletes an actor. A Possessable binding breaks and its track goes orange — the sequence is now animating nothing. A Spawnable cannot break that way, because the sequence carries its own copy.
| Possessable | Spawnable | |
|---|---|---|
| Actor lives in | The level | The sequence |
| Exists outside playback | Yes | No |
| Use for | Player, existing props, doors | Cutscene cameras, one-off props |
| Breaks if actor deleted | Yes — binding goes orange | Not possible |
Camera cuts are their own track
Moving a camera is a Transform track like any other. Deciding which camera the viewer is looking through is a Camera Cut track, and it is separate on purpose — one cut track can switch between several bound cameras across the timeline, which is how you get shot-reverse-shot without moving anything.
Each section on the cut track points at one bound camera for one time range. A gap in the cut track means the viewer falls back to the player camera, which is occasionally intentional and more often a mistake at the end of a sequence.
The editor calls that build it
| # | Tool | What it does |
|---|---|---|
| 1 | bind_actor_to_sequence | Binds a level actor as a Possessable — required before any track |
| 2 | add_sequencer_track | Adds a track — Transform, Float, Bool, Audio, Animation |
| 3 | add_sequencer_keyframe | Keys a value at a time for a bound actor |
| 4 | add_camera_cut_track | Adds a cut section binding a camera for a time range |
| 5 | add_audio_track | Adds a master audio track with a sound asset |
| 6 | set_sequencer_range | Sets the playback range |
| 7 | preview_sequence | Opens it in the Sequencer editor to play back |
| 8 | get_sequence_info | Reads duration, range, frame rates and every binding |
Why it does not play in game
Pressing play in the Sequencer editor plays the asset. It says nothing about what happens during gameplay, because a Level Sequence asset is not itself in the level — a Level Sequence Actor is, and that actor decides when playback happens.
So a sequence plays in game when its actor has Auto Play enabled, or when something explicitly tells it to play — a trigger volume, a Blueprint call, the end of a load. A cutscene that works in the editor and not in PIE is nearly always missing that one step.
Put an AI copilot inside your editor
The free Cosindra desktop app connects to your UE 5.7/5.8 project — the assistant works in your open editor, and what you generate with the web tools applies straight into it. Windows & macOS.
Download CosindraFrequently asked questions
What is the difference between Possessable and Spawnable in UE5 Sequencer?
A Possessable binds an actor that already exists in the level — the sequence borrows it during playback and returns it afterwards, which is what you want for the player or an existing prop. A Spawnable is created by the sequence when playback starts and destroyed when it ends, which suits cutscene-only cameras and props that should not exist otherwise. Deleting the level actor breaks a Possessable binding; a Spawnable cannot break that way because it carries its own copy.
Why does my Level Sequence not play during gameplay?
Because playing it in the Sequencer editor and playing it in the game are different things. The asset needs a Level Sequence Actor in the level, and that actor needs either Auto Play ticked or something to trigger it — a trigger volume, a Blueprint call, a level-load event. A sequence that looks perfect in the editor and does nothing in PIE is nearly always missing exactly this.
How do I cut between multiple cameras in Sequencer?
Bind each camera to the sequence, then add a Camera Cut track and give it one section per shot, each pointing at a camera for its time range. The cut track only decides what the viewer looks through — moving the cameras is still ordinary Transform tracks on each one. Watch for gaps between sections: any uncovered time falls back to the player camera, which is usually not what you want at the end of a cutscene.