SocialVidDownloader.
English
Download

Capture dates, embedded metadata and copied-file timestamps

A filesystem timestamp can change during copying or export without changing when the scene was recorded. A photo-library date and an embedded media date are also different kinds of evidence. Keep their meanings separate when organizing an archive, and do not infer capture history from one newly created file’s date.

More help on this subject

Open the relevant downloader · Platform tools and access limits

Video Information

Record where each date came from

Inspect the actual source file and note which program reports the date. A library can organize a movie using its own catalog information; a file manager can display creation or modification information from the receiving filesystem. A media inspector may expose an embedded tag whose meaning depends on how that resource was created.

Label those observations explicitly instead of merging them into an unexplained capture-date column. A timestamp with an absent or uncertain timezone should not be silently converted into an exact universal moment. Recording notes and trusted original context can be necessary when the file alone does not establish the event time.

Keep export identity separate from library organization

Before an authorized Photos export or ordinary copy, identify whether the operation produces an original resource or an edited derivative. Record the chosen source item and save to a distinct destination. A library’s displayed date need not become every date shown by the new file’s filesystem.

Do not assume that a fresh destination creation time means the movie contains a new event. Equally, preserving a timestamp label does not prove the copied bytes are the same. Verify the recording’s identity, duration and representative content independently, and retain a source-to-export note when library organization matters.

Check unexpected dates without overwriting evidence

Compare the original and receiving copy’s metadata, names and actual content before applying bulk renaming or date correction. Identify whether the discrepancy concerns timezone display, an export-created file, an edited library date or missing original metadata. Correct the organizing scheme only when the intended interpretation is established.

The downloader and processing utilities do not certify historical capture dates or reconstruct missing chronology. Processing can create a derivative with its own file history. Preserve original observations in an accompanying archive note rather than pretending that a converted media tag is independently verified proof of when an event occurred.

Worked example

A camera recording is exported from a library months after capture. Its destination file shows today’s creation time, while the library displays an earlier recording date. The archivist labels the first observation as export-file information, preserves the second with its source context, and checks the actual movie before deciding whether a date discrepancy represents the wrong version.

Related guidance

Sources and verification

Reviewed 2026-10-12. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.