Every release of Facet, newest first. Both editions — Facet and the free Facet Reader — are built from one source tree and share a version number, so a fix listed here lands in both. Get the latest build →
Pressing Tab while typing notes moved the keyboard focus out of the detail card altogether — usually into a control belonging to another window, often one scrolled out of sight. The notes lost their caret and further typing went somewhere invisible, so the box looked frozen; clicking away from the item and back restored it. Tab now indents instead, which is what it was being pressed for: two spaces, the amount that nests one Markdown list item under another. Shift+Tab outdents, a multi-line selection shifts every line it touches, and Ctrl+Tab is there when you do want to move on to the next field. Indents join the normal undo history, so Ctrl+Z behaves as it does for typing.
Adding items and then pressing Back up now reported everything already backed up and wrote nothing, because today's backup merely existing was taken as proof that it still matched. Facet now compares the backup against the database itself — the database file byte for byte, and every bundled image and queued capture by presence, size and modification time — and writes a fresh package when the two have parted company. The extra one is stamped with the time as well as the date, so the morning's backup survives: an explicit backup adds a restore point rather than replacing one. Press it twice with no editing in between and the second press still correctly does nothing.
Every path shown on Settings → File Locations — the database folder, the backup folder, and each database in the daily backup list — now has a Copy path button beside it, for pasting into Explorer, a terminal, or an email without retyping it.
The user guide (57 pages) and developer guide (23 pages) cover the new backup behaviour and the notes shortcuts, as do the in-app Markdown help and the Ctrl+/ shortcut cheat-sheet.
If the drive or folder holding your data went away — an unplugged USB stick, an unmapped network drive, a dropped VPN share, a deleted folder — Facet failed on startup before any window appeared, leaving no way to fix it except editing the settings file by hand. Facet now always starts: it falls back to a location that works and tells you, once, which location failed and which one it opened.
A missing stick or a dropped share is usually temporary, so Facet deliberately does not rewrite the saved database path when it falls back. Reconnect the drive, restart, and your real database is back with nothing to tidy up. The stand-in database is added to Open Recent so it stays reachable either way.
The same fault could also strike one save later, with the app already open. A backup that cannot be written no longer aborts the save it was guarding, and a save that cannot be written no longer takes the app down with the unsaved work still in it. Facet stays open with your data intact, writes a timestamped rescue copy, reports it on the status bar, and names that file plainly if you close while the drive is still missing.
Itemised notes start at 1.3.0. Versions 1.1.0 through 1.2.4 (June 2026) were the early run-up to a public release — the Explorer capture inbox, Facet packages and the free Facet Reader, licensing, and a long tail of fixes — and were not written up release by release at the time.
Updating is always free within your licence, and installing over an existing copy keeps your databases, settings and backups exactly where they are. Downloads →
Facet