This read-only workflow fingerprints an exact 32 KiB Nintendo 64 Controller Pak image with SHA-256, records each redundant ID checksum pair and both index-page checksums, compares redundant copies, exports the 123 checksum-covered raw index-node words without inferring allocation chains, maps the metadata and opaque payload byte ranges, and records whether the existing Phase 48 one-defect rule would be eligible. No repaired Controller Pak is produced.
Emulator & Retro Tools
N64 Controller Pak Forensic Report
Generate a deterministic read-only evidence report for all four Controller Pak ID copies, both index mirrors, raw index nodes, byte ranges and the exact Phase 48 recovery decision.
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.
Session change summary
No output has been built in this session.
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
.mpk.bin
Platforms
Nintendo 64
Supported versions / editions
Standard 32 KiB Nintendo 64 Controller Pak / Mempak images using the documented redundant page-0 ID blocks and page-1/page-2 mirrored index table already verified in Phase 48.
Input constraints
Input must be exactly 32,768 bytes. The report may document clean, single-defect, ambiguous or multi-defect metadata states, but does not reconstruct a directory, infer a chain, choose between conflicting valid copies or alter any source byte.
Known limitations
Read-only evidence only. Raw index words are exported as evidence, not interpreted as a recovered directory or allocation chain. No majority voting, directory synthesis, chain/orphan repair, formatting, payload repair or simultaneous multi-region repair is authorized.
Output / result
A deterministic local JSON forensic report bound to the source SHA-256 plus a local CSV byte-range map. Neither output contains a repaired Controller Pak or raw game payload bytes.
03 / Instructions
Use a reversible workflow.
File-oriented workflows start with an untouched original. Tool-specific instructions add only details documented for this utility.
- 01Keep the original
Preserve an untouched copy before creating or transforming binary output.
- 02Confirm scope
Match the file size, format, platform, and version to the support information on this page.
- 03Process locally
Use the runtime only when the page reports that its declared engine is loaded.
- 04Validate output
Compare or test the result before replacing any working source file.
Tool-specific steps
Choose the original 32 KiB Controller Pak image. Generate and preserve the report with the source file. Use the decision log to understand why the existing exact Phase 48 recovery rule is clean, eligible or refused.
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 49 reads only the explicitly selected local file in the browser. The forensic-v1 runtime contains no fetch, XMLHttpRequest, WebSocket, sendBeacon, form upload, server-side save processing, or telemetry path. Reports are generated locally, contain no raw save payload bytes, and never alter or replace the selected source file.
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.
Re-check the documented input type and browser size limit before retrying.
A generic converter does not imply support for every game-specific container, signing scheme, or serialization format.
Return to the untouched source instead of repeatedly processing a damaged or partially transformed file.
Known Tool issues
If valid ID copies disagree, both index pages fail, both valid index pages differ, or more than one metadata region is defective, preserve the original and avoid forced reconstruction. This Tool intentionally reports ambiguity instead of guessing.
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
Profilen64-controller-pak-forensic-report
Method notes
Verified with deterministic clean/corrupt fixtures, independent SHA-256 and metadata calculations, exact byte-range maps, redundant-copy comparison checks, recovery-decision parity with the preserved Phase 47/48 rules, deterministic stable JSON export, CSV range export, immutable-source assertions, no repaired-file output, source/installable parity, and fresh-extract release regression.
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 N64 Controller Pak Forensic Report 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.
Related guides
Read the guidance connected to this tool.
Only reviewed, index-ready Guides that explicitly reference this Tool are included.
Beginner
Backups & Safety
Nintendo 64 Controller Pak Backup & Identification Guide
A safety-first Nintendo 64 Controller Pak guide for identifying the intended representation, preserving an untouched source copy, and choosing only a verified compatible Tool.
Beginner
Save File Formats
Nintendo 64 Controller Pak Integrity & Troubleshooting Guide
A fail-closed Nintendo 64 Controller Pak troubleshooting guide for distinguishing representation problems from unsupported semantics and for selecting read-only integrity checks before any repair attempt.