Encrypt Text Online: Free AES Encryption Without Software
Learn how to encrypt text online with AES-256 and share a password-protected note link. No software download or signup is needed to start.

You have a piece of text that needs to stay private. A password, a personal note, sensitive instructions, financial details, or a message meant for only one person's eyes. You could install encryption software like GPG, learn command-line tools, or set up a PGP key pair. Or you could encrypt it right now, with nothing but a browser tab, using a suitable browser-based tool.
You can use Private Note to encrypt text on LOCK.PUB and share it behind a password without installing software. The important part is understanding where encryption happens and what the service can see.
What is encrypted text, and how do you read it?
Encrypted text is ciphertext: a message transformed using an encryption algorithm and key. To read it, the intended recipient needs the matching decryption method and key, or the password-based workflow that derives that key. A string of unreadable characters alone does not prove that something is encrypted.
| What you have | What it means | How it is read |
|---|---|---|
| Ciphertext from an encryption tool | Encrypted bytes, sometimes displayed as Base64 or hex | Use the compatible tool, key and required parameters |
| Base64-encoded plain text | An encoding, not confidentiality protection | Decode it; no secret is required |
| A hash such as SHA-256 | A digest used for comparison, not an encrypted message | There is no matching decryption operation |
| A LOCK.PUB private-note link | An address for a password-gated memo | Open the link and enter its unlock password |
For a raw encrypted message, keep the format and parameters required by its tool. For example, Web Crypto AES-GCM decryption requires the appropriate key and the IV used during encryption; the IV is not the password. See the Web Crypto decryption reference and AES-GCM parameters.
LOCK.PUB's memo workflow gives you a sharing link rather than an arbitrary ciphertext decoder. It does not recover unknown encrypted messages or reverse password hashes. Choose it when you want to deliver private text through the service's password gate; use a compatible encryption application when you need a portable encrypted file or a specific end-to-end protocol.
How AES-256 Encryption Works
AES stands for Advanced Encryption Standard. The "256" refers to the key length in bits. The algorithm protects data with a symmetric key, but how that key is generated and handled matters as much as the name of the cipher.
The Basic Process
- Plaintext -- Your original readable message
- Key -- Cryptographic key material; a password-based system derives it from the password and its configured inputs
- Encryption -- AES algorithm transforms plaintext into ciphertext using the key
- Ciphertext -- Encrypted bytes, often encoded as text for storage or transport
- Decryption -- The same key reverses the process, recovering the original plaintext
Why Key Strength Matters
The 256-bit key means there are 2^256 possible combinations. Searching that entire space is impractical, but the key length alone does not guarantee the security of an online service. Password strength, key handling, the implementation, and the devices used to read the text also matter.
Symmetric vs. Asymmetric Encryption
AES is symmetric encryption, meaning the same key encrypts and decrypts. This is different from public-key encryption (for example, RSA; systems such as OpenPGP combine public-key and symmetric techniques), where you have a public key and a private key. Symmetric encryption is faster and simpler, but it requires you to share the key with your recipient securely.
End-to-End Encryption Explained
"End-to-end encryption" (E2E) means the encryption and decryption happen on the endpoints -- your device and the recipient's device -- and nowhere in between.
In an end-to-end encrypted design:
- The server never sees the plaintext
- The service does not receive the content decryption key
- A copy of stored ciphertext does not reveal the content without the key
This is different from "encryption in transit" (HTTPS), which protects data between your browser and the server, but the server itself can read your data.
| Type | Your Browser | Server | Recipient |
|---|---|---|---|
| No encryption | Readable | Readable | Readable |
| Encryption in transit (HTTPS) | Readable | Readable | Readable |
| Server-side encryption | Readable | Encrypted at rest, readable in memory | Readable |
| End-to-end encryption | Readable | Encrypted (unreadable) | Readable |
| LOCK.PUB memo | Readable | Encrypted at rest; server processes text and password during creation and unlock | Readable |
For a closer comparison of these layers, read encryption at rest vs in transit vs end-to-end.
Not All Server-Side Encryption Is the Same
"Encrypted" does not describe the whole sharing flow. You also need to know where the keys come from and when the server receives readable text.
- A service-managed key can let the service decrypt stored content without asking the viewer for a password.
- A password-derived key can require a password to reopen stored content. If the server performs the encryption, it still processes the text and password when creating or unlocking the note.
LOCK.PUB's memo flow uses a password together with a server secret. Keep the password out of the shared link: a link alone should not give its viewer the secret text. This is server-side encryption, not a claim that the service cannot see plaintext during processing.
How LOCK.PUB Handles Encryption
Memos are encrypted on our servers with a key built from your password together with a server secret:
When You Create a Memo
- You type your text in the browser
- You set a password
- The text and the password travel to LOCK.PUB over HTTPS
- The server combines your password with a secret of its own -- one that lives outside the database -- and encrypts the text with the result
- Your secret text is kept only as ciphertext, alongside a salted scrypt verifier of your password -- never the plaintext, and never the password itself
When the Recipient Opens the Memo
- They enter the password
- Their browser sends it over HTTPS
- The server checks it against the stored verifier -- a match it can confirm without your password ever being written to our database
- On a match, the key is rebuilt from the password and our secret, the memo is decrypted, and the text is returned
- The plaintext appears in the browser; a one-time link then blocks further reveals
The stored memo is ciphertext, and the password is represented by a verifier rather than stored as plaintext. During creation and unlock, however, the server receives the password and processes readable content. This memo flow is not end-to-end encryption and does not promise protection from a compromised application server. The recipient can also copy or screenshot the text after opening it.
Step-by-Step: Encrypt Text with LOCK.PUB
- Open Private Note for a reusable password-protected note
- Paste or type your text -- anything from a single password to a multi-paragraph document
- Set a strong password -- this is an input to the key derivation, so make it strong and unique
- Write the public introduction -- the one line visitors see before they enter the password, so keep the secret part out of it
- Create the note -- you can begin as a guest without signing up first
- Copy the generated link and share it with your recipient
- Share the password through a separate channel (phone call, different messaging app, in person)
The private text is stored encrypted and revealed after a successful password check. The public introduction is readable before unlock, so it must not contain the secret itself.
If the recipient should get one successful reveal, use One-Time Secret. One free guest creation is available, and Pro supports repeated creation. After the first reveal, later access is blocked; this does not promise immediate deletion of the encrypted record. Pro also offers configurable expiration and access limits in the standard memo creator.
Choosing a strong password
Use a password manager to generate a long, unique password, or independently select random words for a passphrase. Do not reuse published examples, names or an account password. A familiar phrase is not random just because it is long. The password is one input to key derivation; it is not literally half of a 256-bit key.
When to Use Online Encryption
Sharing Passwords
Need to send a colleague their new account password? Encrypt it in a LOCK.PUB memo rather than sending it in plain text over Slack or email.
Sensitive Instructions
Medical dosage information, security alarm codes, safe combinations, server credentials -- anything you would not want a third party to read.
Legal or Financial Details
Bank account numbers, tax IDs, contract terms -- information that could cause harm if intercepted.
Personal Messages
Love letters, confessions, surprise plans -- sometimes privacy is about emotion, not just security.
Limitations to Know
Password Sharing Is Your Responsibility
AES encryption is only as secure as your password management. If you send the memo link and the password in the same email, you have effectively left the vault door open with the key taped to it.
Your Password Is One Input to the Key
For memos, the key uses your password and a server secret. Use a strong, unique password and trusted devices: a compromised browser, extension, or application server can expose text while it is being processed or displayed.
No Recovery Without the Password
If you forget the password, the text can never be opened again. There is no "forgot password" option because the password is never stored -- only a salted verifier of it, which cannot be reversed. This is a feature, not a bug -- but it means you need to remember or securely store the password.
Encrypt Without the Learning Curve
LOCK.PUB handles memo encryption on the server using your password and a server secret, and stores the private text as ciphertext. Use a strong password, keep secrets out of the public label, and share the password separately from the link. Choose reusable or one-time access based on how often the recipient needs to open it.
Create a private note link
Send a secret memo with a separate password. This reusable link lets your recipient reopen the private note in a browser without an account.
Create private noteKeywords
You might also like
Create an Anonymous Message Link for KakaoTalk Groups and Profiles
Make a password-protected question board, share its public link on KakaoTalk, test the visitor view, and understand what anonymous questions do and do not hide.
How to Create an Anonymous Confession Page (No App Required)
Learn how to create an anonymous confession page for schools, communities, or teams using LOCK.PUB Ask Board. Browser-based, no app download, no account required.
How to Send an Anonymous Crush Confession (Without Getting Caught)
Want to tell your crush how you feel without revealing your identity? Here's how to send an anonymous crush confession using secret messages, from playful to romantic.