linkHow local backup sync works
Amplenote Desktop can maintain local backup copies of your notes on your device for offline access, backups, and external workflows.
When you make a change to a note inside Amplenote, that change is written both to your local backup files and, when connected to the internet, synced to Amplenote’s servers. These notes are saved in Markdown format (.md), and use internal identifiers to maintain backup continuity.
Renaming backup files or moving them from their original locations can break continuity with future backups. When this happens, Amplenote may generate a new backup file for the original note instead of continuing to update the renamed file.
However, it's important to understand that local backups are a one-way export from Amplenote. Changes made to local files are not synced back into the app, and local modifications may be overwritten by future updates from Amplenote.
linkUsing external tools with local backups
You can use external tools to interact with locally saved notes just as you would with any other file stored on your device. While workflows vary depending on the tool being used, some common use cases include:
Saving these notes as an external archive
Accessing them from file lookup apps such as RayCast or Ulauncher
Reading the files with another text editor
Searching note contents using terminal commands or local indexing tools
Using AI agents to analyze, summarize or transform these backup files
These workflows can work well for experimentation, offline analysis, or temporary workflows.
linkUsing AI tools with local backups
As AI workflows become more common, some users choose to use AI tools that can directly access files stored on their devices, such as Claude Cowork.
Because Amplenote saves local backups as Markdown (.md) files, AI tools can read and modify them like any other text file stored on your computer. However, changes made by these tools to local backup files are not synced back into Amplenote and may be overwritten the next time the original note is updated inside the app.
For this reason, local backups are best suited for experimentation, information analysis, temporary workflows, or providing additional context to external tools rather than serving as a primary editing workflow.
This behavior helps ensure that Amplenote remains the single source of truth while reducing the risk of accidental changes or deletions in the local backup folder affecting notes stored inside the app.
linkCommon misconceptions
linkIf I edit a local file, will the note update inside Amplenote as well?
No. Changes made to local backup files are not imported back into Amplenote.
linkCan my local edits be overwritten?
Yes. Future note updates from Amplenote may replace the contents of local backup files.
linkCan I rename my backup files?
You can, but Amplenote may generate a new backup file for the original note instead of continuing to update the renamed file.
linkAre local backups safe to use with external AI tools?
That depends on your own privacy and security preferences, as well as the external tool being used. Amplenote does not control how third-party tools process data.
linkWhen to use external AI tools vs Ample Agent Pro
Ample Agent Pro is a paid plugin for Amplenote that allows you to use frontier AI models within your app.
Depending on your workflow, external AI tools and Ample Agent Pro may serve different purposes:
Use Case | Local Backups + External Tools | Ample Agent Pro |
Offline / local experimentation | Good fit | Less relevant |
Persistent Note Editing | Not recommended | Better fit |
Safe in-app workflows | Limited | Designed for this |
Automatic integration with notes | No | Yes |
Controlled product experience | No | Yes |
Risk of unintended AI modifications syncing into notes | Lower | Depends on workflow |
linkBest practices
Treat local backups as exports or backup copies rather than a bidirectional sync system
Keep Amplenote as the primary location for editing notes
Avoid relying on local file edits as permanent changes
Be cautious when sharing notes with third-party AI tools
Test experimental workflows on non-critical notes first