Three small additions landed in the Hash Generator's algorithm bar and results panel: two new algorithm families you can turn on with a click, and two new ways to save a single result to disk. None of it changes how the tool works by default — it's all opt-in. Here's exactly where to find each addition and what it's for.
New chips: SHA3-256 and SHA3-512
Quick answerThe algorithm bar above the "Generate Hash" button now has two additional pill-shaped chips labeled SHA3-256 and SHA3-512, next to the original MD5/SHA-1/SHA-256/SHA-384/SHA-512 chips. Click either one to add that algorithm's digest to your results — it computes alongside whatever else you already have selected.
Until now, this tool covered MD5 and the SHA-2 family (SHA-1, SHA-256, SHA-384, SHA-512). Those five chips are still there, still selected by default, and still the ones most people will use. What's new is that if a project you're working on specifically calls for SHA-3 — a NIST-standardized family that computes hashes through a different internal structure than SHA-2 — you no longer need to reach for a separate tool.
SHA3-256 produces a 64-character hex digest, the same length as SHA-256's output, and SHA3-512 produces a 128-character digest matching SHA-512's length. The digest values themselves are entirely different between the two families, so don't mistake a SHA3-256 chip for a second way to compute SHA-256 — it's a distinct algorithm that happens to share a digest length.
New chips: BLAKE2b-512 and BLAKE3
Quick answerTwo more chips, BLAKE2b-512 and BLAKE3, sit at the end of the same algorithm row. Like the SHA-3 chips, they're off by default — click to enable, click again to disable — and the tool computes them entirely with pure JavaScript in your browser, the same as MD5.
BLAKE2b and BLAKE3 aren't NIST standards, but they show up frequently in developer tooling and cryptographic libraries where speed matters — BLAKE2b, for instance, is the hash function underneath the Argon2 password-hashing scheme. Having them available as chips means you can quickly check what a library's documented "BLAKE2b hash of this file" value should look like, or sanity-check output from a script that used BLAKE3, without leaving the browser tab.
As with every other algorithm here, turning on BLAKE2b-512 or BLAKE3 doesn't replace or interfere with your other selections. If you had MD5 and SHA-256 checked and add BLAKE3 on top, the result panel will list all three digests for the same input, one row per algorithm.
New export buttons: JSON and TXT for single results
Quick answerUnder a single text or single-file result, the share row now includes "Download JSON" and "Download TXT" buttons, alongside the existing "Copy all results" and "Copy link" buttons. This is separate from the CSV/JSON/TXT export already available for batch (multi-file) results — the new buttons apply specifically to a single result.
Previously, saving a single text or file hash result to disk meant copying the values to your clipboard and pasting them into a file yourself. Now, clicking "Download JSON" saves a small file with the algorithm-to-digest mapping ready to parse, and "Download TXT" saves a human-readable plain-text listing — the kind of thing you might attach to a support ticket, drop next to a downloaded installer as a manifest, or archive for later without needing to re-hash the file.
Where it lives: both buttons sit in the results card that appears after clicking "Generate Hash" for text or a single file — not in the batch table that appears when you hash multiple files at once. Batch mode has always had its own CSV, JSON, and TXT export buttons for the full table of files.
The distinction matters mainly for what the file contains: the single-result export describes one input and every algorithm you selected for it, while the batch export describes a list of files, each with its own set of digests. If you're only ever hashing one file or one piece of text at a time, this is the export path you'll use going forward.
A quick walkthrough
As a hypothetical example: suppose you're verifying a downloaded configuration file and a colleague's build script reports its hash as a BLAKE2b-512 value instead of the more common SHA-256. Here's how you'd check it with the new additions:
- Switch to the File tab and drop the config file in, or paste its contents into the Text tab.
- In the algorithm bar, click the BLAKE2b-512 chip to turn it on (leave the default five checked too, if you want them).
- Click Generate Hash. The result card lists a row for every selected algorithm, including the new BLAKE2b-512 digest.
- Paste your colleague's reported value into the Expected hash field before generating, and the tool will automatically flag a match or mismatch.
- If you want a saved record, click Download TXT or Download JSON in the share row instead of just copying to clipboard.
None of these steps require anything beyond what was already on the page — the new chips and buttons just extend the same workflow to two more algorithm families and two more export formats.
Try the updated algorithm picker yourself
MD5, SHA-1, SHA-256, SHA-384, SHA-512, plus SHA3-256, SHA3-512, BLAKE2b-512, and BLAKE3 — all computed in your browser, with JSON/TXT export for single results and CSV/JSON/TXT for batches.
Open the free Hash Generator →
Frequently asked questions
Are the new algorithm chips turned on by default?
No. MD5, SHA-1, SHA-256, SHA-384, and SHA-512 are selected by default because they cover the most common use cases. The new SHA3-256, SHA3-512, BLAKE2b-512, and BLAKE3 chips start unselected in the algorithm bar above the Generate button — click a chip to turn it on, and its digest will appear in the results list alongside the others you already have selected.
Can I select SHA-3 or BLAKE alongside the original five algorithms?
Yes. The algorithm chips are independent toggles, not a single dropdown choice — you can leave all five original algorithms on and additionally turn on SHA3-256, SHA3-512, BLAKE2b-512, and BLAKE3, and the result panel will list every selected algorithm's digest for the same text or file in one pass.
Does the new JSON export for a single result include the same fields as the batch JSON export?
Both are structured JSON, but they answer different questions. The single-result JSON export (the "Download JSON" button under a text or single-file result) captures one input and every algorithm's digest for it. The batch JSON export (under the multi-file results table) captures a list of files, each with its own set of digests, since batch mode processes several files in one run.
What does the TXT export look like compared to just copying the results?
"Copy all results" puts a formatted block of algorithm-and-digest lines on your clipboard for pasting somewhere else immediately. The "Download TXT" button saves that same information as a small .txt file on disk instead, which is useful when you want a record you can attach to a ticket, archive next to a downloaded file, or open later without having re-run the hash.
Do the new algorithms run in the browser the same way as MD5 and SHA-256?
Yes. Every algorithm in this tool, including SHA3-256, SHA3-512, BLAKE2b-512, and BLAKE3, runs entirely client-side via JavaScript in your browser. No text or file you hash is sent to a server, regardless of which algorithm chips you have turned on.