An Applescript to push all of your LittleSnapper snaps into Evernote, including tags/ratings/title/date
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
Property List Tools.osax/Contents

LittleSnapper to Evernote migration applescript

Evernote does everything LittleSnapper does, and it syncs to the web and all your devices. It also won't drop your tags, has better methods for adding images and does OCR.


This script will move all of your LittleSnapper snaps into Evernote, including the rating, tags, title, date created and type. It makes a tag in the form "****" for a four star snap, etc. It adds a tag "websnap" to anything that was a websnap in LittleSnapper.


  1. Download all of these files.
  2. Copy the Property List Tools.osax file to ~/Library/ScriptingAdditions (create that directory if it doesn't exist). Source:
  3. To ensure all of the property list files are in place for your snaps, export all of them as Snap Bundles: 1. Highlight all of your snaps in LittleSnapper. Go to File > Export Images. 2. Make sure you pick "Snap Bundle" as the File Type. 3. Once this finishes, you can delete the exported files. The export was only necessary to force a rebuild of your metadata.
  4. Run the "Run Me" application.
  5. Pick your library file and notebook name. You can leave the notebook name blank and it will use the default. If you enter a new notebook name it will be created. If you don't want to run into your Syncing limits, create a new, local-only notebook to sync to. You can move notes over to a syncing notebook later (in batches if necessary).
  6. Let the script run through - you'll see the notes being added in real time. It took a few hours for my 2000+ snaps to be brought into Evernote.


You may want to check Evernote once and a while, as it will stop the export's progress if you try to import a file over 25MB, which is not allowed. Just press OK on the dialog box and the export will continue.


  • Let user know if there's a file without an info.plist, ask them to do step 3.
  • Make a parent script that copies over the plist lib then runs the main script.