In many cases this is not possible, data will be lost, and warnings will be shown.Įxporting to older versions is intended only as a last resort to partially recover work when a project was accidentally saved with a newer version of Spine. If an older JSON version is chosen, Spine attempts to write data compatible with that older version of the Spine Runtimes. When checked, the JSON is formatted to be more easily read by humans. This format requires a lenient JSON parser, such as the one in libgdx. Minimal Like JSON, but most names and values are not quoted.JavaScript Like JSON, but names are only quoted if necessary.Spine can optionally write in JSON-like formats that are slightly smaller, easier to read, and easier to edit. The JSON files will use this file extension. The name of the file will use the name of the skeleton. When doing so, be sure that Nonessential data is checked.Ī JSON file will be created in this folder for each skeleton in your project. It is perfectly reasonable to export to JSON, process the JSON data, then import the data back into a Spine project. However, JSON is human readable and it is easy to write tools to parse and manipulate the data, if needed. JSON data is much larger than binary and loading JSON data is much slower, so generally using binary data in your applications is preferred. If the speed the data file is loaded at runtime is important, use binary. If the size of the data file is important, use binary.

Loading gif transparent small