Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
4 years agoDoes 1Password 8 change local backup situation?
In https://1password.community/discussion/114953/do-i-need-to-create-my-own-backup-of-my-vaults-1password-com Ben explained:
"1Password keeps a "local cache" of all of your data in a database that...
1P_Rob
1Password Team
4 years agoHey, @mikebore. Sorry for the delayed response here.
CSV exports are great for tabular data but notoriously awful for structured data. There is typically an expectation with CSV that a column means the same thing for every cell in the column. If we follow that approach, you'd have Login items with blank credit card number fields, Credit Cards with blank username and password fields, and all sorts of other combinations like that which would make the CSV have tons of mostly empty columns and be very hard to use. A better option would probably be to export multiple CSVs, one for every item type, but that's hard to use in other ways, and you still have the same problem for every custom field you add to an item. For now, we felt that the use case of exporting just usernames and passwords in a CSV was the most clear.
I don't have a status update on 1PEX, but it's not going to be more accessible than 1PUX, mostly because the data will be encrypted. Both of those formats are designed for computers, not humans, to parse, but because 1PUX is unencrypted, it's possible to use it for your Armageddon scenario, even though it's not designed for that purpose.