Export & Delivery

Spine JSON / SKEL, 3.8 / 4.2, and Atlas Files

Choose a Spine version and data format, then understand the data, atlas, and texture delivery set.

IntermediateAbout 18 minFor Editor v1.0 · Tutorial updated Oct 26, 2026

After this article

Export data, atlas, and texture files that match your runtime and verify the complete set.

Dialog selection	Format	Export result and use
4.2 and later	JSON	JSON data + .atlas atlas + .png texture; convenient for inspection and debugging
4.2 and later	Binary	.skel data + .atlas atlas + .png texture for runtimes supporting 4.2 binary
3.8.99 (Cocos Creator 3.8 compatible)	JSON	Cocos-compatible ZIP containing JSON, atlas, and texture
3.8.99 (Cocos Creator 3.8 compatible)	Binary	Cocos-compatible ZIP containing SKEL, atlas, and texture

1
Save and open Spine export
Save, then click Export in the toolbar and choose Export Spine Skeletal Data. The output contains skeleton and animation data, not just a picture of the canvas.
Expected resultThe version and format dialog opens.
Choose the runtime version first, then the data format.
2
Check binary entitlement
If binary is marked as a member feature, check your current plan. Do not assume every account can export SKEL from someone else's screenshot. JSON and binary express the same source project in different encodings.
Expected resultThe selected format is available to your account.

1
Confirm and wait
Confirm the export. Data, atlas, and texture may be downloaded as several files; 3.8-compatible output is packaged as ZIP. Do not keep only the first download.
Expected resultThe completion notification includes the file name and animation count.
This is a real exported-file preview, not a success toast. Also check that JSON, ATLAS, and PNG are all present in the download folder.
2
Inspect the data file
For 4.2, check .json or .skel as appropriate; for 3.8, extract the ZIP first. The file name includes project and export-time information.
Expected resultThe data file is nonempty and its version and format match your selection.
3
Inspect atlas and texture
Keep the .png referenced by the .atlas beside it without changing their relative paths. Delivering only JSON or SKEL without the atlas and texture prevents images from displaying.
Expected resultData, atlas, and texture form a complete set with the expected animation count.
4
Review mesh repair notices
If a warning says mesh weight data was repaired during export, record the count and inspect the source mesh. Automatic export repair is not a long-term debugging strategy.
Expected resultYou know what was repaired and have verified the source project.

The target Spine runtime version matches the selected 3.8 or 4.2 output.
JSON / SKEL, ATLAS, PNG, or ZIP are all preserved with their relative paths unchanged.
The seven defaults or your project's actual animation count is correct; inspect events and draw order as needed.
Meshes, weights, IK, physics, and path behavior are verified in the target runtime or by reimporting.
Export file names correspond to a known project version, so an old ZIP cannot be mistaken for the latest result.