-
Notifications
You must be signed in to change notification settings - Fork 39
Files
Password-Manager can attach small encrypted files to password entries.
Files are encrypted in the browser before upload. The backend stores encrypted file data.
File support is controlled by:
src/backend/function/config.php
Set:
$FILE_ENABLED = true;or:
$FILE_ENABLED = false;After changing this setting, reload the frontend.
Password-Manager is designed for small attachments such as license files, keys, or notes.
Current practical limits:
- recommended maximum file size: about 2 MB
- current UI may show a 3 MB limit
- maximum supported file name length: 38 bytes
For larger files, store them in a dedicated encrypted file storage system and save the link or access notes in Password-Manager.
Open an entry's details and use the file upload action.
Only one attached file is supported per entry. Uploading another file for the same entry replaces the old attachment.
Open the entry details and click the file name.
The browser downloads and decrypts the file.
Open the entry details and use the delete-file action.
File deletion is irreversible unless the file is present in a backup.
Files are not always included automatically in backups.
When generating a backup, check:
Include Files
if you want file attachments included.
Backups with files can be much larger and slower to generate or recover.
If file upload fails, check:
- PHP
post_max_size - PHP
upload_max_filesize - web server request body size
- WAF or ModSecurity limits
- MySQL/MariaDB
max_allowed_packet
Files are sent as encoded data, so the request size can be larger than the original file size.
- Files are encrypted in the browser before upload.
- File names and metadata may still reveal information.
- Keep attachments small.
- Test backup and recovery if you rely on attached files.