COLLECTION INSPECTOR

Archive Manifest Format Converter

Convert supported checksum manifests while retaining relative paths and algorithms.

Collection contents

Load the worked example or open your own input.

Preparing local example…Local processing · Review before use

Start with the worked example. Edit your input or settings, inspect the result, and open Export for task files or a complete ZIP. Save project keeps editable text and settings; image/file projects need their original source files when reopened.

Record details

Using Archive Manifest Format Converter

Convert supported checksum manifests while retaining relative paths and algorithms.

  1. Select Try example to see a complete archive manifest format converter workflow. Use the editable worked example as the JSON structure, or open a local JSON/YAML text fixture. File inspectors accept their stated local formats.
  2. Adjust the labelled controls or open Input/Geometry to change the evidence. Run workflow applies the current input; undo and redo restore text/settings decisions.
  3. Inspect the task preview, record details and method notes. Findings describe cases that need review; missing evidence remains unknown.
  4. Open Export for task artifacts, JSON/CSV results or a complete ZIP. Save project keeps input/settings; projects with local binary files need their original files to be reselected when reopened.

Example

The worked example for Archive Manifest Format Converter produces 2 evidence records and 2 task artifacts. Supports unescaped GNU-style and BSD-style MD5/SHA-256/SHA-512 records or explicit JSON rows. Hash values and relative paths are retained; escaped/newline filename variants require manual handling.

Questions & answers

What does Archive Manifest Format Converter do?

Supports unescaped GNU-style and BSD-style MD5/SHA-256/SHA-512 records or explicit JSON rows. Hash values and relative paths are retained; escaped/newline filename variants require manual handling.

What should I open or paste?

Use the editable worked example as the JSON structure, or open a local JSON/YAML text fixture. File inspectors accept their stated local formats. The worked example defines the supported input fields. Edit its values, run the workflow and inspect the method notes before exporting. Each selected file must be nonempty and at most 25 MiB, with at most 30 files and 80 MiB total. Image jobs use up to 12 still frames, six million pixels per image and 18 million total pixels. Individual format inspectors may apply stricter limits.

What results can I export?

The Export view includes the task-specific artifacts listed for your actual result, a typed JSON report, a CSV table and a complete ZIP. Save project stores editable input and settings; selected binary sources are represented by fingerprints and must be reselected. Secret-option values are excluded from saved projects.

Does it upload files, run commands or change a live system?

Processing uses your supplied evidence in this browser. Planners and protocol tools do not connect to services, execute imported code or apply changes automatically. Public pages include the site’s approved advertising and optional consent-based analytics.

Help improve this tool

Report a problem or suggest an improvement

Describe the issue without pasting private tool input. Feedback goes to our admin inbox.

Find another tool · Read practical guides