macOS Extended (Journaled) is the default file system for many Apple computers and refers to HFS+ with a journal. Journaling records metadata updates in a dedicated journal before committing them to the main volume, which helps reduce the risk of corruption after an unexpected restart. This article explains what macOS Extended (Journaled) is, how journaling works, its benefits and limits, and practical steps for verifying, enabling, and managing it on your Mac.
What macOS Extended (Journaled) Means
macOS Extended (Journaled) is Apple’s name for the HFS+ file system with journaling enabled. In this context, journaling means the file system maintains a record of planned changes in a separate journal before those changes are written to the main file system structures. If a crisis such as a power loss occurs mid-write, the journal can be replayed at startup to help restore the file system to a consistent state. macOS Extended (Journaled) is commonly used on internal drives by default and is designed for general desktop and laptop use rather than high-end enterprise workloads or network file sharing.
How Journaling Works on macOS
The Journal as a Record of Intent
When you perform a file system operation, macOS writes a description of the intended changes to the journal. Only after the journal entry is safely recorded does the system apply the changes to the catalog, allocation blocks, and other metadata. If the Mac shuts down unexpectedly while changes are in progress, on reboot the file system consults the journal to complete or roll back the operation. This behavior contrasts with a non-journaled file system, where an interruption can leave metadata in an inconsistent state that requires a longer first-aid routine.
Metadata Operations and Crash Recovery
Journaling primarily protects metadata—information such as file and directory structures, permissions, and allocation maps. It is less effective at protecting the actual content of large files that are actively being written when power is lost. For this reason, journaling is a best practice for reliability but is not a substitute for regular backups. Apple’s implementation stores the journal in a dedicated area of the volume, periodically rolling old entries so that the log remains efficient without user intervention.
Benefits and Practical Effects of Journaling
Using macOS Extended (Journaled) generally reduces the time required for automatic crash recovery and lowers the chance that you will see a message that the volume must be repaired. It also tends to simplify troubleshooting, because the sequence of recorded operations makes it easier for diagnostics and first-aid tools to identify mismatches between metadata and journal state. For most users, this translates into faster startup after an outage and fewer situations in which you feel prompted to run First Aid manually.
Limitations and What Journaling Does Not Do
It is important to understand what journaling does not guarantee. It does not prevent data loss from malware, accidental deletion, or hardware failure. A journaled file system can still become corrupted due to directory errors, failing storage media, or rare software bugs. Nor does journaling improve everyday write performance; in some cases, maintaining the journal can introduce a small overhead because each operation is written twice—once to the journal and once to the main volume. Therefore, while macOS Extended (Journaled) is more resilient to crashes than non-journaled alternatives, it does not replace a thoughtful backup strategy.
APFS, Fusion, and Modern Mac Considerations
On Macs introduced in 2016 and later, Apple typically uses APFS rather than macOS Extended (Journaled). APFS also uses journaling, but with a copy-on-write design that is more efficient for flash and SSD storage. macOS Extended (Journaled) is still present on spinning‑disk Fusion drives and as a supported format for external mechanical hard drives or legacy volumes. If you are reformatting a drive, APFS is generally recommended for internal SSDs and Fusion drives, while macOS Extended (Journaled) remains a valid choice for older internal hard drives or when compatibility with macOS earlier versions is required.
Verifying and Managing Journaling Status
You can check whether a volume is journaled from the command line, which is often the fastest way to confirm current settings. The results will tell you the file system name and whether journaling is enabled. Note that only an administrator can enable or disable journaling, and the operation typically requires the target volume to be unmounted, which means it cannot be performed on the system volume while macOS is running.
Using diskutil to View and Change Journaling
- To verify status:
diskutil info / | grep Journal - To enable journaling:
diskutil enableJournaling / - To disable journaling:
diskutil disableJournaling /
Before changing journaling, ensure that no important operations are in progress and confirm you have backups. On modern Macs with APFS, commands refer to the appropriate APFS volume; for HFS+ volumes, these commands apply to macOS Extended (Journaled).
When to Use or Avoid macOS Extended (Journaled)
Use macOS Extended (Journaled) when you are working with an HFS+-formatted internal drive on an older Mac, or when you need a format that older versions of macOS can read without third-party tools. It is also suitable for external drives that must be used interchangeably between Macs running older macOS versions. Avoid relying on it for new internal SSD installations on supported hardware, where APFS provides better efficiency, snapshots, and security features. Evaluate your workflow, required compatibility, and backup practices before choosing this file system.
Quick Comparison at a Glance
| Attribute | macOS Extended (Journaled) | APFS | Typical Use Case |
|---|---|---|---|
| File System Type | Journaled HFS+ | Copy-on-write with built-in journaling | Compatibility and legacy drives |
| Default on New Macs | No | Yes (internal SSDs and Fusion) | Modern performance and features |
| Snapshot and Cloning Support | Limited | Yes | Advanced data management |
| Encryption Integration | td>FileVault at volume levelNative file-level and volume-level encryption | Security requirements | |
| Best For | External drives, older Macs, HFS+ compatibility | Internal SSDs and Fusion drives | Matching storage to workload |
Practical Steps and Recommendations
If you are unsure whether journaling is needed, leaving it enabled on HFS+ volumes is generally safe and beneficial for crash recovery. To manage journaling, use Disk Utility to verify status or the diskutil commands in Terminal. Schedule backups that align with your data tolerance and recovery time objectives, and test restores periodically. For new projects or drives, consider APFS on compatible hardware to take advantage of modern features while retaining journaling for protection.
Final Notes
macOS Extended (Journaled) remains a dependable choice for certain workflows, particularly when compatibility with older systems or specific external drives is required. Understanding how journaling works, its advantages, and its limits helps you make informed decisions about file system selection and data protection. Pair journaling with consistent backups and periodic verification to keep your Mac environment resilient and predictable over time.