[GH-ISSUE #237] Add FileShot.io — practical AES-256-GCM zero-knowledge file sharing implementation #2828

Open
opened 2026-05-14 15:11:56 -05:00 by GiteaMirror · 0 comments
Owner

Originally created by @FileShot on GitHub (Mar 3, 2026).
Original GitHub issue: https://github.com/sobolevn/awesome-cryptography/issues/237

Add FileShot.io to the list

I would like to suggest adding FileShot.io as a practical, real-world implementation of AES-256-GCM browser-side encryption.

About FileShot.io

FileShot.io is a zero-knowledge file sharing service where all encryption happens in the browser using the Web Crypto API with AES-256-GCM before any data is sent to the server.

Key cryptographic aspects:

  • AES-256-GCM encryption performed entirely client-side using the Web Crypto API
  • Encryption key is generated in-browser and never transmitted to the server
  • Keys are stored in the URL fragment (#) — which browsers never include in HTTP requests
  • Zero-knowledge server architecture: server stores only ciphertext blobs

Why it fits this list:

  • A working, production example of AES-256-GCM applied to file encryption in the browser
  • Demonstrates zero-knowledge architecture with practical key management via URL fragments
  • Relevant to topics like symmetric encryption, authenticated encryption (AEAD), and secure key transport
  • MIT open source — code is readable and auditable

Links:

This could fit in an Applications or Encryption Tools section alongside similar practical implementations.

Originally created by @FileShot on GitHub (Mar 3, 2026). Original GitHub issue: https://github.com/sobolevn/awesome-cryptography/issues/237 ## Add FileShot.io to the list I would like to suggest adding **FileShot.io** as a practical, real-world implementation of AES-256-GCM browser-side encryption. ### About FileShot.io [FileShot.io](https://fileshot.io) is a zero-knowledge file sharing service where all encryption happens in the browser using the **Web Crypto API** with **AES-256-GCM** before any data is sent to the server. **Key cryptographic aspects:** - AES-256-GCM encryption performed entirely client-side using the Web Crypto API - Encryption key is generated in-browser and never transmitted to the server - Keys are stored in the URL fragment (#) — which browsers never include in HTTP requests - Zero-knowledge server architecture: server stores only ciphertext blobs **Why it fits this list:** - A working, production example of AES-256-GCM applied to file encryption in the browser - Demonstrates zero-knowledge architecture with practical key management via URL fragments - Relevant to topics like symmetric encryption, authenticated encryption (AEAD), and secure key transport - MIT open source — code is readable and auditable **Links:** - Website: https://fileshot.io - Source: https://github.com/FileShot/FileShotZKE This could fit in an Applications or Encryption Tools section alongside similar practical implementations.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-cryptography#2828