change maximum file size #1372

Closed
opened 2025-10-09 17:13:03 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @vista-narvas on GitHub.

Subject of the issue

when uploading a file for send, i get the error
"Maximum file size is 100 MB."
i cant find any config for changing the maximum file size

Deployment environment

  • vaultwarden version:
    vaultwarden/server:latest
    just pulled again
  • Install method:
    docker

  • Clients used:
    web vault and browser addon

  • Reverse proxy and version:
    traefik

  • MySQL/MariaDB or PostgreSQL version:
    nope

  • Other relevant details:

Steps to reproduce

Expected behaviour

a way to set the maximum file size

Actual behaviour

Troubleshooting data

Originally created by @vista-narvas on GitHub. <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue <!-- Describe your issue here. --> when uploading a file for send, i get the error "Maximum file size is 100 MB." i cant find any config for changing the maximum file size ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: vaultwarden/server:latest just pulled again <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: docker * Clients used: <!-- web vault, desktop, Android, iOS, etc. (if applicable) --> web vault and browser addon * Reverse proxy and version: <!-- if applicable --> traefik * MySQL/MariaDB or PostgreSQL version: <!-- if applicable --> nope * Other relevant details: ### Steps to reproduce <!-- Tell us how to reproduce this issue. What parameters did you set (differently from the defaults) and how did you start vaultwarden? --> ### Expected behaviour <!-- Tell us what you expected to happen --> a way to set the maximum file size ### Actual behaviour <!-- Tell us what actually happened --> ### Troubleshooting data <!-- Share any log files, screenshots, or other relevant troubleshooting data -->
Author
Owner

@jjlin commented on GitHub:

Max attachment size is primarily limited by what the clients are designed to handle, and you can't change that without building your own version of the client. See https://bitwarden.com/help/article/attachments/ for details.

In principle, the server could handle arbitrarily large attachments, but it also has some checks to mirror the client limits.

@jjlin commented on GitHub: Max attachment size is primarily limited by what the clients are designed to handle, and you can't change that without building your own version of the client. See https://bitwarden.com/help/article/attachments/ for details. In principle, the server could handle arbitrarily large attachments, but it also has some checks to mirror the client limits.
Author
Owner

@RealOrangeOne commented on GitHub:

Looking at the code, the default is 110MB, but it can be overriden with the $USER_ATTACHMENT_LIMIT environment variable

@RealOrangeOne commented on GitHub: Looking at the code, the [default is 110MB](https://github.com/dani-garcia/vaultwarden/blob/main/src/api/core/sends.rs#L171), but it can be overriden with the [`$USER_ATTACHMENT_LIMIT`](https://github.com/dani-garcia/vaultwarden/blob/main/.env.template#L202) environment variable
Author
Owner

@vista-narvas commented on GitHub:

ok so the limiting factor is the client
i guess there is nothing to do about that
thank you for your time

@vista-narvas commented on GitHub: ok so the limiting factor is the client i guess there is nothing to do about that thank you for your time
Author
Owner

@vista-narvas commented on GitHub:

i tried using USER_ATTACHMENT_LIMIT: 8388608 in my docker-compose.yml
and im still not able to upload bigger files

i think USER_ATTACHMENT_LIMIT is only for the global limit
in the error it says "Attachment size limit reached! Delete some files to open space"
if i change USER_ATTACHMENT_LIMIT to 1 when i try to upload a small file i get that error

@vista-narvas commented on GitHub: i tried using USER_ATTACHMENT_LIMIT: 8388608 in my docker-compose.yml and im still not able to upload bigger files i think USER_ATTACHMENT_LIMIT is only for the global limit in the [error](https://github.com/dani-garcia/vaultwarden/blob/main/src/api/core/sends.rs#L167) it says "Attachment size limit reached! Delete some files to open space" if i change USER_ATTACHMENT_LIMIT to 1 when i try to upload a small file i get that error
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#1372