Kronos 3 tutorial

Backing up a Kronos 3: a sane library strategy

Every Kronos owner has heard the horror story: years of custom sounds on one machine, then a dead drive, a botched update, or a theft. The instrument holds your work hostage in its own memory unless you take it out. This is a practical strategy for getting your Korg Kronos 3 sounds onto your Mac as ordinary files, kept in a library you can search, version, and restore from, using Kronos 3 Editor.

The principle: files, not slots

The Kronos has a finite number of USER slots; your computer does not. The moment a sound you care about exists only inside the instrument, it is one accident away from gone. The strategy in this guide is simple: the instrument holds the working set, and your Mac holds the library. Every sound worth keeping becomes a .syx file, and .syx files are just files: they back up to iCloud or Time Machine with everything else, they email, they fit on a USB stick.

A .syx file is a standard MIDI patch format, so your library is not locked to any one tool either. It is the closest thing hardware synths have to a universal container.

The mechanics in one minute

In the editor, two buttons at the top of the librarian do all the file work, and they are deliberately boring:

  • Save .syx exports the current program exactly as it is, edits and name included. A complete, faithful snapshot of the whole sound.
  • Load .syx opens a file back into the editor and sends it to the instrument, so you hear it straight away.

The important property: Save and Load only ever touch files. They never write the instrument's memory, so you can load anything, audition it, and walk away with the Kronos exactly as it was. Committing a sound to the hardware is a separate, deliberate act (WRITE), and the editor does it read-first: it writes the program, reads it back to verify it landed correctly, and only then commits.

A folder layout that scales

Any layout beats no layout, but this one has survived contact with real libraries:

  • One top-level folder, inside whatever your backups already cover: Kronos Library.
  • Subfolders by role, not by engine: Pianos, Organs, Pads, Leads, Splits, Gig sounds. You reach for "a pad", not "an MOD-7 patch".
  • Name files with more context than the 24-character program name allows: "Warm EP, verse sound for Hallelujah, 2026-07.syx" costs nothing on disk and saves you an audition later.
  • Keep a Sets folder too: set lists save and load as .syx in exactly the same way, so the running order for each gig lives beside the sounds it uses.

Version before you edit

The cheapest insurance in sound design is a copy taken before you start. About to rework your main piano? Save .syx first, suffix the filename with the date, then edit freely. If the new direction works, save it as the new current version; if it does not, load the file and nothing was lost. Disk space is free; your Tuesday-night tweaking session is not reversible any other way.

The same habit applies before every WRITE: the editor warns you exactly what you are replacing in a slot, but a .syx copy of the outgoing sound is the only way to get it back later if you change your mind next month.

The pre-update checklist

Korg OS updates are generally well behaved, but "generally" is not a backup strategy, and the same goes for lending the instrument, moving studios, or selling it. Before any of those:

  • Walk your USER banks (USER-A through USER-GG) and Save .syx for every sound you made or bought. The librarian's search and favourites make the walk quick.
  • Save .syx for every set list you use.
  • Also run the Kronos's own Save All to a USB drive from Disk mode. Belt and braces: the editor's library covers sounds and set lists; the instrument's full save covers everything else on the machine.
  • Check the library folder is actually inside your Mac backup (Time Machine or cloud sync), not just on the desktop of a machine that is itself unbacked up.

Restoring: the way back

Restoring is the mechanics in reverse: Load .syx brings the sound into the editor and onto the instrument's edit buffer, you play it to confirm it is the right one, then WRITE it into a USER slot. Pick the bank with care: Kronos USER banks are typed HD-1 or EXi and the instrument refuses a mismatch; the editor warns you up front, and flags empty slots (Init Program) as safe targets.

That is the whole loop: save freely, organise like a library, version before edits, checklist before updates, restore without drama. The button-by-button reference is in the Kronos 3 Editor user guide. If you do not have the editor yet, the free 7-day trial includes the librarian, so you can back up your whole Kronos this evening before spending a penny.

All guides