You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Store offloaded files in a local folder, not just S3. A new Storage mode setting offers "S3 only" (unchanged), "Local only" (move files to a folder outside the vault, such as a synced OneDrive, Dropbox, or NAS path), and "Local and S3" (write both, read from the fast local copy, and keep S3 as an off-machine backup). Set the local folder in settings; environment variables like %OneDriveCommercial% and $HOME are expanded so one setting resolves the right folder on each machine. Offloaded files mirror their vault path under the folder.
Paired offload is atomic: in "Local and S3" mode both copies are written and verified before the local original is trashed, and if either copy fails the other is rolled back and your original is kept. You are never left with a pointer whose storage does not actually hold the file.
Open and restore now prefer the local copy when both exist and fall back to S3 if the local copy is missing, so a file always opens as long as any of its backends still has it.
Pointer notes now have working action links for each storage location a file lives in: Open and Reveal in the file explorer for a local copy, and Open (downloads the object to a temp file and opens it) plus Copy reference for an S3 copy. A paired file shows both rows, and opening tells you which copy it used so it is clear whether the file opened locally or from S3.
Check backend integrity: a read-only command that confirms every pointer's storage still holds its file and reports any that are missing.
Add a local mirror / Add an S3 mirror: commands that upgrade your existing pointers in place, copying each file to the other backend and verifying the copy, so you can move from S3 only to paired (or the reverse) without re-offloading by hand.
Changed
This is now a desktop-only version. Writing to a local folder uses desktop file access that the mobile app does not provide, so the plugin no longer loads on Obsidian mobile.
Existing S3 pointer notes keep working unchanged; they are read as a single S3 backend and upgraded to the new format only when you next write them.