Updating

What an update keeps

Your folders, settings and job history live in a database beside the application, not inside it. Updating replaces the program and leaves all of that alone.

The version you are running is shown in the sidebar and under Über.

Windows

Download the current installer from GitHub Releases and run it. It installs over the existing version; there is no need to uninstall first.

Close Printy before you start — including the tray icon, not just the window. An installer that finds the application running may need a restart to finish.

Portable variant: replace Printy.exe with the new one and keep pdfium.dll beside it. If the new release also ships a newer library, replace both.

macOS

brew update
brew upgrade --cask printy

If you installed from the DMG instead, download the new one and drag Printy into Applications again, replacing the existing copy.

Before updating a machine that prints all day

Export the configuration — Einstellungen → Konfiguration → Konfiguration exportieren. It is one file and it makes any rollback trivial.
Let the queue drain, or switch Alles pausieren on and wait for jobs in flight to finish. Nothing is lost if you do not, but it saves explaining why a document printed twenty minutes late.

Going back to an older version

Downgrading is not supported. A newer version may have upgraded the database, and an older one does not know how to read that — it can refuse to start rather than quietly work.

The reliable route back is the exported configuration: install the older version, let it create a fresh database, and import the export. That is exactly what the export exists for, and it is why the step before updating is worth the ten seconds. See Backup and transfer.

What changed between versions

See the Changelog.