Comparison of file systems#Metadata

! scope="col" | File system

! scope="col" | Creator

! scope="col" | Year of introduction

! scope="col" | Original operating system

| DEC

| 1964

| PDP-6 Monitor

| IBM

| 1964

| OS/360

| DEC

| 1968

| TOPS-10

| ICT (later ICL)

| 1968

| George 3

| Bell Labs

| 1972

| Version 6 Unix

| DEC

| 1973

| RT-11

| GEC

| 1973

| Core Operating System

| Digital Research (Gary Kildall)

| 1974

| CP/M{{cite web |url=http://www.computerhistory.org/atchm/in-his-own-words-gary-kildall/ |title=In His Own Words: Gary Kildall |author-first=Len |author-last=Shustek |date=2016-08-02 |work=Remarkable People |publisher=Computer History Museum}}{{cite web|orig-year=1993|date=2016-08-02|title=Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry|author-first=Gary Arlen|author-last=Kildall|author-link=Gary Kildall|editor-first1=Scott|editor-last1=Kildall|editor-link=Scott Kildall|editor-first2=Kristin|editor-last2=Kildall|publisher=Kildall Family|type=Manuscript, part 1|url=http://www.computerhistory.org/atchm/computer-history-museum-license-agreement-for-the-kildall-manuscript/|access-date=2016-11-17}}

| DEC

| 1975

| RSX-11

| GEC

| 1977

| OS4000

| Microsoft (Marc McDonald) for NCR

| 1977

| Microsoft Standalone Disk BASIC-80 (later Microsoft Standalone Disk BASIC-86)

| Apple

| 1978

| Apple DOS

| UCSD

| 1978

| UCSD p-System

| Commodore

| 1978

| Commodore BASIC

| Atari

| 1979

| Atari 8-bit

| Bell Labs

| 1979

| Version 7 Unix

| DEC

| 1979

| OpenVMS

| Seattle Computer Products (Tim Paterson)

| 1980

| QDOS/86-DOS (later IBM PC DOS 1.0)

| Apple

| 1980

| Apple SOS (later ProDOS 8)

| Acorn Computers Ltd

| 1982

| Acorn BBC Micro MOS

| Acorn Computers Ltd

| 1983

| Acorn Electron (later Arthur/RISC OS)

| Kirk McKusick

| 1983

| 4.2BSD

| IBM, Microsoft

| 1984

| PC DOS 3.0, MS-DOS 3.0

| Apple

| 1984

| System 1

| NPO "Scientific centre" (now Sitronics)

| 1985

| Vilnius Basic, BK monitor program

| Apple

| 1985

| System 2.1

| Metacomco for Commodore

| 1985

| Amiga OS

| Digital Research

| 1985

| Atari TOS

| Novell

| 1985

| NetWare 286

| Ecma International

| 1986

| MSCDEX for MS-DOS 3.1/3.2{{cite journal |title=Extensions to MS-DOS Run CD-ROM |author-first=Scott |author-last=Mace |journal=InfoWorld |volume=8 |issue=38 |date=1986-09-22 |pages=1, 8 |url=https://books.google.com/books?id=ZS8EAAAAMBAJ&pg=PA1 |access-date=2016-11-09}}

| Compaq

| 1987

| Compaq MS-DOS 3.31

| Andrew S. Tanenbaum

| 1987

| MINIX 1.0

| Commodore

| 1988

| Amiga OS 1.3

| Ecma International, ISO

| 1988

| MS-DOS, "classic" Mac OS, and AmigaOS

| IBM & Microsoft

| 1989

| OS/2 1.2

| IEEE

| {{Circa|1990|sortable=yes}}

| Unix

| IBM

| 1990

| AIX{{efn |name=note-11 |IBM introduced JFS with the initial release of AIX Version 3.1 in 1990. This file system now called JFS1. The new JFS, on which the Linux port was based, was first shipped in OS/2 Warp Server for e-Business in 1999. The same sourcebase was also used for release JFS2 on AIX 5L.}}

| VERITAS

| 1991

| SVR4.0

| Rémy Card

| 1992

| Linux

| DEC

| 1993{{cite web |last1=Warren |first1=David |date=20 October 1993 |title=Polycenter File System - - HELP |url=http://www.ornl.gov/lists/mailing-lists/tru64-unix-managers/1993/10/msg00043.html |archive-url=https://web.archive.org/web/20120309144054/http://www.ornl.gov/lists/mailing-lists/tru64-unix-managers/1993/10/msg00043.html |archive-date=9 March 2012 |url-status=dead}}

| Digital Unix

| Microsoft (Gary Kimura, Tom Miller)

| 1993

| Windows NT 3.1

| Margo Seltzer

| 1993

| Berkeley Sprite

| Rémy Card

| 1993

| Linux, Hurd

| Q. Frank Xia

| 1993

| Linux

| Kirk McKusick

| 1994

| 4.4BSD

| SGI

| 1994

| IRIX

| IBM

| 1994

| MVS/ESA (now z/OS)

| Microsoft

| 1995

| MS-DOS 7.0 / Windows 95

| Microsoft

| 1995

| Microsoft Windows, Linux, "classic" Mac OS, and FreeBSD

| ISO/ECMA/OSTA

| 1995

| {{n/a}}

| Microsoft

| 1996

| MS-DOS 7.10 / Windows 95 OSR2{{efn |name=note-10 |Microsoft first introduced FAT32 in MS-DOS 7.1 / Windows 95 OSR2 (OEM Service Release 2) and then later in Windows 98. NT-based Windows did not have any support for FAT32 up to Windows NT4; Windows 2000 was the first NT-based Windows OS that received the ability to work with it.}}

| Sun Microsystems

| 1996

| Solaris

| IBM

| 1996

| AIX, Linux

| Be Inc. (D. Giampaolo, Cyril Meurillon)

| 1996

| BeOS

| Andrew S. Tanenbaum

| 1997

| MINIX 2.0

| Apple

| 1998

| Mac OS 8.1

| Novell

| 1998

| NetWare 5

| PolyServe

| 1998

| Windows, Linux

| DEC

| 1998

| OpenVMS V7.2

| NetApp

| 1998

| Data ONTAP

| Stephen Tweedie

| 1999

| Linux

| Ecma International, ISO

| 1999

| Microsoft Windows, Linux, "classic" Mac OS, FreeBSD, and AmigaOS

| IBM

| 1999

| OS/2 Warp Server for e-business

| Sistina (Red Hat)

| 2000

| Linux

| Namesys

| 2001

| Linux

| IBM

| 2001

| z/OS (backported to OS/390)

| Microsoft

| 2002

| Xbox

| Kirk McKusick

| 2002

| FreeBSD 5.0

| Oracle Corporation

| 2002

| Linux

| Phillip Lougher, Robert Lougher

| 2002

| Linux

| VMware

| 2002

| VMware ESX Server 2.0

| Cluster File Systems{{cite press release |title=Sun Microsystems Expands High Performance Computing Portfolio with Definitive Agreement to Acquire Assets of Cluster File Systems, Including the Lustre File System |location=Santa Clara, Calif. |date=12 September 2007 |publisher=Sun Microsystems, Inc. |url=http://www.sun.com/aboutsun/pr/2007-09/sunflash.20070912.2.xml |archive-url=https://web.archive.org/web/20071002091821/http://www.sun.com/aboutsun/pr/2007-09/sunflash.20070912.2.xml |archive-date=2 October 2007}}

| 2002

| Linux

| Bell Labs

| 2003

| Plan 9 version 4

| Google

| 2003

| Linux

| Sun Microsystems

| 2004

| Solaris

| Namesys

| 2004

| Linux

| Palm, Inc.

| 2004

| Palm OS Garnet

|Fraunhofer/ [http://thinkparq.com/ ThinkParQ]

|2005

|Linux

| Gluster Inc.

| 2005

| Linux

| Andrew S. Tanenbaum

| 2005

| MINIX 3

| Oracle Corporation

| 2005

| Linux

| NTT

| 2005

| Linux

| VMware

| 2005

| VMware ESX Server 3.0

| Red Hat

| 2006

| Linux

| various

| 2006

| Linux

| Microsoft

| 2006

| Windows CE 6.0

| Chris Mason

| 2007

| Linux

| Hyperion Entertainment

| 2008

| AmigaOS 4.1

| Matthew Dillon

| 2008

| DragonFly BSD 2.0

| StarWind Software

| 2009

| Linux, FreeBSD, Windows

| Nasuni

| 2009

| Cloud

| Nimble Storage

| 2010

| Linux

|Omnibond and others

|2011

| Linux

| VMware

| 2011

| vSphere 5.0+

| University of Szeged

| 2011

| NetBSD 6.0+

| Microsoft

| 2012

| Windows Server 2012

| Samsung Electronics

| 2012

| Linux

| Kent Overstreet

| 2015

| Linux

| Apple

| 2016

| macOS High Sierra, iOS 10.3

| UC, San Diego

| 2017

| Linux

| Red Hat, University of California, Santa Cruz

|2017

|Linux

| Matthew Dillon{{cite web|url=http://bxr.su/d/sys/vfs/hammer2/DESIGN|title=hammer2/DESIGN|author=Matthew Dillon|author-link=Matthew Dillon (computer scientist)|website=BSD Cross Reference|publisher=DragonFly BSD|date=2018-12-09|access-date=2019-03-06}}

| 2017

| DragonFly BSD 5.0

|Huawei{{Cite news|url=https://www.xda-developers.com/huawei-erofs-linux-file-system-android/|title=Huawei announces the EROFS Linux file system intended for Android devices|date=June 1, 2018|work=XDA Developer}}

|2018

|Linux, Android

|Swiss Vault

|2022

|Linux / Unix

! File system

! {{verth|Stores file owner}}

! {{verth|POSIX
file permissions}}

! {{verth|Creation timestamps}}

! {{verth|Last access/
read timestamps}}

! {{verth|Last metadata change
timestamps}}

! {{verth|Last archive
timestamps}}

! {{verth|Access control lists}}

! {{verth|Security/
MAC labels}}

! {{verth|Extended attributes/
Alternate data streams/
forks}}

! {{verth|Metadata checksum/
ECC}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{dunno}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}{{efn |Implemented in later versions as an extension}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}} (date only)

| {{yes}}

| {{yes}}

| {{yes}} (FILDAE)

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}{{efn |name=fat-ctime |Some FAT implementations, such as in Linux, show file modification timestamp (mtime) in the metadata change timestamp (ctime) field. This timestamp is however, not updated on file metadata change.}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}{{efn |name=note-22 |Particular Installable File System drivers and operating systems may not support extended attributes on FAT12 and FAT16. The OS/2 and Windows NT filesystem drivers for FAT12 and FAT16 support extended attributes (using a "EA DATA. SF" pseudo-file to reserve the clusters allocated to them). Other filesystem drivers for other operating systems do not.}}

| {{no}}

| {{yes}}{{efn |name=note-14 |The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{dunno}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}{{efn |name=note-5 |NTFS access control lists can express any access policy possible using simple POSIX file permissions (and far more), but use of a POSIX-like interface is not supported without an add-on such as Services for UNIX or Cygwin.}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}{{efn |As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.{{cite web|url=https://docs.microsoft.com/en-us/windows/win32/secauthz/mandatory-integrity-control|title=Mandatory Integrity Control|website=Microsoft Docs|date=25 March 2021 |access-date=2022-08-14}}}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{dunno}}

| {{yes}}{{efn |Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{dunno}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-33 |Access-control lists and MAC labels are layered on top of extended attributes.}}

| {{yes}}{{efn |name=note-33}}

| {{no}}{{efn |name=note-32 |Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-33}}

| {{yes}}{{efn |name=note-33}}

| {{yes}}

| {{partial}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{dunno}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-23 |Some Installable File System drivers and operating systems may not support extended attributes, access control lists or security labels on these filesystems. Linux kernels prior to 2.6.x may either be missing support for these altogether or require a patch.}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}

| {{partial}}{{efn | Metadata is mostly checksummed,{{cite web | title=Ext4 Disk Layout | url=https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Checksums}} however Direct/indirect/triple-indirect block maps are not protected by checksums{{cite web | title=Ext4 Metadata Checksums | url=https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums#Metadata_Not_Being_Upgraded}} }}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}{{efn |name=note-35 |Creation time stored since June 2015, xfsprogs version 3.2.3}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}{{efn |name=note-23}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{no}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}{{efn |name=note-31 |The local time, time zone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.}}

| {{yes}}{{efn |name=note-31}}

| {{yes}}

| {{yes}}{{efn |name=note-31}}

| {{yes}}

| {{dunno}}

| {{yes}}{{efn |name=note-19 |Novell calls this feature "multiple data streams". Published specifications say that NWFS allows for 16 attributes and 10 data streams, and NSS allows for unlimited quantities of both.}}{{efn |name=note-29 |Some file and directory metadata is stored on the NetWare server irrespective of whether Directory Services is installed or not, like date/time of creation, file size, purge status, etc; and some file and directory metadata is stored in NDS/eDirectory, like file/object permissions, ownership, etc.}}

| {{no}}

| {{yes}}

| {{dunno}}

| {{yes}}{{efn |name=note-31}}

| {{yes}}{{efn |name=note-31}}

| {{yes}}

| {{yes}}{{efn |name=note-31}}

| {{yes}}

| {{dunno}}

| {{yes}}{{efn |name=note-19}}{{efn |name=note-29}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{dunno}}

| {{dunno}}

| {{yes}}

| {{yes}}

| {{dunno}}

| {{yes}}{{efn |name=note-17 |Record Management Services (RMS) attributes include record type and size, among many others.}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{dunno}}

| {{yes}}{{efn |name=note-23}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}{{efn |name=note-61 |File permission in 9P are a variation of the traditional Unix permissions with some minor changes, e.g. the suid bit is replaced by a new 'exclusive access' bit.}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}{{efn |name=note-69 |Supported on FreeBSD and Linux implementations, support may not be available on all operating systems.}}

| {{yes}}{{efn |name=note-60 |Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS.}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}{{efn|Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.}}

| {{yes}}

| {{no}}

| {{no}}{{efn|libburnia can back up and restore ACLs with file system creation and extraction programs, but no kernel support exists.}}

| {{no}}{{efn|name=note-78|libburnia can back up and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.}}

| {{no}}{{efn|name=note-78}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}

| {{no}}

| {{no}}

| {{yes}}

| {{yes}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{dunno}}

| {{no}}

| {{yes}}

| {{yes}}

| {{yes}}

| {{yes}}

! File system

! {{verth|va=top|Stores file owner}}

! {{verth|va=top|POSIX
file permissions}}

! {{verth|va=top|Creation timestamps}}

! {{verth|va=top|Last access/
read timestamps}}

! {{verth|va=top|Last metadata change
timestamps}}

! {{verth|va=top|Last archive
timestamps}}

! {{verth|va=top|Access control lists}}

! {{verth|va=top|Security/
MAC labels}}

! {{verth|va=top|Extended attributes/
Alternate data streams/
forks}}

! {{verth|va=top|Metadata checksum/
ECC}}

! File system

!Sparse files

!Block suballocation

! Tail packing

! Extents

! Variable file block size{{efn |name=note-41 |Variable block size refers to systems which support different block sizes on a per-file basis. (This is similar to extents but a slightly different implementational choice.) The current implementation in UFS2 is read-only.}}

! Allocate-on-flush

! Copy on write

! Trim support

! File system

!Sparse files

!Block suballocation

! Tail packing

! Extents

! Variable file block size{{efn |name=note-41}}

! Allocate-on-flush

! Copy on write

! Trim support

! File system

! DOS

! Linux

! macOS

! Windows 9x (historic)

! Windows (current)

! Classic
Mac OS

! FreeBSD

! OS/2

! BeOS

! Minix

! Solaris

! z/OS

! Android{{cite tech report |type=Documentation |title=Android Kernel File System Support |publisher=Android Open Source Project |access-date=2023-01-11 |url=https://source.android.com/docs/core/architecture/android-kernel-file-system-support}}

! File system

! DOS

! Linux

! macOS

! Windows 9x (historic)

! Windows (current)

! Classic
Mac OS

! FreeBSD

! OS/2

! BeOS

! Minix

! Solaris

! z/OS

! Android

! File system

! Maximum filename length

! Allowable characters in directory entries{{efn |name=note-25 |These are the restrictions imposed by the on-disk directory entry structures themselves. Particular Installable File System drivers may place restrictions of their own on file and directory names; operating systems may also place restrictions of their own, across all filesystems. DOS, Windows, and OS/2 allow only the following characters from the current 8-bit OEM codepage in SFNs: A-Z, 0-9, characters ! # $ % & ' ( ) - @ ^ _ ` { } ~, as well as 0x80-0xFF and 0x20 (SPACE). Specifically, lowercase letters a-z, characters " * / : < > ? \ | + , . ; = [ ], control codes 0x00-0x1F, 0x7F and in some cases also 0xE5 are not allowed.) In LFNs, any UCS-2 Unicode except \ / : ? * " > < | and NUL are allowed in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.}}

! Maximum pathname length

! Maximum file size

! Maximum volume size{{efn |name=note-4 |For filesystems that have variable allocation unit (block/cluster) sizes, a range of size are given, indicating the maximum volume sizes for the minimum and the maximum possible allocation unit sizes of the filesystem (e.g. 512 bytes and 128 KiB (131.0 KB) for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and operating systems do not support cluster sizes larger than 32 KiB (32.76 KB)).}}

! Max number of files

| 255 characters

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="17592186044416" | 16 TiB (17.59 TB)

| data-sort-type="number" data-sort-value="17592186044416" | 16 TiB (17.59 TB)

| {{dunno}}

| 255 UTF-8 characters

| Unicode 9.0 encoded in UTF-8{{Cite web |title=Frequently Asked Questions |url=https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html}}

| {{dunno}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 8 EiB (9.223 EB)

| data-sort-type="number" data-sort-value="0" {{dunno}}

|2⁶³ {{Cite web |title=Volume Format Comparison |url=https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/VolumeFormatComparison/VolumeFormatComparison.html}}

| 255 bytes

| Any byte except '/' and NUL

| No limit defined

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

|2⁶⁴

|255 bytes

|Any byte except NUL{{efn |name=note-26}}

|No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="279172874240" | 12,288 bytes to 260 GiB (279.1 GB){{efn |name=note-3 |Varies wildly according to block size and fragmentation of block allocation groups.}}

| data-sort-type="number" data-sort-value="2305843009213693952" | 256 PiB (288.2 PB) to 2 EiB (2.305 EB)

| Unlimited

| 255 characters

| any byte, except null, "/"

| No limit defined

| Max. 2⁶⁴ bytes, 1 TiB (1.099 TB) by default {{cite web |title=CephFS Maximum File Sizes and Performance |url=https://docs.ceph.com/en/mimic/cephfs/administration/}}

| Not limited

| Not limited, default is 100,000 files per directory {{cite web |title=CephFS Directory Fragmentation |url=https://docs.ceph.com/en/latest/cephfs/dirfrags/}}

| 255 bytes

| Any byte except '/' and NUL

| No limit defined

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

|2⁶⁴

| 16 bytes

| Any byte except NUL

| 0 (no directory hierarchy)

| data-sort-type="number" data-sort-value="16777216" | 16 MiB (16.77 MB)

| data-sort-type="number" data-sort-value="16777216" | 16 MiB (16.77 MB)

| {{dunno}}

| 8.3

| ASCII except for < > . , ; : = ? * [ ]

| No directory hierarchy (but accessibility of files depends on user areas via USER command since CP/M 2.2)

| data-sort-type="number" data-sort-value="0" | 32 MiB (33.55 MB)

| data-sort-type="number" data-sort-value="0" | 512 MiB (536.8 MB)

| {{dunno}}

| 6.3

| A–Z, 0–9

| DTxN:FILNAM.EXT = 15

| data-sort-type="number" data-sort-value="369280" | 369,280 bytes
(577{{times}}640)

| data-sort-type="number" data-sort-value="369280" | 369,920 bytes
(578{{times}}640)

| {{dunno}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}} at least 131,072 bytes

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 16 bytes

| {{dunno}}

| No directory hierarchy

| data-sort-type="number" data-sort-value="65536" | 64 KiB (65.53 KB)

| data-sort-type="number" data-sort-value="800000" | Not limited. Approx. 800 KiB (819.2 KB) (one side) for 90 min cassette

| {{dunno}}

| 255 bytes

| Any byte except NUL, /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="1152921504606846976" | 1 EiB (1.152 EB)

| 2⁶⁴

| 255 UTF-16 characters

| Unicode except for control codes 0x0000 - 0x001F or " * / : < > ? \ | {{cite web | url=https://www.ntfs.com/exfat-filename-dentry.htm | title=ExFAT: File Name Directory Entry }}

| 32,760 characters with each path component no more than 255 characters{{cite web |date=2021-01-07 |title=File System Functionality Comparison |url=https://docs.microsoft.com/en-us/windows/win32/fileio/filesystem-functionality-comparison?redirectedfrom=MSDN#limits |access-date=2022-08-14 |website=Microsoft Docs |publisher=Microsoft}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="75557863725914323419136" | 64 ZiB (75.55 ZB) (2⁷⁶ bytes)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2147483648" | 2 GiB (2.147 GB)

| data-sort-type="number" data-sort-value="2147483648" | 2 GiB (2.147 GB)

| {{dunno}}

| 255 bytes

| Any byte except NUL, /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2199023255552" | 16 GiB (17.17 GB) to 2 TiB (2.199 TB){{efn |name=note-4}}

| data-sort-type="number" data-sort-value="35184372088832" | 2 TiB (2.199 TB) to 32 TiB (35.18 TB)

| {{dunno}}

| 255 bytes

| Any byte except NUL, /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2199023255552" | 16 GiB (17.17 GB) to 2 TiB (2.199 TB){{efn |name=note-4}}

| data-sort-type="number" data-sort-value="35184372088832" | 2 TiB (2.199 TB) to 32 TiB (35.18 TB)

| {{dunno}}

| 255 bytes{{cite web |author=Vimal A.R |date=16 July 2016 |title=Max file-name length in an EXT4 file system. |url=https://arvimal.blog/2016/07/21/max-file-name-length-in-an-ext4-file-system/ |archive-url=https://web.archive.org/web/20210228121426/https://arvimal.blog/2016/07/21/max-file-name-length-in-an-ext4-file-system/ |archive-date=28 February 2021 |url-status=dead |website=arvimal.blog}}

| Any byte except NUL, /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="17592186044416" | 16 GiB (17.17 GB) to 16 TiB (17.59 TB){{efn |name=note-4}}{{cite web |date=9 June 2008 |title=Interviews/EricSandeen |url=http://fedoraproject.org/wiki/Interviews/EricSandeen |website=Fedora Project Wiki}}

| data-sort-type="number" data-sort-value="1152921504606846976" | 1 EiB (1.152 EB)

|2³² (static inode limit specified at creation)

| 255 bytes

| Any byte except NUL, /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="4329690886144" | 4,228,213,756 KiB (4.329 TB)

| data-sort-type="number" data-sort-value="17592186044416" | 16 TiB (17.59 TB)

| {{dunno}}

| 6.3 (binary files) / 9 characters (ASCII files)

| ASCII (0x00 and 0xFF not allowed in first character)

| No directory hierarchy

| data-sort-type="number" data-sort-value="0" {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 8.3 (255 UCS-2 characters with LFN){{efn |name=note-24 |Depends on whether the FAT12, FAT16, and FAT32 implementation has support for LFNs. Where it does not, as in OS/2, DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 8.3 format of 8-bit OEM characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also must not contain lowercase letters. A few special device names (CON, NUL, AUX, PRN, LPT1, COM1, etc.) should be avoided, as some operating systems (notably DOS, OS/2 and Windows) reserve them.}}

| SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | {{efn |name=note-25}}{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="33554432" | 32 MiB (33.55 MB) (4 GiB (4.294 GB)){{efn |name="note-fsize"|On-disk structures would support up to 4 GiB (4.294 GB), but practical file size is limited by volume size.}}

| data-sort-type="number" data-sort-value="33554432" | 1 MiB (1.048 MB) to 32 MiB (33.55 MB)

| {{dunno}}

| 8.3 (255 UCS-2 characters with LFN){{efn |name=note-24}}

| SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | {{efn |name=note-25}}{{efn |name=note-24}}{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2147483648" | 2 (4) GiB{{efn |name="note-fsize"}} (2.147 GB)

| data-sort-type="number" data-sort-value="2147483648" | 16 MiB (16.77 MB) to 2 (4) GiB (2.147 GB)

| {{dunno}}

| 8.3 (255 UCS-2 characters with LFN){{efn |name=note-24}}

| SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | {{efn |name=note-25}}{{efn |name=note-24}}{{efn |name=note-26}}

| 32,760 characters with each path component no more than 255 characters

| data-sort-type="number" data-sort-value="4294967295" | 4 GiB (4.294 GB)

| data-sort-type="number" data-sort-value="17592186044415" | 512 MiB (536.8 MB) to 16 TiB (17.59 TB){{efn |While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GiB (34.35 GB). This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use FDISK from a Windows ME Emergency Boot Disk to avoid.{{cite web |title= Limitations of the FAT32 File System in Windows XP |publisher=Microsoft |url=http://support.microsoft.com/kb/314463 |archive-url=https://web.archive.org/web/20140330033436/http://support.microsoft.com/kb/314463 |archive-date=2014-03-30 |url-status=dead}}}}

| {{dunno}}

| 42 bytes{{efn |name=note-24}}

| ASCII.

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2147483648" | 2 GiB (2.147 GB)

| data-sort-type="number" data-sort-value="2147483648" | 16 MiB (16.77 MB) to 2 GiB (2.147 GB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="4294967296" | 4 GiB (4.294 GB)

| data-sort-type="number" data-sort-value="281474976710656" | 256 TiB (281.4 TB)

| {{dunno}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 8 bytes

| A–Z, 0–9. Period was directory separator

| {{dunno}} No limit defined (workaround for OS limit)

| data-sort-type="number" data-sort-value="0" {{dunno}} at least 131,072 bytes

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 8.3

| A-Z, a-z, 0-9 ! @ # $ % ^ & ( ) + - = ~ ` ; ' " , < > | [ ] ( ) _{{cite web |title=GEMDOS Overview |url=http://cd.textfiles.com/ataricompendium/BOOK/HTML/CHAP2.HTM}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 100 TiB (109.95 TB) to 8 EiB (9.223 EB){{efn |name=note-83 |Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). {{cite web|url=https://access.redhat.com/solutions/1532|title=What are the file and file system size limitations for Red Hat Enterprise Linux?|website=Red Hat|date=2023-03-21}}}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 100 TiB (109.95 TB) to 8 EiB (9.223 EB){{efn |name=note-84 |Depends on CPU arch. For 32bit kernels the max is 16 TiB (17.59 TB). {{cite web|url=https://access.redhat.com/solutions/1532|title=What are the file and file system size limitations for Red Hat Enterprise Linux?|website=Red Hat|date=2023-03-21}}}}

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 2 TiB (2.199 TB) to 8 EiB (9.223 EB){{efn |name=note-63 |Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB (2.199 TB). For 32-bit 2.6 kernels it is 16 TiB (17.59 TB). For 64-bit 2.6 kernels it is 8 EiB (9.223 EB).}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 2 TiB (2.199 TB) to 8 EiB (9.223 EB){{efn |name=note-63}}

| {{dunno}}

| 255 UTF-8 codepoints

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="0" | 9 EiB (10.37 EB)

| data-sort-type="number" data-sort-value="633825300114114700748351602688" | 524,288 YiB (2⁹⁹ bytes)

| {{dunno}}

| 1023 bytes{{cite web |author=Matthew Dillon |title=HAMMER2 Design Document |url=http://apollo.backplane.com/DFlyMisc/hammer2.txt |quote=we can allow filenames up to 1023 bytes long}}

| Any byte except NUL{{efn |name=note-26}}

| {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| data-sort-type="number" data-sort-value="1152921504606846976" | 1 EiB (1.152 EB){{cite web |author=Matthew Dillon |date=June 21, 2008 |title=The HAMMER Filesystem |url=http://www.dragonflybsd.org/hammer/hammer.pdf}}

| {{dunno}}

| 31 bytes

| Any byte except :

| Unlimited

| data-sort-type="number" data-sort-value="2147483648" | 2 GiB (2.147 GB)

| data-sort-type="number" data-sort-value="2199023255552" | 2 TiB (2.199 TB)

| {{dunno}}

| 255 UTF-16 characters{{efn |name=note-1 |The "classic" Mac OS provides two sets of functions to retrieve file names from an HFS Plus volume, one of them returning the full Unicode names, the other shortened names fitting in the older 31 byte limit to accommodate older applications.}}

| Any valid Unicode{{efn |name=note-26}}{{efn |name=note-2 |HFS Plus mandates support for an escape sequence to allow arbitrary Unicode. Users of older software might see the escape sequences instead of the desired characters.}}

| Unlimited

| data-sort-type="number" data-sort-value="9223372036854775808" | slightly less than 8 EiB (9.223 EB)

| data-sort-type="number" data-sort-value="9223372036854775808" | slightly less than 8 EiB (9.223 EB){{cite web |date=July 26, 2016 |title=Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits |url=https://support.apple.com/en-us/HT201711 |url-status=dead |archive-url=https://web.archive.org/web/20190408213105/https://support.apple.com/en-us/HT201711 |archive-date=2019-04-08 |website=support.apple.com}}{{cite web |date=February 20, 2012 |title=Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits |url=https://support.apple.com/kb/TA21924 |website=support.apple.com}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-27 |The "." and ".." directory entries in HPFS that are seen by applications programs are a partial fiction created by the Installable File System drivers. The on-disk data structure for a directory does not contain entries by those names, but instead contains a special "start" entry. Whilst on-disk directory entries by those names are not physically prohibited, they cannot be created in normal operation, and a directory containing such entries is corrupt.}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2147483648" | 2 GiB (2.147 GB)

| data-sort-type="number" data-sort-value="2199023255552" | 2 TiB (2.199 TB){{efn |name=note-13 |This is the limit of the on-disk structures. The HPFS Installable File System driver for OS/2 uses the top 5 bits of the volume sector number for its own use, limiting the volume size that it can handle to 64 GiB (68.71 GB).}}

| {{dunno}}

| 8.8

| {{dunno}}

| {{dunno}}

| data-sort-type="number" data-sort-value="0" | Non-hierarchical{{cite web |date=2015-06-03 |title=SFS file system |url=https://www.ibm.com/docs/en/cobol-aix/5.1?topic=systems-sfs-file-system |url-status=live |archive-url=https://web.archive.org/web/20220913063022/https://www.ibm.com/docs/en/cobol-aix/5.1?topic=systems-sfs-file-system |archive-date=2022-09-13 |access-date=2022-09-13 |website=www.ibm.com}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| Level 1: 8.3,
Level 2 & 3: ~ 180

| Depends on Level{{efn |ISO 9660#Restrictions}}

| ~ 180 bytes?

| data-sort-type="number" data-sort-value="8796093022208" | 4 GiB (4.294 GB) (Level 1 & 2) to 8 TiB (8.796 TB) (Level 3){{efn |Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB (4.294 GB) in size. See ISO 9660#The 2 GiB (2.147 GB) (or 4 GiB (4.294 GB) depending on implementation) file size limit}}

| data-sort-type="number" data-sort-value="8796093022208" | 8 TiB (8.796 TB){{efn |Assuming the typical 2048 Byte sector size. The volume size is specified as a 32 bit value identifying the number of sectors on the volume.}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 255 bytes

| Any Unicode except NUL

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="4503599627370496" | 4 PiB (4.503 PB)

| data-sort-type="number" data-sort-value="36028797018963968" | 32 PiB (36.02 PB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 8 EiB (9.223 EB)

| data-sort-type="number" data-sort-value="4503599627370496" | 512 TiB (562.9 TB) to 4 PiB (4.503 PB)

| {{dunno}}

| 64 characters

| All UCS-2 code except *, /, \, :, ;, and ?{{cite web |date=22 May 1995 |title=Joliet Specification |url=http://bmrc.berkeley.edu/people/chaffee/jolspec.html |archive-url=https://web.archive.org/web/20090414104421/http://bmrc.berkeley.edu/people/chaffee/jolspec.html |archive-date=14 April 2009 |url-status=dead}}

| {{dunno}}

| data-sort-type="number" data-sort-value="8796093022208" | same as ISO 9660:1988

| data-sort-type="number" data-sort-value="8796093022208" | same as ISO 9660:1988

| {{dunno}}

| 6.3

| A–Z, 0–9

| DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67

| data-sort-type="number" data-sort-value="206158430208" | 34,359,738,368 words (2³⁵); 206,158,430,208 SIXBIT bytes

| data-sort-type="number" data-sort-value="11392000000" | Approx 12 GiB (12.88 GB) (64{{times}}178 MiB (186.6 MB))

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB) on ZFS

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| {{dunno}}

| 255 bytes

| Any byte except :

| No path (flat filesystem)

| data-sort-type="number" data-sort-value="268435456" | 256 MiB (268.4 MB)

| data-sort-type="number" data-sort-value="268435456" | 256 MiB (268.4 MB)

| {{dunno}}

| 14 bytes

| {{dunno}}

| {{dunno}}

| data-sort-type="number" data-sort-value="16777216" | 16 MiB (16.77 MB)

| data-sort-type="number" data-sort-value="33554432" | 32 MiB (33.55 MB)

| {{dunno}}

| 14 or 30 bytes, set at filesystem creation time

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="268966912" | 256.5 MiB (268.9 MB) {{efn |name=note-file-size-vs-filesystem-size |Sparse files can be larger than the file system size, even though they can't contain more data.}}

| data-sort-type="number" data-sort-value="67108864" | 64 MiB (67.10 MB)

| {{dunno}}

| 14 or 30 bytes, set at filesystem creation time

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2147483647" | 2 GiB (2.147 GB) {{efn |name=note-file-size-vs-filesystem-size}}

| data-sort-type="number" data-sort-value="1073741824" | 1 GiB (1.073 GB)

| {{dunno}}

| 60 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="2147483647" | 2 GiB (2.147 GB)

| data-sort-type="number" data-sort-value="4294967296" | 4 GiB (4.294 GB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 8 EiB (9.223 EB)

| data-sort-type="number" data-sort-value="9223372036854775808" | 8 EiB (9.223 EB)

| {{dunno}}

| 255 bytes

| Any byte except NUL, /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| {{dunno}}

| 256 characters

| Depends on namespace used{{efn |name=note-28 |NSS allows files to have multiple names, in separate namespaces.}}

| Only limited by client

| data-sort-type="number" data-sort-value="8796093022208" | 8 TiB (8.796 TB)

| data-sort-type="number" data-sort-value="8796093022208" | 8 TiB (8.796 TB)

| {{dunno}}

| 255 characters

| In Win32 namespace: any UTF-16 code unit (case-insensitive) except /\:*"?<>| as well as NUL

In POSIX namespace: any UTF-16 code unit (case-sensitive) except / as well as NUL{{cite web |last1=Russon |first1=Richard |last2=Fledel |first2=Yuval |title=NTFS Documentation |url=http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf}}

| 32,767 characters with each path component (directory or filename) up to 255 characters long{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 TiB (17.59 TB) to 8 PiB (9.007 PB){{efn |name=note-55 |This is the limit of the on-disk structures. The NTFS driver for Windows NT limits the volume size that it can handle to 256 TiB (281.4 TB) and the file size to 16 TiB (17.59 TB) respectively; in Windows 10 version 1709, the limit is 8 PiB (9.007 PB) when using 2 MiB (2.097 MB) cluster size.}}{{Cite web |date=2022-05-26 |title=NTFS overview |url=https://docs.microsoft.com/en-us/windows-server/storage/file-server/ntfs-overview |url-status=live |archive-url=https://web.archive.org/web/20220526213037/https://docs.microsoft.com/en-us/windows-server/storage/file-server/ntfs-overview |archive-date=2022-05-26 |access-date=2022-06-05 |website=Microsoft Docs}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 TiB (17.59 TB) to 8 PiB (9.007 PB){{efn |name=note-55}}

| 2³²

| 80 bytes{{efn |name=note-52 |Some namespaces had lower name length limits. "LONG" had an 80-byte limit, "NWFS" 80 bytes, "NFS" 40 bytes and "DOS" imposed 8.3 filename.}}

| Depends on namespace used{{efn |name=note-28}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="4294967296" | 4 GiB (4.294 GB)

| data-sort-type="number" data-sort-value="1099511627776" | 1 TiB (1.099 TB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="8796093022208" | 8 TiB (8.796 TB)

| data-sort-type="number" data-sort-value="8796093022208" | 8 TiB (8.796 TB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="4503599627370496" | 4 PiB (4.503 PB)

| data-sort-type="number" data-sort-value="4503599627370496" | 4 PiB (4.503 PB)

| {{dunno}}

| 236 bytes{{efn |name=note-15 |Maximum combined filename/filetype length is 236 bytes; each component has an individual maximum length of 255 bytes.}}

| {{dunno}}

| 4,096 bytes{{efn |name=note-16 |Maximum pathname length is 4,096 bytes, but quoted limits on individual components add up to 1,664 bytes.}}

| data-sort-type="number" data-sort-value="1099511627776" | 1 TiB (1.099 TB)

| data-sort-type="number" data-sort-value="1099511627776" | 1 TiB (1.099 TB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB){{efn |name=note-72 |QFS allows files to exceed the size of disk when used with its integrated HSM, as only part of the file need reside on disk at any one time.}}

| data-sort-type="number" data-sort-value="4503599627370496" | 4 PiB (4.503 PB){{efn |name=note-72}}

| {{dunno}}

| 255 UTF-16 characters{{cite web |author=Steven Sinofsky |author-link=Steven Sinofsky |date=January 16, 2012 |title=Building the next generation file system for Windows: ReFS |url=https://blogs.msdn.microsoft.com/b8/2012/01/16/building-the-next-generation-file-system-for-windows-refs/}}

| In Win32 namespace: any UTF-16 code unit (case-insensitive) except /\:*"?<>| as well as NUL

In POSIX namespace: any UTF-16 code unit (case-sensitive) except / as well as NUL{{Cite web |last=Amigo |date=2015-04-02 |title=Invalid Characters in File Names |url=https://amigotechnotes.wordpress.com/2015/04/02/invalid-characters-in-file-names/ |access-date=2020-10-20 |website=Amigo's Technical Notes |language=en}}

| 32,767 characters with each path component (directory or filename) up to 255 characters long

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB){{Cite web |title=Resilient File System (ReFS) overview |url=https://docs.microsoft.com/en-us/windows-server/storage/refs/refs-overview |access-date=2017-11-07 |website=Microsoft Docs |language=en-us}}

| data-sort-type="number" data-sort-value="1208925819614629174706176" | 1 YiB (1.208 YB)

| {{dunno}}

| 4,032 bytes/255 characters

| Any byte except NUL or '/'{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="8796093022208" | 8 TiB (8.796 TB){{efn |ReiserFS has a theoretical maximum file size of 1 EiB (1.152 EB), but "page cache limits this to 8 Ti on architectures with 32 bit int"{{cite web |title=FAQ |date=15 October 2003 |website=namesys |url=http://www.namesys.com/faq.html#reiserfsspecs |archive-url=https://web.archive.org/web/20060719110322/http://www.namesys.com/faq.html#reiserfsspecs |archive-date=19 July 2006}}}} (v3.6), 4 GiB (4.294 GB) (v3.5)

| data-sort-type="number" data-sort-value="17592186044416" | 16 TiB (17.59 TB)

| {{dunno}}

| 3,976 bytes

| Any byte except / and NUL

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="8796093022208" | 8 TiB (8.796 TB) on x86

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 255 bytes

| Any byte except NUL or /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="8796093022208" | same as ISO 9660:1988

| data-sort-type="number" data-sort-value="8796093022208" | same as ISO 9660:1988

| {{dunno}}

| 6.3

| A–Z, 0–9, $

| 0 (no directory hierarchy)

| data-sort-type="number" data-sort-value="33554432" | 33,554,432 bytes
(65536{{times}}512)

| data-sort-type="number" data-sort-value="33554432" | 33,554,432 bytes

| {{dunno}}

| 256 bytes

| {{dunno}}

| No limit defined

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| {{dunno}}

| 255 bytes

| Any Unicode except NUL

| 1,023 bytes{{efn |name=note-43 |This restriction might be lifted in newer versions.}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="17592186044415" | 512 MiB (536.8 MB) to 16 TiB (17.59 TB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="281474976710656" | 16 GiB (17.17 GB) to 256 TiB (281.4 TB)

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| Subdirectory per directory is 32,767{{cite web |title=Maximum Number of UFS Subdirectories |url=https://docs.oracle.com/cd/E19120-01/open.solaris/819-2723/fsfilesysappx-5/index.html |access-date=2019-02-12 |publisher=Oracle}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="36028797018963968" | 512 GiB (549.7 GB) to 32 PiB (36.02 PB)

| data-sort-type="number" data-sort-value="649037107316853896642560" | 512 ZiB (604.4 ZB){{cite web |title=Frequently Asked Questions for FreeBSD 9.X and 10.X |url=https://www.freebsd.org/doc/faq/book.html |access-date=2016-03-20 |publisher=FreeBSD Documentation Project |quote=If there was not a fsck(8) memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32 KiB (32.76 KB) => 16 Exa * 32 KiB (32.76 KB) => 512 ZettaBytes.}} (2⁷⁹ bytes)

| Subdirectory per directory is 32,767

| No limit defined (depends on client)

| {{dunno}}

| No limit defined (depends on client)

| Available cache space at time of write (depends on platform)

| No limit defined

| No limit defined

| configurable (1024 default)

| Any byte except NUL

| No limit defined

| No limit defined

| No limit defined

| No limit defined

| 14 bytes

| Any byte except NUL and /{{efn |name=note-26 |In these filesystems the directory entries named "." and ".." have special status. Directory entries with these names are not prohibited, and indeed exist as normal directory entries in the on-disk data structures. However, they are mandatory directory entries, with mandatory values, that are automatically created in each directory when it is created; and directories without them are considered corrupt.}}

| No limit defined{{efn |name=note-12 |The on-disk structures have no inherent limit. Particular Installable File System drivers and operating systems may impose limits of their own, however. Limited by its Current Directory Structure (CDS), DOS does not support more than 32 directory levels (except for DR DOS 3.31-6.0) or full pathnames longer than 66 bytes for FAT, or 255 characters for LFNs. Windows NT does not support full pathnames longer than 32,767 bytes for NTFS. Older POSIX APIs which rely on the PATH_MAX constant have a limit of 4,096 bytes on Linux but this can be worked around. Linux itself has no hard path length limits.{{cite web|url=https://eklitzke.org/path-max-is-tricky|title=PATH_MAX Is Tricky|website=Evan Klitzke’s web log}}{{cite web|url=https://insanecoding.blogspot.com/2007/11/pathmax-simply-isnt.html|title=PATH_MAX simply isn't|website=Insane Coding|date=2007-11-03}}}}

| data-sort-type="number" data-sort-value="16777216" | 16 MiB (16.77 MB){{efn |name=note-57 |The file size in the inode is 1 8-bit byte followed by 1 16-bit word, for 24 bits. The actual maximum was 8,847,360 bytes, with 7 singly-indirect blocks and 1 doubly-indirect block; PWB/UNIX 1.0's variant had 8 singly-indirect blocks, making the maximum 524,288 bytes or half a MB.}}

| data-sort-type="number" data-sort-value="33554432" | 32 MiB (33.55 MB)

| {{dunno}}

| 14 bytes

| Any byte except NUL or /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="1073741824" | 1 GiB (1.073 GB){{efn |name=note-58 |The actual maximum was 1,082,201,088 bytes, with 10 direct blocks, 1 singly-indirect block, 1 doubly-indirect block, and 1 triply-indirect block. The 4.0BSD and 4.1BSD versions, and the System V version, used 1,024-byte blocks rather than 512-byte blocks, making the maximum 4,311,812,608 bytes or approximately 4 GiB (4.294 GB).}}

| data-sort-type="number" data-sort-value="2199023255552" | 2 TiB (2.199 TB)

| {{dunno}}

| 128

| Any byte except NUL or /{{efn |name=note-26}}

| 2,048

| data-sort-type="number" data-sort-value="4398046511104" | 4 TiB (4.398 TB){{efn |name=note-74 |Maximum file size on a VMFS volume depends on the block size for that VMFS volume. The figures here are obtained by using the maximum block size.}}

| data-sort-type="number" data-sort-value="70368744177664" | 64 TiB (70.36 TB)

| {{dunno}}

| 128

| Any byte except NUL or /{{efn |name=note-26}}

| 2,048

| data-sort-type="number" data-sort-value="2199023255552" | 2 TiB (2.199 TB){{efn |name=note-74}}

| data-sort-type="number" data-sort-value="70368744177664" | 64 TiB (70.36 TB)

| {{dunno}}

| 255 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="0" {{dunno}}

| {{dunno}}

| 255 bytes{{efn |Note that the filename can be much longer XFS#Extended attributes}}

| Any byte except NUL or /{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 8 EiB (9.223 EB){{efn |name=note-9 |XFS has a limitation under Linux 2.4 of 64 TiB (70.36 TB) file size, but Linux 2.4 only supports a maximum block size of 2 TiB (2.199 TB). This limitation is not present under IRIX.}}

| data-sort-type="number" data-sort-value="9223372036854775808" | 8 EiB (9.223 EB){{efn |name=note-9}}

| 2⁶⁴

| 248 bytes

| Any byte except NUL{{efn |name=note-26}}

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="67108864" | 64 MiB (67.10 MB)

| data-sort-type="number" data-sort-value="2147483648" | 2 GiB (2.147 GB)

| {{dunno}}

| 1023 bytes

| Any Unicode except NUL

| No limit defined{{efn |name=note-12}}

| data-sort-type="number" data-sort-value="18446744073709551616" | 16 EiB (18.44 EB)

| data-sort-type="number" data-sort-value="340282366920938463463374607431768211456" | 281,474,976,710,656 YiB (2¹²⁸ bytes)

|2¹²⁸

! File system

! Maximum filename length

! Allowable characters in directory entries{{efn |name=note-25}}

! Maximum pathname length

! Maximum file size

! Maximum volume size{{efn |name=note-4}}

! Max number of files