Linux · Published June 20, 2026

Does Linux Use NTFS or Ext4?

Short answer: Linux installs onto Ext4, while NTFS belongs to Windows. The longer answer is where it gets useful, because Linux can read and write NTFS just fine when it needs to.

If you install Ubuntu, Fedora, Mint, or just about any mainstream distro and click through the defaults, your root partition lands on Ext4. NTFS doesn't enter the picture. So the plain answer to "does Linux use NTFS or Ext4?" is Ext4 for the system itself, with NTFS treated as a guest format Linux can deal with when you plug in a Windows drive or share a disk between two operating systems.

That's the headline. The reason both filesystems exist, and why you'd ever touch NTFS on a Linux box, takes a little more unpacking.

what these two formats actually are

A filesystem is the bookkeeping layer that decides how files get stored, named, and tracked on a disk. It manages where each chunk of data sits, who owns it, when it changed, and how to recover if the power dies mid-write. Ext4 and NTFS solve that problem in different worlds.

NTFS, the New Technology File System, is Microsoft's. It shipped with Windows NT in 1993 and became the default for Windows 2000 onward. Per Wikipedia's entry on NTFS, it supports file-level permissions, journaling, compression, and a maximum volume size that runs into the exabytes. It's proprietary, though Microsoft has published documentation over the years that let other projects reverse-engineer and reimplement it.

Ext4, the fourth extended filesystem, is the Linux native default and has been since around 2008, when it was marked stable in the 2.6.28 kernel. It's the successor to ext3 and ext2. It handles journaling, supports volumes up to 1 exbibyte and individual files up to 16 tebibytes, and it understands the Unix permission model down to its bones. That last part matters more than people expect.

why does Linux use Ext4 instead of NTFS?

This is one of the most common follow-up questions, and the answer comes down to permissions and ownership.

Linux is built on the Unix permission system. Every file has an owner, a group, and a set of read/write/execute bits. The system relies on this for security, for keeping user accounts separate, and for letting services run without root privileges. Ext4 stores all of that natively. When you set a file to be owned by user 1000 and readable only by them, Ext4 records exactly that.

NTFS uses a completely different permission model called ACLs (access control lists) tied to Windows security identifiers. Those don't map cleanly onto Linux user IDs. You can mount an NTFS drive on Linux, but the ownership and permission handling gets awkward, because the two systems are speaking different languages about who owns what. For a root partition where the kernel needs precise control over thousands of system files, that mismatch is a dealbreaker.

There's also the legal and practical history. NTFS was closed and undocumented for years. The Linux community couldn't ship a default filesystem it didn't fully control and couldn't guarantee would stay compatible. Ext4 is open, documented, and maintained inside the kernel tree itself. It's reliable, it's fast enough, and nobody can pull the rug out from under it. If you want to see where that kernel code lives, the Linux kernel on GitHub mirror includes the ext4 driver right there in the source.

is Ext4 actually better than NTFS?

"Better" depends on the job. For a Linux system disk, Ext4 wins easily because it fits the operating system it was designed for. It's stable, well-tested across hundreds of millions of machines, and its journaling recovers gracefully from crashes.

For a drive shared between Windows and Linux, NTFS often wins on convenience, because Windows reads and writes it with zero effort and Linux can now handle it well too. NTFS also has features Ext4 lacks, like built-in transparent compression. Ext4, meanwhile, tends to be faster on Linux for everyday workloads and doesn't carry the overhead of cross-platform compatibility shims.

The folks at It's FOSS have a good practical breakdown of how Linux filesystems compare, and the recurring theme is that the "best" filesystem is the one matched to your use case rather than a single champion that beats everything.

does Linux work with NTFS at all?

Yes, and these days it works well. This trips people up because for a long time NTFS support on Linux was shaky.

The old approach was a userspace driver called NTFS-3G, built on FUSE. It worked, it was reliable for reading and writing, but it ran outside the kernel and was slower than a native driver. Most distros still ship it as a fallback.

The bigger change came in Linux kernel 5.15, released in late 2021, which merged a new in-kernel NTFS driver called ntfs3, contributed by Paragon Software. This was a real shift. For the first time Linux had fast, native read and write support for NTFS baked into the kernel itself, no FUSE layer required. If you're on a reasonably current distro, you almost certainly have it. You can confirm your kernel version with the methods in our guide on how to check your Linux version.

So when someone asks "does Linux read NTFS?" the honest answer in 2026 is: yes, reliably, including writing files back. The days of mounting Windows drives read-only out of caution are mostly behind us.

how to use an NTFS drive on Linux

In practice you rarely have to do anything. Plug in a USB drive formatted NTFS, and most desktop environments (GNOME, KDE, Cinnamon) mount it automatically when you click it in the file manager. It shows up, you copy files, you eject it. Done.

If you want to mount it manually from the terminal, the command looks like this:

• Find the drive: lsblk lists your disks and partitions, so you can spot something like /dev/sdb1.
• Make a mount point: sudo mkdir /mnt/windows
• Mount it: sudo mount -t ntfs3 /dev/sdb1 /mnt/windows

The -t ntfs3 flag tells the kernel to use the fast native driver. If your system is older and only has NTFS-3G, you'd use -t ntfs-3g instead, or just leave the type off and let the system pick. When you're finished, sudo umount /mnt/windows unmounts it cleanly. If terminal commands feel foreign, the essential Linux commands rundown covers mount, lsblk, and the rest.

does Linux use NTFS or exFAT? and what about FAT32?

These come up constantly alongside the Ext4 question, so let's sort them out.

Linux uses neither exFAT nor FAT32 for its system. Both are Microsoft-designed formats, and like NTFS they're guests on a Linux machine rather than the host filesystem. The difference is what they're good for.

FAT32 is ancient (it dates to 1996) and almost universally compatible. Every operating system, camera, game console, and car stereo reads it. Its fatal flaw is a 4 GB maximum file size, which means a single large video or disk image won't fit. Linux reads and writes it without any fuss.

exFAT was Microsoft's fix for that limit, designed for flash storage and large files. It drops the 4 GB cap and stays simpler than NTFS, with no journaling and no permissions overhead. Linux gained solid native exFAT support in kernel 5.4 (2019) when Microsoft released the spec and the driver got merged. For a USB stick or SD card you move between a Linux laptop, a Windows PC, and a phone, exFAT is usually the smartest pick because everything reads it and there's no 4 GB ceiling.

So a rough hierarchy for removable drives shared across systems:

• exFAT for large files and broad compatibility, the modern default for USB sticks.
• NTFS if you specifically need Windows features or you're mostly working with Windows.
• FAT32 only when something old refuses to read anything else.
• Ext4 if the drive will only ever touch Linux machines, since you get proper permissions and better speed.

the difference between NTFS and Ext4, side by side

Here's the practical comparison most people are actually after:

• Native to: NTFS is Windows. Ext4 is Linux.
• Permissions: NTFS uses Windows ACLs. Ext4 uses Unix owner/group/mode bits, which Linux needs.
• Cross-platform: NTFS is read/write on Windows, macOS (read-only by default), and Linux. Ext4 needs extra drivers on Windows and macOS, so it's awkward outside Linux.
• Journaling: Both have it, so both survive a crash reasonably well.
• Max file size: NTFS handles enormous files. Ext4 caps individual files at 16 TiB, which no normal user will ever hit.
• Speed on Linux: Ext4 is generally faster on Linux for day-to-day use.

If you only ever run Linux, you'll never think about NTFS. If you bridge two operating systems, you'll meet both, and knowing which is which saves a lot of confusion. For the bigger question of whether to commit to Linux at all, our Linux vs Windows comparison goes past the filesystem and into daily-driver reality.

what about Btrfs, XFS, and ZFS?

Worth a mention, because Ext4 isn't the only Linux native option. Fedora switched its desktop default to Btrfs back in Fedora 33, betting on its snapshots and built-in checksumming. openSUSE has used Btrfs for years. Red Hat-based server systems often favor XFS for large workloads. ZFS, originally from Sun, is loved for data integrity but ships separately due to licensing.

Ext4 remains the safe, boring, dependable default across Ubuntu, Debian, Mint, and most beginner-friendly distros, which is exactly why it's still the answer to this question. If you're picking a first distro and wondering what you'll land on, the honest beginner distro picks note where each one stands. For a deeper look at what's running underneath, see our breakdown of the most common Linux file system.

so which one should you actually use?

Format your Linux drives Ext4 and stop thinking about it. The system was built for it, it's fast, it handles permissions correctly, and it recovers from crashes. There's no good reason to install Linux onto NTFS, and the installer won't even nudge you toward it.

Keep NTFS in mind for one specific situation: a drive you share with Windows. Plug it in, let Linux mount it with the kernel's ntfs3 driver, copy your files, move on. If that shared drive holds files bigger than 4 GB and travels between phones and tablets too, reach for exFAT instead.

The mistake worth avoiding is overthinking it. People agonize over filesystem choice for a single USB stick when the difference for them amounts to a few seconds and zero real consequences. Pick based on what other devices need to read the drive, format it once, and get back to the work you actually opened the laptop to do.