Scratch Pad Online: A Free Browser Notepad That Saves As You Type
A scratch pad earns its place the moment you stop thinking about it. You open a tab, type a phone number, a paragraph that arrived mid-call, or the first line of a bug report, and the text should still be there when the meeting ends. Our scratch pad online does exactly that and almost nothing else: one large monospace text area, an autosave that fires 800 milliseconds after you stop typing, and three counters that tell you what you have written so far.
There is no account, no sync prompt, no onboarding tour. The page is a plain-text editor with a fixed 65vh writing area, and every keystroke is written into your browser's own storage. Close the tab, reboot the machine, come back tomorrow — the draft is waiting. That single design decision is what separates a scratch pad from a document editor, and it is worth understanding what the browser actually does with your text.
What the scratch pad does, field by field
The editor is intentionally narrow in scope, so the whole feature list fits in a table. Everything below is part of the page you open, not a plugin or a paid tier.
| Control | What it does | Detail |
|---|---|---|
| Text area | Free-text input | Monospace, 65vh tall, no formatting toolbar |
| Autosave | Saves locally as you type | Debounced 800 ms after the last keystroke |
| Word counter | Words written | Whitespace-split, updates live |
| Character counter | Characters written | Raw string length, spaces included |
| Line counter | Number of lines | Newline count, so trailing blank lines show up |
| Copy | Copies everything | Uses the clipboard API |
| Download | Saves a .txt file | Named notepad-{timestamp}.txt |
| Clear | Empties editor and storage | Removes the stored draft for this origin |
The status badge in the corner tells you where the save stands: it reads "Saved {time}" once the debounce window closes, and "Auto-saves locally" describes the behaviour you can rely on. If you want a second copy outside the browser, the download button hands you a plain .txt file with a timestamped name — useful before you clear browser data, which is the one action that deletes everything.
How browser autosave actually works
Everything happens through the Web Storage API, specifically localStorage. That is a key-value store that belongs to the page's origin and has no expiry date attached to it. When you pause typing for more than 800 milliseconds, the editor serialises the full contents of the text area and writes it to a single storage key scoped to this site.
Three properties of localStorage explain most of the behaviour you will notice:
- It persists. Data survives page reloads, tab closures, browser restarts and even full operating system reboots. Nothing is cleared on exit the way session storage is.
- It is synchronous. A write blocks the main thread for however long it takes, so writing on every single keystroke is a bad idea on large documents. That is the entire reason autosave is debounced rather than instant.
- It is per-origin, per-browser, per-device. Chrome and Firefox on the same laptop keep separate copies, and neither of them knows anything about the phone in your pocket.
The debounce interval matters more than it sounds. Some editors save on a 300-millisecond timer, others wait a full second; ours sits at 800 milliseconds, which is short enough that you will never see the "Saved" badge lag behind a paragraph, and long enough that a fast typist does not trigger a synchronous storage write after every character. A write on every keystroke is how you get a text editor that stutters when you paste a long document.
What survives, and what quietly deletes your text
The persistence is real, but it is not immortal, and the failure modes are worth knowing before you trust the pad with something you need.
| Event | What happens to your text |
|---|---|
| Refresh the page | Restored from storage on load |
| Close the tab or browser | Restored on your next visit |
| Restart the computer | Restored — storage lives on disk |
| Private / incognito window | Deleted when you close the window |
| "Clear browsing data" | Deleted with the site data |
| Switch browser or device | Nothing there; each browser keeps its own copy |
| Storage full or disabled | The write throws, and the draft is not saved |
Clearing site data is the big one. Browsers do not treat "clear history" and "clear cookies and site data" as the same thing, and most of them let you keep site data while wiping the rest. If you use the pad for anything that matters, downloading the .txt before a cleanup is the habit worth building. Incognito mode is the other trap: it looks identical, saves identically during the session, and then erases everything the moment the window closes.
How much text fits: the 5 MB budget
Browsers give each origin roughly 5 megabytes of local storage, with some allowing 10. Plain text is cheap, so that budget is enormous in practice.
| What you store | Rough capacity at 5 MB |
|---|---|
| Plain text characters | About 5 million |
| Words of English prose | Roughly 2 to 4 million |
| Pages of typical writing | Around 1,000 to 2,000 |
For a scratch pad used the way a scratch pad is meant to be used — a paragraph here, a list there — the limit is invisible. It becomes visible only if you paste entire books into the editor, and even then the symptom is not a warning message but a failed write, which is why the status badge in the corner exists. When a storage write fails because the quota is exhausted, the badge stops reporting "Saved" and your last few keystrokes live only in the text area until you copy them out.
Counting words, characters and lines
The counters update on every keystroke and each one counts something slightly different. Words are split on whitespace, so well-known and don't each count as one word, which matches how Microsoft Word and Google Docs count ordinary prose. Characters are counted by raw string length, spaces included, so a paragraph with heavy indentation reports a larger number than the visible letters suggest. Lines are counted by newlines, which means a trailing empty line is a line.
That split matters when you are writing to a limit. An essay with a 500-word ceiling is a word-count problem; a metadata field with a 160-character boundary is a character-count problem; and a script whose line count is part of a code review is a line problem. Having all three in the same window means you never switch tabs to a separate counting tool to check a number.
Why local-only text is a privacy feature
The text you type is never transmitted. There is no server-side copy, no account, no analytics payload carrying your words, and no sync service that could be breached — the draft physically exists only in your browser's storage on your machine. That is the structural difference between this kind of tool and a cloud document editor, where "private" usually means "only the vendor and its subprocessors can read it".
The honest caveat is that local storage is not encrypted. Anyone with access to your unlocked computer and a browser debugging console can read what you saved, in the same way they could read an unsaved document on screen. Local-only protects you from the network, not from your own device. For notes that need to survive a stolen laptop, a password manager or an encrypted disk is the right tool, not a browser pad.
The convenience argument is real too. A 2023 Statista survey found that 62% of knowledge workers use at least three note-taking or writing applications in a typical week, and the friction of switching between them — signing in, waiting for sync, fighting formatting — is estimated to cost around 20 minutes of lost productivity per person per day. A scratch pad that opens instantly and saves locally removes the sign-in step entirely, which is why people keep one pinned.
Scratch pad or full text editor?
Neither category is better; they answer different questions. A scratch pad optimises for time-to-first-character and for never losing the text you just typed. A desktop editor optimises for file handling, syntax awareness and long sessions.
| Browser scratch pad | Desktop editor (e.g. Notepad++) | Cloud document editor | |
|---|---|---|---|
| Time to start typing | One tab, zero installs | Install once, then instant | Sign-in and sync wait |
| Where the text lives | Browser local storage | Local file on disk | Vendor servers |
| Survives device change | No | Only if synced manually | Yes |
| Works offline | Yes, once loaded | Yes | Partially |
| Formatting and syntax tools | None by design | Syntax highlighting for 70+ languages | Rich documents |
| Risk of losing work | Clearing site data, incognito | Disk failure, unsaved buffer | Account issues, outages |
A practical split that works well: use the browser pad for capture and for anything you want to paste straight into another window, then move it to a file-based editor once the text has earned a name. If your working style involves a lot of quick snippets — a SQL fragment, a regex you are testing, a list of names read out during a call — the scratch pad will carry most of that load.
Practical habits that keep the pad useful
The tool is simple enough that a few small habits cover almost every way people lose text with it.
- Download before cleanup. Any time you touch browsing data settings, use the download button first; the .txt file with its timestamp is a real backup that no storage setting can reach.
- Keep one pad per task, not one pad for everything. Since a single storage key holds the whole draft, pasting a new task over an old one while the cursor is inside the text area replaces it silently.
- Watch the badge after a big paste. Pasting a very large document is exactly the case where the storage quota can be hit, and the badge is the only signal you get.
- Stay out of incognito for anything worth keeping. The pad will save normally and delete everything on close, with no warning at the end.
- Use the counters instead of a second tool. The word, character and line numbers update as you type, so checking a limit costs nothing and requires no tab switch.
- Treat it as a staging area, not an archive. Local storage is durable across restarts, but it is still tied to one browser profile on one machine.
Frequently asked questions
Do I need an account to use the scratch pad online?
No. The pad opens straight into the editor, there is no registration step, no email field and no sign-in wall. The absence of an account is not a marketing choice — without a user identity there is nothing to sync to, which is exactly why the text stays on your device.
Will my notes still be there if I close the browser?
Yes. The draft is written to browser local storage, which has no expiry, so closing the tab, quitting the browser or restarting the computer does not remove it. Reopen the page in the same browser and the text is restored before you start typing, with no restore prompt to dismiss.
What happens if I clear my browsing data?
The stored draft is deleted along with the site data for this origin. If you only clear history and keep cookies and site data, the pad is usually unaffected, but the safe assumption is that a full cleanup wipes it. Download the .txt first if the text matters.
Does the scratch pad work offline?
Yes, once the page has loaded. Autosave writes to storage on your own machine and never waits for a network round trip, so the editor keeps working with no connection at all. Note that the page itself still has to load once while you are online.
How many words can I store?
The practical ceiling comes from the browser, not from the pad. Most browsers allow about 5 MB per origin, which translates to roughly 2 to 4 million words of plain text or around 1,000 to 2,000 pages. Ordinary note-taking will never approach that.
Can I sync my notes between my phone and my laptop?
Not through this tool, because there is no account and no server that holds your text. Local storage is bound to one browser profile on one device. If you need the same draft on two devices, download it as a .txt file and move the file, or keep cloud notes for that specific job.
Why does the editor wait 800 milliseconds before saving?
Storage writes are synchronous and block the main thread, so saving after every keystroke makes typing feel sluggish on long documents. An 800 ms debounce is short enough that the save badge never visibly lags behind your typing, and long enough to skip the writes that a fast typist would otherwise generate.
Is the text encrypted?
No. It is stored as plain text inside your browser's storage area. That protects you from anything happening on the network, since nothing is ever sent, but it does not protect you from someone using your unlocked computer. For confidential notes, use an encrypted local file or a password manager.
When a scratch pad is the right tool
The scratch pad wins wherever the cost of opening a bigger application is higher than the value of the text itself: capturing a phone number while a call is still running, drafting a commit message, holding a list of search terms, or parking a paragraph that needs to survive a browser restart. It loses exactly where local-only storage stops being an advantage — when you need the same text on three devices, when the notes must outlive a browser cleanup, or when the content is confidential enough to need encryption at rest.
Inside those boundaries, a scratch pad that saves itself every 800 milliseconds and never asks you to log in is about as much tool as the job needs. Open the page, type, and let the badge do the worrying.
England, United Kingdom · SO reputation 1999 · Badges: 1🥇16🥈7🥉 · SO member since 2009