MessagingStore |
Supported MessagingStore file formats (IdClassification.MessagingStore - Messaging export container formats (e.g., Slack export, WhatsApp export, etc))
- All entries in table below are supported for file format identification.
- 'X' in "Text" column indicates text extraction is supported for the file format.
- 'X**' in "Text" column indicates text extraction is supported BUT binary-to-text filtering is used on partially parsed document records.
- 'X' in "Metadata" column indicates metadata extraction is supported for the file format.
- 'X' in "EmbeddedItem" column indicates embedded item/attachment extraction is supported for the file format.
- 'X' in "ContentHash" column indicates a content hash is supported for the file format (see MD5ContentHash and SHA1ContentHash)
If a file format does not have a supported content extractor that extracts text then, optionally (default), a binary-to-text content extractor will be used to extract UTF-8, UTF-16, Windows-1252, and ASCII from the binary. In many cases, indexable text can be extract from unknown document formats.
File Format Id Enum Value | Text | Metadata | EmbeddedItem | ContentHash | Description |
|---|---|---|---|---|---|
Skype chatsync data file, stores 'removed' messages, along with edits, locally (.dat). | |||||
X | X | X | Skype chat history export file (Skype accounts can request an export of their chat history and/or files) (.tar). | ||
X | X | Slack export data file (.zip). | |||
X | X | X | Instant Bloomberg (IB) chat (.xml). | ||
X | X | X | WhatsApp message collection exported by Cellebrite Endpoint Inspector software (.zip). | ||
X | X | Telegram message collection exported by Cellebrite Endpoint Inspector software (.zip). |