Hash Generator computes a checksum of text or a file in five common algorithms at once, useful for verifying a downloaded file matches its published checksum, or generating one yourself.
Match whatever the source provides a checksum in; that's usually SHA-256 these days. MD5 and SHA-1 are still common for legacy checksums but are considered cryptographically broken for security purposes (though still fine for verifying accidental corruption, like a bad download).
No. The file is read and hashed entirely in your browser, using the Web Crypto API for SHA-1/256/384/512 and a local implementation for MD5 (since MD5 isn't available through Web Crypto). Nothing is sent to a server.
Yes, that's the main use case. Hash the downloaded file and compare it against the checksum published by whoever distributed it (on their site, release notes, etc.). A match means the file is byte-for-byte identical to what they published.