MBOX and MSG are two very different ways of storing email. An MBOX file usually contains many email messages concatenated into one mailbox file or mailbox package, while an MSG file normally represents one individual Microsoft Outlook item with its message properties, attachments, recipients, timestamps, and other metadata. On a Mac, converting MBOX to MSG is not as simple as renaming the extension. Apple Mail can import and export MBOX, and modern Outlook for Mac can open and save EML files, but Microsoft does not provide a built-in bulk “MBOX to MSG” conversion wizard for macOS. That means the right workflow depends on what you actually need. If you want to migrate email into Outlook or Microsoft 365, you may not need MSG files at all. If a legal, archiving, CRM, eDiscovery, or Windows Outlook workflow specifically requires individual .msg files, then a dedicated converter or a staged MBOX → EML → MSG process may be necessary. This updated guide explains what MBOX and MSG are, why the old claims that MBOX is “not human-readable” or has “low encryption” are misleading, which native Mac tools can handle MBOX, when an MBOX Converter for Mac may be useful, how to verify message fidelity after conversion, and how to avoid turning an email-format conversion into a data-loss problem.
What MBOX and MSG Files Are
MBOX is a family of mailbox formats in which multiple email messages are stored together. MBOX or MBOX-style mailbox storage is associated with applications and systems such as: Apple Mail; Mozilla Thunderbird; Unix mail systems; Google Takeout exports; other email clients and archival tools. The exact implementation can vary.
MBOX Is Not “Unreadable”. The original article said MBOX files are not human-readable. That is inaccurate. An MBOX file is generally text-based and can often be opened in a text editor, where you may see: email headers; message bodies; MIME boundaries; encoded attachments; HTML source. However, manually reading a large MBOX in a text editor is impractical because:
hundreds or thousands of messages may be combined; attachments are encoded; HTML messages contain markup; character encoding varies; mailbox separators must be interpreted correctly. An email client or parser provides the useful structure. MBOX Does Not Have “Low Encryption”. Another misleading statement in the old post was that MBOX has “very low encryption.” MBOX itself is a storage format. It does not define a universal encryption strength. Security depends on: filesystem permissions; full-disk encryption such as FileVault; encrypted backup; application security; device access. A plain MBOX on an unencrypted drive can be read by anyone who gains file access. An MBOX stored on an encrypted Mac volume can be protected by that encryption. What Is an MSG File?. MSG is Microsoft’s compound message format used by Outlook and related Windows workflows. An MSG file can preserve one Outlook item, such as: email; meeting request; appointment; contact; task. For email, it can store: subject; sender; recipients; body formats; attachments; timestamps; MAPI properties; categories or flags in some cases.
Why Convert MBOX to MSG on a Mac
Common reasons include: moving archived mail into a Microsoft-centric workflow; creating one file per message; eDiscovery review; document-management ingestion; CRM attachment requirements; legal production; Windows Outlook compatibility; preserving messages as standalone files. Do You Really Need MSG?. Before converting thousands of emails, determine the final destination. If your goal is: Move email into Microsoft 365. You may be better off importing or synchronizing messages into a mailbox rather than generating MSG files. Open individual messages on Mac. EML may be more convenient because modern Outlook for Mac supports opening and saving EML files. Archive mail independently of Outlook. MBOX may already be suitable. Deliver messages to Windows users or a Windows document system. MSG may be justified. Apple Support — Import or Export Mailboxes in Mail confirms that Apple Mail can import messages from MBOX and export mailboxes back to MBOX. That makes Apple Mail useful for inspecting and organizing an archive before conversion, and it also means a user who only needs to read or reorganize the mail may not need MSG at all.
What macOS and Outlook Can Already Do Without Conversion
Apple’s current documentation confirms that Mail on Mac can import mailboxes in MBOX format. The native process is: Open Apple Mail.; Choose File > Import Mailboxes.; Select “Files in mbox format.”; Select the MBOX file or folder.; Complete the import.; Review the messages in the Import mailbox. This is useful for checking whether the MBOX itself is healthy before converting it. Apple Mail Also Exports MBOX. Apple Mail can export selected mailboxes in MBOX format. That makes MBOX a practical interchange/archive format in Mac workflows, not an inherently obsolete or problematic file type. Microsoft Support — Outlook for Mac Features shows that current Outlook for Mac can open and save EML files. Microsoft also notes that legacy Outlook for Mac support ends in October 2026, so workflows that depend on old Mac-only import/export behavior should be tested against the current Outlook version rather than copied from older instructions. Outlook for Mac and EML. Microsoft’s current Outlook for Mac feature documentation lists support for opening and saving .eml files. This makes EML a useful intermediate format because an EML normally stores one RFC-style email message per file. What About MSG Support on Mac?. MSG support differs by Outlook product and version. Microsoft’s Windows feature comparison shows broad MSG support in modern and classic Outlook for Windows, but the Outlook for Mac feature list prominently documents EML handling rather than providing a native bulk MBOX-to-MSG conversion workflow. If your final destination is Windows Outlook, creating MSG files may make more sense after transferring the messages to a Windows environment.
Method 1: Review and Organize the MBOX in Apple Mail
If you receive an unknown MBOX archive, first validate it. Make a backup copy.; Import the copy into Apple Mail.; Check folder/message counts.; Open old and new messages.; Check attachments.; Check special characters.; Verify dates. If Apple Mail cannot import it correctly, the problem may be the source MBOX rather than the converter.
Method 2: Use EML as an Intermediate Format
For users who want more control, a staged conversion can be useful. The broad process is: Import MBOX into an email client that supports it.; Export individual messages as EML.; Transfer the EML files to Windows Outlook or a conversion environment.; Open/convert the messages to MSG where required.; Verify attachments and metadata. This is not necessarily the fastest method for 100,000 messages, but it makes each stage easier to inspect.
Method 3: Use a Dedicated Converter for Large or Structured Jobs
A dedicated MBOX conversion tool may offer direct output to MSG. Possible benefits: batch conversion; one MSG file per email; folder preservation; attachment preservation; date filtering; duplicate handling; naming options. Capabilities differ by product. Do not assume every feature listed in an old blog is still supported by the current version.
What a Reliable Conversion Must Preserve
A good conversion should preserve more than visible message text. Check: From; To; Cc; Bcc where present; subject; sent date; received date; plain-text body; HTML body; attachments; inline images; internet headers; Unicode characters; folder relationship. Bcc Can Be Difficult. Bcc information is not always present in a received message because of how email delivery works.
If you are converting Sent Items, more recipient metadata may exist than in received messages. Do not assume a converter can reconstruct metadata that the MBOX never contained. Message Flags and Categories May Not Map Perfectly. MBOX is fundamentally message-oriented, while Outlook MSG can contain Microsoft-specific properties. Depending on the source client, items such as:
flag status; categories; labels; read/unread state; custom properties. may not have a direct equivalent. Folder Structure. An “MBOX archive” may actually be: one mailbox file; many MBOX files in nested folders; an Apple Mail .mbox package; Thunderbird profile directories. The converter needs to interpret the structure correctly. Google Takeout MBOX. Google Takeout can export Gmail data in MBOX. Labels can complicate migration because Gmail labels do not map perfectly to traditional folders. A message with multiple Gmail labels might: appear in more than one exported context; produce duplicate-looking results after conversion; lose label semantics. Plan duplicate handling carefully. Thunderbird MBOX. Thunderbird profiles may store mail in MBOX-style files accompanied by index files. If extracting directly from a profile, identify the real mailbox files rather than converting temporary or index files. Apple Mail MBOX Packages. Apple Mail exports .mbox packages that may contain internal folder structures. A converter should explicitly support Apple Mail output if that is your source.
Protect the Source Archive Before Conversion
Never test a converter on your only archive. Recommended structure: Original — untouched backup; Working Copy — input for conversion; Output — MSG files; Verification Report — counts and errors. Check File Integrity Before Conversion. Warning signs include: zero-byte MBOX; abrupt truncation; messages missing headers; corrupt MIME boundaries; attachments that never open. A converter cannot reliably recreate data that is absent from the source. Choose a Naming Scheme for MSG Files. Exporting thousands of messages as: message1.msg, message2.msg, message3.msg makes the archive difficult to use. Better filename components can include: date; sender; subject; unique counter; message ID fragment. Example: 2026-08-21_Jane-Doe_Project-Approval_000123.msg Sanitize Filenames. Email subjects may contain characters that are invalid or problematic in filenames. The converter should handle: slashes; colons; question marks; very long subjects; Unicode characters; duplicate filenames.
Path Length Matters. Deep folder trees plus long subjects can create very long file paths. This can cause problems when the MSG files are later copied to Windows, network storage, SharePoint, or document-management platforms. Use reasonable folder and filename lengths.
Attachments, Inline Images, Dates, and International Text
Verify several attachment types after conversion: PDF; Word; Excel; images; ZIP; calendar invitations; attached email messages. Nested message attachments deserve special attention. Inline Images. HTML signatures and newsletters often use inline MIME images. A weak converter may: show broken placeholders; turn inline images into ordinary attachments; lose Content-ID relationships. Spot-check image-heavy messages. Date Preservation. An email can have several dates: Date header; server received dates; filesystem modification date; import date. Do not judge conversion success by Finder’s file creation date alone. Open the MSG and verify the actual email timestamp. Unicode and International Text. Test messages containing: Arabic; Chinese; Urdu; accented European characters; emoji; right-to-left text. Character-encoding failures can make an archive unusable even when the conversion finishes without an error. HTML vs. Plain Text. Some emails contain both HTML and plain-text MIME alternatives. The converter should preserve enough structure for Outlook to render the intended message correctly.
Large Archives, Batching, and Duplicate Handling
A multi-gigabyte MBOX can stress: RAM; disk space; converter indexing; output filesystem; backup. Before starting, ensure free disk space is substantially larger than the MBOX size because thousands of individual MSG files can consume more filesystem space than one compact mailbox file. Convert in Batches. For very large archives, divide by: mailbox; year; folder; source account. This makes failures easier to isolate. Duplicate Email. MBOX archives can contain duplicates because of: repeated exports; Gmail labels; mailbox merges; migration history. If the converter offers deduplication, understand its matching criteria before enabling it. Two emails with the same subject are not necessarily duplicates. How to Detect Duplicates More Reliably. Useful fields include: Message-ID; sender; recipient; date; subject; body hash; attachment hash.
Privacy, Legal Holds, and Verification
If the conversion is for litigation, compliance, or investigation, preserving evidentiary integrity may be more important than convenience. Consider: hashing original files; chain of custody; logging; metadata preservation; read-only originals; validated software; legal review. A generic desktop converter may not be sufficient for formal forensic requirements. Security and Privacy. Email archives can contain: password reset links; contracts; personal data; financial information; health information; customer records; attachments. Before using software, determine whether conversion occurs: locally on the Mac; on a cloud server; through an upload portal. Avoid Uploading Confidential MBOX Files to Random Websites. A browser converter may require you to upload the entire mailbox. That could expose years of private email. For sensitive archives, prefer: local processing; approved enterprise tools; contractual privacy controls. macOS Security. For downloaded conversion software, check: developer identity; code signing; notarization; requested permissions; supported macOS versions; Apple silicon compatibility. Do Not Disable Gatekeeper Permanently. If a tool requires bypassing macOS security controls broadly, reconsider whether you trust it. Use vendor-supported installation methods.
Verify Before Deleting MBOX. After conversion, compare: source message count; output MSG count; failed items; attachment counts; date range; folder structure. Open a sample from: beginning of archive; middle; end; each major folder; messages with large attachments; HTML messages; Unicode messages. Why Counts May Not Match Exactly. Differences can come from: duplicates removed; deleted messages; corrupt records; non-email items; Gmail label duplicates; parser errors. The conversion report should explain the difference. Should You Convert Attachments Separately?. Usually no. Keeping attachments inside the MSG preserves context. Separate attachment extraction may be useful for: document review; virus scanning; content indexing; storage deduplication. But do not discard the message relationship. MBOX to PDF Is a Different Goal. PDF is useful for: reading; printing; sharing selected messages. It is not a substitute for MSG when you need: machine-readable mail headers; Outlook message properties; original attachments; email workflow integration.
MBOX to PST May Be Better Than MBOX to MSG. If your true goal is to migrate a complete mailbox into Outlook for Windows, PST can be more efficient than creating tens of thousands of standalone MSG files. PST preserves a mailbox/folder database rather than creating one filesystem object per message. Choose the Destination First. Use this rule: Need Apple Mail/Thunderbird archive: keep MBOX.; Need portable individual messages on Mac: consider EML.; Need full Outlook mailbox migration: consider PST or mailbox synchronization.; Need standalone Outlook Windows item files: MSG may be appropriate.
A Practical MBOX-to-MSG Workflow
Back up the source MBOX.; Import it into Apple Mail to validate.; Determine whether MSG is really required.; Test a small batch with the chosen conversion method.; Verify headers, dates, bodies, and attachments.; Define a filename/folder strategy.; Convert in batches.; Review failures.; Keep the original MBOX permanently or until retention policy allows deletion. Does it support my exact MBOX source?; Does it produce individual MSG files?; Does it preserve attachments?; Does it preserve HTML?; Does it preserve internet headers?; Does it preserve folder hierarchy?; What happens to duplicate names?; Does it process locally?; Is it compatible with Apple silicon?; Can I preview before purchase?; Does it produce a conversion log?.
Conclusion
Converting MBOX to MSG on a Mac is a legitimate requirement for some Outlook, legal, archival, and document-management workflows, but it is not always necessary. MBOX is a practical mailbox format supported by Apple Mail and other applications. It is not inherently “low encryption” or unreadable. MSG is useful when you specifically need individual Outlook-style message files. Start by validating the MBOX with a native mail client, decide whether EML or PST would satisfy the actual destination more efficiently, and use a dedicated MSG converter only when MSG is truly required. Whatever method you choose, preserve the original archive, test a sample, and verify metadata and attachments before treating the conversion as complete.