Skip to main content
Filesvo

Hash Generator

Paste any text and get all five common digests at once — MD5, SHA-1, SHA-256, SHA-384 and SHA-512 — as lowercase hex, each with its own copy button. The SHA family is computed by your browser's native Web Crypto engine. Nothing is uploaded to Filesvo.

Processed on your device — files are never uploaded to Filesvo.

How to use Filesvo

  1. Type or paste the text to hash.
  2. Click Compute hashes.
  3. Copy the digest you need from the results.

Which hash should you use?

A hash is a fixed-length fingerprint of your input: the same text always produces the same digest, and any change — even one character — produces a completely different one. The text is encoded as UTF-8 first, so results match what command-line tools like sha256sum produce for the same text.

For anything security-related — passwords, signatures, integrity checks against tampering — use SHA-256 or stronger. MD5 and SHA-1 are cryptographically broken (collisions can be manufactured) and are included here only because legacy systems and checksums still use them; the tool labels them accordingly.

Private by design

Your files are processed directly in your browser using the browser's built-in APIs and are not uploaded to Filesvo. Nothing is stored on our servers, because nothing ever reaches them.

Frequently asked questions

Why does my hash differ from another tool's?
Almost always a trailing newline or different encoding. This tool hashes exactly the text in the box as UTF-8, with nothing added. Command-line tools like echo often append a newline, which changes the digest completely.
Can a hash be reversed to get my text back?
No — hashing is one-way. But short or common inputs can be guessed by brute force, which is why passwords need salted, slow hashing (bcrypt, argon2) rather than any of these plain digests.
Why are MD5 and SHA-1 marked 'not for security'?
Both have practical collision attacks — different inputs can be crafted to share the same digest — so they can't guarantee integrity against a deliberate attacker. They remain fine for detecting accidental corruption and matching legacy checksums.
Is my text sent to a server?
No. All hashing runs in your browser — the SHA family via the native Web Crypto API — and your text never leaves your device.