Back to Tools

Crypto Workbench

Chain Base64, JWT, hashes, PBKDF2, and AES-GCM with browser-side salted encryption workflows

Last updated
My tools
No tools yet

Loading...

How to build a recipe

  1. 1

    Paste input

    Paste a token, ciphertext, encoded string, or plaintext into the input area.

  2. 2

    Add steps

    Add encoding, hashing, KDF, or encryption steps from suggestions or the operation library.

  3. 3

    Tune parameters

    Fill in keys, passphrases, salt, IV, and iteration counts for HMAC, PBKDF2, or AES-GCM.

  4. 4

    Inspect the trace

    Review each step output to find the layer that needs adjustment.

Features Overview

Crypto Workbench is a browser-side workspace for encoding, decoding, hashing, HMAC, PBKDF2, and AES-GCM. Build repeatable recipes to inspect JWTs, Base64URL, URL encoding, Hex, HTML entities, and encrypted envelopes.

Tool Description

A local-first encoding and cryptography workbench. Combine Base64/Base64URL, Hex, URL, HTML, JWT, SHA, HMAC, PBKDF2, and AES-GCM operations into repeatable recipes without uploading keys or input.

Capabilities Checklist

  • Convert Base64, Base64URL, Hex, URL, and HTML entities in both directions.
  • Decode JWTs and run SHA digests, HMAC-SHA256, PBKDF2-SHA256, and AES-GCM.
  • Configure salt, IV, iterations, and output length with random salt / IV generation.
  • Run recipes step by step with intermediate output, errors, and warnings.
  • Everything runs in the browser; inputs and keys are not uploaded.

Related Tools

Frequently Asked Questions

Does this tool upload keys or input data?
No. The current version runs operations in the browser, and history is stored only in local browser storage.
Why is there no MD5 decrypt action?
Hashes are one-way digests and cannot truly be decrypted. The tool keeps hashing, KDFs, encryption, and encoding separate.
What is the agcm1 AES-GCM output?
It is the tool envelope containing iterations, salt, IV, and ciphertext so the AES-GCM decrypt step can restore the plaintext later.