Blender 5 for Game Artists: What Changed in Rigging, Animation, and Export (2026)

Last updated: September 2026.

If you make characters and props for a game engine, install Blender 5.2 LTS. It shipped on July 14, 2026, gets bug fixes until July 2028, and it's the first long-term release that contains every Blender 5 change at once: slotted actions with the old Action API gone, the C++ FBX importer as the default, meshopt compression in the glTF exporter, and a Python 3.13 runtime that add-ons had to be rebuilt for. Blender 4.2 LTS stopped receiving fixes in July 2026, so if you're still on it, 5.2 LTS is the move, with 4.5 LTS as the fallback for Intel Macs and older GPUs.

We refresh this page at every Blender release. This revision is dated September 6, 2026 and covers 5.0, 5.1, 5.2 LTS and the 5.3 alpha.

Quick answer

• Production version today: Blender 5.2 LTS (5.2.1, August 25, 2026). Supported to July 2028. Source: the LTS page.
• Still on 4.2 LTS? Its two years ended in July 2026 (last update 4.2.23). Move to 5.2 LTS, or to 4.5 LTS if your Mac is Intel or your GPU is older than a GeForce 900, Radeon RX 400 or Intel Kaby Lake.
• Biggest animation change: Actions have slots (since 4.4) and the legacy action.fcurves and action.groups API was removed in 5.0. Any exporter or retargeting script written before 4.4 breaks. Layered animation is still not in the UI as of 5.2 LTS.
• Biggest export change: the C++ FBX importer is the default in 5.0, Collada is gone, and the glTF exporter gained EXT_meshopt_compression and KHR_meshopt_compression in 5.2.
• Biggest add-on change: 5.1 moved to Python 3.13, so any extension that bundles compiled wheels needs a cp313 build. 5.0 removed dict-style access to bpy.props data and the BGL drawing API.
• Blender 5.3 is in alpha until September 30, 2026 and is scheduled for November 10, 2026. It makes Vulkan the default backend on Windows and Linux.

Quick reference

Dates come from the Blender release notes index, the LTS page and the 5.3 milestone.

Version	Released	Status in September 2026	What it means for game assets
4.2 LTS	July 16, 2024	Support ended July 2026 (4.2.23)	Extensions platform arrived. Legacy Action API still present
4.4	March 18, 2025	Unsupported	Slotted actions introduced, legacy API deprecated
4.5 LTS	July 15, 2025	Supported to July 2027 (4.5.13)	Last Intel Mac build, last Collada, Vulkan officially supported
5.0	November 18, 2025	Unsupported (5.0.1, December 16, 2025)	Legacy Action API removed, C++ FBX import default, new file format
5.1	March 17, 2026	Unsupported (5.1.2, May 19, 2026)	Python 3.13, 2x faster action evaluation, FBX shape key normals
5.2 LTS	July 14, 2026	Current stable, supported to July 2028 (5.2.1)	glTF meshopt, Duplicate and Rename bones, EEVEE raytracing overhaul
5.3	November 10, 2026 (planned)	Alpha until September 30, 2026	Vulkan default on Windows and Linux, rotation mode conversion
6.0	November 2027 (planned)	Not started	Listed on the compatibility page, no details yet

Three releases a year, one of them LTS. The regular releases (grey and blue) are supported only until the next release, so 5.0 and 5.1 are already unsupported. The 5.3 and 6.0 dates are the planned schedule from the Blender milestones and compatibility page, not promises.

Which version to use for production, and why

Blender's release cycle targets a new version every four months, and the release notes index states the support rule plainly: every release is supported until its successor, and once a year an LTS version is maintained for two years. The LTS page adds the part that matters for a pipeline: an LTS version "will not have any new features, API changes or improvements", only critical fixes ported from the current release.

That's the whole argument for 5.2 LTS. A game project runs longer than four months. Build on 5.1 and your only path to a fix after July 2026 is 5.2, with whatever changes it brings. Build on 5.2 LTS and you keep the same Python API, exporters and file format until July 2028, with 4.5 LTS overlapping until July 2027 if a studio you work with hasn't moved yet.

Two groups should pick 4.5 LTS instead. Intel Mac owners, because the requirements page says 4.5 LTS is the last release to support Intel, and 5.0 and later require Apple Silicon on macOS 13 or newer. And anyone on an older GPU, because the compatibility page raised the 5.0 minimum to NVIDIA GeForce 900, AMD Radeon RX 400 and Intel Kaby Lake. Older cards may still run it, but bugs on them won't be fixed.

Don't mix versions casually. The compatibility page says blend files created with 5.0 and later "can only be opened by Blender 4.5 or later", and older versions "will report them as invalid". A teammate on 4.2 can't open your 5.2 files at all.

What changed for animation

Slotted actions are the foundation, and the old API is gone. The 4.4 release notes introduced slots: "slots make it possible to store the animation of multiple 'things' in the same Action". A walk cycle can carry the bone curves in one slot and the shape key curves in another. Every action in every file is slotted now, and old actions were upgraded with a single "Legacy Slot". The 5.2 manual puts it simply: a data-block "specifies both an action and a slot within that action".

For scripts, the 5.0 Python notes are the breaking point: "The legacy Action API has been removed. This covered the properties action.fcurves, action.groups, and action.id_root." We confirmed it on a local 5.0.1 build: bpy.data.actions.new('t').fcurves no longer exists, while .slots and .layers do. A batch exporter or bake script from the 4.2 days fails on its first action.fcurves call. The fix is in the same notes: get a channelbag with bpy_extras.anim_utils.action_ensure_channelbag_for_slot(action, action_slot) and call channelbag.fcurves.find(), .new() or the new .ensure(). The 4.4 upgrade guide has side-by-side examples.

One behaviour change trips people who never touch Python. Since 4.4, assigning an Action also has to pick a slot, and the auto-assignment rules deliberately don't pick "the only slot" for a plain assignment, so that assigning Cube's action to Suzanne and keying her creates a new slot instead of overwriting her with Cube's motion. If you assign an action and nothing moves, look at the slot selector next to the action name.

Layered animation is still not in the UI. Project Baklava, described in Animation 2025: Progress and Planning, has two pillars: multi-ID animation (that became slots) and layers. The Layered Animation Workshop 2024 post settled a minimal feature set: named, lockable, mutable layers with replace and combine blend modes, animatable influence and a bake-down. As of 5.2 LTS none of it has shipped. The manual says the layers and strips under every action are "not currently exposed in the UI", the 5.0 to 5.2 notes contain no layer editor, and the Winter of Quality 2026 report lists only documentation work on it. Additive layers for game animation still happen in the NLA or in the engine.

The NLA didn't change structurally. Tracks and strips work as before per the NLA manual. What changed is how exporters read it: the glTF manual notes that "with Blender 4.4, and the introduction of slotted actions, this default behavior has been changed. Now, tracks are merged by the action they are using", not by name. More in the export section.

Performance: 5.1 roughly doubled action evaluation. The 5.1 animation notes benchmarked a 2,600-bone armature keyed for about 1,000 frames at 32.8 fps in 5.0 against 74.1 fps in 5.1 on 4 threads, and a million-vertex shape key mesh went from 39.2 to 158.7 fps on 24 threads. A production character file improved 4 to 14 percent, so the win is for heavy rigs and dense blend shapes.

Pose library. The asset-based pose library is unchanged in shape, and since a pose asset is a one-frame action it can carry slots, which the manual recommends against for generic poses ("use single-slot actions"). 5.0 removed the converter for 2.93-era pose libraries, so convert those in 4.5 first. 5.2 corrects rotation mode when a pose asset and the bone differ.

Smaller items. 5.1 added a Replace Action operator (Object > Animation or Pose > Animation) that swaps an action on every object using it. 5.2 added Select > Select by Type in the Dope Sheet, playback loop modes, and turned on the "Only Insert Available" preference by default, so pressing I now keys only channels that already exist unless you change it back. 5.3 alpha adds anim.rotation_mode_convert on Ctrl+R and deprecates Rigify's own pos.convert_rotation.

What changed for rigging

Bones on instanced armatures. The 5.0 animation and rigging notes moved bone visibility and selection in Object and Pose mode onto the pose bone, so two instances of the same armature can hide and select bones independently. The cost is an API break: bpy.data.armatures[...].bones[0].select was removed, bones[0].hide now affects edit-bone visibility only, and Pose mode uses object.pose.bones[0].hide and .select. Rig UI scripts that toggle bone visibility need the new path, and anim.version_bone_hide_property moves animated hide curves for you.

New constraint and custom-shape options. 5.0 added the Geometry Attribute constraint, which reads a vector, quaternion or matrix attribute from geometry and applies it to a bone's transform, plus two Custom Shape options, Affect Gizmo and Use As Pivot.

Weight tools. The 4.5 notes made the vertex group Assign button respect auto-normalize, and the 5.1 notes added loop selection in Weight Paint mode when vertex selection is on. There is no new skinning algorithm in 5.x: Automatic Weights is still bone heat. That's why Voxel Heat Diffuse Skinning keeps selling on Superhive at around $30, and why one-click riggers exist. If you'd rather not paint weights at all on a humanoid, the Cinevva Rig add-on rigs a mesh into a skinned, Mixamo-named skeleton on your own machine, offline, for a one-time $29 launch price, and it declares Blender 4.2.0 as its minimum so it runs on 4.2, 4.5 and every 5.x release on Windows, macOS and Linux.

Armature editing quality of life in 5.2. The 5.2 notes added Duplicate and Rename in the Armature menu, which duplicates selected bones and runs a search and replace on the name so you stop getting .001 suffixes when mirroring a chain by hand. Bone parenting gained a Head/Tail slider, adding a bone exposes Space, Align, Length and Deform in the redo panel, and Copy Constraints joined the Ctrl+L Link/Transfer Data menu. In-between tools (breakdowner and friends) now work in Object mode under Object > Animation > In-Betweens.

Rigify. Rigify is still the bundled, free generator and the manual still describes the same deal: it "only automates the creation of the rig controls and bones. It does not attach the rig to a mesh, so you still have to do skinning etc. yourself". The 5.x release notes carry almost nothing Rigify-specific beyond a 5.1.x UI fix and the 5.3 deprecation above. Auto-Rig Pro, the paid category leader, is a third-party extension and its 5.x compatibility is the author's to declare, which brings us to add-ons in a moment.

Shape keys. 5.0 rebuilt the shape key list with multi-select and drag and drop, and added Make Basis. 5.1 added Apply to Basis, which bakes selected shape keys into the base mesh and deletes them, a handy step before export when a generator left you with corrective shapes you don't want in the GLB.

What changed for import and export

FBX. The 5.0 pipeline notes made the C++ FBX importer (experimental in 4.5) the default and marked the Python importer legacy: add-ons using bpy.ops.import_scene.fbx "are advised to switch to bpy.ops.wm.fbx_import". The FBX manual describes what the new importer does with animation: "Each FBX 'take' is imported as a separate Action, with each animated object assigned to its own Action Slot." Export is unchanged in mechanism: File > Export > FBX (.fbx) still runs the Python add-on with the same Forward, Up, Apply Scalings, Add Leaf Bones and Bake Animation options. One real export fix landed in 5.1: the exporter "now also exports shapekey normals, when exporting normals for the base mesh is enabled", which the notes say solves "some import issues with some game engines". Better FBX Importer and Exporter still sells for a reason: the built-in exporter's own Missing list in the manual includes vertex shape keys and material textures.

glTF. The exporter got the most game-relevant additions. The 5.2 notes list EXT_meshopt_compression and KHR_meshopt_compression export and import behind a new Data > Meshopt Compression panel, official KHR primitive attributes, point clouds, iridescence and dispersion materials, and hooks that can stop the export. Draco is still there. The 5.3 alpha adds Animation Pointer for custom properties. The glTF manual documents the slot-era import behaviour: "Each animation will be imported as a single action, with multiple slots if the animation affects multiple objects." On export, the default Actions mode exports an action only if it is active or stashed to an NLA track ("If you have multiple actions you want to export, make sure they are stashed!"), and Merge Animation is now "by Action (using slot), by NLA Track Name, or no merge". If your clips merged unexpectedly after upgrading past 4.4, that setting is the reason.

USD. The USD manual imports USD skeletons as armatures and blend shapes as shape keys, and exports armatures and Armature-modifier meshes as USD skeletons and skinned meshes, with two stated limits: "Modifiers in addition to Armature modifiers will not be applied" and "Bendy bones are not supported". 5.1 made mesh export write indexed UVs so other apps can rebuild UV islands, and 5.2 added colour space tagging on export and conversion on import.

Collada is gone. Removed in 5.0. If an old pipeline still emits .dae, 4.5 LTS is the last version that reads it. And 5.0 changed the blend file header and switched compression on by default, so only 4.5 and newer open 5.x files.

Every cell is taken from the release notes for that version. The 5.3 column is the alpha as of September 2026 and will change before November.

Blender's official 5.2 LTS overview. Most of the runtime is Geometry Nodes physics and remote asset libraries, which is a fair picture of where the 5.x releases spent their effort: the rigging and export changes above are the quiet part.

Add-ons: the Extensions platform and what broke

Extensions replaced legacy add-ons in 4.2. Add-ons now ship as extensions with a blender_manifest.toml, install from Preferences > Get Extensions, and live on extensions.blender.org, which "only offers GNU GPL compliant software". The manual requires blender_version_min (at least 4.2.0) and allows an optional blender_version_max, "Blender version that the extension does not support". Legacy add-ons still install through Install from Disk in 5.2, but the old way is deprecated, and the extensions site warns that "Extensions don't update automatically".

How to check whether an add-on works on 5.2. Read the Blender version range on the extension's page, or search it in Preferences > Get Extensions, where the listing shows whether a build exists for your version. Install it, open Window > Toggle System Console on Windows or launch Blender from a terminal on macOS and Linux, and enable it: the manual's tip is that if an add-on doesn't activate, "check the Console window for any errors". Three errors account for most post-upgrade failures.

An AttributeError on fcurves, groups or id_root means the add-on uses the legacy Action API removed in 5.0. A wheel that refuses to load means the extension bundles a compiled module built for Python 3.11, which 5.0 still used (our local 5.0.1 reports 3.11.13), while the 5.1 Python notes moved Blender to Python 3.13, so anything bundling numpy or an inference runtime needs cp313 wheels from 5.1 on. And if a tool that relied on pip install --user packages can't find them, that's the 5.1 core change: "The Python user-site-directory is no longer loaded by default", restorable with --python-use-user-env.

The other 5.0 breaks that hit game tooling. The 5.0 Python notes removed dict-style access to bpy.props storage ("bpy.context.scene['cycles'] will not give access to Cycles' scene settings"). The BGL module and Image.bindcode were removed, so anything drawing in the viewport with raw OpenGL calls (older bone pickers, weight visualisers) needs the gpu module. scene.node_tree became scene.compositing_node_group, and the EEVEE engine identifier changed from BLENDER_EEVEE_NEXT to BLENDER_EEVEE, which trips render scripts that pick an engine by name. In 5.2, the Geometry Nodes modifier API changed from modifier["identifier"] = 5.0 to modifier.properties.inputs.identifier.value = 5.0, so batch tools that drive a GN decimation or LOD setup by name need updating for the LTS.

Where the Cinevva Rig add-on stands. It's a standard extension with a 4.2.0 minimum, version 0.4.0 from September 5, 2026, and it runs on 5.0, 5.1 and 5.2 LTS. Rigging is the paid half, unlocked by the $29 key and run locally after a one-time engine download of about 2.4 GB. The 260 CC0 animation clips and the export presets for Unity, Unreal, Godot and the web work without a key or an account. Against a plain Blender GLB export, the presets produced files 68 to 98 percent smaller on the four models we measured, mostly by capping and re-encoding textures.

Viewport and performance for asset work

GPU backend. The System preferences offer OpenGL and Vulkan, with a restart to switch and Metal fixed on macOS. The Q2 2025 projects update declared Vulkan "officially supported in the upcoming Blender 4.5 LTS, offering feature parity and comparable performance to OpenGL". 5.1's EEVEE notes measured Vulkan cold-start material compilation on the Barbershop scene dropping from 24.87 to 11.67 seconds and texture pool memory from 406 to 245 MB, and the 5.3 alpha notes finally flip it: "Vulkan backend is now default on Windows (not ARM) and Linux. Existing user preferences will not be migrated." On 5.2 LTS it's opt-in. Try it, and switch back to OpenGL if a viewport-drawing add-on misbehaves. The 5.1.x corrective releases fixed Vulkan issues on Intel Iris Xe and NVIDIA 595 drivers, so keep drivers current.

EEVEE and material compile times. The 5.0 EEVEE notes say simple materials compile about four times faster on NVIDIA OpenGL, and 5.1 added parallel pipeline compilation on every backend. For look-dev on a character with a dozen materials, that's a grey viewport for seconds instead of a minute. 5.2's screen-space raytracing overhaul changes how existing scenes look ("some scenes might render darker than in 5.1"), and EEVEE inherited the Workbench instancing optimisation, up to twice as fast on scenes with many instances, which describes a modular environment kit exactly.

Curves and hair got heavier. A 5.0 gotcha for characters with particle hair: curve drawing now honours the resolution attribute, and the notes warn that a default hair system "will now render 15 times more geometry in 5.0". If a file that opened fine in 4.5 crawls in 5.x, lower the curve resolution.

Platform minimums decide whether you can install 5.x at all: Apple Silicon on macOS 13 or newer, and on Windows and Linux a GPU with OpenGL 4.3 and 2 GB of VRAM from the GeForce 900, Radeon RX 400 or Kaby Lake generation onward, per the requirements page.

Upgrade checklist for a game-asset pipeline

Do this once per project, in this order, on a copy of your files.

1. Pick the version and pin it. Install 5.2 LTS from the LTS page. If any teammate is on an Intel Mac or a pre-2016 GPU, the team pins 4.5 LTS instead, because 4.2 can't open 5.x files and 4.5 truncates long names.
2. Open your oldest rig in 4.5 first if it dates from 2.79 or earlier. 5.0 dropped loading of pre-2.50 animation data and the 2.93-era pose library converter. The notes recommend opening and saving such files in 4.5 before moving on.
3. Inventory add-ons against the version range. For each one, read blender_version_min and blender_version_max on its extension page. Reinstall from Preferences > Get Extensions rather than copying an old add-ons folder, and check the console on first enable.
4. Grep your scripts. Search for action.fcurves, action.groups, id_root, bones[...].select, import_scene.fbx, scene.node_tree, BLENDER_EEVEE_NEXT, bgl and bracket access like modifier["Socket_. Each is a documented 5.x break with a documented replacement.
5. Re-import one FBX character pack and inspect actions. With the C++ importer, every take becomes an action with one slot per animated object. Confirm clip names and that the armature slot is assigned before you batch anything.
6. Re-export one animated GLB and check the animation list. Set Animation > Mode to Actions, stash every clip you want to an NLA track, and set Merge Animation to the mode you intend. Open the result in a viewer and count the clips. Then try Meshopt Compression against Draco on a real asset and keep whichever your engine or loader decodes.
7. Re-export one FBX for your engine with normals on. 5.1's shape key normals fix changes what Unity and Unreal receive for blend-shape characters. Import it and check facial shapes for shading seams.
8. Decide on the GPU backend deliberately. Stay on OpenGL for 5.2 LTS unless you've tested Vulkan with your add-ons. When 5.3 arrives it defaults to Vulkan on Windows and Linux without migrating your preference, so note the choice now.
9. Re-save assets that use Node Tools or Geometry Nodes assets. 5.1 and 5.2 both require opening and re-saving asset files for node tools to work, per the compatibility notes.
10. Turn compression back off if a tool reads .blend files directly. 5.0 enables blend file compression on saving by default and changed the block header format, so external parsers need updating or uncompressed files.

The same checklist as a card you can keep open in a second window. The right column is the part people skip, and it's the part that catches the slot and merge changes before an engine import does.

Common Questions

When was Blender 5.0 released and is it still supported?

Blender 5.0 was released on November 18, 2025, with the 5.0.1 corrective release on December 16, 2025. It is no longer supported: Blender supports a regular release only until its successor, and 5.1 replaced it on March 17, 2026. If you're on 5.0, move to 5.2 LTS, which keeps the same slotted-action model and adds fixes through July 2028.

What are the new features in Blender 5.0 for animators and riggers?

The headline 5.0 features were colour management (ACES, HDR, working colour space) and the sequencer overhaul. For animation and rigging the notes list the Geometry Attribute constraint, per-instance bone visibility and selection, a shape key UI rebuild with multi-select and Make Basis, Copy Global Transform moving into core, Jump Time by Delta, and slot selectors that show the slot type. The removals matter as much: the legacy Action API, pre-2.50 animation loading and the old pose library converter.

What is Blender 5.1 and what did it change for game artists?

Blender 5.1 shipped on March 17, 2026. For game work the changes are performance and plumbing: action evaluation roughly doubled on heavy rigs, shape key evaluation up to four times faster, Python moved to 3.13, the user site-packages directory stopped loading, the FBX exporter began writing shape key normals, and EEVEE materials compile faster on every backend. It was superseded by 5.2 LTS on July 14, 2026.

Is Blender 5.2 an LTS release and until when?

Yes. Blender 5.2 LTS was released on July 14, 2026 and will be maintained until July 2028, with 5.2.1 released on August 25, 2026. It overlaps with 4.5 LTS, supported until July 2027. 4.2 LTS ended in July 2026.

What are slotted actions in Blender?

A slot is a named, typed sub-container inside an Action, so one Action can animate several data-blocks at once, for example an armature's bones and its mesh's shape keys. Slots arrived in 4.4 and every action is slotted now. For users, the visible change is a slot selector next to the action name and a Merge Animation choice in the glTF exporter. For scripts, action.fcurves was removed in 5.0 in favour of the per-slot channelbag.

Does Blender 5 have layered animation?

Not in the interface, as of 5.2 LTS. The data model has layers and strips underneath every action, and the manual says this is "purely in preparation for future animation features that are not yet in Blender". The layer editor, blend modes and bake-down described in the Layered Animation Workshop 2024 post have not shipped in 5.0, 5.1, 5.2 or the 5.3 alpha notes.

Do my Blender 4.2 add-ons work in Blender 5?

Some do. An extension declares blender_version_min and optionally blender_version_max, and legacy add-ons still install from disk. What breaks is code, not packaging: the legacy Action API, bones[].select, BGL drawing, dict access to bpy.props data, and compiled wheels built for Python 3.11 rather than 3.13 (from 5.1). Check the console when you enable an add-on, and check the extension page for a 5.2 build before you upgrade.

Related

• How Automatic Rigging Works (and How to Prepare a Model for It): what a rig is, how riggers place joints, and how to prep a mesh so the 5.x weight tools have less to fix
• Cinevva Rig for Blender: one-click humanoid rigging on your own machine, 260 CC0 clips, and export presets for Unity, Unreal, Godot and the web, on Blender 4.2 and newer
• How to Rig a Character in Blender (2026): Rigify, manual armatures and the one-click route, step by step on 5.2 LTS
• Blender to Unity Export Checklist: the FBX settings, scale and axis choices that survive the 5.x importer changes
• How to Optimize a GLB for the Web: what Draco, meshopt and texture caps do to a file after it leaves the glTF exporter
• GLB Viewer: count the animation clips in an exported GLB and check the skeleton before it goes into an engine