Official workflows

Morfs: file workflows that prove they worked.

Pick an outcome, see the exact plan, run it locally in your browser, and walk away with a verification receipt — not just output files and hope.

Visible plan

Every step is shown before you run — no opaque automation, no surprises.

Outcome checks

Each Morf declares what “done” means — page counts, size caps, metadata removal — and verifies it after the run.

Verification receipt

A downloadable record with file fingerprints and every check's result. Generated locally, yours to share.

Official Morfs

Need a different outcome?

Chain any of FileMorf's tools yourself in the Recipe runner — run on batches or whole folders and share the result as a link.

Build a custom recipe

Questions

What is a Morf?

A Morf is an official FileMorf workflow: a fixed chain of file tools with a visible plan, a set of outcome checks that define what “done” means, and a receipt that records whether every check passed. Everything runs locally in your browser.

What does the verification receipt contain?

The steps that ran, SHA-256 fingerprints of your inputs and outputs, the deployed build that executed the run, each outcome check with its observed value, and a pass/fail verdict. It is generated on your device and never uploaded.

Can I customize a Morf?

Yes — every Morf opens in the Recipe runner, where you can change parameters, add steps, run on whole folders, and share your version as a link.

Do Morfs upload my files?

No. Official Morfs are built only from FileMorf's browser-local tools, so your files never leave your device — including during verification.