Learn
What Is a Media File System?
A file system is the method an operating system uses to organise and store data on a drive. It determines how files are named, where their data is written on the physical or solid-state storage medium, how that data is retrieved, and how metadata such as permissions, timestamps, and ownership is tracked. Every drive you use, whether internal, external, or network-attached, has a file system. Common ones include NTFS, APFS, HFS+, exFAT, and EXT4.
For most computing tasks, the file system operates invisibly. You save a document, you open it later, and the file system handles everything in between without requiring your attention. Media production is one of the areas where this invisibility breaks down. Video, audio, and image files are large, often very large, and the demands they place on storage expose differences between file systems that other types of work rarely encounter.
A single clip from a modern cinema camera can easily exceed 10 GB. A day of shooting might produce a terabyte or more of footage. Editing, grading, and compositing workflows read and write data continuously, often from multiple files simultaneously. These demands make the choice of file system a practical concern rather than an abstract technical detail.
Why file systems matter for media
The most immediate way a file system affects media work is through file size limits. Some file systems impose a maximum size for individual files, and in video production, those limits can be a real constraint. A long recording from a high-bitrate camera, a rendered visual effects plate, or a multichannel audio session can all produce files that test or exceed these limits.
Performance is another factor. Different file systems handle read and write operations differently, and these differences affect playback, recording, and rendering. A file system that fragments files heavily (scattering pieces of a file across the drive) can slow sequential reads, which matters when playing back high-resolution video. Write performance affects how reliably a camera or recording device can capture data without dropping frames.
Reliability and data integrity features vary between file systems. Journaling, a feature where the file system logs changes before making them, protects against corruption if a drive is disconnected or power is lost during a write operation. For media work, where losing a file can mean losing hours or days of production effort, this kind of protection has real value.
Cross-platform compatibility is perhaps the most frequently encountered file system issue in media production. A drive formatted on a Mac may not be readable on a Windows machine, and vice versa. In collaborative environments where video editors, colourists, sound designers, and VFX artists may be working on different operating systems, this incompatibility creates friction. Understanding which file systems work across platforms, and what trade-offs each involves, saves time and prevents data access problems on set and in post.
The major file systems for media work
Several file systems are commonly encountered in media production, each with distinct characteristics.
NTFS (New Technology File System) is the default file system for Windows. It supports very large files (up to 16 TB with standard settings), includes journaling for data integrity, handles permissions and encryption, and performs well with both HDDs and SSDs. For Windows-based editing, grading, and VFX workstations, NTFS is the natural and well-suited choice. Its limitation in media workflows is cross-platform: macOS can read NTFS drives natively but cannot write to them without third-party software. This means an NTFS-formatted shuttle drive brought to a Mac-based facility requires additional tools to be fully usable.
APFS (Apple File System) is Apple's modern file system, introduced in 2017 to replace HFS+. It is optimised for solid-state storage and offers strong performance on SSDs, with features including native encryption, snapshots, and space sharing between volumes. For Mac-based media work, APFS provides excellent performance and reliability. Its cross-platform limitation mirrors NTFS in reverse: Windows cannot read APFS drives natively. APFS is also relatively new compared to HFS+, which means some legacy tools and workflows may not fully support it. Understanding the characteristics of your storage ties into the broader question of how much cloud storage you need and how local and remote storage interact in your workflow.
HFS+ (Mac OS Extended) is Apple's legacy file system, still in wide use. It has broader third-party support than APFS, with several tools available for reading and writing HFS+ drives on Windows. Some media professionals continue to format shuttle drives in HFS+ specifically because of this wider compatibility. HFS+ includes journaling and supports large files, though it lacks some of APFS's more advanced features.
exFAT (Extended File Allocation Table) is the cross-platform compromise. Developed by Microsoft, exFAT is supported natively on macOS, Windows, and most Linux distributions. It supports files larger than 4 GB (the maximum individual file size is 16 exabytes, which is effectively unlimited), making it suitable for large media files. It is the file system most commonly used for shuttle drives, memory cards, and any storage that needs to move between Mac and Windows systems. Its weaknesses are the absence of journaling (making it more vulnerable to corruption from improper ejection) and limited metadata and permission features.
EXT4 (Fourth Extended File System) is the default file system for most Linux distributions. It is robust, well-tested, and supports very large files and volumes. It includes journaling and handles fragmentation well. Its relevance to media production is somewhat specialised: EXT4 is commonly used on NAS (network-attached storage) devices, Linux-based render farms, and cinema servers (DCPs, for instance, are typically delivered on drives formatted in EXT2 or EXT3, which are predecessors of EXT4). macOS and Windows cannot read EXT4 drives without additional software. For those working with theatrical delivery formats, the relationship between file systems and DCPs is worth noting.
The 4 GB file size limit
One of the most common file system problems in media work involves FAT32, an older file system that remains widespread on USB drives, memory cards, and other portable storage. FAT32 has a maximum file size of 4 GB, and in modern video production, this limit is routinely exceeded.
A single clip from a camera recording in a high-quality codec at 4K resolution can surpass 4 GB in a few minutes of recording. Some cameras handle this by splitting recordings into multiple files at the 4 GB boundary (a behaviour called "file spanning"), which works but complicates file management and can cause issues in some editing workflows if the files are separated or renamed.
The 4 GB limit is the primary reason FAT32 is unsuitable for video work despite its near-universal compatibility. Every operating system, camera, and media device can read FAT32, making it tempting as a universal format. But the file size ceiling makes it impractical for anything beyond small files and short clips.
exFAT was created in part to address this limitation: it retains much of FAT32's cross-platform compatibility while removing the 4 GB file size restriction. When a drive needs to work across multiple operating systems and will hold large media files, exFAT is the typical choice. Understanding these constraints relates to broader decisions about video file formats and how different codecs affect file sizes.
Choosing a file system for external drives
The choice of file system for external and shuttle drives is one of the most common practical decisions in media production, and it usually comes down to a question of compatibility versus features.
If a drive will only be used with Mac systems, APFS (for SSDs) or HFS+ (for HDDs or when broader legacy compatibility is needed) offers the best performance and feature set. If a drive will only be used with Windows systems, NTFS is the clear choice. The decision becomes more complex when a drive must work across both platforms.
exFAT is the standard cross-platform choice. It works natively on Mac, Windows, and modern Linux distributions, supports large files, and is simple to format on any operating system. The trade-off is the lack of journaling, which means that improperly ejecting an exFAT drive (pulling it out without using the operating system's eject function) carries a higher risk of file corruption than it would on a journaled file system like NTFS, APFS, or HFS+.
For productions where drives shuttle between Mac and Windows environments frequently, exFAT's convenience usually outweighs its limitations. The key mitigation is disciplined drive handling: always eject before disconnecting, avoid removing drives during active reads or writes, and maintain backups. Collaborative workflows where creative teams share physical media benefit from establishing clear protocols around drive formatting and handling.
Some productions maintain dedicated drives for each platform, formatted in the native file system, and transfer files between them over a network. This avoids the compromises of exFAT but adds a transfer step. Network-based workflows, including cloud storage solutions, can eliminate the shuttle drive problem entirely by making files accessible to any platform via a browser or application, regardless of local file system considerations.
The question of drive formatting is closely tied to camera media. Many cameras format their recording media in exFAT or a proprietary file system. Understanding what file system your camera uses, and ensuring your editing workstation can read it natively, prevents problems on set. Camera manufacturers' documentation specifies the file system and any formatting requirements, and it is worth checking this before a shoot rather than discovering an incompatibility when offloading footage.
RAID and media storage
RAID (Redundant Array of Independent Disks) configurations are common in media production, providing increased performance, redundancy, or both by combining multiple drives into a single logical volume. The file system used on a RAID array affects its performance and reliability characteristics.
Most RAID arrays use the same file systems as individual drives: NTFS on Windows, APFS or HFS+ on Mac, EXT4 on Linux. The RAID controller (either hardware-based or software-based) presents the array to the operating system as a single volume, and the file system operates on that volume as it would on any single drive. The RAID level (RAID 0 for performance, RAID 1 for mirroring, RAID 5 or 6 for a balance of performance and redundancy) determines how data is distributed across the physical drives, but the file system sitting on top of that layer handles the logical organisation of files.
For media work, RAID performance matters because real-time playback of high-resolution, high-bitrate footage requires sustained read speeds that may exceed what a single drive can deliver. A RAID 0 array (which stripes data across multiple drives) can achieve read speeds that are multiples of a single drive's speed, making it suitable for demanding playback requirements. The trade-off is that RAID 0 offers no redundancy: if any drive in the array fails, all data is lost. RAID 5 and RAID 6 provide redundancy at some cost to write performance, which is often an acceptable trade-off for media storage where the footage is irreplaceable.
Network-attached storage (NAS) devices use their own file system internally (often EXT4 or a proprietary variant) but present files to connected computers using network protocols such as SMB (for Windows and Mac) or NFS (for Linux and Mac). The client computer accesses files over the network without needing to understand the NAS's internal file system. This abstraction simplifies cross-platform access but introduces network bandwidth as a potential bottleneck for high-resolution media playback. Proxy workflows can mitigate this by allowing editors to work with smaller files locally while the full-resolution media remains on the NAS.
File system corruption and recovery
Media production workflows stress file systems in ways that increase the risk of corruption. Large files, sustained high-speed writes (during recording or rendering), and the frequent connection and disconnection of external drives all create opportunities for things to go wrong.
The most common cause of file system corruption in media work is improper drive ejection. When an operating system writes to a drive, it may cache data in memory before committing it to the drive. Disconnecting the drive before the cache is flushed can leave the file system in an inconsistent state, with partially written files or corrupted metadata. Journaling file systems (NTFS, APFS, HFS+, EXT4) are more resilient to this because they log changes before making them, allowing the file system to recover to a consistent state after an unexpected disconnection. exFAT, which lacks journaling, is more vulnerable.
Corruption can manifest in several ways: files that cannot be opened, directories that appear empty when they should contain files, drives that are not recognised by the operating system, or error messages when attempting to read or write data. The severity ranges from losing a single file to losing access to an entire drive's contents.
Recovery tools exist for all major file systems. On macOS, Disk Utility and fsck can attempt repairs. On Windows, chkdsk performs similar functions for NTFS. Third-party recovery tools can sometimes retrieve data from corrupted drives, including drives with damaged file system structures. However, recovery is never guaranteed, and the time and cost involved can be significant.
The practical lesson is prevention. Always eject drives before disconnecting them. Use journaled file systems when possible. Maintain backups of critical media, ideally following a 3-2-1 backup strategy (three copies, on two different types of storage, with one off-site). For productions handling valuable footage, the minor inconvenience of proper drive handling is trivial compared to the cost of data loss.
Videographers working on location are particularly exposed to corruption risks, since drives are frequently connected and disconnected in the field under time pressure. Establishing a consistent offloading workflow, one that includes verification of copied files before formatting or reusing camera media, is one of the most important habits in production.
Emerging approaches
The traditional model of media storage, files on local drives managed by a local file system, is being supplemented and in some cases replaced by approaches that abstract away the file system entirely.
Network file systems have been part of post-production for years, but their role is expanding. High-speed networks and storage appliances designed specifically for media workflows can provide shared access to footage for entire editing teams, eliminating the need to duplicate files across individual workstations. The file system in these environments is managed by the storage server, and individual users interact with files through network shares that behave like local folders.
Cloud-based media storage represents a more fundamental shift. When files are stored in the cloud, the file system is managed by the storage provider's infrastructure, and users access files through applications, web interfaces, or mounted virtual drives. The local file system becomes less relevant because the files do not reside locally (or if they do, they are cached copies managed by a sync engine).
For media work, cloud storage introduces both opportunities and challenges. The opportunity is simplified access: any device, on any operating system, can reach the files without worrying about drive formatting or cross-platform compatibility. Search and organisation become features of the storage platform rather than the file system. Metadata, previews, and transcription can be applied to media files in ways that a local file system does not support natively.
The challenge is bandwidth. High-resolution media files are large, and working with them over a network connection requires sufficient speed to support playback and editing. This is where proxy workflows become particularly important: editors can work with lightweight proxy files streamed or synced from the cloud while the full-resolution originals remain in cloud storage, downloaded only when needed for final output. Understanding the differences between local and cloud storage and the various types of cloud storage helps productions make informed decisions about where their media lives.
Platforms like Fabric approach this by providing a cloud workspace where media files can be stored, organised, searched, and shared without requiring users to think about file systems at all. The files are accessible from any device, the platform handles previews and metadata, and collaboration happens through the platform rather than through exchanging physical drives. For teams tired of formatting drives and troubleshooting cross-platform incompatibilities, this kind of abstraction can be a meaningful improvement to daily workflows. Whether this model suits a given production depends on the scale of the media, the available bandwidth, and the specific requirements of the editing and finishing pipeline.
The file system is one of those technical layers that most people prefer not to think about, and the trend in media technology is toward making that preference viable. But for now, understanding the constraints and capabilities of the major file systems remains practical knowledge for anyone working with large media files, particularly when drives need to move between systems, reliability is critical, and the files themselves represent significant creative and financial investment.
Frequently asked questions
What file system should I use for an external hard drive used with both Mac and Windows?
exFAT is the most practical choice. It is supported natively on both macOS and Windows, handles large files without issue, and is easy to format on either platform. The main drawback is the lack of journaling, so proper ejection before disconnecting the drive is important to avoid corruption.
Can macOS write to NTFS drives?
macOS can read NTFS drives natively but cannot write to them without third-party software. Tools such as Paragon NTFS for Mac or Tuxera NTFS add write capability. Some users prefer to reformat shuttle drives as exFAT to avoid needing additional software.
Why does my camera split video files at 4 GB?
Your camera is recording to media formatted in FAT32, which has a 4 GB maximum file size. The camera splits the recording into sequential files to work around this limit. Reformatting your recording media to exFAT (if your camera supports it) will eliminate the splitting. Check your camera's documentation to confirm exFAT support before reformatting.
Is exFAT reliable enough for professional video work?
exFAT is widely used in professional video production, particularly for shuttle drives and camera media. Its lack of journaling makes it more vulnerable to corruption from improper ejection than NTFS or HFS+, but with disciplined drive handling (always ejecting before disconnecting, maintaining backups), it is reliable enough for professional use. It should not be used as the sole location for irreplaceable footage without backups.
What is journaling and why does it matter?
Journaling is a file system feature that logs intended changes before writing them to the drive. If the drive is disconnected or loses power during a write, the journal allows the file system to identify and recover from the incomplete operation. For media work, where files are large and writes can take a long time, journaling provides meaningful protection against data loss.
Can I use a Mac-formatted drive in a Windows-based edit suite?
HFS+ drives can be read on Windows using third-party software such as Paragon HFS+ for Windows or MacDrive. APFS drives have more limited Windows support. If cross-platform access is a regular need, formatting the drive as exFAT avoids the need for additional software. Alternatively, transferring files over a network bypasses the file system compatibility issue entirely.
What file system do NAS devices use?
Most NAS devices use EXT4 or a proprietary file system internally. However, the NAS presents files to connected computers using network protocols (SMB, NFS, or AFP), so the client computers do not need to understand the NAS's internal file system. This is one of the advantages of network-attached storage: it abstracts the file system layer, providing access from any operating system.
How do I check what file system a drive is using?
On macOS, open Disk Utility and select the drive; the file system is listed in the drive information panel. On Windows, right-click the drive in File Explorer and select Properties; the file system is displayed on the General tab. On Linux, the lsblk -f or df -T commands show file system information for mounted drives.
Does the file system affect video playback performance?
It can, though the drive's hardware (HDD vs SSD, connection interface, read speed) has a larger effect in most cases. File systems that fragment files heavily can slow sequential reads, which affects video playback. Modern file systems on SSDs generally provide sufficient performance for most video playback needs. For demanding workflows involving high-bitrate, high-resolution footage, the combination of file system, drive hardware, and connection interface all contribute to whether smooth playback is achievable.
Should I format my SSD differently from my HDD?
Some file systems are optimised for SSDs. APFS, for instance, was designed specifically with flash storage in mind and includes features like TRIM support and wear-levelling awareness. NTFS on Windows handles SSDs well with proper TRIM support enabled. EXT4 on Linux also supports TRIM. exFAT works on both SSDs and HDDs without issue. In general, using your operating system's preferred modern file system (APFS on Mac, NTFS on Windows, EXT4 on Linux) will provide good SSD performance without special configuration.