Un utility per la crittografia, leggera e semplice ma comunque molto sicura
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Evan Su a6544477d2 Add macOS test 1 day ago
.github Update issue templates 1 week ago
images Add files via upload 2 weeks ago
internals Create version.txt 2 weeks ago
src remove external dependencies dir 1 week ago
testing Add macOS test 1 day ago
Changelog.md Fixed typo 2 weeks ago
Internals.md Update Internals.md 1 week ago
LICENSE Initial commit 3 months ago
README.md details++ 1 week ago
Roadmap.md Update Roadmap.md 2 weeks ago
Security.md Update Security.md 1 week ago
notestoself.txt Update notestoself.txt 2 weeks ago
snapcraft.yaml Update to working snapcraft.yaml 2 weeks ago



Picocrypt is a very small (hence Pico), very simple, yet very secure cryptography utility that you can use to encrypt files, generate checksums, shred files, and much more. It’s designed to be the go-to tool for encryption, with a focus on security, simplicity, and reliability. Picocrypt uses the secure XChaCha20 cipher and the Poly1305 message authentication code to provide a high level of security, even from three-letter agencies like the NSA. It’s designed for maximal security, making absolutely no compromises security-wise, and is built with an audited cryptography library. Your privacy and security are under attack. Take it back with confidence by protecting your files with Picocrypt.



Please donate to Picocrypt on Open Collective to raise money for a potential audit from Cure53. Because this is a project that I spend many hours on and make no money from, I cannot pay for an audit myself. Picocrypt needs support from its community.


Important: There’s an outdated and useless piece of abandonware called PicoCrypt on the Internet, which was last updated in 2005. PicoCrypt is not related in any way to Picocrypt (this project). Make sure you only download Picocrypt from this repository to ensure that you get the authentic and backdoor-free Picocrypt.


Picocrypt for Windows is as simple as it gets. To download the latest, standalone, and portable executable for Windows, click here. Note that Picocrypt may trigger your antivirus. Picocrypt is not a virus, so please submit it as a false positive to your antivirus provider to prevent this in the future. Older releases are available under the Releases tab.


Coming soon...


A Snap is available for Linux. Make sure you have Snap installed. Next, ensure the core snap image is installed: sudo snap install core. Finally, install Picocrypt: sudo snap install picocrypt.

Why Picocrypt?

Why should you use Picocrypt instead of BitLocker, NordLocker, VeraCrypt, AxCrypt, or 7-Zip? Here are a few reasons why you should use Picocrypt:

  • Unlike NordLocker, BitLocker, AxCrypt, and most cloud storage providers, Picocrypt and its dependencies are completely open-source and auditable. You can verify for yourself that there aren't any backdoors or flaws.
  • Picocrypt is tiny. While NordLocker is over 100MB and VeraCrypt is over 30MB, Picocrypt sits at just 3MB, about the size of a high-resolution image. And that's not all - Picocrypt is portable, doesn't need to be installed, and doesn't require administrator/root privileges.
  • Picocrypt is easier and more productive to use than VeraCrypt. To encrypt files with VeraCrypt, you'd have to spend at least five minutes setting up a volume. With Picocrypt's simple UI, all you have to do is drag and drop your files, enter a password, and hit Start. All the complex settings are handled by Picocrypt internally.
  • Picocrypt is designed for security. 7-Zip is an archive utility and not an encryption tool, so its focus is not on security. Picocrypt, however, is built with security above everything. Every part of Picocrypt is there for a reason and anything that could impact the security of Picocrypt is removed. Picocrypt is cryptography you can trust.
  • Picocrypt authenticates data in addition to protecting it, preventing hackers from maliciously modifying sensitive data. This is useful when you are sending encrypted files over an insecure channel and want to be sure that it arrives untouched. Picocrypt uses Poly1305 for authenticity, which is a secure and respected message authentication code.
  • Picocrypt actively prevents protects your files from corruption by adding extra Reed-Solomon bits, so if your encrypted data corrupts (e.g., hard drive failure), Picocrypt can still recover your data with a high success rate.


Picocrypt is a very simple tool, and most users will understand how to use it in a few seconds. There are some advanced options, however, that you can use.

  • File metadata: Use this to store notes, information, and text along with the file (it won't be encrypted). For example, you can put a description of the file before sending it to someone. When the person you sent it to drops the file into Picocrypt, your description will be shown to that person.
  • Keep decrypted output even if it's corrupted or modified: Picocrypt automatically checks for integrity upon decryption. If the file has been modified or is corrupted, Picocrypt will automatically delete the output for the user's safety. If you want to keep the corrupted or modified data after decryption, check this option. Also, if this option is checked and the Reed-Solomon feature was used on the encrypted file, Picocrypt will attempt to recover as much of the file as possible during decryption, if it's corrupted.
  • Securely shred the original file(s) and folder(s): If checked, Picocrypt will use system internals to shred the input file(s). This method is more secure than just deleting the original file because the original file, in that case, can still be recovered by hackers using special software. Picocrypt securely deletes the original file making sure that it's impossible to retrieve the original file(s) after being shredded.
  • Prevent corruption using Reed-Solomon: This feature is very useful if you are planning to archive important data on a cloud provider or external hard drive for a long time. If checked, Picocrypt will use the Reed-Solomon error correction code to add 13 extra bytes for every 128 bytes to prevent file corruption. This means that up to ~5% of your file can corrupt and Picocrypt will still be able to correct the errors and decrypt your files with no corruption. Obviously, if your file corrupts very badly (e.g., you dropped your hard drive), Picocrypt won't be able to fully recover your files, but it will try its best to recover what it can. Note that this option will slow down encryption and decryption by a small amount.


For more information on how Picocrypt handles cryptography, see Internals for the technical details. If you’re worried about the practical security of Picocrypt, let me assure you that this repository won’t be hijacked. I have 2FA (TOTP) enabled on all accounts with a tie to Picocrypt (GitHub, Google, Reddit, Discord, etc.), so you can feel confident about using Picocrypt.


See Roadmap for a list of new features and improvements that I’m considering.


Here’s some places where you can see the latest news about Picocrypt and get involved:

Only trust these communities and be aware of scammers and hackers that might try to impersonate me and get you to download malicious software.


Stargazers over time


If you find a bug or have a feature request, please create an Issue. I’m open to collaborators, and all Issues and PRs are appreciated. If you find a security issue, please follow the instructions here to report it.


If you find Picocrypt useful, consider supporting me on Patreon. As I’m providing this software completely free of charge, I would love to have some supporters that will motivate me to continue my work on Picocrypt.

Thank You’s

A huge thanks to the following list of five people, who were the first people to donate and support Picocrypt:

  • W.Graham
  • N. Chin
  • Manjot
  • Phil P.
  • E. Zahard

Also thanks to these people:

  • Fuderal on Discord for helping me setup a Discord server
  • u/greenreddits for constant feedback and support
  • u/Tall_Escape for helping me test Picocrypt
  • samuel-lucas6 (on GitHub) for valuable feedback and support