Shouldn’t be a feature, should be standard with the export function.
There is even no warning as soon you do your export.
I do get a warning in Chrome extension version 2024.5.2, Windows desktop 2024.4.1 and in the web vault. Are you maybe running an old version?
Also, I asked in one of the vault hours a few months ago and exporting attachments is in the pipeline.
Hi and thanks,
I am using the Firefox extension 2024.4.2, the android app 2024.5.1 and the Linux Client 2024.5.0 and I do not see any of that text in your screenshot. I am not using the web vault. As far as I can see, that are the latest versions for my programs.
Also, I asked in one of the vault hours a few months ago and exporting attachments is in the pipeline.
That would be good. I noticed unfortunately too late that the export/import that I did removed all my attachments. Was quite a surprise and not in a good way.
Might be that I pay for “family” and have an “organization”.
This does not show on the iOS mobile app.
This seems like a good idea in theory. However, the backup file might get a bit large, especially with attachments that are 10MB+ in size.
I think a nice alternative for Bitwarden would be to allow .zip attachment exports. Yes, that would mean that your password backup JSON/CSV would be separate from the attachments, but it would be nice to be able to export all attachments at once.
3 Likes
Is it possible to re-import that zip file with all attachments and everything is back in place? All attachments are back at their place?
From the PR,
No importing is added. Since the data.json is included, that can be imported for now, but we could add full zip + attachment import in a second step"
2 Likes
Just unencrypted export for now. Might add import & encryption in a separate PR, but it will probably take a while until I come back around to it. Not sure. But the filestructure would allow it.
I would love to see this without the data.json (at least until such time that encryption can be added).
1 Like
Yeah, I saw the same comment on Reddit. I’d rather encrypt the data.json and all attachments, so it still makes sense as an importable export of the vault. But very valid point.
1 Like
Attachments could be uuencoded and decoded.
For cloud users, how are attachments stored right now (binary or uuencoded)?
I think I saw a recent release note of an issue in a browser where when clicking an attachment it would open into a new tab; thereby viewing the attachment.
A fix was implemented it so that this could be downloaded instead 
. So proof that this can be done.