Skip to content

Spine IO

by Digital-Art-Freedom·Workflow

Images © Digital-Art-Freedom. Used for product review; image policy.

Why we like it

Spine IO earns its place in the Blender Extensions library as a focused, export-only bridge to Spine 4.3 JSON, covering meshes, armatures, weights, blend modes and FK animation. It's export-only at present, with an importer planned by the developer.

What is Spine IO?

Spine IO is a Blender add-on from Digital-Art-Freedom that converts bone-driven rigs into Spine 4.3 JSON files. It exports armatures, meshes, weights, internal edges and basic FK animation from Blender 4.2 and newer, and supports OCA/OCO-friendly project structures alongside procedural blend-modes through a dedicated BLEND-MODE node.

On the mesh side it handles quads, tris and n-gons, preserves internal edges for accurate Spine deformation, and reconstructs hulls automatically. Armatures export with Spine-compatible bone hierarchy and lengths plus local rig-space pose conversion, while weights carry up to four influences per vertex with correct Spine-space coordinates and automatic parent-bone assignment for unparented weighted meshes. Blend modes map from Blender to Spine, covering normal, additive, multiply and screen. Quick Export lives in the Spine-IO panel, with optional texture copying and OCA/OCO-style relative image pathing.

Spine IO is export-only for now, with an importer planned, and targets Spine 4.3 JSON specifically. IK, drivers and constraint animation are not yet exported, and the add-on needs a saved .blend file for export paths to resolve.

Who is Spine IO best for?

Spine IO is best for blender artists exporting rigged, weighted meshes and FK animation to Spine 4.3 JSON.

How much does Spine IO cost?

Spine IO is completely free to download and use.

Key features

  • Mesh export supporting quads, tris and n-gons, with internal edges preserved for accurate Spine deformation and automatic hull reconstruction
  • Spine-compatible bone hierarchy and lengths, with local rig-space pose conversion
  • Vertex weights up to four influences per vertex, with correct Spine-space coordinates and automatic parent-bone assignment for unparented weighted meshes
  • FK animation export from the active Action to Spine-compatible timelines
  • Optional BLEND-MODE node detection mapping Blender modes (Normal, Add/Screen, Luminosity/Additive, Multiply) to Spine modes
  • Quick Export via the Spine-IO panel with optional texture copying and OCA/OCO-style relative image pathing

Tags

#Spine#Blender#Exporter#Armature Export#Vertex Weights#FK Animation#Spine 4.3 JSON

Frequently asked questions

Does Spine IO work with Blender 4.2 and newer?

Spine IO targets Blender 4.2 LTS and newer, so it runs on 4.2 and later releases. One open issue on the developer's page reports that animation export is not working on Blender 5.+, so if you're on a 5.x build you may hit problems exporting FK animation specifically. Mesh, armature and weight export are listed separately from that report. For the current state of Blender 5 support, check the developer's page before relying on animation output in a production pipeline.

What Spine version does Spine IO export to?

Spine IO exports to Spine 4.3 JSON only, so it writes files matching that Spine version's format. It handles armatures, meshes, weights, internal edges and basic FK animation, and it maps Blender blend modes to Spine modes such as normal, additive, multiply and screen. It is export-only at the moment, with an importer planned by the developer. If you work with a different Spine version, confirm compatibility on the developer's page before setting up your export workflow.

Does Spine IO require a saved .blend file?

Spine IO requires a saved .blend file so its export paths can resolve correctly. Until the file is saved, the add-on cannot reliably work out where to write the Spine JSON or copy textures. It uses safe, predictable file-path resolution and OCA/OCO-style relative image pathing, so saving your project first keeps texture and JSON output pointing to the right locations. Save the .blend before running Quick Export from the Spine-IO panel to avoid path issues.

Is Spine IO free, and how is it licensed?

Spine IO is listed as free here, and it's distributed under the GNU General Public License v3.0 or later. That license governs how you can use, modify and redistribute the add-on. For the current licensing terms and any conditions attached to it, check the developer's page. The add-on is available through the Blender Extensions library, where you can also review its version history and permissions before installing it.

Can Spine IO export IK and constraint animation?

Spine IO does not yet export IK, drivers or constraint animation; those sit outside its current scope. It exports FK animation from the active Action to Spine-compatible timelines, along with armatures, meshes and weights. The developer lists it as export-only, with an importer planned. If your rig depends on IK or constraints, you would need to bake or convert that motion to FK before export, or wait for expanded animation support noted on the developer's page.

Alternatives to Spine IO

Also in Workflow for Blender.

Similar plugins