Importing a Claude data export now gives a clear error on a corrupt file instead of failing deep inside.
What's wrong with this entry?
Importing a Claude data export now checks the file shapes up front, so a corrupt or partial export gives a clear error instead of failing somewhere deep in the import.
- Input that is not JSON, and a conversations.json that will not parse, each raise their own explicit error.
- A missing manifest is rebuilt from the parsed conversations and projects rather than guessed from loosely typed fields.
- Project directory names are checked against a name pattern and a length cap; ones that fail are skipped rather than aborting the import.
- Directory entries inside the zip are excluded from the extracted file map.
- Array contents are parsed leniently: a single malformed element is dropped instead of failing the whole list.
export conversations.json is not valid JSON
Strings lifted out of the shipped bundle, so the claim above can be checked against them.