Skip to main content
File registration creates a dated record of a SHA-256 fingerprint and the details you supply. A matching fingerprint can show that two file copies have the same bytes. Registration does not prevent copying, grant copyright, or independently prove authorship or the truth of the file’s contents.

​
Register in your workspace

  1. Sign in at Truthlocks Verify and open Register your work.
  2. Select or drop a file up to 50 MB. Your browser computes its SHA-256 fingerprint.
  3. Enter a title and optional description. Check that the details are accurate and suitable for your chosen visibility.
  4. Choose private or public descriptive details. You can check for exact matches among public fingerprints; this is not an originality search.
  5. Review and confirm, then submit registration. If the service reports a failure, check your collection before retrying with the same file.
The original file is not uploaded for registration. Keep your own copy so you can compare it later. The record stores the fingerprint and supplied metadata, not a backup of the file.

​
Optional Gemini suggestions

For files up to 10 MB, Suggest with Gemini can use the filename, type and size to suggest a title and description. A separate optional checkbox permits a short text excerpt or basic image metadata to be sent too. Review any suggestions before registering. You can write all details yourself. AI assistance is not required, and its output is not a verification or identity decision.

​
Review the result

After a successful response, open your collection entry to inspect its fingerprint, record ID and saved details. Use Check this record to run a current verification. The public record page and downloadable summary show stored information; they do not replace a current check. Private visibility limits the descriptive details shown publicly. Anyone with a record identifier can still request the available signature, issuer and integrity checks. See public collections for sharing selected records under a public handle.

​
Register through the API

Use a personal-session bearer token. Compute the SHA-256 fingerprint of the complete original file before calling this endpoint. The example fingerprint below represents an empty file; replace it with your file’s actual 64-character hexadecimal fingerprint.
The service resolves the personal signing identity for the account. A successful result includes the protection ID, attestation ID, content fingerprint, registration time, and record links. Treat an error as an unconfirmed result; do not invent a record URL or assume signing succeeded. Retrying an already registered fingerprint for the same account returns its existing record. It does not update the original descriptive details. Use the record visibility endpoint for a visibility change. The current monthly allowance is checked before creating a new registration. Consult the billing page for the recorded plan and contact support if its capacity is inconsistent. Existing records remain available for inspection when a monthly registration allowance is exhausted.

​
Limits of the evidence

  • A fingerprint comparison concerns file integrity, not whether its claims are true.
  • A stored registration time is not proof of when the original work was first created.
  • A personal signing identity is not independent document-based identity verification.
  • Making a record private cannot recall copies of public details already saved by others.

​
Download a readable certificate

Open a record’s shareable proof page and choose Download certificate. The SVG certificate includes the recorded UTC timestamp, record identifier, available fingerprint and issuer details, and a QR link back to the record. Business Console attestation details and the record checker use the same certificate design. Choose Print / save as PDF on the proof page or Console record details, then use your browser’s Print command. The document-generated timestamp is separate from the original recorded timestamp. If the original timestamp is missing from storage, the certificate says so instead of substituting today’s date. A certificate is a readable record summary. For machine verification, download the separate proof bundle and check the available evidence. A certificate does not establish ownership or guarantee that the record remains active.