[GH-ISSUE #865] Feature request: Disable attachments #613

New issue

Closed

opened 2026-03-03 02:01:21 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 02:01:21 +03:00

Owner

Originally created by @Dubz on GitHub (Feb 16, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/865

Title says it all.

I want to be able to disable the attachments feature on my system. Attachments take up storage space. Storage costs me money. I do not want to be paying excessive costs to host user attachments.

Logins aren't as much space so I'm alright with that, but when you can multiply someone's storage usage with a few attachments, that's not really something I'd like to have to pay for. They may add a few, or many, files, which would grow the used space exponentially.

Originally created by @Dubz on GitHub (Feb 16, 2020). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/865 Title says it all. I want to be able to disable the attachments feature on my system. Attachments take up storage space. Storage costs me money. I do not want to be paying excessive costs to host user attachments. Logins aren't as much space so I'm alright with that, but when you can multiply someone's storage usage with a few attachments, that's not really something I'd like to have to pay for. They may add a few, or many, files, which would grow the used space exponentially.

kerem closed this issue

2026-03-03 02:01:22 +03:00

kerem commented

2026-03-03 02:01:22 +03:00

Author

Owner

@mprasil commented on GitHub (Feb 16, 2020):

That sounds like good idea. I've created a PR to enable that.

@mprasil commented on GitHub (Feb 16, 2020): That sounds like good idea. I've created a PR to enable that.

kerem commented

2026-03-03 02:01:22 +03:00

Author

Owner

@dani-garcia commented on GitHub (Feb 18, 2020):

I've implemented the size limit functionality, with two limits, one for users and another for organizations, so depending where the cipher is located it can be one or the other, and setting it to zero disables uploading at all. The options are USER_ATTACHMENT_LIMIT and ORG_ATTACHMENT_LIMIT and they use KB.

github.com/dani-garcia/bitwarden_rs@325039c316

@dani-garcia commented on GitHub (Feb 18, 2020): I've implemented the size limit functionality, with two limits, one for users and another for organizations, so depending where the cipher is located it can be one or the other, and setting it to zero disables uploading at all. The options are `USER_ATTACHMENT_LIMIT` and `ORG_ATTACHMENT_LIMIT` and they use KB. https://github.com/dani-garcia/bitwarden_rs/commit/325039c31695ac981da3b88dbbe6c6f40c6a180d

kerem commented

2026-03-03 02:01:22 +03:00

Author

Owner

@7heMech commented on GitHub (Feb 21, 2025):

I've implemented the size limit functionality, with two limits, one for users and another for organizations, so depending where the cipher is located it can be one or the other, and setting it to zero disables uploading at all. The options are USER_ATTACHMENT_LIMIT and ORG_ATTACHMENT_LIMIT and they use KB.

github.com/dani-garcia/bitwarden_rs@325039c316

That's awesome, I set the limit to 0 and to 1000 and I tried to upload a 100MB file and couldn't help, but notice the server downloads the entire file and then rejects it, isn't that possibly bad? I'm not sure if that was my proxy though.

@7heMech commented on GitHub (Feb 21, 2025): > I've implemented the size limit functionality, with two limits, one for users and another for organizations, so depending where the cipher is located it can be one or the other, and setting it to zero disables uploading at all. The options are `USER_ATTACHMENT_LIMIT` and `ORG_ATTACHMENT_LIMIT` and they use KB. > > https://github.com/dani-garcia/bitwarden_rs/commit/325039c31695ac981da3b88dbbe6c6f40c6a180d That's awesome, I set the limit to 0 and to 1000 and I tried to upload a 100MB file and couldn't help, but notice the server downloads the entire file and then rejects it, isn't that possibly bad? I'm not sure if that was my proxy though.