{"version":"2.1.234","anchor":"claude-data-export-import-validates-what-it-reads","canonical_anchor":"claude-data-export-import-validates-what-it-reads","heading":"Claude data-export import validates what it reads","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/claude-data-export-import-validates-what-it-reads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Claude data-export import validates what it reads\n\nImporting a Claude data export now gives a clear error on a corrupt file instead of failing deep inside.\n\n**What**\n\nImporting 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.\n\n**Details**\n\n- Input that is not JSON, and a conversations.json that will not parse, each raise their own explicit error.\n- A missing manifest is rebuilt from the parsed conversations and projects rather than guessed from loosely typed fields.\n- Project directory names are checked against a name pattern and a length cap; ones that fail are skipped rather than aborting the import.\n- Directory entries inside the zip are excluded from the extracted file map.\n- Array contents are parsed leniently: a single malformed element is dropped instead of failing the whole list.\n\n**Evidence**\n\n`export conversations.json is not valid JSON`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}