A multi-platform desktop application that provides client-side encryption for cloud storage files, ensuring privacy and control.
Cryptomator is a desktop application that provides client-side encryption for files stored in cloud services like Dropbox, Google Drive, and OneDrive. It encrypts data locally before uploading, ensuring that only the user holds the decryption keys and cloud providers cannot access the plaintext content. The tool creates a virtual drive where users can work with their files transparently, with automatic encryption and decryption handled in the background.
Individuals and professionals who use cloud storage services and need to protect sensitive files from unauthorized access, including those concerned about cloud provider privacy policies or data breaches.
Developers and privacy-conscious users choose Cryptomator because it is open-source (ensuring no backdoors), requires no accounts, and gives full client-side control. Its transparent operation and strong AES-256 encryption provide robust security without complicating the user experience.
Cryptomator for Windows, macOS, and Linux: Secure client-side encryption for your cloud storage, ensuring privacy and control over your data.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Native applications for Windows, macOS, and Linux ensure consistent encryption across major desktop operating systems, as highlighted in the README's features.
Works with Dropbox, Google Drive, OneDrive, and others, allowing encryption for any cloud that syncs locally, per the README's list of supported services.
Uses AES-256 encryption with encrypted file names and obfuscated folder structures, providing robust security without relying on cloud providers, as detailed in the README.
No accounts required and sensitive data is wiped from memory promptly, emphasizing user control and minimal data exposure, as stated in the privacy section.
Cryptomator is limited to desktop platforms, making it unsuitable for users who need to access encrypted files on smartphones or tablets, a gap not addressed in the README.
Building from source requires JDK 25 and Maven 3, which can be a barrier for developers wanting to customize or contribute, as outlined in the building instructions.
Relies solely on user-managed passwords with no built-in key recovery, meaning lost passwords result in permanently inaccessible data, a trade-off for enhanced security.