FileLocker
A Windows encryption tool designed to make strong security feel approachable.
Combined strong encryption primitives with a drag-and-drop desktop workflow so the security model stayed usable instead of intimidating.
role
Solo Developer
team size
Solo build
updated
2026-04-07
overview
What the project is and why it mattered.
FileLocker is a Windows application built around secure file and folder protection. The goal was to pair modern cryptography with a workflow that feels understandable for real users, not only technical ones.
01
Encryption
AES-256-GCM
02
UX
Drag-and-drop file handling
03
Repo
Public on GitHub
problem
A lot of security tools are powerful but unfriendly. I wanted to build something that preserved strong encryption choices while making the experience practical for everyday file protection.
role
I built the application as a solo project, shaping the UX, cryptographic workflow, and desktop implementation details around clarity, safety, and a streamlined encryption flow.
build details
Stack, constraints, and decisions.
Stack
Constraints
- Security-sensitive features needed to be understandable without oversimplifying the underlying risks.
- The app had to support both single-file and folder-based workflows.
- Metadata exposure and storage overhead both mattered, not just raw encryption.
Decisions Made
01
Use authenticated encryption by default
AES-256-GCM gave the project a strong baseline for confidentiality and integrity instead of treating encryption as a checkbox feature.
02
Reduce leakage beyond file contents
Metadata stripping and optional renaming focused on limiting information leaks that many basic tools ignore.
03
Build around a simple desktop workflow
Drag-and-drop support, password validation, and folder handling helped the app stay practical instead of feeling like a crypto demo.
outcome
What came out of it.
Outcome
- Implemented AES-256-GCM encryption for files and folders.
- Added password protection, optional password strength validation, and metadata stripping.
- Included compression and optional steganography mode as part of the workflow.
Lessons
- Security tooling earns trust through both correctness and clarity.
- UX details matter even more when users are making irreversible decisions like encryption.
- Thinking about metadata and side channels leads to better product choices.
Next
- Add more recovery guidance and guardrails around destructive actions.
- Expand automated verification around encryption and restore flows.
- Refine release packaging and documentation for easier adoption.
keep browsing
Keep moving through the archive or reach out if you want to talk through similar work.