Unfortunately this is false. I mean, it's technically true if they are the "exact" bit-for-bit files but maintaining fixity of files locally isn't guaranteed just through storage but...

this already has caveats on top of other issues, such as the fact that the metadata associated directly with your NFT probably doesn't directly point to ipfs.io but a custom gateway, where the link rot is completely out of your control.

Remember that the NFT in most cases isn't the artwork but its relationship to the artwork is usually not something you can control. This could change but platforms would need to make those changes.

You might be wondering why ClubNFT thinks this is true. The IPFS hash is basically a checksum, meaning the hash it generates is based on the files fingerprint aka bit-for-bit what makes that file what it is. In digital preservation we run them all the time.

But just because you've downloaded a file locally to your computer doesn't mean it can't become corrupted, suffer from generational loss, bit rot, or really any error that would change the file in some way at a level you may not be able to even see with your own eyes.

So, you can't necessarily guarantee the file will be the same if you try to re-upload it to IPFS. This actually happened to me recently. I was asked to send a video file to someone and I asked them to generate a checksum to make sure it matched mine. It didn't!

It turns out the file I sent on IPFS was then downloaded by a colleague of theirs onto google drive and then downloaded from google drive to their local computer. This alone caused the file to change, although you'd only know it if you ran a checksum.

So, if one tried, this file would generate a different IPFS hash then the video that was sent! Anyway, I had to send the file again and, this time, it came up with an identical checksum. Stay vigilant.