Spine Files Are Uploaded but a Page Image Is 404? Trace the Resolved URL

The archive is intact, yet a page-image request returns 404 after deployment. Capture the request before renaming files. A resource existing somewhere on a server does not establish that the requested URL addresses it.

Identify the component resolving the name

The official Spine atlas format records a page-image name. Its location is up to the loader, typically relative to the atlas directory. That convention is not a guarantee for every wrapper.

Ask for the atlas URL, original page name and actual loader base or resource mapping. A local folder screenshot does not reveal the final request.

Separate relative paths from site-root paths

The MDN relative-URL guide distinguishes current-directory, parent-directory and site-root references. With the fictional standard base https://assets.example/hero/hero.atlas, page.png resolves under /hero/, while /page.png addresses the site root.

This is a conditional resolution example, not a test of a custom loader. Bundle mappings and signed routes need their own confirmed contract. Do not copy the illustrative host into production.

Connect four delivery observations

1. Preserve the matching atlas and images with their uploaded names and directory.
2. Record the failing path, status and redirects, excluding secret query credentials from public reports.
3. Compare the resolved page address with the request actually made and locate the first difference.
4. Correct one confirmed mapping in a copy and retest the other pages.

Check spelling, case and escaping. Case sensitivity depends on hosting and routing. Creating many guessed copies can conceal the original mapping error.

A successful status is another checkpoint

A 200 response containing HTML login content is not image acceptance. Inspect type and content. If the right image arrives but regions are scrambled, use the separate original-versus-preview atlas checklist.

Resolving a path does not validate runtime version, texture support and all region data. Keep the original failure and the next result rather than declaring the entire integration complete.

Accept the full export

Retain the export from Spine Workbench using its guide. Check each page and representative movements in the receiving project.

No new loader or target-engine experiment is supplied here. Record files, resolution rules, requests and observations, not merely that uploading finished.