When a copy of a file is made, the copy is exactly the same as the original (assuming that there were no errors during the copy). This is true whether the file is copied to another location on the same device or to a different device.
The copy might have a different filename, or maybe a different timestamp or different permissions, but the contents are identical.
This can be verified by running some sort of checksum or hashing algorithm (e.g.
md5sum) on the original and the copy.
$ cp original /tmp/thecopy
$ md5sum original /tmp/thecopy
Both files have the exact same md5sum.
original was stored on an NVME.
/tmp/ is a ramdisk.
It is technically possible for two different files to have the same
md5sum. The probability of that happening is extremely low.
md5sum is mostly "good enough" for many simple purposes, but most people use & recommend stronger hashing methods these days to reduce the probability even further. Here's what
sha512sum has to say about the same-ness of the files.
$ sha512sum original /tmp/thecopy