Skip to main content
Memvid supports encrypting memory files into secure capsules using industry-standard encryption. Encrypted files use the .mv2e extension and require a password to access.

Overview


Encrypting a Memory File

Interactive Password

Password from Stdin (for Scripts)

Options

JSON output:

Decrypting a Capsule

Interactive Password

Password from Stdin

Options


Working with Encrypted Files

Encrypted files must be decrypted before use:

Workflow: Edit and Re-encrypt


Security Details

AES-256-GCM

  • 256-bit key: Derived from your password via Argon2id
  • Authenticated: Detects tampering or corruption
  • Unique nonce: Each encryption uses a fresh random nonce
  • No metadata leakage: File size is only indicator of content size

Argon2id Key Derivation

  • Memory-hard: Requires significant RAM, resists GPU attacks
  • Time-hard: Configurable iterations for speed/security tradeoff
  • Salt: Unique random salt per encryption
  • Winner: Password Hashing Competition (2015)
Default parameters: These parameters make brute-force attacks extremely expensive.

Password Requirements

Recommendations

Strong Password Examples

Weak Passwords to Avoid

  • Dictionary words: password, memory, secret
  • Simple patterns: 123456, qwerty, abcdef
  • Personal info: birthdays, names, addresses
  • Short passwords: anything under 12 characters

Automation & CI/CD

Environment Variables

GitHub Actions Example

Docker Example


Use Cases

Sensitive Documents

Encrypt memories containing confidential information:

Backup & Archive

Secure long-term storage:

Sharing Encrypted Memories

Share with password communicated separately:

Compliance Requirements

For HIPAA, GDPR, SOC2, etc.:

Error Handling

Wrong Password

Corrupted File

AES-GCM detects any modification to the encrypted file.

File Already Exists


Best Practices

1. Use Strong Passwords

2. Keep Backups of Unencrypted Data

If you lose the password, data is unrecoverable:

3. Separate Password from Encrypted File

  • Never store password in same location as encrypted file
  • Use different channels (email file, text password)
  • Use secrets managers (Vault, 1Password, etc.)

4. Rotate Passwords Periodically

5. Verify After Encryption


Limitations


Future Features

Coming soon:
  • Key file support (in addition to password)
  • Hardware security module (HSM) integration
  • Partial decryption for large files
  • Key rotation without full re-encryption

Next Steps

Security & Compliance

Security FAQ and compliance info

CLI Reference

Full CLI command reference