Lossy versus lossless media: what a preserved copy means

An exact copy can faithfully preserve a video that was already encoded lossily. That is different from a lossless recording of the original scene. When keeping an authorized file, distinguish unchanged bytes, unchanged compressed streams and a newly encoded derivative before describing the result as lossless or original quality.

Locate the comparison that a claim refers to

Lossy compression discards information according to the encoding process. Lossless compression permits recovery of its input representation. Neither label, on its own, tells you whether the input was an unaltered camera source, an edited master or an already compressed platform rendition.

A lossless encoding of an already degraded picture preserves that degraded input. It cannot restore details removed by an earlier processing stage. Conversely, copying an existing lossy file exactly adds no new encoding loss merely because the file's codec is lossy.

Ask what is being compared: the scene, the camera output, the uploader's export, the platform stream or the retained file. A preservation statement becomes meaningful only when its reference is clear. Avoid the unqualified phrase original quality when you do not have the original for comparison.

Distinguish byte copying from stream copying

An ordinary file copy can preserve every byte, which can be verified with a suitable checksum comparison. Stream copying moves existing encoded streams into an output container without re-encoding those pictures or sound. FFmpeg documents that distinction in its processing model.

A remuxed file can preserve the encoded streams while having different container bytes, metadata or ordering. Therefore a whole-file checksum can differ even when the compressed media was not re-encoded. Do not treat that mismatch alone as proof of visual degradation.

Keep the verification method matched to the claim. A checksum demonstrates byte identity between the compared files; a media report describes stream properties; playback checks assess usability. None independently certifies permission, authenticity or equivalence to an unseen camera master.

Check whether a later workflow re-encoded the media

An editor export, format conversion or resized delivery copy can introduce another encoding stage. The settings and source determine the result. A high bitrate may reduce visible damage, but it does not turn a lossy conversion into mathematical recovery of discarded information.

Changing an extension does not change compression. Increasing dimensions cannot recreate missing captured detail. A large output file is not proof of losslessness, and a small unchanged copy is not proof that the transfer discarded additional data.

SocialVidDownloader exposes actual source formats and performs required merging for supported results. Do not infer a lossless source from a successful download or a container label. For a preservation-critical task, keep the available source representation and record exactly what was selected.

Keep honest archive and derivative records

Store an authorized source copy separately from edits or delivery conversions. Note its source item, selection date, available stream information and any subsequent processing. This allows later reviewers to identify which file was retained and which was changed.

If a copied file matches a known original's checksum, describe it as an exact copy of that file. If a remux preserves encoded streams, state that narrower claim after appropriate verification. If a derivative was re-encoded, identify it as a derivative even when you cannot see a difference during ordinary viewing.

When the camera master is unavailable, say so. A useful archive can still preserve the best accessible permitted version without claiming recovered detail, universal losslessness or source authenticity that was never established.

Worked example

Example: a creator supplies an MP4 that already uses lossy video encoding. An exact backup preserves that supplied file without adding a new compression stage. A separate smaller viewing export is a derivative. Calling the backup an exact copy is supportable after verification; calling either file a lossless capture of the scene is not established by that verification.

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.