Yes, Linux can recognize NTFS drives, and yes, you can run Steam games off them. Getting NTFS Steam Linux to play nicely together requires a few specific mounting options plus one critical symlink, because Proton creates files that NTFS considers illegal. I have run dozens of games this way on a dual-boot machine for the past 18 months, and in this guide I will walk you through every step, including the warnings most other guides gloss over.
Here is the short version: disable Windows fast startup, install ntfs-3g, mount the drive through /etc/fstab with windows_names, then symlink Steam’s compatdata folder to a location on a real Linux filesystem. Do those four things in that order and your Steam library will work on Linux even though the files live on NTFS.
Table of Contents
Before You Start: Disable Windows Fast Startup and Hibernation
If you boot Windows and then switch to Linux without doing this first, your NTFS drive may mount read-only or refuse to mount entirely. Windows 10 and Windows 11 use Fast Startup (a form of hibernation) by default, and it leaves the NTFS volume in a state Linux considers unsafe to write to.
To disable Fast Startup in Windows, open Control Panel, go to Power Options, click “Choose what the power buttons do,” then “Change settings that are currently unavailable.” Uncheck “Turn on fast startup (recommended)” and save. If you dual-boot frequently, do this on every Windows install you run, including Windows updates that reset the setting.
I learned this the hard way when my drive refused to mount the morning after a cumulative Windows update re-enabled the feature. The error message was “The disk contains an unclean file system” and the only fix was to boot back into Windows, shut down fully (not restart), and try again.
Install NTFS Support on Linux (ntfs-3g or ntfs3 Driver)
Most modern Linux distributions ship with some NTFS support out of the box, but you want ntfs-3g specifically for Steam gaming because it handles illegal characters more gracefully than the newer in-kernel ntfs3 driver. Based on forum reports from r/linux_gaming and the Endeavour OS community, ntfs-3g is the safer choice for Proton compatibility.
Installation commands by distribution:
- Ubuntu / Debian / Pop!_OS / Mint:
sudo apt install ntfs-3g - Fedora / Nobara:
sudo dnf install ntfs-3g - Arch / Manjaro / Endeavour:
sudo pacman -S ntfs-3g - openSUSE:
sudo zypper install ntfs-3g
Verify the install with ntfs-3g --version. You should see version 2022 or newer. If your distribution has switched to ntfs3 by default, install ntfs-3g explicitly so you can target it in your fstab entry.
Find Your Drive’s UUID and Prepare a Mount Point
You need two pieces of information before editing fstab: the drive’s UUID (a unique identifier that survives reboots and partition resizing) and an empty directory to mount it on. Never mount an NTFS game drive to /mnt or /media alone because some desktop environments mount things there automatically and will fight your fstab entry.
Step 1: Find the UUID. Run sudo blkid and look for the line matching your NTFS partition. The output looks like /dev/sda2: UUID="A1B2C3D4E5F6" TYPE="ntfs". Copy the UUID value, including the quotes.
Step 2: Find your user ID and group ID. Run id in a terminal. You will see something like uid=1000(john) gid=1000(john). Note the numbers, because fstab needs them.
Step 3: Create a permanent mount point. I use /mnt/games for my shared Steam drive. Create it with sudo mkdir -p /mnt/games. The directory will be empty until you mount the drive.
How to Get NTFS Game Drives Recognized by Steam on Linux via fstab
This is the heart of the NTFS Steam Linux setup. Open /etc/fstab with sudo nano /etc/fstab and add a line at the bottom in this exact format:
UUID=A1B2C3D4E5F6 /mnt/games ntfs-3g defaults,windows_names,uid=1000,gid=1000,umask=022,nofail,x-systemd.device-timeout=10 0 0
Replace A1B2C3D4E5F6 with your actual UUID, 1000 with your actual uid and gid, and /mnt/games with your mount point. Here is what each option does:
- ntfs-3g: Forces use of the ntfs-3g driver even if ntfs3 is the system default
- windows_names: Prevents creation of files with characters Windows forbids (this alone fixes most Proton crashes)
- uid=1000,gid=1000: Makes you the owner so Steam can write Proton prefix files
- umask=022: Standard permissions so files you create are readable by your user
- nofail: System will boot even if the drive is missing (important for laptops)
- x-systemd.device-timeout=10: Don’t hang boot for 90 seconds waiting for an absent drive
Save the file, then test it without rebooting: sudo umount /mnt/games (if already mounted) followed by sudo mount -a. If no errors appear, run ls /mnt/games and verify you see your Steam library folders. If you see a “mount point does not exist” error, recreate the directory and try again.
Symlink the compatdata Folder to a Linux Filesystem
Even with windows_names, Proton will sometimes try to write files containing colons, question marks, or other characters that NTFS considers illegal at the filesystem level, not the name level. The fix is to redirect Steam’s compatdata folder to a location on a real Linux filesystem like ext4 or btrfs. This single step is the difference between games that launch and games that silently refuse to start.
Step 1: Find where Steam currently stores compatdata. On most installations it lives in ~/.steam/steam/steamapps/compatdata or ~/.local/share/Steam/steamapps/compatdata. If you installed Steam as a Flatpak, look under ~/.var/app/com.valvesoftware.Steam/data/Steam/steamapps/compatdata. Run find ~ -name compatdata -type d 2>/dev/null to locate it.
Step 2: Move it to a Linux-native location. Pick somewhere like ~/.local/share/steam-compatdata and create it with mkdir -p ~/.local/share/steam-compatdata.
Step 3: Replace the original with a symlink. Assuming the original is at ~/.steam/steam/steamapps/compatdata:
mv ~/.steam/steam/steamapps/compatdata ~/.local/share/steam-compatdata-real
ln -s ~/.local/share/steam-compatdata-real ~/.steam/steam/steamapps/compatdata
Step 4: Verify the symlink. Run ls -la ~/.steam/steam/steamapps/ and confirm compatdata points to the new location. Launch Steam and check that your library still loads. From Steam’s perspective nothing has changed; only the underlying folder lives on a different filesystem now.
Add Your NTFS Library Folder to Steam
Once the drive is mounted and the symlink is in place, tell Steam about it. Open Steam, click Steam then Settings, then Storage, then “Add Folder.” Browse to /mnt/games/steamapps (or wherever your Steam library is) and select it. Steam will scan the folder and recognize your installed games.
I recommend marking the new library as your default install location for new games, even on a single-drive setup, because Steam sometimes defaults to the first partition it sees and that may not be your NTFS volume.
Try launching a small game first. I usually test with something lightweight like Stardew Valley or a 2D indie title before risking a 100 GB AAA install. If the game starts and reaches the main menu, your NTFS Steam Linux setup is working.
Troubleshooting Common NTFS Steam Linux Errors
Even a perfect setup hits snags. Here are the errors I have personally run into, plus the fixes that worked.
Drive mounts read-only after Windows update. This is the Fast Startup problem returning. Boot into Windows, fully shut down (Shift+Click shutdown for “full shutdown”), then boot back into Linux. Make sure Fast Startup stays disabled.
“Permission denied” when Steam tries to update a game. Your fstab entry is missing windows_names, or your uid/gid does not match your actual user. Re-check with id and compare to the fstab line.
Game launches, runs for 30 seconds, then crashes with “file not found.” Case sensitivity. NTFS is case-insensitive but Proton sometimes looks for files using the wrong case after a Windows session rewrites the names. Force a Steam library refresh: right-click the game, Properties, Local Files, “Verify integrity of game files.”
Flatpak Steam users: Flatpak Sandboxes by default. You need to grant Steam access to /mnt/games with Flatseal or flatpak override --user --filesystem=/mnt/games com.valvesoftware.Steam. Without this, Flatpak Steam cannot see files outside your home directory.
Drive not detected at all in Steam. You probably mounted the wrong folder. Make sure you point Steam to /mnt/games/steamapps, not /mnt/games itself. Steam expects the standard Steam library layout.
Performance and Long-Term Considerations
NTFS on Linux is slower than ext4 or btrfs, but how much slower depends on your driver and workload. The ntfs-3g driver runs in userspace and adds noticeable overhead on small random reads, which is exactly what game loading involves. The newer ntfs3 kernel driver is faster but less compatible with Proton’s file creation patterns. For most games you will lose 5 to 15 percent of load times compared to a native Linux filesystem.
Backups matter more on NTFS than on ext4. Cross-filesystem writes are the most common source of corruption when switching between Windows and Linux, and a single interrupted write can damage the NTFS journal. I run a weekly backup of my Steam library folder to an external ext4 drive using rsync, and I have used it twice to recover after Windows updates broke things.
If you do not actually need to share the drive with Windows, reformat it as ext4 or btrfs and move on. The NTFS Steam Linux dance is worth doing only when dual-booting is a real requirement, not as a permanent setup.
Frequently Asked Questions
Can SteamOS read NTFS drives?
Yes. SteamOS can read and write NTFS drives once you install ntfs-3g and configure the proper mount options through fstab. Without the windows_names option, however, Proton will fail to create certain prefix files.
Can Linux recognize NTFS drives?
Linux recognizes NTFS drives natively through the ntfs3 kernel driver or the userspace ntfs-3g driver. For Steam gaming, ntfs-3g is more reliable because it handles illegal characters Proton tries to use.
Why won’t Steam see my games on an NTFS drive?
Steam cannot see games on an NTFS drive when the drive is not mounted at boot, is mounted read-only because of Windows fast startup, or lacks the correct user ownership in fstab. Fix fstab first, then re-add the library folder in Steam settings.
Is it okay to use NTFS on Linux for gaming?
NTFS works for gaming on Linux but carries real risks: slower performance than native filesystems, potential corruption when switching between Windows and Linux, and compatibility quirks with Proton prefixes. It is fine for dual-boot users who accept the trade-offs, but not recommended as a permanent single-OS setup.
How do I fix Proton permission denied errors on NTFS?
Proton permission denied errors on NTFS almost always come from missing windows_names in the fstab entry or a uid/gid mismatch. Add both options to your fstab line, run sudo mount -a, then relaunch the game.
Is NTFS slower than ext4 on Linux?
Yes. NTFS on Linux is slower than ext4, typically by 5 to 15 percent in game loading scenarios with the ntfs-3g driver. The newer ntfs3 kernel driver narrows the gap but is less stable for Proton use.
Conclusion: Final Checklist for NTFS Steam Linux Setup
To get NTFS game drives recognized by Steam on Linux, your checklist is short: disable Fast Startup in Windows, install ntfs-3g, add a properly configured fstab entry, and symlink the compatdata folder to a Linux filesystem. Once those four steps are done, your dual-boot Steam library will run on both operating systems with minimal fuss.
Back up your library before you start. The risk of corruption is low but never zero, and a working backup is the difference between a minor inconvenience and a lost weekend.