Docs / Keeping code
Export and import
Export Library… keeps every Saved Snippet in one .json file. Import Library… adds them back.
The export is your backup of the Library, and the way to take it to another computer. JSpark doesn’t sync the Library anywhere.
Export the Library
- Choose File → Export Library…, or in the Library window click the … button under the list and choose Export Library…
- Choose where to save the file. JSpark suggests your Documents folder and a name with the day’s date, such as
JSpark Library 2026-09-30.json. - Click Save.
Due date in 30 days
addDays, then format
The file holds every Saved Snippet: its title, notes, Tags and code, the Kind, Language and Load Mode it was saved with, and when it was saved. It is plain JSON, so any text editor can open it.
Exporting works the same in JSpark and JSpark+.
Import a Library JSpark+
- Choose File → Import Library…, or choose Import Library… from the … button in the Library window. An empty Library also shows an Import Library… button.
- Pick a file made by Export Library…
JSpark adds the Saved Snippets your Library doesn’t have yet, and says how many, for example “Added 3 Snippets to your Library”. Nothing already in your Library is changed or deleted.
- A Saved Snippet with the same title, notes and code, and the same Kind, Language and Load Mode, counts as already there, even if its Tags differ. It is left as it is.
- Importing the same file again adds nothing: JSpark says “Nothing new to add”.
- A file that isn’t an export says “That file isn’t a Library exported from JSpark.”
In JSpark, Import Library… says “Importing a Library needs JSpark+” and reads nothing.
Move to a new computer
- On the old computer, export the Library.
- Copy the
.jsonfile to the new computer. - On the new computer, open the Library and choose Import Library…
Importing needs JSpark+. The file keeps every Saved Snippet either way, and exporting never needs JSpark+, so your Saved Snippets can always leave the app.
The pictures show JSpark on a Mac. On Windows, the window looks a little different and uses Ctrl for ⌘, but everything works the same way.