Exploring 2D game development in Unreal Engine 5.2 with Paper2D and PaperZD: sprites, tilemaps, and animation state machines for 2D characters.
This project is a collection of 2D game prototypes built in Blueprints with Unreal Engine 5.2, developed following this Udemy course. The central question it answers is a practical one: can Unreal — an engine built around 3D rendering and physics — be used effectively for 2D games? The answer, via Paper2D and the PaperZD plugin, is yes, with some important caveats worth understanding.
You can watch the prototypes in action here: YouTube
Paper2D: Unreal’s Native 2D Framework
Paper2D is Unreal’s built-in plugin for 2D game development. It introduces two core asset types that replace the 3D primitives used in standard Unreal projects:
Sprites are the 2D equivalent of Static Meshes — a texture region rendered on a flat quad, positioned in world space. Paper2D sprites support per-pixel collision extraction from the sprite texture, which is useful for precise 2D collision shapes without manually defining collision primitives. They also support sprite atlases (multiple sprites packed into a single texture) and flipbooks — sequences of sprites played at a defined frame rate to produce 2D frame animation.
Tilemaps are grids of sprite tiles used to build 2D levels. A tileset defines the available tiles and their collision properties; a tilemap places them in a grid that renders efficiently as a single draw call. Tilemaps are the standard tool for building 2D platformer and top-down levels — they’re fast to edit in the Tile Map editor and cheap to render at runtime.
The APaperCharacter class is the 2D equivalent of ACharacter — it provides a capsule collision component and movement component configured for side-scrolling or top-down 2D movement, with the sprite component as its visual representation.
PaperZD: Animation State Machines for 2D
Paper2D’s built-in animation system — Flipbooks — is a simple frame-sequence player. It works for static animations but has no native state machine: transitioning between animations (idle → walk → jump → fall) requires manual Blueprint logic that checks conditions and switches the active Flipbook. As the number of animation states grows, this becomes unwieldy.
PaperZD is a community plugin that brings Unreal’s Animation Blueprint paradigm to 2D sprites. It introduces an Animation Source asset that holds sprite sequences, and an Animation Blueprint with a state machine graph — the same visual state machine used for skeletal mesh animation, but driving 2D sprite sequences instead. States represent animation clips (Idle, Walk, Run, Jump, Fall), and transitions define the conditions under which the character moves between them.
This is architecturally significant: it means the animation logic is separated from the character Blueprint. The character Blueprint manages movement and input; the Animation Blueprint manages which animation is playing based on the character’s velocity, grounded state, and other variables. The same separation of concerns that makes 3D animation maintainable applies directly to 2D.
PaperZD also supports animation notifies — events fired at specific frames of an animation — which are essential for 2D games where gameplay events need to be synchronized with animation frames (footstep sounds on specific frames, attack hitboxes active for specific frames).
2D Physics and Collision in a 3D Engine
One of the practical challenges of using Unreal for 2D games is that its physics engine is inherently 3D. Constraining a character to a 2D plane requires explicit configuration: locking the Z position, locking X and Y rotation, and ensuring the movement component doesn’t apply forces in the depth axis. Paper2D’s APaperCharacter handles most of this automatically, but custom actors need these constraints set manually.
Collision in 2D Paper2D projects uses the same channel and profile system as 3D projects — which is an advantage, because the full power of Unreal’s collision filtering is available. Sprite collision shapes can be extracted from the sprite texture automatically (pixel-perfect, though expensive) or defined as simple boxes and capsules (cheaper and usually sufficient for gameplay).
Unreal as a 2D Engine: Tradeoffs
Using Unreal for 2D development has genuine advantages: the rendering pipeline produces high-quality results, the Blueprint system is fully available, and systems like the UI (UMG), audio, and physics work identically to 3D projects. For a team already working in Unreal, building a 2D game doesn’t require switching engines or toolchains.
The tradeoffs are also real. Paper2D has not received significant updates from Epic in recent years — PaperZD exists precisely because the native animation tooling is insufficient. The Tile Map editor is functional but less polished than dedicated 2D editors like Tiled. And the engine’s overall complexity — shaders, rendering features, build times — is sized for 3D projects, which means 2D projects carry overhead they don’t strictly need.
For prototyping and learning, these tradeoffs are acceptable. For a production 2D game, the choice between Unreal and a purpose-built 2D engine like Godot or Unity depends heavily on team context and existing expertise.
Reflection
What this project demonstrates most clearly is that the architectural patterns of game development don’t change between 2D and 3D — state machines for animation, collision profiles for interaction filtering, component-based actor design — they just operate on different primitive types. Learning them in a 2D context, where the visual complexity is lower, makes the underlying patterns easier to see and internalize.
PaperZD in particular is a good introduction to Animation Blueprints for developers who haven’t worked with skeletal mesh animation yet. The state machine concepts — states, transitions, blend variables — are identical to what Unreal’s 3D animation system uses, just applied to sprite sequences. Understanding it here makes the 3D version significantly more approachable.
Nicolás Bertoa 
Leave a comment