Export text messages for documentation
An export fit for documentation should be clean, searchable, and clear on sender and time — without legal promises iExport can't make.
What a good documentation export includes
- Clear timeline with accurate dates and times.
- Sender identification for every message.
- Attachments where present in the source.
- Page numbers and a conversation identifier.
- Searchable text (the PDF is not an image of text).
Step by step
- Preserve the original file (chat.db, .txt, or .xml) — do not edit it.
- Open iExport and load the file.
- Pick conversation and range.
- Preview. Verify dates and senders look correct.
- Download PDF for archive, and HTML if you also need search.
Disclaimer
iExport exports what's in your source file. We can't guarantee acceptance as legal evidence — that depends on context, opposing party, and court. Treat it as orderly documentation, not proof of authenticity.
Frequently asked questions
- Is the PDF valid as court evidence?
- iExport makes no guarantee that the export is accepted as evidence. The file is suitable for orderly documentation, review, and archiving — legal value is determined by the court and opposing party.
- What should a professional export include?
- Sender, date/time, message text, attachments where present, page numbers, and a clear conversation identifier.
- Can I remove messages before export?
- iExport exports what you selected. If used as documentation, preserve the original source file unchanged and don't edit the export.