Since metadata like tags and created/updated time are included as meta tags in the exported HTML files, I don’t think anything important is lost by using the HTML format rather than the enex format. This hasn’t been an issue with the HTML export so far, even though updates to the application do sometimes cause a large number of the exported files to be altered. I originally tried exporting using the enex file format instead - which dumps all data into one large file - but I found that the repo’s size grew out of control due to excessive changes in that output. Display a notification with stats about the commit.

(All files in the repo are git rm’d before starting the export, so that notes which no longer exist will be deleted in the commit.) Export notes in HTML format into a git repo, using separate subdirectories for each notebook, and commit the changes.I thought it would be nice to additionally commit the notes to a git repository. The Mac app syncs all your notes locally in an HTML format, so you can get some protection by doing automated backups of its folder (which is within ~/Library/Application Support//accounts/with a backup service like CrashPlan.

I love Evernote, but I don’t trust it to never lose my data. Update on : I wrote an easily installed command-line tool for invoking Evernote export, in case you prefer that over copying a shell script. Backing up Evernote to git -> Technical -> Backup Tooling -> Backing up Evernote to git

Export evernote to html