Take example these 2 images. They have the same MD5 hash:
(253DD04E87492E4FC3471DE5E776BC3D)
https://drive.google.com/open?id=1DdJPc0uShVfueYydBO0-WSoDr0Qzhf3F
https://drive.google.com/open?id=1HSUHhLRBLoyHYT72GZWaB_E6PQ1uWTcD
MD5 is broken and it's trivial to construct files with the same hash by slightly changing a small amount of data appended to both files. Same happened with SHA-1, except it would still require a big chunk of processing power, unlike with MD5 which can be attacked in that way even on old CPU. But, MD5 still has pretty much full preimage resistance, meaning if you hash some data, the attacker would only be able to brute force it to try to find a message that hashes to the same hash value. This means that even with MD5 hash collisions effectively cannot be encountered accidentally.
Until there are known practical attacks against SHA-256, hash collisions are out of the question.
Yeah because SHA256 has 11579208923731619542357098500869e+77 different combinations. So big number...