Skip to main content

Protected Text &
Secure Online Notepad

Write notes online, protect sensitive text, and keep your information private with Inkrypt. Use our secure online notepad to create password-protected notes whenever you need them.

No signup required • Private text protection • Easy online notes

A person writing a private note on a laptop, with Inkrypt's browser encryption running alongside

AES-256 GCM

Secured
Client-Side Encryption100%
e2b8c9a1d4f6...
Zero-Knowledge Architecture

Why users trust Inkrypt

Inkrypt is designed for people who need a simple way to write and share private notes online. Security is built into the product from the start, not added as marketing tags.

Encrypted in your browser

Notes are encrypted with AES-256-GCM before they leave your device. Our servers only store ciphertext.

We cannot read your notes

Inkrypt uses zero-knowledge encryption. Passwords are never stored, so only people with the password can decrypt content.

Built for real privacy needs

Share sensitive text with expiry times, view limits, and optional passwords. No account is required.

How Inkrypt Works Secure Online Notepad

Inkrypt is a free online notepad that uses browser-based, client-side AES-256 encryption to protect your text. Whether you need an online notebook for personal thoughts or a secure place for secret text, your password never travels to our servers. Your plaintext is never stored anywhere. Here's how our notepad online works.

Protected Text &
Secure Notepad
Enter your secure note name...
Open Note →

Create Your Online Note

Type a unique notes page URL and click Go. For a new note online, you'll create it fresh. Existing note? You'll be prompted for the password.

Secure This Note

Set a password to encrypt the contents and create your private workspace.

Create a strong password
Retype password
There is no 'Forgot Password' option. If you lose your password, the note is lost forever.
Create Note

Set Password Protected Notes

Your password acts as the AES 256 encryption key. We never store your password, ensuring your private text remains truly secure in our online notebook.

Inkrypt
Share
Save

Title

Write here...

Write & Protect Secret Text

Write, format, and auto-save your private online notes. Use the Share button to send self-destructing links of your protected text with expiry times.

Self-Destructing Notes & Secret Links

Inkrypt's sharing system is built for sensitive information. Create self-destructing encrypted share links with expiry times, view limits, and optional passwords. When your note has been seen enough, it vanishes. No logs, no traces.

"Shared notes are encrypted snapshots. They are read-only views where recipients cannot edit the original note, but you can share updated versions anytime, keeping long-term control."

Custom Expiry Times

Set exactly when your shared encrypted link expires by picking a date and time. The link automatically becomes inaccessible when the window closes. Ideal for sharing temporary credentials.

Optional Share Password

Add an independent password layer to every share link. This is separate from your note's main password. Even if the URL leaks, your encrypted note content stays protected.

View Limits

Restrict your shared note to a set number of views. Set it to a single view for a true one-time secret link. Once the limit is reached, the link self-destructs.

Why Use Inkrypt for Online Notes?

Private Notes

Keep private text away from unwanted access and create notes that are meant only for you.

Protected Text

Protect important text with password protection so your sensitive information stays secure.

Write Notes Online

Use Inkrypt as your everyday online notepad for quick ideas, reminders, drafts, and personal notes.

Easy and Free

Create online notes instantly with a clean, simple, and free online notepad experience.

How it works

What happens between typing and storing

Four steps, all of them in your browser. Nothing readable leaves your device.

  1. You write and set a password

    The password is the only input to the encryption key. It is never transmitted, never logged, and never stored — not even as a hash.
  2. Your browser derives a key

    A 256-bit key is stretched from your password using PBKDF2-HMAC-SHA256 at 310,000 iterations, with a fresh random salt. This is the brief pause you notice on save — it costs any attacker the same on every guess.
  3. Your browser encrypts the text

    AES-256-GCM produces ciphertext plus an authentication tag, so later tampering is detected rather than silently decrypted into altered text.
  4. Only ciphertext is uploaded

    Our servers receive the encrypted blob, the salt and the IV. They perform no cryptographic operation and hold nothing that could decrypt it. See the full walkthrough.

You can check this in thirty seconds

Open your browser's developer tools, switch to the Network tab, and save a note. Inspect the request body — you should see a base64 blob, not your text. This works on any service making this claim, and we would rather you ran it than took our word for it.

Why it matters

Why encrypting in the browser changes who you have to trust

Almost every service encrypts your data. The question that decides everything is who holds the key.

In the usual arrangement, your text travels to a server over TLS and the server encrypts it before writing it to disk. That is genuinely useful — it defeats a stolen hard drive and a network eavesdropper. It does not defeat the service itself, because the service holds the key and handles your plaintext in memory on the way through.

Everything that touches that moment becomes part of your exposure: application logs, error reporting, performance monitoring capturing request bodies, a debugging session someone left running. None of it is malicious. All of it is plaintext.

Encrypting before the network removes the moment entirely. There is no window in which our infrastructure could see your text, so there is nothing for a log or a breach or a subpoena to reach.

The same note under two architectures. The third row is the one that matters.
StageServer-side encryptionInkrypt
You type itPlaintext on your devicePlaintext on your device
Leaving your browserPlaintext, wrapped in TLSCiphertext, wrapped in TLS
At the serverPlaintext, briefly readableCiphertext — unreadable to us
Written to storageEncrypted with the provider's keyAlready encrypted with yours
Who can read itYou and the providerOnly whoever knows the password
The same note under two architectures. The third row is the one that matters.

The full comparison, including when server-side encryption is the better choice, is in client-side vs server-side encryption.

Security architecture

The exact parameters, published

These are the values in the shipping code. We publish them so the design can be evaluated rather than taken on faith.

CipherAES-256-GCM
Key derivationPBKDF2-HMAC-SHA256
KDF iterations310,000
Salt16 bytes, random, per note
IV12 bytes, random, per operation
Authentication tag128 bits
ImplementationWeb Crypto API (SubtleCrypto)
Runs onYour device

Field-level detail on what the database holds, plus the reasoning behind each parameter, is on the security architecture page.

Threat model

What this protects you from — and what it does not

A security tool is only meaningful relative to a specific adversary. Here is ours, including the parts where we fall short.

Summary posture. The full reasoning for each row is on the threat model page.
AdversaryDefendedWhy
A breach of our databaseYesWe hold only ciphertext; no master key exists
Network interceptionYesPlaintext never enters the network
Us, the operatorYesNo key ever exists on our infrastructure
A legal demand for contentYesWe can only produce ciphertext
Someone with only the share linkYesThe link retrieves ciphertext; the password is separate
Offline password guessingPartial310,000-iteration KDF, but bounded by your password
Malware on your deviceNoPlaintext exists before encryption runs
The recipient copying itNoOutside any technical boundary
A forgotten passwordNoDeliberate — recovery would mean we hold a key
Summary posture. The full reasoning for each row is on the threat model page.

If the bottom rows are your problem, use something else

Against an adversary who could compel a provider to serve modified code, no browser-based tool is the right answer — including this one. We would rather say so here than have you find out later. Read the full threat model.

Who uses it

Where an encrypted note is the right tool

Not a password manager, not a document editor, not a messenger. Good at one specific thing.

Encrypted notes fill a narrow gap: getting a piece of sensitive text from you to someone else, once, without leaving a permanent copy in an inbox or a chat log. Almost every situation below is a variation of that.

  • Developers handing over an API key or connection string that would otherwise sit in Slack forever.
  • IT and DevOps teams doing onboarding, contractor access and emergency handoffs.
  • HR and recruiting sending offer details and personal data without a permanent copy in two mailboxes.
  • Agencies and freelancers exchanging client credentials across organisations that share no tooling.
  • Personal use — shared logins, travel details, and private drafts you would rather not leave in a chat history.

When to use something else

Storing hundreds of credentials long-term? Use a password manager. Automated access for an application? Use a secrets manager. Ongoing private conversation? Use an end-to-end encrypted messenger. We would rather point you at the right tool than win a use case we are bad at.

Transparency

Why you should be sceptical, and what we publish because of it

Every privacy product claims to protect you. That claim is worth exactly as much as your ability to check it.

We cannot prove our good intentions, and you should not extend them on the strength of a marketing page. What we can do is publish enough specific, checkable detail that you do not have to rely on trust — and be explicit about the places where our design falls short.

Things we state plainly rather than bury

Inkrypt has not had an independent cryptographic audit. We use PBKDF2 rather than the stronger Argon2id, for reasons explained on the security page. And like every browser-based encryption tool, we serve the code that does the encrypting. All three are on the changelog as open trade-offs.

Use Inkrypt as Your Private Online Notebook

Save personal reminders and daily notes
Create protected text for confidential information
Write drafts before sharing them
Store temporary private notes securely
Keep secret text protected with a password
Use a simple notes page from any device

Protect Your Notes and Sensitive Text

Inkrypt helps you create private online notes and protect sensitive text before sharing or saving it. Use it for personal information, temporary passwords, confidential drafts, and other text you want to keep private.

Latest Insights on Encryption & Online Privacy

Explore our latest guides on zero-knowledge encryption, client-side security, and self-destructing notes. Learn how AES-256, browser-based encryption, and expiring messages protect sensitive data for individuals and teams worldwide.

Read How to Share Passwords Securely Online
How to Share Passwords Securely Online
15 min read

How to Share Passwords Securely Online

Learn the safest ways to share passwords online, why sending plain text credentials via email or chat apps is risky, and how secure sharing tools help protect your data.

Read More
Read Self-Destructing Notes vs Encrypted Email: Which Is Safer?
Self-Destructing Notes vs Encrypted Email: Which Is Safer?
15 min read

Self-Destructing Notes vs Encrypted Email: Which Is Safer?

Learn the difference between self-destructing notes and encrypted email, when to use each for sensitive information, and how to protect confidential data.

Read More
Read AES vs RSA Encryption: What Is the Difference?
AES vs RSA Encryption: What Is the Difference?
9 min read

AES vs RSA Encryption: What Is the Difference?

Learn the core differences between AES vs RSA encryption. Understand symmetric vs asymmetric keys, AES-256-GCM, and how hybrid encryption secures your data.

Read More

Free Encrypted Notepad Online – Secure, Private & Zero-Knowledge

Inkrypt is a free encrypted notepad online that lets you create, store and share secure notes with end to end AES 256 encryption. Unlike traditional note apps, all encryption happens inside your browser, ensuring complete zero knowledge privacy. No signup required, no tracking, and no plaintext storage for truly private note sharing.

No Signup Required

Create secure encrypted notes instantly without creating an account. No email, no login, and no personal data collected for private note sharing from any browser.

Self-Destructing Notes

Generate self-destructing note links that automatically expire after a specific time or number of views. Perfect for sharing confidential messages safely.

Password-Protected Links

Add an extra password layer to your encrypted note links. Even if someone accesses the URL, your private message remains protected.

Client Side AES 256 Encryption

All encryption happens locally in your browser using AES 256 client side encryption. Your password and plaintext data never reach our servers, ensuring true zero knowledge security.

Works on All Devices

Inkrypt is a responsive secure online notepad that works on any device and any modern browser. No downloads, no installations, no platform restrictions.

Frequently Asked Questions About Inkrypt

Learn more about how to use our free online notepad and keep your private notes secure.

What is an online notepad?
Is Inkrypt a free online notepad?
Can I create password-protected notes?
Can I use Inkrypt for private notes?
Can I access my notes online from any device?
Is Inkrypt an encrypted notepad?