What Is Kryptor and What Is It Used For?

Updated

Kryptor is a file encryption and signing tool for Windows, Linux, and macOS, used to protect files for backups and sharing with a focus on limiting metadata. It is designed as a simpler, more user-friendly alternative to combining age and Minisign, and it is explicitly not a full replacement for GPG. If you need to encrypt or sign individual files without GPG's complexity, Kryptor is aimed at you; if you need GPG's broader ecosystem or compatibility, it is not.

What Kryptor does

The project describes two core functions:

  • File encryption — protecting files so their contents are unreadable without the right key.
  • File signing — attaching a cryptographic signature so recipients can verify a file's origin and integrity.

The stated use case is protecting files for backups and sharing, with an emphasis on limiting metadata. That makes it a fit for scenarios such as encrypting a backup archive before uploading it, or signing a release binary so downloaders can check it.

Where it sits relative to age, Minisign, and GPG

Kryptor positions itself as "a better version of age and Minisign" — a leaner, user-friendly alternative to GPG. The project is candid about the trade-off: it is not trying to replace GPG, because doing so would recreate GPG's problems, namely considerable complexity and too much code for a single maintainer to audit.

Tool Role according to Kryptor's framing
age File encryption; Kryptor aims to improve on it
Minisign File signing; Kryptor aims to improve on it
GPG Broad tool Kryptor does not attempt to replace
Kryptor Combined encryption + signing, simpler and smaller

The practical takeaway: choose Kryptor when you want straightforward encrypt-and-sign file workflows; keep GPG if you depend on its wider compatibility or features.

Supported platforms and how to get it

Pre-built binaries are published for:

  • Windows (x64)
  • Linux (x64 and ARM64)
  • macOS (x64 and ARM64)

Each download is accompanied by a Kryptor signature and a SHA-256 digest, and the project's Installation page explains how to verify them. Verifying before use is worth doing for any security tool.

Package manager options listed by the project:

  • Windows: choco install kryptor (Chocolatey) or scoop bucket add extras; scoop install kryptor (Scoop)
  • Arch Linux: yay -S kryptor (from source) or yay -S kryptor-bin (published binary)
  • NixOS: nix-shell -p kryptor
  • macOS: Homebrew support is listed as "help wanted," so no Homebrew command is currently provided.

A known macOS caveat

On macOS (both x64 and ARM64), an upstream .NET SDK issue prevents the libsodium library from being bundled correctly into the Kryptor executable. The project notes the .NET team has not investigated this for over a year and considers a fix unlikely. Until it is resolved, you must keep the libsodium.dylib file from the download ZIP in the same directory as the kryptor file. If you move the executable without that library, expect it not to run correctly.

Licensing, source, and support

  • License: GPLv3.
  • Source code: available on GitHub, which the project also names as the place for bug reports, feedback, questions, and technical support.
  • Security issues: reported via the SECURITY.md file rather than general channels.
  • Other enquiries: by email to the address listed on the project site.

Because the code is GPLv3 and publicly available, you can inspect or build it yourself — relevant if you care about auditing a security tool rather than trusting a binary.

Who should use it — and who shouldn't

A reasonable fit if you:

  • Encrypt or sign individual files for backups or sharing.
  • Want something simpler than GPG for that narrow job.
  • Care about minimizing metadata in the files you protect.
  • Are comfortable verifying signatures and digests, or installing via a package manager.

Look elsewhere if you:

  • Need GPG compatibility or its broader feature set — the project explicitly does not target this.
  • Are on macOS and unwilling to manage the separate libsodium.dylib file alongside the executable.
  • Want a Homebrew-based install on macOS today; that package does not yet exist.

The project is maintained by a single developer (a student, per the donation note), which is worth weighing when adopting a security tool for critical backups. The small codebase is presented as an auditability advantage, but it also means fewer hands on maintenance.