Screen evidence and authenticity
How to record when a web page was captured
Record the page URL, capture time with timezone, capture method and visible state alongside the original file. Note whether the view was signed in. Preserve an integrity record promptly. A computer clock or filename alone is weak timing evidence; use independent records or an appropriate timestamping process when timing is disputed.
- URL and timezone
- Signed-in state
- Independent corroboration
Capture record
Describe the page you actually saw.
For a sequence, record start and finish times rather than pretending every segment was captured at one instant. Note changes during capture. A page can change between requests, even when its address stays the same.
- The full relevant URL and page title, with sensitive tokens excluded from shared copies.
- Date and time with an explicit timezone or UTC offset, and the source of that time.
- The visible area, scrolling extent, filters, expanded sections and loading state.
- Whether the view was public or signed in, without storing login credentials.
- The capture method, original filename, operator or controlled record identifier, and known limitations.
Time confidence
Separate a claimed time from an independent record.
A local clock can be wrong or changed. A timestamp drawn into an image repeats what the machine claimed; it does not independently validate it. A file’s modified date can also change when it is copied or edited.
A trusted timestamping process can bind a digest to a time assertion under that service’s rules. It does not prove when the screen content was first created or whether it was true. Choose a process suited to the required assurance and retain its validation material.
Public alternatives
An archive sees a different view from a signed-in user.
For a public page you are authorised to preserve, a public archiving service can provide an independently hosted snapshot and an archive URL. Check that the snapshot actually saved the required page, images and text. Dynamic content, blocked access and missing assets can limit the result.
An archive cannot be assumed to see your account’s private dashboard, personalised results or expanded session state. Never send credentials, private URLs or confidential material to a public archive. Keep signed-in captures within approved handling controls.
Retain the original file, a contextual record and any independent archive reference separately from the presentation copy. State when an archive and your screenshot show different views.
Tool choice
Choose a method that fits the job.
Manual capture notes, public archives and specialist timestamping services address different parts of the problem. Bundlepix can record screenshot provenance, including capture method and signed-in versus public rendering context, but should not be described as an independent trusted time authority.
Further reading
Sources and reference material
Straight answers
Frequently asked questions
Is a date in the filename sufficient?
No. It is a useful label, but can be changed and does not independently establish when capture occurred.
Can a public archive preserve my signed-in page?
Do not assume so, and do not provide credentials to make it do so. Its publicly fetched view differs from your authenticated session.
What if the page changes during capture?
Record the interval and visible changes. Keep source segments and identify the composite as a sequence, not a single simultaneous page state.