Updated October 2026
Legal discovery and document review regularly involves handling folders full of exported .msg files — opposing counsel's production, a client's email export, or an internal investigation's evidence set. Here's what's actually involved in reading them without specialized (and often expensive) forensic email software.
Outlook remains the dominant corporate email client, and when organizations export email for a legal hold, discovery production, or internal investigation, a common export method is Outlook's native "Save As" or drag-to-folder behavior, which produces individual .msg files — one per message. A production can easily contain hundreds or thousands of these files, often without any accompanying viewer software, leaving the recipient (frequently opposing counsel, a reviewing attorney, or paralegal staff) to find their own way to open them.
For most review purposes, the relevant fields are the same ones this tool extracts directly: sender, recipients (to confirm who was on the communication, relevant for privilege and relevance review), date (for chronology and timeline reconstruction), subject and body text (for substantive content review), and the attachment list (attachments are frequently the actual substantive evidence, with the email itself serving as a cover/context). This tool surfaces all of these fields immediately on opening a file, without needing Outlook or a dedicated eDiscovery platform for a quick individual-document review.
For reviewing a specific document or a small batch — rather than running a full-scale eDiscovery platform ingestion — opening each .msg file individually in a browser-based viewer, reading the extracted fields, and using the Export body as .txt feature to save a plain-text copy for a review log or privilege log entry is a workable lightweight process. Each attachment can also be downloaded individually via its own link, preserving the original file for separate review or production logging.
This tool is a single-file, client-side viewer — it is not a replacement for a proper eDiscovery platform when volume, chain-of-custody, metadata preservation, or load-file/production formatting requirements are involved. For a large-scale review (hundreds or thousands of documents), proper eDiscovery software provides batch processing, tagging, privilege logging, search across the full document set, and defensible metadata handling that a one-file-at-a-time browser tool doesn't attempt to replicate. Use a tool like this for individual document review, spot-checks, or situations where a full platform isn't warranted — not as a substitute for proper discovery-management software on a real matter at scale.
Legal documents are often subject to confidentiality obligations, privilege, or protective orders — which makes a tool that uploads files to a third-party server a meaningfully worse choice than one that parses entirely client-side. This tool reads the file using the browser's local File API and hands it directly to an in-page JavaScript parser; no network request carrying the file's contents is made (verifiable yourself in your browser's developer tools Network panel). The page also works offline after the first load, which wouldn't be possible if reading a message required a server round-trip. See the privacy policy for the full statement.
Can this tool bulk-process a whole folder of .msg files at once? No — it's a one-file-at-a-time viewer in this version. For true batch processing of large productions, a dedicated eDiscovery platform is the appropriate tool.
Does this preserve metadata needed for a load file or Bates numbering? No — this tool displays message content for human review; it doesn't generate load files, apply Bates numbers, or preserve chain-of-custody metadata in the way litigation-support software does.
Is this appropriate for privileged or highly sensitive documents? The local-only, no-upload processing is favorable for confidentiality compared to any tool that requires uploading files to a server — but always follow your firm's or organization's specific policies and any protective order terms governing how discovery materials may be handled and on what devices.