Spine Atlas Regions Look Scrambled Online? Check for a Resized Preview

The export looks correct locally, but a hand displays another region after the files move online. Keep the page image actually requested by the receiving project before repainting the hand. Check whether that image still matches the pixel canvas described by its atlas.

A recognizable preview is not a matching runtime asset

The official Spine atlas format records page dimensions and a region's pixel location and packed size. Recognizing the same character in a resized preview does not validate its use with unchanged coordinates.

Thumbnails serve a display purpose. Runtime pages have a delivery contract with their data. This checklist does not allege a current Tooliva thumbnail fault; it addresses handoffs through storage and image-processing services.

Compare three stages of the delivery

1. Preserve the original archive, atlas and page images with their export batch.
2. Capture the real network response, final URL, content type, decoded dimensions and file hash.
3. Confirm which returned file the project actually loads, distinguishing old cached data and similarly named previews.
4. Compare dimensions, cropping, added borders and encoding changes with the original.

A changed hash proves different bytes, not necessarily damaged pixels. Equal dimensions alone do not exclude rearranged contents or a crop placed on a new canvas.

Changing one size field is not a repacking workflow

Suppose a 1024-by-1024 page is delivered as 512-by-512. The original pixel rectangles cannot simply be assumed to describe the new page. This is a conditional example, not a measured failure. Editing only the page size does not validate every region, rotation and offset.

If the runtime asset needs resizing, use a workflow confirmed to support the format and deliver images and matching data as a distinct batch. Retain the baseline instead of patching a few production numbers in place.

Separate article-image processing from game-asset delivery

A blog cover can be resized for display. A downloadable Spine atlas has coordinate relationships. Keep those policies separate, retain the original download route and avoid supplying a list thumbnail as a runtime texture.

Even encoding at unchanged dimensions needs alpha, color and decoder checks. That does not mean every compression operation scrambles regions, or that a small file establishes a valid handoff.

Accept the batch in its real consumer

Retain the actual export from Spine Workbench using the guide. In the receiving project, check every page and representative regions, then required skins and animations.

No target-engine experiment or image-service console change was performed here. Record original, returned and loaded files plus a rollback version. Establish delivery integrity before deciding whether new art is required.