SHA-512 hash

512 bits, printed as 128 lowercase hex characters, on the line after the algorithm name and your file name. There are no settings and no variants to choose, so the same file always produces the same value, and it lines up with what sha512sum prints for the same bytes.

Not necessarily. SHA-512 works on 64-bit words while SHA-256 works on 32-bit words, so on 64-bit hardware SHA-512 does fewer rounds of work per byte, and on 32-bit hardware the balance goes the other way. Either way the hashing runs in a Web Worker so the page stays responsive on a large file.

Only if something asks for it. Both are SHA-2, both are unbroken, and SHA-256 is what most tooling and most published checksums use. SHA-512 gives you a longer digest and a larger birthday bound, which matters when a specification or a policy says it does.

No, and please do not. A plain fast hash of a password can be guessed at enormous speed, and this tool adds no salt and no work factor. Use the bcrypt, scrypt or Argon2id tools on this site, which are deliberately slow and salted for exactly that job, and which take the password as a text field rather than a file.

Yes. Drop as many as you like and each file comes back with its own digest, so twenty files in means twenty results out. If you want every algorithm at once for a single file instead, Generate all hashes prints the whole hash-wasm table in one pass, SHA-512 included.