SafeShare

Paid APILinuxSelf-hostedWeb

What SafeShare is

SafeShare is a free, MIT-licensed, open-source file-sharing service that you deploy yourself through its web interface, API, Linux binary, Docker, Docker Compose, or installable PWA. Accounts are not required for uploads, which can have automatic expiration, download limits, and optional passwords. Resumable transfers support large files. Optional browser-side end-to-end encryption uses AES-256-GCM before upload, keeping plaintext and the decryption key from the server; this mode holds the file in browser memory twice and warns about files over 500 MB. Configured at-rest encryption protects stored files with AES-256, but losing its key makes files unrecoverable. Anonymous mode redacts IP addresses, and metadata stripping supports selected formats. Optional accounts add invite-only registration, roles, MFA, and SSO. An admin dashboard manages files, users, and configuration. The API offers tokens, lifecycle webhooks, HMAC signatures, and Prometheus monitoring.

Who it suits

SafeShare suits people and organizations that want self-hosted file transfer with expiration, access controls, and optional encryption. Its documentation names whistleblowers, journalists, activists, corporate users, and regulated organizations as possible audiences.

What it does well

No required user accounts
Automatic expiration and download limits
Optional browser end-to-end encryption
Docker and Linux deployment options
API, webhooks, and Prometheus monitoring

What to know first

Browser encryption warns about files over 500 MB
Losing the storage key prevents recovery
Metadata stripping excludes several formats
Fortress mode lacks planned PostgreSQL, S3, and malware scanning

Verdict

SafeShare offers self-hosted sharing with granular upload controls, privacy modes, encryption options, and administration features. Review its encryption memory warning, unsupported metadata formats, and Fortress-mode limitations before deployment.

Facts from SafeShare's own pages

Accounts and access: Optional user accounts support invite-only registration, MFA, and SSO; the security guide also describes role-based access and anonymous uploads. · github.com, 12 Oct 2026
Administration: An optional admin dashboard supports file management, user administration, and system configuration. · github.com, 12 Oct 2026
API access: Yes · github.com, 23 Sept 2026
At-rest encryption: The README says configuring an encryption key enables AES-256 encryption at rest for stored files. · github.com, 12 Oct 2026
Authentication: Optional user accounts support invite-only registration, role-based access, MFA, and SSO. · github.com, 12 Oct 2026
Browser encryption: Optional end-to-end encryption encrypts files in the browser with AES-256-GCM before upload, so the server does not receive the plaintext or decryption key. · github.com, 12 Oct 2026
Compliance: The deployment guide maps features to HIPAA, SOC 2, GDPR, and PCI-DSS requirements; it describes Fortress mode for regulated industries. · github.com, 12 Oct 2026
Compliance limits: The README describes a Fortress mode for regulated industries but says PostgreSQL/S3 support and malware scanning are planned, not yet supported. · github.com, 12 Oct 2026
Deployment: The README documents Docker deployment and a downloadable Linux amd64 binary, plus an installable PWA. · github.com, 12 Oct 2026
Deployment options: The README gives Docker and Docker Compose deployment instructions and a Linux amd64 binary download. · github.com, 12 Oct 2026
Download tracking: Yes · github.com, 23 Sept 2026
Encryption at rest: When configured, SafeShare encrypts stored files with AES-256-GCM; losing the encryption key means the files cannot be recovered. · github.com, 12 Oct 2026
Encryption limit: End-to-end encryption keeps the whole file in browser memory twice and the documentation warns about files larger than 500 MB. · github.com, 12 Oct 2026
File controls: Uploads can have automatic expiration, download limits, and password protection. · github.com, 12 Oct 2026
Integrations: SafeShare provides an API with tokens, webhooks for file lifecycle events, and documented Prometheus monitoring. · github.com, 12 Oct 2026
Intended users: The deployment guide names whistleblowers, journalists, activists, corporate file-transfer users, and organizations with compliance requirements as example audiences for different configurations. · github.com, 12 Oct 2026
Large files: SafeShare supports resumable uploads and downloads for large files. · github.com, 12 Oct 2026
License: The repository README identifies SafeShare as MIT licensed. · github.com, 12 Oct 2026
Metadata limit: Metadata stripping does not support HEIC/HEIF, FLAC, WAV, OGG, WebM, or legacy Office formats, and does not remove Office comments or tracked changes. · github.com, 12 Oct 2026
Notable limit: The repository says PostgreSQL, S3, and malware scanning are planned but not yet supported in Fortress mode. · github.com, 12 Oct 2026
Privacy features: Anonymous mode redacts IP addresses from logs and the database, and metadata stripping can remove identifying metadata from supported file types. · github.com, 12 Oct 2026
Purpose: SafeShare is a self-hosted file-sharing service with automatic expiration and no required accounts. · github.com, 12 Oct 2026
Security caveat: The API reference says production deployments must run behind HTTPS. · github.com, 12 Oct 2026
Sharing controls: Uploads can have expiration times, download limits, and optional password protection. · github.com, 12 Oct 2026

Where SafeShare stands on Freedom251

File transfer services#101 of 105