A file address is not a date

A familiar view can return with the same vehicles, shadow or patch of sky you noticed earlier. It is natural to wonder whether the camera has stopped. The image alone cannot answer that. A stable web address tells the browser where to ask for a resource; it does not promise that the scene is newly photographed every time the page is opened.

There are several events that can be mistaken for one another: the camera captures a frame, a service receives or stores an image, a web server answers a request, and your browser displays the response. A date in the page or a recent network request may describe one of the later events. Unless a trustworthy mark identifies the capture, it cannot be treated as the time the street was seen.

This distinction matters because browsers and intermediate services may reuse stored responses. The HTTP caching model describes how a stored response can be reused or revalidated; it does not make the cached object a live sensor. The MDN caching guide explains freshness as a property of stored web responses, while RFC 9111 defines the protocol rules.

Freshness belongs to the response

“Fresh” has a precise web meaning: a cache may reuse a response without contacting its source when the response’s cache rules allow it. That is useful for speed and reliability. It is not the same as “the camera just took this picture”. A response can be freshly served from a store and still contain an older frame.

The Cache-Control header can influence how caches store and reuse a response. It describes handling rules for the response, not the shutter time of the camera. If an image includes a timestamp overlay, you still need to know whether that mark comes from the camera, a provider system or an editorial label. TfL’s camera-place API identifies camera records and related information; it should not be read as proof that every displayed pixel has a verified capture time.

This is why a visible clock, file name or “last updated” label deserves careful reading. Ask what event it names. If the source does not say, keep the distinction open instead of subtracting times and calling the result the age of the scene.

What a reload can tell you

Reloading is a modest troubleshooting step. It tells you that the browser made another attempt to show the page. Depending on the browser and cache rules, the image request may be answered from a stored copy, checked with a server or fetched anew. A reload cannot independently prove that the camera captured a later frame.

If the image changes, you can say that the displayed image changed between visits. You cannot infer precisely when either frame was captured unless the source supplies reliable capture evidence. If it does not change, that could mean the scene stayed similar, the image stayed the same, or an upstream layer reused a response. The appearance alone cannot choose among those explanations.

A browser’s refresh button is not a diagnostic instrument for the entire delivery chain. Avoid repeatedly refreshing in the hope of forcing a new exposure. It can add requests without improving your evidence. One sensible reload, followed by a different camera or an official current-information source, is usually a clearer way to proceed.

Choose a useful next step

If you are learning the shape of a place, compare stable features: a bridge parapet, building edge or road junction. Westminster Bridge, Oxford Street–Selfridges and Piccadilly Circus offer different compositions; their camera labels identify places, not guaranteed viewing directions or present conditions.

If you need a time-sensitive answer, use information that was published for that decision and carries an appropriate time context. A camera can provide visual orientation, but a still does not report service disruption, a road closure outside its frame or the exact moment shown. For two frames, do not compare vehicle counts as if they were sampled together unless their capture times are verified to match.

When you describe an image to someone else, record the visible marking separately from your inference. “The page was opened at 14:08” is a browser event. “The picture was taken at 14:08” needs evidence about capture. Keeping those sentences apart prevents a plausible clock from becoming a false certainty.

Sources & further reading

Official references inform this guide. Check the responsible organisation for current access, opening times and travel advice.