Can I prove somebody uploaded content to a website?¶

Provider or platform records may prove that an account transferred a file or submitted content. Identifying the person behind that action requires corroboration.

Reconstruct the upload event¶

Useful records include the account, timestamp, source address, session, user role, file name, size, type, metadata and hash. Revision or publishing history may show whether the upload was saved, approved, edited or made public.

The device may contain the original file, working copies, upload history, saved credentials or messages discussing publication. A matching hash can connect the local file to the uploaded object.

Uploading, writing and publishing are not the same. One person may create a file, another upload it and an automated workflow publish it later. Shared accounts, API integrations and compromise can also explain the event.

Think of submitting artwork to a printer: the artist, person delivering the file, approver and distributor may all differ.

Align provider and device timestamps and establish who controlled the session. Communications, instructions and benefit may explain direction or knowledge, but should not replace evidence of the technical act.