Before you start: privacy notice

This website does not use Google Analytics or Google AdSense, and does not include traffic analytics or advertising tracking code.

This is a summary of data handling. “Got it” only closes this notice; it does not authorize tracking or Google access. A read marker is saved in this browser until you clear site data or the notice is updated. You can reopen it from the footer.

Text and file encryption, in your browser.

MsgDemo online encryption tool: protect text, images and files with AES-256-GCM.
Explore envelope encryption hands-on: key derivation, data protection and decryption, one step at a time.

Encryption runs in your browser. Msg exchange sends encrypted content after both people agree.
01

Create your key

Set four parameters to derive a reproducible 256-bit key encryption key (KEK).

You can leave this field blank. Providing a username can help Google Chrome remember and autofill securityCode; save prompts depend on your browser settings. The username is not used in key derivation.

No security code yet. Use Generate random for a strong starting point.

The exact security code participates in key derivation: case, spaces and every symbol matter. Generate random creates 24 bytes (48 hexadecimal characters). Decryption requires exactly the same code.

Enter exactly 24 hexadecimal characters, two per byte, or generate 12 random bytes. The seed affects key derivation. New .mcc.json files store seedValue as plaintext metadata to rebuild the key later. It is not the IV used to encrypt the data.

Provided by the encryption core

v4: the seed participates in HMAC and slow PBKDF2 master-key derivation, followed by HKDF for the final key. Different seeds produce different master keys. Different versions produce different keys even with otherwise identical inputs. New and downloaded .mcc.json files store v3 or v4 in keyVersion. The separate version: envelope-v1 field identifies the envelope format.

Key engineengineContent

Choose one of three fixed engines. Their contents cannot be edited. Each engine produces a different key. The file stores engineId and engineName. On import, engineId selects the fixed engine content; engineName is used only for identification and consistency checks.

View fixed content for Engine AMsgDemo::public-demo-engine::A::2026-09::8c619ad0b6e2437fa193d24570ec8b62
PBKDF2 · 660,000 iterations
This takes a moment. Please wait.
Waiting for a key

The full generated key is visible by default. Hiding it disables copying and saves hideKek: true in the JSON. Importing reuses this editable display preference; it is not access control. Keys use a mha-kek-v4: prefix with a Base64URL value. Anyone who obtains a key can decrypt its envelopes.

No securityCode needed

If A securely shares a complete KEK with B, B can decrypt by pasting the KEK and envelope, without knowing securityCode, seedValue or engine content. A supplied KEK is used only for decryption and takes precedence over the derived key. Possession of the KEK grants access to its envelopes.

02

Try encryption and decryption

Enter text or a file, create an envelope, then decrypt, preview or download in your browser.

Generate or enter a KEK first
87 bytes

Enter text, upload any file, or paste text and images from the clipboard. Maximum 1 MiB. Empty text can also be encrypted. Every encryption creates a new DEK and IVs, so identical plaintext normally produces different ciphertext.

Paste clipboard loads the envelope, folders and tags using the same flow as Upload .mcc.json, then decrypts automatically after you enter the security code. You can also paste or edit full JSON to test it. content is ciphertext and wrappedKey is the wrapped DEK. A complete KEK can decrypt without securityCode.

KEY ROTATION / REWRAP · Optional

Rewrap the DEK without changing ciphertext

Authenticate and unwrap the DEK with the current KEK, then derive a new KEK from new parameters and replace only the wrapped key.

Expand settingsCollapse settings
  1. Generate the current KEK from the four original parameters above and prepare the envelope.
  2. Enter new parameters below. You may reuse or change seedValue, but save it together with the new security code.
  3. Choose Rewrap DEK, verify the result, then download the updated envelope.

No security code yet. Use Generate random for a strong starting point.

Use the random generator above, at least 20 random characters, or 6 random words. The security code is not stored in the envelope. Save it separately and securely.

Changing the seed is optional. Reuse it to rotate only the security code, or change it to derive a different KEK together with the other new parameters.

New key enginenew engineContent

Plaintext is not encrypted again. content, content IV, content authTag and envelopeId remain byte-for-byte unchanged. wrappedKey uses a fresh random IV, so even reusing the same KEK produces a different wrapped value.

Take your encrypted envelope with you

Upload / Download.mcc.json

Files are read locally in the browser, up to 2 MiB. New files include keyVersion, seedValue, engineId and engineName so the next upload needs only securityCode. They contain no plaintext, KEK or securityCode. These parameters are plaintext metadata outside the prototype's AES-GCM authentication. Decryption still requires the correct code and cryptographic verification. Older files missing automatic-decryption fields can use the manual JSON flow above. Only envelope-v1 (Base64 or hex) is supported, not legacy iv.authTag.content, v1/v2 keys or existing MCC export formats.

Decrypted resultDecrypted result

Content appears only after the correct key passes AES-GCM authentication. Changes to parameters or data clear the previous result so it cannot be mistaken for a newly verified result.

LOCAL FILE LIBRARY / TAGS + DIRECTORIES

Browser file library

Search by tags, or organize the same .mcc.json file in multiple folders without copying ciphertext. Downloads preserve folders and tags; uploads create missing folders automatically.

0 files · 0 folders

Files, folders and links are stored in this browser and origin's IndexedDB by default. Backups are uploaded only when you choose Back up ZIP to Drive. Folder links do not copy ciphertext; removing a link does not delete the file. Filenames, tags and folder names are not encrypted. Do not include sensitive information.

PERSISTENCE / GOOGLE DRIVE

Storage and account spaces

Google not configured
Persistent browser storage

Checking storage statusChecking with your browser. Please wait.

Backup and batch restore

Download all files, tags, folders and links. The ZIP itself is not encrypted; envelope ciphertext is unchanged. Maximum 64 MiB, 10,000 files and 5,000 folders.

CURRENT VIEW

All files

0 files
Folders (select multiple)

No folders yet. Create one on the left, or use tags only.

A file may appear in multiple folders without duplicating ciphertext. Set at least one tag or folder.

No saved files yet. Encrypt or upload a .mcc.json file, then add tags or folders.

Online text encryption, file decryption and encrypted data exchange

MsgDemo is an interactive envelope encryption tool that runs in your browser. Local encryption and decryption require no signup or software installation. Encrypt text and files, organize local encrypted envelopes, and explore AES-256-GCM, key derivation and the roles of KEK and DEK.

Encrypt and decrypt text

Enter a security code and text to create an encrypted envelope. Express mode prepares the remaining parameters automatically. The key workbench also lets you explore PBKDF2 key derivation, choose v3 or v4, and verify decrypted content with AES-GCM authentication.

Open the key workbench →

File encryption and local library

Select an image, document or another file type, encrypt it locally and download a .mcc.json file. Import the encrypted file later and enter the original security code to restore its content. The local library stores encrypted envelopes with tags and folders.

Open the encryption tools →

Exchange encrypted text, files and clipboard content

Open Msg exchange from the navigation and invite another person using their exchange ID. Once paired, you can sync encrypted text. Each file or clipboard transfer requires the recipient's approval before content is sent. The server temporarily holds ciphertext and necessary connection and transfer data.

Encryption and decryption FAQ

What is envelope encryption, and how do KEK and DEK differ?

Envelope encryption uses two layers of keys. Each encryption creates a new data encryption key (DEK) to encrypt content with AES-256-GCM. A key encryption key (KEK), derived from the security code and other parameters, wraps the DEK. Rewrapping replaces the KEK protecting the DEK without encrypting the content again.

Does online encryption upload my plaintext, files or security code?

Local encryption and decryption run in your browser without uploading plaintext, original files, security codes or keys. Data exchange temporarily stores encrypted content on the server and exposes transfer details such as file names and sizes. If you enable Google Drive backup, encrypted envelopes and library backup data are uploaded. These features require your action.

How do I decrypt a .mcc.json file? Can I recover a forgotten security code?

Import a .mcc.json file created by MsgDemo and enter the exact original security code. The app derives the key and decrypts using the file's version, seed and engine information. An original, valid complete KEK can also decrypt it. Files contain neither the security code nor the KEK. If both are lost, this app cannot recover the content.

What are the file size limits and usage considerations?

Local encryption accepts up to 1 MiB of text or original file data. Imported encrypted envelopes can be up to 2 MiB. Data exchange has separate limits shown in its window. Use HTTPS or localhost and keep a sufficiently long, random security code safe. This is a public interactive demonstration with visible fixed engines. Verify the connection code through a trusted channel when exchanging data. The app cannot protect against compromised devices or malicious website code.