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

Emulator & Retro Tools

Xbox 360 XContent Header Inspector

Inspect bounded Xbox 360 CON/PIRS/LIVE XContent header metadata without claiming package trust, filesystem extraction or resigning.

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 XContent Header 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.

Inspect bounded Xbox 360 CON/PIRS/LIVE XContent header metadata without claiming package trust, filesystem extraction or resigning.

Header metadata only. RSA/signature verification, STFS hash-tree validation, directory traversal, profile/account mutation and signing/resigning are not implemented.

Choose a local Xbox 360 XContent package and inspect its bounded header 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 / xbox-360

Supported versions / editions

Current documented container family only; exact structural checks in the profile are authoritative.

Input constraints

At least the documented 0x971A-byte STFS header must be present; magic must be CON/PIRS/LIVE and header_size must fit inside the selected file.

Known limitations

Header metadata only. RSA/signature verification, STFS hash-tree validation, directory traversal, profile/account mutation and signing/resigning are not implemented.

Output / result

Read-only package family, header size, metadata version, content type and declared content size.

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 a local Xbox 360 XContent package and inspect its bounded header fields.

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 46 reads only a user-selected local file and processes it in the browser. The console-v1 runtime contains no fetch, XMLHttpRequest, WebSocket, sendBeacon, form-upload, or server-side save processing. The shared input ceiling is 16 MiB, with stricter per-profile ceilings where applicable.

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

Short files, unknown magic or impossible header_size fail closed; deeper package validation remains unsupported.

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-09
Profilexbox-360-xcontent-header-inspector

Method notes

Verified by Phase 46 deterministic fixtures, an independent Python differential verifier, strict malformed-input negatives, source/package parity, and fresh-extraction release regression. Do not treat a parsed header as proof that the package is authentic, internally hash-valid or safe for a console.

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 XContent Header 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 tools

Continue with the same tool family.

Only index-ready verified records from the same Tool Family are shown here.