File and Folder Naming Limits by Platform

Different platforms have different rules about what a file or folder name can contain. A name that saves without complaint in one place can still refuse to sync, break a link, or create duplicates somewhere else. This page covers the specific limits behind that behavior: what each platform allows, what it blocks, and where conflicts are most likely to happen.

If you arrived here because something stopped syncing or sharing and you are not sure why, the FAQ may be a faster starting point. If you want a practical naming standard you can adopt right away, start with the best-practices guide.

Check a file or folder name →

Windows

Windows is often the platform that causes trouble because many cloud tools and office workflows eventually sync back to a Windows computer.

Key limits

• Maximum path length: 260 characters by default
• Maximum filename length: 255 characters
• Characters that are not allowed: < > : " / \ | ? *
• Names that are not allowed: CON, PRN, AUX, NUL, COM1 through COM9, and LPT1 through LPT9. Windows reserves these names for internal use and will reject them as file or folder names.
• Uppercase and lowercase: treated as the same name, but the original casing is kept

What that means in practice

A filename can look fine and still fail if it contains one of the reserved characters, uses a reserved name like CON, or ends up buried in a folder structure that pushes the full path over 260 characters. Very large folders are also technically possible but hard to work in. Keeping folders under about 1,000 items is a practical target for ordinary office use.

---

SharePoint and OneDrive

SharePoint and OneDrive are Microsoft's cloud storage tools. They sit between browser-based storage and a synced folder on a Windows computer, which creates its own complications.

Key limits

• Maximum path length: 400 characters for the web address, but ~260 characters is the safer target once files are synced to a computer
• Maximum filename length: 255 characters
• Characters that are not allowed: ~ " # % & * : < > ? / \ { | }
• Trailing character issue: folder names cannot end with a space or a period when synced to Windows
• Scale note: performance degrades noticeably when a single library holds more than about 300,000 files
• File size limit: 250 GB per file

What that means in practice

A name may look fine in the browser and still cause trouble once it is synced to a Windows computer. The full path also grows quickly once account names, company names, and library names are added in front of the filename. If your organization uses Microsoft 365 heavily, treating 260 characters as the working path limit is safer than relying on the longer web address allowance.

---

macOS and iOS

Apple platforms are less restrictive in some ways, but they introduce complications in offices where Macs and Windows PCs share the same files.

Key limits

• Maximum path length: 1,024 characters
• Maximum filename length: 255 characters
• Characters that are not allowed: / and :
• Uppercase and lowercase: treated as the same name by default on macOS, but the original casing is kept; iOS users typically follow the rules of whatever cloud platform they are using

What that means in practice

Two issues come up most often in mixed environments.

Hidden extra files. When Macs write to shared drives or folders, they can create extra files that Mac users never see, including files named .DS_Store, ._filename, and __MACOSX inside ZIP archives. Windows and Linux users do see them, which can inflate folder counts, cause confusion, and make shared ZIP archives look messy.

Accented characters. Names containing letters like é or ñ may look correct on a Mac while causing duplicate-name or sync problems when those files are shared with Windows computers. Plain letters avoid the problem.

---

Linux and Android

Linux and Android allow more in filenames than Windows does, but that flexibility can create problems when files are shared with Windows computers or Microsoft 365.

Key limits

• Maximum path length: 4,096 characters
• Maximum filename length: 255 characters
• Characters that are not allowed: /
• Uppercase and lowercase: treated as different names (case-sensitive)

What that means in practice

Linux and Android will often allow names that fail immediately on Windows or SharePoint. A name that works on a Linux system can cause problems later if it relies on case differences (for example, treating Report.docx and report.docx as two different files) or contains characters that Windows rejects.

In most business environments, Android and iOS users access shared files through cloud-platform apps, so the cloud platform's rules are usually the effective constraint rather than the device's own rules.

---

Google Drive

Google Drive behaves differently because its web interface is not tied to the same filesystem rules as Windows or macOS.

Key limits

• Web interface: very few character restrictions
• Duplicate names: the web interface allows multiple files to share the same name in the same folder
• Desktop sync: when Google Drive is synced to a computer, the computer's own rules apply
• Uppercase and lowercase: treated as different names on the web; follows the computer's rules when synced

What that means in practice

Google Drive can look very flexible in a browser, but that can be misleading. A naming approach that works on the web can still create problems when files are synced to a Windows or Mac computer, or when duplicate names are hard to tell apart. If a Google Drive is being synced to computers, the computer's rules matter more than the browser's rules.

---

Dropbox

Dropbox is designed to keep files in sync across different devices and operating systems, which means it surfaces naming conflicts quickly when files do not meet the stricter platform rules.

Key limits

• Practical path target: stay under 260 characters
• Characters that are not allowed: / and \
• Characters to avoid: < > : " | ? * .
• Trailing character issue: names should not end with a space or period
• Uppercase and lowercase: treated as the same name

What that means in practice

Common problems include sync issues caused by characters that Windows rejects, conflicts when two files have names that differ only in uppercase and lowercase letters, and long paths that work on one device but fail when shared across platforms.

---

USB drives and older storage media

USB drives, SD cards, and other removable media often use an older storage format that adds another layer of restrictions.

Key limits

• Filename length: 255 characters
• Character restrictions: same as Windows
• Uppercase and lowercase: treated as the same name
• File size limit: 4 GB maximum per file
• Other limitation: shallower practical folder limits than modern computer storage

If files are ever copied to USB drives, SD cards, or older shared systems, conservative Windows-style naming is the safest habit. This applies especially to field data collection, media handoff workflows, and environments with older hardware.

---

Cross-platform patterns that cause the most trouble

The strictest platform sets the practical rule. If any part of the workflow touches Windows, SharePoint, OneDrive, or Dropbox, those restrictions apply to everyone in the workflow, regardless of what device they personally use.

Cloud tools follow computer rules when synced. Cloud platforms may look flexible in a browser, but once files are synced to a computer, that computer's rules apply. A name that works in a browser can still fail on someone's desktop.

Uppercase and lowercase mismatches. Windows treats Proposal.docx and proposal.docx as the same file. Linux treats them as two different files. Files moving between these environments can produce confusion, duplicates, or conflicts.

Deep folder structures create path problems faster than people expect. Most path-length failures are not caused by one very long filename. They happen because of deeply nested folders, repeated words across folder levels, and long account or company names added automatically by sync tools.

Mac extra files create visible clutter for Windows users. The hidden files that Macs create when writing to shared folders inflate folder counts, confuse Windows users, and make shared ZIP archives look messy.

---

Practical takeaways