Make the captures, work through the checklist, close the file. That is all the person making the captures has to do: the app puts the date, time and place into the image, works without a signal, and has an independent service timestamp the file. Below is everything the app and the dashboard do, part by part.

On site, with wet hands: the app says what is still missing and draws the details into the image.

Signed on the device and sealed by an independent service. Every check but one works without us, and the confirmation for green comes from our registry.

What you send on, how you share it, and where your captures stay.


Orders set out, captures gathered from outside, and everything in your own system.

Date, time to the second, address and your company name, drawn into the image rather than stored beside it. It is on a printout, a screenshot and a photocopy too, and it stays readable in black and white, because a report often arrives on paper. Nothing to set up: the first capture already carries it.
The time in the bar is the device’s clock; the file carries the timestamped time next to it, and that one is fixed.

A step asks for a minimum number of photos and for the things a photo cannot show: a licence plate, a meter reading, a serial number, a date, a choice from a list. The app can read the plate or the meter in the viewfinder and propose it; you confirm, and your confirmation is what goes in. Every value travels inside the capture, under the device signature and the seal, so it sits under the same signature as the photo.


The signing key is created inside the secure hardware of the phone and cannot be exported, on either platform: the Secure Enclave on iPhone, the hardware keystore on Android. Apple attests it through App Attest, Google through hardware key attestation. Every capture carries a sequence number and the fingerprint of the one before it, under that signature.
To the person receiving the file it is the same file, the same report and the same verification page, with the same checks. Two differences remain: who vouches for the key, Apple or Google, and where the counter comes from: on iPhone from App Attest, on Android kept by the app. A team where half the crew is on Android does not end up with two kinds of file.
The number of captures is part of what is stamped, together with every image and their order. Leave a capture out of the archive afterwards, and the check shows it.
While the file is open you can strike a capture through, for example a photo of your own feet. The image goes, but the strike stays visible with your reason, and it still counts. A file that shows its own corrections is worth more than one where something quietly disappeared.
That is also why you share a file as a whole: the report, the archive or a share link. For a single photo from the archive the verification page verifies only its own Content Credentials; only the whole file shows that it was in the sealed series.


A company with five people on the road has a different question from a single user: who is going where, with which checklist, and is it done. The dashboard answers that. You set up orders with an address, a template and a person; they appear on that person’s phone under “Prepared for you”; and you watch the status move from prepared to picked up to registered. Members, roles and your own templates live there too, and you can search across everything your field staff recorded, including licence plates and meter readings.
With Business by quote and Enterprise, the same thing is available as an API with webhooks, so files land in your own system instead of in an inbox. That is the route for an insurer or a lender who wants the files to arrive where the claim already is.
The dashboard opens captures only where an organisation asked for it: for the delivery on a request, and for files kept at EverStamp. For a kept file the gallery shows previews straight away, for recognition: small images the app made when storing, not checked against the file. The original, photo or video, comes only after a click, checked against the file; in the export it fetches everything. A file without previews the gallery opens only after a click. Every opening goes into the audit log, with who and when: a page of previews as one line naming its files, and the originals as one line per file. EverStamp opens them only at the organisation’s written request, or when a court or authority orders or demands it under the law.

An insurer needs photos from the policyholder. An energy supplier needs a meter reading when someone moves house. A valuer needs photos of the property before a desktop valuation. None of those people want an account or a subscription.
So you send a link. They see who is asking and what for, they work through the checklist, and what comes back is a file with the same device signature, the same seal and the same registry entry as one made by your own field worker. They make the captures in the EverStamp app, which they install first if they do not have it yet.
What is fixed. That the captures and their order existed in this form at the time of the stamp, and that a later change shows up. The clock in the bar and the place are statements by the device, and what the captures show is for the other side to judge. How it works, exactly →
The chain in four links, the standards by name, the window instead of a moment, and the checks.
Read the explanation →Drag a file onto the page and see it for yourself. Four samples of stamped PDFs are ready, one of them a PDF with a forged timestamp date.
Open the verification page →About the app, a file, your plan or Business: write to support@everstamp.app, in Dutch or English. Your answer comes from the people who make the app and the registry. The answers to most questions are already on the support page, and in the user guide in the app, under Settings, Help, User guide. With Enterprise you have a named contact, and a service level by agreement.