Skip to content
Game save workbench
Local-first tools No installation Support status shown
SAVEEDITOR.COM
Browse tools
DEVICE-LOCAL Favorites and recent pages stay in this browser.

File Analysis

Xbox 360 STFS File Table Chain Inspector

Follow only the declared STFS file-table block chain using documented hash-entry next-block fields.

xbox-360

01 / Tool workbench

Use the runtime only when it is actually ready.

The application shell fails closed. An input interface is not enabled merely because a WordPress Tool record exists; the declared engine must be registered in the current build.

Xbox 360 STFS File Table Chain Inspector
BROWSER LOCAL

Checking whether the declared runtime module is loaded. No input has been processed.

Session change summary

No output has been built in this session.

Read-only Phase 65 boundary

This Tool exposes one distinct Xbox 360 XContent/STFS/SVOD structural diagnostic. It never repairs, extracts package files, decrypts, signs, resigns, migrates, converts, or edits game-specific save fields.

Trust boundary

CON/PIRS/LIVE magic, header bounds and the profile-specific structure must validate. Package RSA signatures and STFS SHA-1 hash-tree digests are explicitly not treated as verified, so structural parsing is never presented as proof of console authenticity.

Xbox 360 STFS File Table Chain Inspector

Follow only the declared STFS file-table block chain using documented hash-entry next-block fields.

02 / Compatibility

Know the supported input before opening a file.

Compatibility fields are intentionally explicit. Missing values stay unclaimed rather than being filled with generic assumptions.

Accepted extensions

.con.live.pirs.stfs.bin

Platforms

xbox-360

Supported versions / editions

Xbox 360 XContent metadata versions 1 and 2. STFS-only profiles require volume_type STFS; the SVOD profile requires volume_type SVOD.

Input constraints

Non-empty local file within the permanent 16 MiB per-file ceiling; valid CON/PIRS/LIVE magic, header_size >= 0x971A within the file, metadata version 1 or 2, STFS/SVOD volume type and 0x24-byte descriptor are required. STFS filesystem profiles impose additional exact block/table/directory bounds.

Known limitations

Read-only structural intelligence only. RSA signature verification, STFS SHA-1 digest verification, package extraction, account/profile mutation, decryption, signing/resigning, migration, conversion and game-field editing are not authorized.

Output / result

A deterministic browser-local JSON report bound to the selected package by SHA-256. Raw contained-file payload bytes and signature bytes are not embedded.

03 / Instructions

Use a reversible workflow.

File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.

  1. 01Keep the original

    Preserve an untouched copy before creating or transforming binary output.

  2. 02Confirm scope

    Match the file size, format, platform, and version to the support information on this page.

  3. 03Process locally

    Use the runtime only when the page reports that its declared engine is loaded.

  4. 04Validate output

    Compare or test the result before replacing any working source file.

Tool-specific steps

Choose one local Xbox 360 XContent package. SaveEditor validates CON/PIRS/LIVE framing and the profile-specific documented metadata or STFS/SVOD structure before producing a read-only report. Failed predicates are refused rather than guessed.

04 / Privacy and processing

The processing mode is part of the product contract.

SaveEditor.com should state local processing only when the implementation truly keeps file contents in the browser. Server or hybrid processing must be disclosed just as clearly.

Declared mode

Browser local

Runtime state

Operational

Tool-specific privacy notes

Phase 65 reads only the explicitly selected local package in the browser under the permanent 16 MiB ceiling. Some profiles can display local console/profile/device identifiers; those values remain in the browser and are never uploaded by the xbox-ecosystem-v2 runtime.

05 / Troubleshooting

When a file is rejected, do not force it.

A rejection can indicate an unsupported size, format, version, platform, or byte sequence. Preserve the original and correct the input instead of bypassing validation.

Wrong file or size

Re-check the documented input type and browser size limit before retrying.

Unsupported format

A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.

Source was modified

Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.

Known Tool issues

A refusal means the selected file did not prove the required XContent/STFS/SVOD structure. Renaming a file or matching a common size does not bypass validation. RSA signatures and STFS SHA-1 hashes are not treated as verified.

06 / Verification

Support claims should be traceable.

The verification date, method notes, and public references are kept separate from marketing language so compatibility can be reviewed over time.

Last verified2026-08-11
Profilexbox-360-stfs-file-table-chain-inspector

Method notes

Verified against Xenia XContent/STFS/SVOD structures and block/directory traversal behavior, deterministic generated fixtures, malformed/truncated negative cases, SHA-256-bound output, source immutability, independent reference checks and full historical release/source-package parity.

Public references

  1. https://github.com/xenia-project/xenia/blob/master/src/xenia/vfs/devices/stfs_xbox.h
  2. https://github.com/xenia-project/xenia/blob/master/src/xenia/vfs/devices/stfs_container_device.cc
  3. https://github.com/xenia-project/xenia/blob/master/src/xenia/xbox.h
  4. https://github.com/xenia-project/xenia/blob/master/src/xenia/kernel/util/xex2_info.h

07 / FAQ

Questions to answer before editing.

These answers are generated from the Tool record and current runtime state rather than generic compatibility promises.

Is Xbox 360 STFS File Table Chain Inspector ready to use?
The Tool record is verified and declares an operational runtime. The page enables its input controls only when the declared engine module is loaded in the current build.
Does processing stay in the browser?
Yes for this declared mode. The loaded runtime processes the explicit input in the browser; Tool-specific privacy notes describe the exact scope and limits.
Should I keep the original file?
Yes. Keep an untouched source file until any generated output has been validated.
What if my input is rejected?
Use the validation message to correct the base, encoding, width, timezone, byte alignment, or size. The runtime does not guess through invalid input.

Related guides

Read the guidance connected to this tool.

Only reviewed, index-ready Guides that explicitly reference this Tool are included.