DocomintText Encryptor
Encrypt any text with a passphrase you set, entirely in your browser — no length limit, no URL required, no link generated.
Share this passphrase with the recipient yourself — by phone, in person, a different message. It is never included in the output, so anyone with only the encrypted text cannot decrypt it, and Docomint has no way to recover it either.
Your data stays in your browser
Docomint encrypts your text directly in your browser, using the Web Crypto API and a passphrase you set — not a fixed key built into the app. Your original text is not uploaded to Docomint servers for encryption or decryption, and neither is the passphrase — both only ever exist in your browser's memory, and are cleared when you clear the tool or leave the page.
Encrypting
- Your text + your passphrase
- Your browser
- AES-256-GCM encryption
- Encrypted payload (no passphrase inside it)
- Encrypted text you copy and share yourself
Decrypting
- Encrypted text + the passphrase, typed in separately
- Your browser
- AES-256-GCM decryption
- Original text
This uses authenticated encryption (AES-256-GCM) with a key derived from your passphrase (PBKDF2), not ordinary URL encoding or Base64 — the encrypted output has no meaningful visual relationship to the original text, and modifying even one character of the encrypted text makes it fail to decrypt rather than silently returning corrupted content. Because the passphrase is never included in the encrypted text, nobody who has only that — including Docomint — can decrypt it; that also means there's no way for Docomint to recover it if the passphrase is lost.
Secret URL Encoder and Private Message Encoder both produce a clickable Docomint link, which is convenient but means the link's domain and path are necessarily visible — a browser has to read them before any decryption code can run, the same way a mail carrier has to read an envelope's address to deliver it. This tool skips the link entirely: the output is nothing but the encrypted text itself, so there's no domain to show and nothing tying it to Docomint at all. It also drops the other two tools' restrictions — no requirement that the input be a valid URL, no word cap — so it works for anything: a whole paragraph, a config value, a set of credentials you need to hand off outside a password manager. The tradeoff is convenience: the recipient has to come to this tool themselves and paste the encrypted text back in, rather than just clicking a link.
Example: Encrypting "the vault code is 4471, don't text it" with a passphrase produces an opaque string like v1.AQH6DkliyOlR2BZxTk627vSYubOqKkhlWpMInx9Qhy71cHm5L6LJxUy6CsRHE4pzNdSpHf1t8BXmpLCTRuXgHfwsqBpnz6qfZ_KfMRMx5GAJsLpXUC5TvQ — pasting that string plus the matching passphrase back into this tool reveals the original text; anything else (wrong passphrase, a Base64 decoder, one changed character) reveals nothing.
How it works
- Paste or type any text — there's no length limit and it doesn't need to be a URL or a short message — and set a passphrase
- It's encrypted with AES-256-GCM entirely in your browser into an unreadable string keyed by that passphrase
- Copy the encrypted text and share it plus the passphrase separately, however you like — email, chat, a text file — there's no generated link at all
Frequently asked questions
Is my text uploaded anywhere?
No — Text Encryptor runs entirely in your browser using JavaScript/WebAssembly. Your text is never sent to a server.
Why doesn't this tool generate a shareable link, like Secret URL Encoder does?
A clickable link needs a domain and path a browser can read before any decryption code runs — the same way a mail carrier needs a readable address to deliver an envelope, no matter how sealed the letter inside is. This tool skips that tradeoff entirely: the output is only the encrypted text, so there's no domain, no path, and nothing tying it to Docomint at all — at the cost of the recipient having to paste it into this tool themselves rather than just clicking a link.
Does this upload the text I encrypt?
No. Encryption happens entirely in your browser using the Web Crypto API, and neither the original text nor the passphrase is sent to a Docomint server at any point.
Can Docomint read my encrypted text?
No. The encryption key is derived from a passphrase you choose, which is never sent to Docomint and never appears in the encrypted output — there's no key anywhere for Docomint, or anyone who only has the encrypted text, to use.
How should I share the passphrase?
Through a different channel than the encrypted text itself — a call, a separate message, in person. If both travel together (the same email, the same document), anyone who gets one likely gets the other, which defeats the point of encrypting in the first place.
What happens if I forget the passphrase?
The text can't be recovered. There's no password reset — Docomint never receives or stores the passphrase, so there's nothing on any server to recover it from. You'd need to encrypt the original text again with a new passphrase.
Is this the same as Base64 encoding?
No. Base64 is trivially reversible by anyone with a decoder — it's not designed to hide content, only to make binary data safe to represent as text. This tool uses authenticated AES-256-GCM encryption with a passphrase-derived key, so the output has no meaningful relationship to the original text and can't be reversed with a Base64 decoder.
What happens if the encrypted text is modified before decrypting?
Decryption fails with a clear error rather than returning corrupted or partial text. AES-GCM authenticates the encrypted data as a whole, so any change — even one character — is detected, the same as an incorrect passphrase.