TrimSafe ← Back to site
Reading a report

How to read a TrimSafe report

Someone has sent you a report made with TrimSafe, an app for iPhone and iPad — as a PDF, or inside a zip called a handover bundle. This page says what the report records, what it cannot tell you, and how to check its fingerprints with a tool already on your computer.

A TrimSafe report records what a video file said about itself at the moment it was read.

These checks are heuristics. They can flag signs of editing; they cannot prove a file is original. It is not a chain of custody and it is not evidence.

Every fact in it was read off the file, on the phone or iPad that made the report — nothing was uploaded, and none of it was typed in. The name and logo at the top, if there are any, are the sender's own; TrimSafe prints them as given.

Since TrimSafe 2.2 a report can describe a photo too, with the same sections and a still's format, size, lens and exposure where a video's length stands — Sample photo report (PDF), drawn by the same code as a real report over a photo that does not exist.

The line under the letterhead

The seven checks together are called the Camera Original Check, and the report gives their result on one line, with the heuristics sentence directly beneath it. A batch report gives the same line beside each file in its index.

Camera Original Check — passed 7/7

Every check found what a camera original carries, and the findings open with “All seven checks passed. Nothing looked wrong.” That is a smaller claim than it sounds: the file passed seven specific tests. No check can establish that a file is original.

Camera Original Check — 2 of 7 failed

Two checks refused the file. Further down, the report marks each one ✕, calls it refused, and says in a sentence what it means for the file's history. A refusal is a finding, not an accusation: a clip trimmed in Photos, sent through a messaging app or saved by an editor refuses for ordinary reasons.

… 1 could not be answered

The file was missing a fact the check needs, so there was nothing to test — usually Dates consistent on a file with no capture date. Unknown is not the same as no; it is counted neither as a pass nor as a failure.

… 1 did not run

The check was never reached, because an earlier one failed.

✓ passed✕ refused? could not be answered— did not run

If a section headed “This file was made by TrimSafe” sits above the checks, the file is a copy the app wrote — stamped, repaired, converted, compressed, joined, or with its sound removed. A copy carries the facts it was given, so the checks describe the copy as it stands, not the recording underneath.

Origin

Above the seven checks, reports from TrimSafe 2.1 on have a section headed Origin. It reads what the file declares about where it came from, and it has a line of its own. It is not an eighth check: the Camera Original Check still counts seven, so a file can read “passed 7/7” and still not pass, with the Origin line saying why.

Origin: nothing declared

The file carries no marker of AI generation. That is not the same as being a camera original. Absence is not clearance: generators and messaging apps strip markers.

Origin: the file declares AI generation

The file states, in its own metadata, that a trained model made or changed it, and the report quotes what it says. That is a statement the file makes about itself, not a reading of its pixels.

AI markers

Refused if the file declares AI generation — an IPTC Digital Source Type naming a trained model, or a generator naming itself in the software, creator-tool or credit field.

The seven checks

They run in this order, under the names the report uses. The first five look for signs that a file is not what the camera wrote; GPS and Duration are what TrimSafe needs to name a clip and trim it.

Photos edits

Refused if the Photos library holds an adjustment for the video — and just as firmly if library access was denied and the edit state couldn't be read at all.

Make / Model

Refused if the file names neither a make nor a model. A camera original always says what shot it.

QT creation date

Refused if the QuickTime creation date is missing. Without it there is nothing to date the recording by.

Encoder

Refused if the writer tag isn't Apple's, or the make isn't Apple. A foreign writer — ffmpeg, HandBrake, Premiere and the rest — is a sign the file has been through an editor.

Dates consistent

Refused if the movie header and the capture date are more than a minute apart, read either as UTC or as local time — a sign the container was rewritten.

GPS

Refused if the video carries no coordinates. TrimSafe names every file it writes by where it was shot.

Duration

Refused if the clip is shorter than two seconds. Below that there isn't enough of it to trim anything meaningful.

Checking a fingerprint

A fingerprint is a SHA-256 value: 64 letters and digits computed from every byte of a file. Change a single byte and the whole value changes. To check one, compute it yourself from the file you were given and compare it with the one the report printed.

Where to find the report's:

In a single-file report

Under SHA-256 fingerprints — the source file, and the export, read back off disk, if the clip was trimmed. A stamped copy is listed separately and marked derived; check the file each row names.

In a batch report

Under each file, after SHA-256 of and the file's name.

In a handover bundle

In checksums.txt, one line per clip: the fingerprint, two spaces, then the file's name. The bundle also holds the clips, the report as PDF, CSV and JSON, and a README.txt that points here.

If the fingerprint rows are covered over, it is the free report: the findings are complete, but there is nothing to compare against. Ask whoever sent it for the full report.

Open a terminal, type the command for your system with a space after it, drag the video into the window to fill in its name, and press Return.

macOS · Terminal, in Applications › Utilities

shasum -a 256 IMG_4801.MOV

Windows · Command Prompt

certutil -hashfile IMG_4801.MOV SHA256

Linux · any terminal

sha256sum IMG_4801.MOV

Each prints the fingerprint — certutil on the line under the file's name. Compare all 64 characters with the report's. Capital letters don't matter, and nor do the spaces some versions of certutil put between pairs; any other difference does.

On macOS or Linux, a whole handover bundle can be checked at once. Unzip it, open a terminal in that folder, and run shasum -a 256 -c checksums.txt (on Linux, sha256sum -c checksums.txt). Each clip should print OK. The warning about improperly formatted lines is the note at the end of the file, which is not a fingerprint.

What a match tells you A matching fingerprint shows that the file you have is byte-identical to the one the report describes. It is not a signature, and it says nothing about who made the file. Copying a file or sending it as an attachment keeps its fingerprint; re-saving, compressing or trimming it gives a new one. A fingerprint that doesn't match means the file is not the one described — not what changed, or why.
Questions about a report? Email support@trimsafe.app. We can explain what any line means. We can't tell you anything about the file itself — TrimSafe reads it on the device that made the report, and we never see it.
Get the app TrimSafe is a free download for iPhone and iPad.