actualNoteContentPart: For users of the Amplenote Desktop app, it's possible to choose a directory that will have all your Amplenote content backed up to your local file system. This help page will describe how to set it up, and what benefits automatic backups can offer.
  
  # How to setup automatic backups
  After you've [downloaded the Amplenote Desktop app](/help/native_desktop_system_requirements) , you can [click "Settings" under the "Amplenote Desktop" menu](https://images.amplenote.com/fdd718cc-d826-11ef-b630-2badab5b1c7d/4f80d7aa-93e8-40e5-a586-e3312bbf89a1.png)  to open settings for the desktop app:
  
  
  Choosing a backup directory in Ample Desktop settings
  
  
  Once you choose a backup directory, Amplenote will begin to download any note content that isn't already refreshed, and will begin to write each note to the chosen directory in a markdown file. [Each note's unique identifier is used as the file name]() .
  
  ## Backing up images, video and PDFs
  All assets uploaded to Amplenote are included in automatic backups. The assets within a media subdirectory of the main directory chosen. Within the media directory, subdirectories correspond to the note name (i.e., its unique identifier).
  
  ## Differences between automatic backup and export
  Amplenote offers the opportunity to export notes, it's one of our Core Customer Values. When you queue an export, these are the differences between that export and the automatic backup:
  "Automatic backup" is only available on Amplenote Desktop app, whereas "Export" is also available within the web app
  Export generates a single zip file with all content, which must be extracted to be utilized. 
  Within the zip file, notes are named according to their note name, rather than their unique identifier. In an automatically backed up note file, [the note title is the first field within the note content](https://images.amplenote.com/fdd718cc-d826-11ef-b630-2badab5b1c7d/52e3835d-1298-41bb-84c9-cf090665934a.png)  
  Automatic backup can export Vault Notes, which currently aren't able to be included in an export
  The reason that automatic backup uses a note's unique identifier rather than its note title is that we want to generate note content that stably preserves your cross-note links. If we identified notes by their title, then when a note title changed, the existing notes that referenced that would have broken links. 
  
  It would also require ongoing developer maintenance to ensure that notes that might be batch renamed, or renamed by a plugin, would know that their previous note file should be deleted and a new note file should be created. Using a stable identifier for notes elides all this complexity & maintenance, while still allowing users to ingest all note content into an LLM (or other tools) that can associate note titles with note content. 
  
  # How to get the unique identifier (UUID) for a note
  Since each automatically backed up note is identified by its unique identifier, and each asset is stored in a directory that corresponds to the UUID of the note it was uploaded to, it's often useful to deduce the unique identifier for a note. 
  
  This is possible by clicking the triple dot in the upper-right corner of a note, and choosing "View all details," or pressing Shift-Ctrl-O:
  
  
  Open all details for a note
  
  
  Then you'll be able to see the UUID, or click a button to copy it:
  
  
  Grabbing the unique identifier for a note
  
  
  # How to change automatic backup directory
  To change the directory used for automatic backup, turn off the "Automatic Backup" toggle, and then re-enable it. This allows us to avoid an ambiguous state about where notes should be saved when a directory swap is requested.
processedNoteContent: ---
  title: Automatic backup for all note content, images, ...
  tags: 
  ---
  For users of the Amplenote Desktop app, it's possible to choose a directory that will have all your Amplenote content backed up to your local file system. This help page will describe how to set it up, and what benefits automatic backups can offer. 
  How to setup automatic backups
  After you've [downloaded the Amplenote Desktop app](/help/native_desktop_system_requirements)
   , you can [click "Settings" under the "Amplenote Desktop" menu](https://images.amplenote.com)`
    to open settings for the desktop app: Choosing a backup directory in Ample Desktop settings Once you choose a backup directory, Amplenote will begin to download any note content that isn't already refreshed, and will begin to write each note to the chosen directory in a markdown file. [Each note's unique identifier is used as the file name]()
   . 
  Backing up images, video and PDFs
  All assets uploaded to Amplenote are included in automatic backups. The assets within a media subdirectory of the main directory chosen. Within the media directory, subdirectories correspond to the note name (i.e., its unique identifier). 
  Differences between automatic backup and export
  Amplenote offers the opportunity to export notes, it's one of our Core Customer Values. When you queue an export, these are the differences between that export and the automatic backup:
  "Automatic backup" is only available on Amplenote Desktop app, whereas "Export" is also available within the web app
  Export generates a single zip file with all content, which must be extracted to be utilized.
  Within the zip file, notes are named according to their note name, rather than their unique identifier. In an automatically backed up note file, [the note title is the first field within the note content](https://images.amplenote.com)`
  
  Automatic backup can export Vault Notes, which currently aren't able to be included in an export
  The reason that automatic backup uses a note's unique identifier rather than its note title is that we want to generate note content that stably preserves your cross-note links. If we identified notes by their title, then when a note title changed, the existing notes that referenced that would have broken links. It would also require ongoing developer maintenance to ensure that notes that might be batch renamed, or renamed by a plugin, would know that their previous note file should be deleted and a new note file should be created. Using a stable identifier for notes elides all this complexity & maintenance, while still allowing users to ingest all note content into an LLM (or other tools) that can associate note titles with note content. 
  How to get the unique identifier (UUID) for a note
  Since each automatically backed up note is identified by its unique identifier, and each asset is stored in a directory that corresponds to the UUID of the note it was uploaded to, it's often useful to deduce the unique identifier for a note. This is possible by clicking the triple dot in the upper-right corner of a note, and choosing "View all details," or pressing Shift-Ctrl-O: Open all details for a note Then you'll be able to see the UUID, or click a button to copy it: Grabbing the unique identifier for a note 
  How to change automatic backup directory
  To change the directory used for automatic backup, turn off the "Automatic Backup" toggle, and then re-enable it. This allows us to avoid an ambiguous state about where notes should be saved when a directory swap is requested.
noteTitle: Automatic backup for all note content, images, PDFs and media to a directory