Encrypted, offline note-taking for Windows. A OneNote-style desktop app (Windows 10 and 11) that keeps your data local and protected with AES-256-GCM encryption.
⬇ Download for Windows (signed installer) · Portable exe · Website · Install with Scoop
- 3-panel layout — Notebooks → Sections → Pages, just like OneNote
- AES-256-GCM encryption — Master password encrypts all data at rest with scrypt key derivation (N=65536)
- Per-notebook locks — Individual password for sensitive notebooks, with per-notebook brute-force rate limiting
- Fully offline — All fonts, scripts, and dependencies bundled locally. The only network request is an optional update check against GitHub Releases on launch
- Rich text editor — Bold, italic, headings, lists, tables, code blocks, links, images, checklists
- Right-to-left writing — Arabic, Farsi, Hebrew and other right-to-left text lines up on the right by itself, paragraph by paragraph, next to English. The Right to Left / Left to Right toolbar buttons (or Ctrl+Right Shift / Ctrl+Left Shift) fix a paragraph's or list's direction, which also moves its bullets, indent and quote bar to that side. Page titles and notebook, section and page names show in their own direction. The menus stay in English
- Image auto-downscale — Pasted photos are automatically resized to 1600px and JPEG-compressed
- Find & Replace — Highlights every match with a live count; Enter / Shift+Enter step through them; match case; replace one or all (undoable)
- Auto-lock — Configurable idle timeout (5/15/30/60 min) + Ctrl+L manual lock + per-notebook "Re-lock Now"
- Encrypted backup — Export/restore
.encbackup files. Restore checks the backup password before touching anything and keeps a rollback copy of your current notes - Crash-safe saves — The data file is written to a temp file, flushed, and renamed into place, so a crash mid-save can't truncate it. If another program holds the file, the save is retried rather than written in place
- Earlier versions — With encryption on, the vault as it was at each of the last 3 unlocks is kept (
noteforge-data.prev-1.encis the newest); open one with File → Restore from Backup - Signed builds — From 2.9.1 the installer, the portable exe and the app are code-signed by James Cupps (Azure Artifact Signing)
- Auto-update — Checks GitHub Releases on launch, downloads and installs updates seamlessly; from 2.9.1 on, an update is installed only if it is signed by the same publisher
- Dark & light themes — Persisted across sessions, applied to all dialogs
- Export — HTML and plain text with unencrypted file warnings
- Keyboard shortcuts help — Press F1 for a list of every shortcut
- Sandboxed renderer — Chromium OS-level process sandbox enabled by default
- Content Security Policy —
connect-src 'none',script-src 'self',img-src data:— no eval, no outbound connections, no remote or UNC images - DOMPurify + hardening hook — All note content sanitized on load, paste and drop; inputs other than checkboxes, the app's own CSS classes and fixed positioning are removed so a note can't imitate the app; images limited to inline
data:images; links to web and email addresses
Full history is in CHANGELOG.md.
2.10.0 (right-to-left writing): Arabic, Farsi, Hebrew and other right-to-left text lines up on the right, paragraph by paragraph, beside English. New Right to Left / Left to Right toolbar buttons and Ctrl+Right Shift / Ctrl+Left Shift fix a paragraph's or list's direction. The word count works in Chinese, Japanese, Thai and other languages written without spaces. Zoom moved from the toolbar to the View menu and Ctrl+= / Ctrl+- / Ctrl+0.
2.9.3 (review fixes): Lock no longer loses edits it can't save: it stays unlocked and says so. A password change also removes the restore's rollback copy, which the old password still opened. Pasting from Excel or Word pastes the text, large screenshots are stored smaller, and the window opens on a connected screen; plus fixes to Find, shortcuts with Caps Lock, the lock screen's menu and start-up with a damaged settings file.
2.9.2 (Electron security fixes): Electron 44.11.1. Each release also carries NoteForge-Setup.exe and NoteForge-portable.exe, so the Download link always gets the newest version.
2.9.1 (signed builds): the installer, the portable exe and the app are code-signed by James Cupps, and from now on the app installs an update only if it carries that signature. No other changes from 2.9.0.
Download the latest installer from Releases:
NoteForge-Setup-x.x.x.exe— Standard Windows installer (recommended)NoteForge-x.x.x-portable.exe— Portable version, no install needed. It keeps its notes in aNoteForge Datafolder next to the exe, so they travel with it (from 2.9.0; on first run it offers to copy notes found on the PC). It doesn't update itself: when a new version is out it opens the download page, and the new exe goes in the same folder
Releases are built automatically by GitHub Actions — no manual build steps required.
Note: From 2.9.1 the installer and the app are signed by James Cupps. If SmartScreen still warns about a new release, More info shows that publisher. Releases up to 2.9.0 were unsigned.
With Scoop (see its site to install Scoop itself):
scoop bucket add jamesccupps https://github.com/jamesccupps/scoop-bucket
scoop install jamesccupps/noteforgeThis installs the portable version and a Start menu shortcut. Scoop keeps its NoteForge Data folder in ~\scoop\persist\noteforge, so your notes survive updates. When NoteForge says a new version is out, run scoop update noteforge.
Uninstalling removes the program but keeps your notes, so a reinstall picks them up again. To keep a copy before removing anything, use File → Export Backup first.
Installed version:
-
Close NoteForge.
-
Uninstall it from Settings → Apps → Installed apps → NoteForge → Uninstall. Or run
Uninstall NoteForge.exein the install folder, by default%LOCALAPPDATA%\Programs\NoteForge. -
To remove your notes and settings too, delete
%APPDATA%\noteforge. Or uninstall with the flag that does it for you:"%LOCALAPPDATA%\Programs\NoteForge\Uninstall NoteForge.exe" --delete-app-data -
Optionally, delete
%LOCALAPPDATA%\noteforge-updater. It holds downloaded update installers, and the uninstaller leaves it behind.
Portable version: delete the exe and the NoteForge Data folder next to it. Portable builds before 2.9.0 kept their notes in %APPDATA%\noteforge, like the installed version.
Scoop: scoop uninstall noteforge keeps your notes in ~\scoop\persist\noteforge; scoop uninstall noteforge --purge deletes them too.
Requires Node.js 22 or 24 (LTS).
git clone https://github.com/jamesccupps/NoteForge.git
cd NoteForge
npm ci
npm run build:jsx
npm test # unit tests (crypto, storage, backup, XSS, install checks)
npm run test:e2e # end-to-end: drives the real app in a temp profile (needs a desktop session)
npm startThe Electron binary is downloaded the first time npm start (or the e2e suite) runs.
To build the installer locally (or use Build.bat on Windows):
npm run distOutput goes to dist/. The predist hook runs tests before building — if any test fails, the build aborts.
| Layer | Algorithm | Key Derivation |
|---|---|---|
| Master (file-level) | AES-256-GCM | scrypt N=65536, r=8, p=1 |
| Notebook locks | AES-256-GCM | scrypt N=65536, r=8, p=1 |
- Master password is never stored — only the derived key (Buffer) lives in memory during the session
- Session key is zeroed (
Buffer.fill(0)) on lock, close, and idle timeout - While the app is locked the main process refuses to write the data file, so a late save can't leave a decrypted copy next to the
.encfile - Password-protected notebooks that are open are encrypted by the main process on every save, with the key cached at unlock, and their plaintext is stripped before the write
- Per-notebook rate limiting with exponential backoff on failed password attempts (persisted across restarts). This only slows guessing through the app; against a copied data file, the scrypt cost is the only barrier, so password strength is what matters
- KDF validation on decrypt: rejects weakened parameters (N < 16384, r < 8) and DoS-sized ones (N > 2¹⁷, more than 128 MiB of scrypt memory, r > 32, p > 16)
- Password strength enforcement: 10+ chars, 3/4 character classes, dictionary check against 160+ common passwords, low-entropy rejection
default-src 'none';
script-src 'self';
style-src 'self' 'unsafe-inline';
font-src 'self';
img-src data:;
connect-src 'none';
All scripts and fonts loaded from local lib/ directory. Zero CDN dependencies at runtime. connect-src 'none' blocks any outbound fetch/XHR from the renderer process, even if code is injected.
img-src deliberately excludes 'self': on a file:// page Chromium matches 'self' against any file: URL, including file://host/share/x.png. That is a UNC path, which Windows fetches over SMB.
Note: The auto-updater runs in the main process (not governed by the renderer's CSP) and makes a single HTTPS request to GitHub Releases on launch to check for new versions. This can be disabled in File → Settings.
- Sandboxed renderer (
sandbox: true) — Chromium OS-level sandbox, on by default - All page navigation is blocked (the app is a single page loaded once)
contextIsolation: true,nodeIntegration: false- All permissions denied (
setPermissionRequestHandler) - DevTools disabled in production builds
- Electron fuses on the packaged app: RunAsNode,
NODE_OPTIONSand--inspectare disabled; embedded asar integrity validation is on, so modified app files fail to load - DOMPurify hook — forces all non-checkbox
<input>elements to lose their type attribute (blocks in-note phishing), and drops any<img src>that isn't an inlinedata:image/ - Links inserted into notes get
target="_blank" rel="noopener noreferrer"automatically - Export dialogs warn about unencrypted output
- Print dialogs warn for password-protected notebooks
- Config keys allowlisted — the renderer can only change
autoUpdate(boolean);sandboxcan only be changed by editing the config file - Backup restore installs only the file picked in the dialog, re-validated just before it is installed
- Data files written atomically (temp file + fsync + rename)
- CI actions pinned to commit SHAs to prevent supply-chain attacks
Security issues? See SECURITY.md for responsible disclosure.
If sandbox: true causes issues on a specific system (rare), close NoteForge and edit noteforge-config.json in the data folder:
{ "autoUpdate": true, "sandbox": false }Then restart. No rebuild required.
NoteForge/
├── .github/workflows/
│ ├── test.yml # CI: unit + e2e tests and a package dry run on every push/PR
│ └── build.yml # Release: test, build and publish on tag push
├── app.jsx # React source (edit this)
├── app.js # Compiled output (generated)
├── main.js # Electron main process + crypto
├── preload.js # IPC bridge (contextBridge)
├── index.html # Shell with CSP
├── styles.css # All styling + @font-face
├── package.json # Scripts + electron-builder config
├── lib/ # Bundled dependencies (React, DOMPurify, fonts)
├── assets/ # Icons
├── test/ # Unit tests (run real main.js / shipped sanitizer)
│ ├── helpers/ # main.js loader with stubbed electron, sanitizer loader
│ └── e2e/ # End-to-end scenarios driving the real Electron app
├── Build.bat # Windows build helper
├── NoteForge.bat # Windows dev launcher
├── LICENSE
└── README.md
- Edit
app.jsx(React/JSX source) - Compile:
npm run build:jsx(commit the regeneratedapp.js; CI fails if it is stale) - Test:
npm test, thennpm run test:e2e - Run:
npm start(uses your real data folder) - Build installer:
npm run dist
To update the bundled DOMPurify: bump the exact dompurify version in package.json, npm install, then npm run vendor:dompurify. test_install fails if lib/purify.min.js and the pinned version disagree.
| OS | Path |
|---|---|
| Windows | %APPDATA%\noteforge\ |
| macOS | ~/Library/Application Support/noteforge/ |
| Linux | ~/.config/noteforge/ |
| Portable build | NoteForge Data next to the portable exe |
| Scoop | ~\scoop\persist\noteforge\NoteForge Data |
Files: noteforge-data.json (unencrypted) or noteforge-data.enc (encrypted), window-state.json, ratelimit.json, noteforge-hint.txt, noteforge-config.json, noteforge-data.enc.pre-restore.bak / noteforge-data.json.pre-restore.bak (after a restore, for rollback), noteforge-data.prev-1.enc to prev-3.enc (the encrypted vault at each of the last 3 unlocks). The earlier versions and the encrypted rollback copy open with the password they were made under, so they're removed when the master password changes or encryption is turned off. A *.tmp file exists only for the moment a save is being written.
Press F1 in the app for an interactive cheat sheet.
| Shortcut | Action |
|---|---|
| Ctrl+N | New Page |
| Ctrl+Shift+N | New Notebook |
| Ctrl+B / I / U | Bold / Italic / Underline |
| Ctrl+D | Duplicate Page |
| Ctrl+F | Find & Replace |
| Ctrl+L | Lock App |
| Ctrl+Z / Ctrl+Y | Undo / Redo |
| Ctrl+Right Shift / Ctrl+Left Shift | Paragraph Right to Left / Left to Right |
| Ctrl+= / Ctrl+- / Ctrl+0 | Zoom In / Out / Reset (also in the View menu) |
| Ctrl+\ | Toggle Sidebar |
| Ctrl+Shift+D | Toggle Theme |
| Ctrl+P | |
| Ctrl+Shift+E | Export HTML |
| F1 | Keyboard Shortcuts |
See docs/CONTRIBUTING.md.
Open an issue for bugs and feature requests. For security reports or general questions, email [email protected].
MIT — James Cupps

