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

Patch Tools

BPS Patcher

Create or apply BPS1 patches locally with source, target, and patch CRC32 validation.

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.

BPS Patcher
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.

What this patch tool does

Create or apply BPS1 patches locally with source, target, and patch CRC32 validation.

Format and input contract

Phase 20 supports the BPS1 header, variable-length integers, metadata skipping, all four action types, relative offsets, and the three little-endian CRC32 footer values. Browser file/output bounds remain 8 MiB.

Integrity and compatibility limits

The Phase 20 generator is deterministic and standards-valid but intentionally uses a simple linear strategy; it does not claim minimum-size BPS optimization using full source/target dictionary search.

Browser-local processing

When operational, Phase 20 reads only files explicitly selected in the browser, enforces bounded buffers, and does not silently upload patch inputs or outputs.

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

.bps

Platforms

No platform assignment is recorded.

Supported versions / editions

Modern evergreen browsers with JavaScript, Uint8Array, Blob, File.arrayBuffer(), and URL.createObjectURL(). Phase 20 bounds source, target, patch, and output files to 8 MiB.

Input constraints

Phase 20 supports the BPS1 header, variable-length integers, metadata skipping, all four action types, relative offsets, and the three little-endian CRC32 footer values. Browser file/output bounds remain 8 MiB.

Known limitations

The Phase 20 generator is deterministic and standards-valid but intentionally uses a simple linear strategy; it does not claim minimum-size BPS optimization using full source/target dictionary search.

Output / result

Apply a checksummed BPS1 patch or generate a deterministic BPS1 patch from source and target files.

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 Apply for an existing BPS1 patch or Create to generate one. Application rejects a wrong source CRC32 and rejects patch/target checksum mismatches.

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 20 patch generation and application are browser-local. Selected source, target, and patch files are read only after explicit user selection. This runtime contains no fetch, XMLHttpRequest, WebSocket, or sendBeacon calls. Source/target/patch/output buffers are each bounded to 8 MiB.

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

If source CRC32 does not match, obtain the exact unmodified source expected by the patch. Do not disable checksum validation.

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-07
Profilebps-patcher

Method notes

Verified against the public-domain BPS1 specification with deterministic variable-integer vectors, all four action types, source/target/patch CRC32 checks, and an independent reference decoder.

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 BPS Patcher 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.