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

Batch Diagnostic Evidence Export

Export deterministic JSON and CSV evidence for a local batch, including hashes, detector states, strict-format inventory, and exact duplicate groups without embedding source save bytes.

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.

Batch Diagnostic Evidence Export
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.

Phase 58 batch-diagnostics boundary

This Tool is browser-local and read-only. It reuses existing SaveEditor validators and SHA-256 hashing, never modifies selected source files, never authorizes recovery or migration, and never treats an extension-only hint as a verified format.

Batch safety limits

Each file remains under the permanent 16 MiB local-file ceiling. A batch is additionally limited to 64 files and 64 MiB total in-memory data. Raw source bytes are not embedded in evidence exports.

Portable evidence

Evidence contains only names, byte lengths, SHA-256 hashes, detector results, inventory counts and exact duplicate groups. Artifacts contain no raw source images and no repaired/migrated output.

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

Multiple local save/container files; identification is content-validated and never extension-only.

Platforms

No platform assignment is recorded.

Supported versions / editions

Files supported by the existing verified SaveEditor browser-local detectors. Strict format inventory counts only high-confidence validated detections.

Input constraints

1-64 non-empty local files; permanent 16 MiB per-file ceiling and 64 MiB total in-memory batch ceiling. No folder traversal, URL import, archive expansion, or server upload.

Known limitations

Read-only diagnostics only. Candidate-only extension/size hints are kept separate from strict detections. Unsupported files remain unsupported; Phase 58 never promotes a guess into a format claim.

Output / result

Deterministic batch diagnostic JSON plus file, format-inventory, and duplicate-group CSV artifacts bound to the batch identity. Raw file payload bytes are excluded.

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 batch, run diagnostics, then download any of the deterministic JSON/CSV evidence artifacts.

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 58 reads only files explicitly selected in the browser. The permanent 16 MiB per-file ceiling remains in force and each batch is additionally capped at 64 files / 64 MiB total in-memory data. The batch-diagnostics-v1 runtime has no fetch, XMLHttpRequest, WebSocket, sendBeacon, FormData upload, server-side save processing, telemetry, directory traversal, or background upload path. Exported evidence contains filenames, lengths, SHA-256 hashes and detector results only; raw source save bytes are never embedded.

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

Empty files, files above 16 MiB, batches above 64 files, or batches above 64 MiB fail closed. A file that lacks a strict existing validator is reported as candidate-only or unsupported rather than guessed from its extension.

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-10
Profilebatch-diagnostic-evidence-export

Method notes

Verified with deterministic multi-file fixtures covering strict detection, candidate/unsupported separation, SHA-256 exact duplicates, order-stable batch identity, bounded limits, deterministic JSON/CSV evidence, source immutability, no-network static checks, and the full historical regression/source-package parity suite.

Public references

  1. https://www.w3.org/TR/FileAPI/
  2. https://www.w3.org/TR/WebCryptoAPI/

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 Batch Diagnostic Evidence Export 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.