AES encrypt then Base64 encode
When sending encrypted data through a channel that only accepts text (JSON fields, HTTP headers, URL parameters), you must encode the raw ciphertext. This chain first AES-encrypts the plaintext with your key, then Base64-encodes the binary ciphertext, producing a string safe to embed in any text medium.
What it solves
Encrypt plaintext with AES and encode the ciphertext as Base64 for text-safe transport.
Input → Output
AES Encryptor input → Base64 Encoder output across 2 steps.
Runs in
2–3 minutes · fully local in your browser.
Before you start
- The plaintext to encrypt
- A 128/192/256-bit AES key
The pipeline
-
Encrypt text or binary data with AES (CBC/GCM/ECB) using Web Crypto API. Free, private, and 100% client-side.
Params: mode=GCM, key=0123456789abcdef0123456789abcdef, iv=0123456789ab
-
Encode text or binary data to Base64 online. Free, private, and 100% client-side.
Runs locally in your browser. The recipe defines the pipeline only — your input never leaves this tab.
▶Run this workflow
Enter your input below and click Run. All processing happens locally in your browser — nothing is uploaded.
Pipeline progress
- AES Encryptoraes-encrypt
- Base64 Encoderbase64-encode
Sample input
Sensitive payload: credit-card=4111111111111111
Expected output
eXN5SlNTcSs4VzJRSlZQY3ltZ1RSaWE4OUt4bHJRNENVS0tzZUx1Y3BKMGJUbFpJdzhNVTlGSGZUbEQ2dUZvLzB1eVZOdWFjOGg2NTNEVFBZNVZ6
This pair is executed against the real tools at build time (tests/unit/recipes.test.ts) — the expected output is verified, not illustrative.
Related workflows
You might also need
Workflows sharing tools or topics with this recipe.