Keep retained sources separate from edited copies

Define source by its role and known provenance

The retained source is the representation from which your project begins. It may be an owner-supplied master or a permitted platform rendition. Describe that distinction explicitly rather than using original as an unsupported production claim.

Preserve the actual source filename or a stable archive identifier, relevant stream information and permission context. If the camera master is unavailable, record that limitation instead of reconstructing a production history from the title.

A larger derivative does not become the original through filesize. Likewise, a remuxed file can preserve streams while differing at the whole-file byte level.

Give each meaningful derivative its own identity

A trim removes context, a captioned edit adds or changes presentation, and a conversion changes a technical representation. Record the actual operation rather than treating every new output as an unchanged copy.

Use distinct names or locations that prevent accidental overwriting. Connect each derivative to its parent source identifier in the manifest. If several derivative stages exist, preserve enough lineage to reproduce the relationship.

Keep permission scope in view. Authorization to retain a source does not automatically establish every redistribution or editing use; preserve the relevant agreement separately.

For a simple Windows Photos trim, Microsoft documents selecting the video, choosing Trim (Ctrl + E), and setting the beginning and ending sliders. Save as Copy creates the modified delivery; the alternative Save action in its dropdown overwrites the original. Choose the copy route when retaining the source is part of the task, then check the actual shortened file independently. A successfully saved trim is a derivative, not proof of an unchanged full-length recording.

Check processing effects instead of assuming equivalence

Compare picture, sound, selected language and duration after each important transformation. A captioned output can accidentally change audio selection, and an editing export can omit a stream the source contained.

Use whole-file checksums for exact-copy claims, not for proving visual equivalence between deliberately different encodings. For derivatives, document the configuration and the practical checks performed.

SocialVidDownloader does not certify edit lineage or manage all subsequent external exports. Its real downloaded artifact is one recorded step in the wider permissioned workflow.

Test recoverability of both sources and required outputs

Back up the source, manifest and any derivative that cannot easily be reproduced. A project file without its referenced media may not reconstruct the intended edit.

Perform a separate-folder recovery test and verify the required artifacts. Keep the source until both the delivery and recovery needs are met.

If a source changes on the platform later, your retained version record should still identify what was obtained at the recorded time. Do not silently replace it and erase the distinction between earlier and later content.

Worked example

Example: retain interview-source as the permitted platform rendition. Give a shortened captioned edit a separate ID, record its parent and the removed interval, and verify its selected audio. Keep both identities in the archive rather than overwriting the source with the final presentation.

Related guidance

• Create a truthful source-and-permission video manifest
• Lossy versus lossless media: what a preserved copy means
• Use an editing proxy without replacing the source

Sources and verification

• Library of Congress: Personal video archiving
• Library of Congress: Moving-image metadata preferences
• Microsoft Support: Edit photos and videos in Windows

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