Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To support an authenticity claim, preserve the camera original or earliest received file, edit only a separate working copy, keep a dated and readable record of meaningful changes, retain hashes and transfer notes when integrity matters, and attach C2PA Content Credentials when your software supports them. This evidence can show where a file came from and how it changed. It cannot, by itself, prove that the scene depicted is truthful or that an event happened as shown.
What an authenticity record can—and cannot—establish
People use “authentic” to mean several different things. A publisher may need to show that an image delivered to an editor is the same file received from a photographer. A photographer may want to disclose that an image was cropped and color-corrected but not composited. A court, insurer, or investigator may ask whether the depicted scene is an accurate representation under defined criteria. Those are related questions, but they are not the same claim.
Provenance
Provenance describes an image’s origin and history: who supplied it, when it was received, what software handled it, which edits were made, and which file was exported. A clear workflow log is provenance evidence.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Integrity
Integrity concerns whether a particular file has remained complete and unchanged since a known point. A cryptographic hash can test whether a later copy matches the bytes that were hashed. It does not describe what happened before the hash was created.
#1 Best Overall
- Capacity Display Variance: 1TB external ssd often appears as around 931GB on Windows. MacOS can show full 1 TB capacity. This is binary calculation difference and doesn’t affect SSD hard drive actual physical storage
- 1050 MB/s Speed: Instantly access to your files with blazing-fast 10Gbps external SSD read up to 1050MB/s and write up to 1000MB/s. LED Light indicates USB SSD instant activity
- Data Security: Solid state drives S.M.A.R.T. health diagnostics and adaptive TRIM optimizing data block management ensures consistent write speeds and extends the longevity of the portable SSD
- USB-C & USB-A Cable: Both cables featuring rapid USB 3.2 Gen2, this USB SSD effortlessly bridges devices, enabling seamless cross-platform file transfers and backup between computers, smartphones, tablets and iPhone
- Always Fast: No slowdowns for large file transfers. With SLC caching (25% of current available capacity allocated as high-speed cache), this external SSD delivers steady 10Gbps for transfers within the cache capacity
Image authentication
Authentication is a forensic assessment of whether imagery is an accurate representation under stated criteria. It can involve the scene, capture conditions, metadata, file structure, visual artifacts, and independent corroboration. A creator’s log and hash may assist that assessment, but neither is a universal certification.
The distinction is explicit in the SWGDE Best Practices for Image Authentication: “For example, the use of a hash function can verify that a copy of a digital image file is identical to the file from which it was copied, but it cannot demonstrate the veracity of the scene depicted in the image.”
Build the record from intake to delivery
Document the workflow as events occur, not months later from memory. The following sequence works for a single photographer, a newsroom, a commercial studio, or an organization handling evidence. Adapt retention periods, access controls, and approval requirements to your policy and jurisdiction.
1. Ingest and identify the source file
- Keep the earliest available file. For a camera capture, this is normally the untouched RAW, JPEG, HEIF, or video frame received from the device. If you received the image from another person or system, preserve that received file before opening it in an editor.
- Record the intake facts. Note the original filename, source or sender, photographer or operator if known, camera or device if known, receipt date and time with time zone, and transfer method (for example, memory card, secure upload, email attachment, or shared drive).
- Record gaps instead of guessing. If the camera model, capture time, or chain of custody is unknown, write “unknown” and explain where your information ends. Do not reconstruct missing facts from assumptions.
- Assign an internal identifier. A case, assignment, or asset ID lets the log refer to the file even if a later export receives a different name.
For work that may become evidence, preserve the source in storage with access controls and an audit trail. NIST guidance on preserving digital evidence recommends recording source and transfer information and storing hash values separately in a secure location.
2. Protect the original and make a working copy
Do not overwrite the source. SWGDE’s image-processing guidance states: “The original image is preserved and processes are performed on a working copy.” Copy the file into a protected originals location, then create a working copy for editing. Make the original read-only or apply an equivalent control under your organization’s storage policy.
Keep the final export in a third location or clearly separate folder. A practical arrangement is:
- 01_originals: untouched intake files, with restricted write access;
- 02_working: the editable project file and linked source assets;
- 03_exports: delivered JPEG, TIFF, PNG, or other output files;
- 04_records: the edit log, hash register, transfer notes, and approvals.
Folder names are not a substitute for policy. The important properties are separation, controlled access, reliable backup, and the ability to show which file is the source and which is derived.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
3. Preserve non-destructive work where possible
Save the native project file or a sidecar containing adjustment settings when the application supports it. Non-destructive layers, masks, adjustment values, and history can make a later review more intelligible than a flattened export. They do not eliminate the need for a human-readable log: project files can depend on unavailable fonts, plug-ins, linked assets, or changing software versions.
Rank #2
- NONSTOP SPEED: Race through projects with our fastest SSD for creators; Load, edit and transfer with sustained read and write speeds of up to 2,000MB/s1; The T9 Portable SSD performs at high speeds even during longer processes
- DYNAMIC THERMAL GUARD: When you’re elbow-deep in a passion project, the T9 Portable SSD stays cool; Its advanced thermal solution withstands and controls heat to keep the SSD at ideal temperatures—even in heavy use2
- ADAPTS TO EVERY NEED: Whether you’re using a desktop, camera or a gaming console3, count on the T9 Portable SSD for extensive compatibility; It’s a true team player when it comes to heavy-duty application usage or file-saving
- STRONG. SOLID. STABLE: From concept to completion – the T9 Portable SSD gives you the longevity to last through heavy use with one convenient drive that dares to go the distance
- WORKS LIKE MAGIC: Your T9 Portable SSD performs like new with the always up-to-date Magician Software; With firmware updates, extra encryption and continual monitoring of your drive health, it works like a charm
If you must flatten an image or convert formats, record that event. Keep the earlier working file when policy and storage allow, and identify the exact export that was delivered.
4. Log meaningful edits as they happen
The log should allow a similarly trained person to understand and, where practical, repeat the work. It is not necessary to describe every mouse click, but an unexplained change that could affect appearance or interpretation should not be omitted.
Record at least:
- operator or editor;
- date and time of the operation, including time zone where relevant;
- application name and version;
- input filename or asset ID;
- purpose of the edit;
- nature of the adjustment;
- output filename or next working-file identifier;
- handoff, approval, or transfer information.
Describe edits that alter what a viewer might infer, including crops, perspective changes, local adjustments, retouching, object removals or additions, compositing, generative changes, and substantial color or tonal changes. Also record routine technical operations—such as demosaicing, noise reduction, sharpening, resizing, color-space conversion, or compression—when the intended use requires a complete processing history.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchA practical edit-log format
There is no single universal legal form. Use a stable spreadsheet, database, or text record that can be exported and preserved with the asset. One row per operation is easier to audit than a paragraph written at the end.
| Field | What to enter | Example |
|---|---|---|
| Asset and input | Internal ID and exact input filename | JOB-2417; DSC_1842.RAW |
| Operator | Name or controlled account | J. Rivera |
| Date and time | Local time, time zone, and optionally UTC | 2026-10-13 14:32 UTC |
| Software | Application and version | Photo editor 12.4.1 |
| Purpose | Why the operation was performed | Prepare a web proof; preserve aspect ratio |
| Operation | Specific adjustment and scope | Crop to 3:2; global exposure +0.4 EV; no local retouching |
| Result | New file or project state | JOB-2417_work_v03 |
| Export details | Format, dimensions, compression, profile, and export time | JPEG, 4,000 × 2,667 px, quality 90, sRGB |
| Handoff | Recipient, method, and time | Uploaded to assignment portal; 2026-10-13 15:05 UTC |
| Notes | Exceptions, missing data, or approvals | Camera model not supplied by sender |
Use plain language. “Removed a person at the left edge with healing tool” is reviewable; “cleaned up” is not. If an edit is intentionally interpretive—for example, a composite made from multiple exposures—say so directly rather than relying on a technical filename.
Record export and conversion details
The delivered file is often not the same as the working file. For every export that matters, record:
- export filename and destination;
- date and time;
- file format and bit depth when relevant;
- pixel dimensions and resolution setting;
- compression or quality setting;
- color profile or color-space conversion;
- whether metadata was retained, stripped, or rewritten;
- any resizing, sharpening, watermarking, or platform-specific conversion.
Record subsequent transformations too. A content-management system, social platform, messaging application, or document converter may recompress the image or remove metadata. Note the upload time, destination, and resulting filename or URL in the custody record. If the platform creates a derivative, preserve the pre-upload export as the version you controlled.
Use hashes to verify file identity
A hash is a fixed-length value calculated from a file’s bytes. If you calculate the same algorithm on a later copy and obtain the same value, you have strong evidence that the copy is byte-for-byte identical to the hashed file. Record the algorithm, the exact filename, the calculation time, and the resulting value.
Rank #3
- Capacity Display Variance: 500GB external ssd often appears as around 465GB on Windows. MacOS can show full 500 GB capacity. This is binary calculation difference and doesn’t affect SSD hard drive actual physical storage
- 1050 MB/s Speed: Instantly access to your files with blazing-fast 10Gbps external SSD read up to 1050MB/s and write up to 1000MB/s. LED Light indicates USB SSD instant activity
- Data Security: Solid state drives S.M.A.R.T. health diagnostics and adaptive TRIM optimizing data block management ensures consistent write speeds and extends the longevity of the portable SSD
- USB-C & USB-A Cable: Both cables featuring rapid USB 3.2 Gen2, this USB SSD effortlessly bridges devices, enabling seamless cross-platform file transfers and backup between computers, smartphones, tablets and iPhone
- Always Fast: No slowdowns for large file transfers. With SLC caching (25% of current available capacity allocated as high-speed cache), this external SSD delivers steady 10Gbps for transfers within the cache capacity
Keep the hash register separately from the file it describes, in a controlled location with appropriate backup and access restrictions. A hash stored only beside an editable file is easier to replace along with that file. For high-consequence work, record who calculated and verified it and preserve the verification event in the custody log.
What a matching hash proves
- The verified copy matches the file that was hashed at the stated time.
- A later transfer or backup did not change the bytes, assuming the algorithm and process were used correctly.
What a matching hash does not prove
- It does not prove that the camera captured the scene as presented.
- It does not prove that the scene was staged, unaltered, or accurately interpreted.
- It does not reveal edits made before the hash was calculated.
- It does not prove who created the file unless the surrounding custody records establish that link.
Hash the retained original, the working project, and the delivered export when each must be independently verified. If a tool changes metadata or recompresses the image, the new file will normally have a different hash; record it as a new derived asset rather than treating the difference as unexplained corruption.
Add signed provenance with C2PA Content Credentials
Content Credentials are a C2PA-based mechanism for attaching signed provenance claims to an asset. A manifest can identify the source asset, software actions, and ingredients used to create a derivative. The signature and tamper-evident structure help a verifier detect whether the recorded manifest was altered after signing.
Support varies by application, export path, and service. Treat credentials as an additional layer, not as a replacement for the original, edit log, hash register, or custody notes.
When using an editor that supports credentials
- Enable the application’s Content Credentials or provenance option before exporting the document. Some applications require enabling it separately for each document.
- Confirm which actions and source assets the application will include in the manifest.
- Export the file through the supported path rather than an intermediate workflow that strips the manifest.
- Verify the delivered file in a compatible viewer or verifier and record whether credentials are present.
- Keep the original, native working file, readable edit log, and hash record even after successful verification.
Adobe’s Lightroom documentation describes an editing-history option that must be enabled for each document. Camera Raw records information that Content Credentials can reference at export. Interface labels and support can change between versions, so check the current application help for the exact control and verify the exported asset rather than assuming that an enabled preference survived delivery.
Credential failure modes
- Credentials missing after upload: the destination may strip metadata or create a recompressed derivative. Preserve and deliver the pre-upload export, and record the platform transformation.
- Manifest does not list an expected edit: the application may not expose that operation to its provenance system. Put the operation in the human-readable log.
- Viewer cannot verify the signature: retain the file and its manifest, note the verifier and result, and avoid claiming that absence of verification proves manipulation.
Maintain custody, storage, and access records
A provenance trail becomes difficult to defend when files move without explanation. For each transfer, record the sender, recipient, date and time, method, source and destination identifiers, and whether a conversion occurred. Include access or download events when your organization’s policy requires them.
Use backups that preserve filenames, timestamps, project files, and logs. Test restoration periodically. Limit write access to originals and records, separate administrative permissions from editing permissions, and retain an audit trail where available. Encryption, retention periods, and deletion schedules should follow the requirements of the organization and the intended matter; do not promise indefinite preservation if policy requires a defined schedule.
Choose the workflow for the intended use
The same photographer may need different controls for a portfolio image and an insurance claim. Compare a proposed workflow on these axes:
Rank #4
- Slim durable design to help take your important files with you
- Vast capacities up to 6TB[1] to store your photos, videos, music, important documents and more
- Back up smarter with included device management software[2] with defense against ransomware
- Help secure your important files with password protection and hardware encryption
- 3-year limited warranty
| Question | Low-consequence portfolio | News, commercial, insurance, or legal matter |
|---|---|---|
| Is the source original preserved? | Strongly recommended | Required by the applicable policy; protect it from alteration |
| How complete is the edit record? | Brief disclosure may be sufficient | Record operator, times, versions, purpose, scope, and every consequential operation |
| Can another person reproduce or review the work? | Native project file and basic notes | Preserve project files, sidecars, dependencies, and a readable log |
| Are signed credentials supported and retained? | Useful when available | Enable, verify, and document retention; never rely on them alone |
| Are hashes and custody records maintained? | Optional for personal work | Use a separate hash register and document every material handoff |
| Who decides whether the image is authentic? | Creator’s disclosure and audience context | Designated editor, insurer, investigator, court, or other authority under its rules |
No workflow guarantees that an outside organization will accept an authenticity claim. Acceptance depends on the applicable rules, the quality of the records, and evidence beyond the file itself.
Common mistakes and how to correct them
Overwriting the only original
Problem: The edited file replaced the intake file, so there is no untouched reference. Correction: Stop further editing, preserve the current file as found, document what happened, and obtain the earliest surviving copy from the sender, device, backup, or system if one exists. Do not label a reconstructed copy as the original.
Writing the log after delivery
Problem: Dates, settings, and intermediate versions are uncertain. Correction: Mark remembered details as recollections, distinguish them from system-recorded facts, and preserve application history or sidecars that can corroborate the account.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Using vague descriptions
Problem: “Enhanced,” “fixed,” or “cleaned” gives no indication of what a viewer might see differently. Correction: Name the tool or operation, its scope, purpose, and whether it added, removed, relocated, or materially changed content.
Treating metadata as proof
Problem: EXIF fields can be rewritten, stripped, or copied. Correction: Preserve metadata as one record, but support it with the source file, edit history, custody notes, and independent corroboration where needed.
Assuming credentials survive every service
Problem: A platform’s derivative no longer carries the signed manifest. Correction: Verify the file after each important handoff, retain the signed pre-upload export, and describe the platform conversion in the log.
Confusing technical processing with truth
Problem: A carefully documented workflow is presented as proof that the pictured event occurred. Correction: State exactly what the record supports: file identity, processing history, and disclosed alterations. A separate authentication assessment may still be required.
Free tools Windows power users keep installed
One-click scans. No signup required.
Final review checklist before making the claim
- The earliest received or captured file is preserved separately and has not been overwritten.
- The working copy, native project, sidecars, and final export are identifiable.
- The log names the operator, times, software versions, inputs, purposes, meaningful edits, and outputs.
- Crops, retouching, removals, additions, composites, generative operations, and significant tonal or color changes are disclosed.
- Export format, dimensions, compression, color profile, metadata treatment, and conversion events are recorded.
- Hashes include the algorithm, filename, calculation time, and value, with the register stored separately.
- Transfers, recipients, storage locations, access events, and platform recompression are documented when relevant.
- Content Credentials were enabled, exported, and independently verified if the tool supports them.
- The wording of the claim matches the evidence: provenance and file integrity are not presented as proof of scene truth.
A defensible workflow is therefore a chain of clearly identified originals, controlled derivatives, reproducible edit records, integrity checks, and honest limits. It gives a reviewer a way to follow the file’s history without asking the record to prove something it cannot.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
