For contributors
Where did my file go?
Check the files you sent against the archive, without uploading them.
If you have sent files to this archive and cannot find them, check them here. Drop in the files you sent and this page will tell you, for each one, whether the archive has it and what was done with it — published, carried on a memorial page, recognised as a copy of a photograph already held, still waiting for a human decision, or never received at all. Where there is a page, you get the link.
Your files are not uploaded. Your browser reads each file and calculates a fingerprint from its contents — a checksum — and sends only that. The files themselves never leave your computer. This is why a folder of video can be checked in moments rather than re-sent over a slow connection, and why checking a photograph is not the same as contributing it.
The fingerprint is what the archive matches on, not the filename. That matters most for Telegram: an export renames every piece of media by the moment the export ran, so the same photograph exported twice comes out under two unrelated names. Matching contents rather than names is how a file you sent can be found here under a name you have never seen, and how the archive knows it already has a picture without being told.
Drag the files here
or
Whole folders can be selected at once. Nothing is uploaded — your browser reads each file and sends only its fingerprint, so even a folder of video is checked in moments.
What happened to these files
What each answer means
- Published
- The file is on the timeline and the report links to its page.
- On the memorial
- A photograph of someone who was killed. These are filed by person rather than by date, on a page at /heroes/.
- Already held
- The archive had this picture before your copy arrived, or received two copies of it. One is shown and the report links to it. Your file was not discarded — it is in the catalogue, recorded as the same picture.
- Held for review
- Received and catalogued, but a person has to decide about it before it is published — usually because its date could not be established, or its provenance could not be confirmed. The reason is shown.
- Outside scope
- Kept, but not published: it falls outside the period this archive covers, or is not of the events it records.
- Not received
- No file with these exact contents has ever reached the archive. If it is a photograph you may have a re-saved or resized version of one the archive does hold, and the report offers a second check for that.
Why a file can be here under a name you don’t recognise
A Telegram export renames every piece of media by the moment the export ran, so the same photograph exported twice arrives under two different names. Nothing in a filename can be trusted to say what a file is. The archive therefore matches on the contents — the fingerprint this page computes — which is why a file you sent may be filed under a name you have never seen. The full accounting explains how that is decided, and breaks each delivery down file by file.
If something here looks wrong — a file marked outside scope that is not, a date that is off, a photograph that should not be public — say so on the feedback page, or write to info@julydiary.com with the report copied in.