SHA-384 hash

384 bits, printed as 96 lowercase hex characters. That sits between SHA-256 at 64 characters and SHA-512 at 128. The tool takes no options at all, so drop as many files as you like and each one comes back with its own two line result: the title with your file name, then the digest.

It is the SHA-2 member that specific standards ask for. Subresource Integrity attributes on script and link tags commonly use it, several TLS cipher suites pair with it, and some government profiles name it directly. If nothing in your situation names SHA-384, SHA-256 is the more ordinary choice.

SHA-384 is built on the same 64-bit SHA-512 core with a different starting state, and its output is that state truncated to 384 bits. So it is not a lighter algorithm, it is a shorter answer from the same work. The two digests are unrelated values, and you cannot derive one from the other.

Not as is. Subresource Integrity expects the digest in base64 after the sha384- prefix, and this tool prints hex. You would have to convert the bytes, so take the value from a tool that emits base64 directly if that is your goal.

A longer digest raises the birthday bound, so the generic effort to find any two colliding inputs grows with the size. That is the whole of the difference here, and SHA-256 already puts that number far out of reach. Pick SHA-384 because a spec asks for it, not because more bits felt safer.