Thank you for taking the time to dig into this and for sharing such detailed findings. I understand how critical a reliable export is, especially when you have a large, long‑term vault and lifetime license, and I’m sorry for the frustration this has caused.

Your observations about:

• Export only working in smaller batches

• Certain entries (passkeys, attachments, special characters) breaking the export

are extremely helpful. I’ve forwarded this thread and your specific notes to our technical team and linked them to the existing internal issue we’re tracking for export failures, so they can use your tests to narrow down the root cause rather than treating it as a generic error.

We really appreciate you sharing concrete, reproducible details instead of just giving up on the app. I know that doesn’t fix the issue today, but it does help move us closer to a proper fix instead of guesswork.

This is very annoying. I have version 6.11.17 (2132) from Mac App Store and I can not export any of my vaults in csv.

Enpass is able to export in json and txt but not in csv.

I hope that any update solves this big issue.

I will try to update and see if this issue was fixed.

I am having the same issue. My vault contains ~790 entries. I have tried all the tips in this thread and found that it is certain entries in my vault that causes the export to error. I found this by copying under 200 of my entries into multiple new vaults and trying to export. I was successful in exporting from two out of the four new vaults. For the two that errored, I slowly removed entries until I was able to export successfully. I then created another vault and slowly added a handful of entries at a time, until it would error. Using this elimination method so far I have found at least one entry that is causing the export to error for whatever reason. If I have a new vault, and copy said entry to the vault by itself, the export will error. I know I have at least one other entry to find.