Download OneDrive for a Mac and pick what stays offline

Searching for the OneDrive download is usually the last step of a decision that has already been made somewhere else. A workplace standardised on Microsoft 365, or a new Mac arrived and the files are already in the cloud. The install itself takes a few minutes. The parts that cause trouble later are the ones nobody reads at install time: which macOS version is actually supported, how much of the disk the sync will claim, and which files will quietly refuse to go up.

All of those are documented, and some of the published numbers disagree with each other. Reading them before the first sync is considerably cheaper than discovering them after 200 GB has landed in the home folder.

Two places to get it, and two different stated requirements

There are two supported routes. Microsoft's own setup instructions direct people to the download page on microsoft.com, and there is a separate Mac App Store listing published by Microsoft Corporation. Both are current. They do not state the same system requirement.

	Mac App Store listing	Microsoft system requirements page
Minimum macOS stated	14.4	15.8 or newer
Version shown	26.163.0823, dated 16 September 2026	not stated per platform
Download size	140.5 MB	not stated
Processor	not stated	Apple silicon or Intel Mac
File system	not stated	APFS, case insensitive
Price	free, with in-app purchases	not stated

That gap of more than a full major release is the single most useful thing to know before starting. A Mac running macOS 14 will be offered the app by the App Store, because 14.4 is what the listing declares, while Microsoft's published requirements say the sync app needs macOS 15.8 or newer. Installing on an older release is therefore possible and unsupported at the same time, which is a bad position for anything holding work files. On a Mac that cannot move past macOS 14, the honest reading is that OneDrive syncing is out of support and the browser at onedrive.com is the safer route.

The same requirements page sets the rest of the floor: Apple silicon or an Intel Mac, 1 GB of RAM or more, a display of at least 1024 by 576, and high speed internet recommended. None of those exclude any Mac still in use. The file system line is the one that does, and it gets its own section below.

What the free tier actually covers

The App Store listing states the storage arrangement plainly: 5 GB of free cloud storage to start, or a Microsoft 365 subscription for 1 TB. The in-app purchases listed on that page are Microsoft 365 Personal at 99.99 US dollars, Microsoft 365 Family at 129.99 US dollars, and a second Microsoft 365 Personal entry at 72.99 US dollars. Those are the figures shown on the United States storefront and they change by country, so the price in the App Store on the machine in question is the one that applies.

Storage is not the only thing behind the subscription. Reading the listing's own footnotes, three of the features advertised on the page are marked as requiring a subscription: ransomware detection and recovery, password protected sharing links, and expiring sharing links. Version history and file encryption are described without that marker.

One item is worth singling out because it is a platform difference rather than a plan difference. Personal Vault, the protected folder inside OneDrive, carries its own footnote on the Mac listing: Mac users access and use Personal Vault by visiting onedrive.com in a browser. It is not a folder that appears in Finder. Anyone planning to keep scanned identity documents in a vault on a Mac should treat that as a web workflow from the start rather than a sync one.

Files On-Demand and folder selection are two different decisions

Space on a Mac is the usual reason people go looking for OneDrive settings a week after installing, and there are two separate mechanisms that both look like the answer.

Files On-Demand lets every file in the account appear locally while the contents stay in the cloud until opened. Microsoft describes it as a way to access all files without downloading all of them and consuming device storage. The account looks complete in Finder and the disk stays mostly empty.

Choosing which folders to sync is the older, coarser control, and it appears during setup. Microsoft's setup walkthrough describes a screen for selecting the folders to sync to the computer, and notes that the choice also reduces the bandwidth the sync process needs. Folders left unselected do not appear locally at all.

The difference matters when something needs to be available on a plane. Files On-Demand keeps everything visible and nothing guaranteed; folder selection keeps a chosen subset fully present and hides the rest. Most people want Files On-Demand for the bulk of the account and a deliberate always available choice for the two or three folders currently in use. Deciding that once is faster than reacting to a full disk later.

There is also a reassurance in the documentation that is easy to miss and worth knowing before experimenting: disabling or uninstalling OneDrive on a computer does not lose files or data.

The file system requirement that stops the install cold

The requirements page lists one file system for macOS: APFS, case insensitive. The restrictions and limitations page states the same thing from the other direction under its macOS heading, that a case sensitive formatted disk volume is not supported.

This is a real obstacle for a specific group of Mac users. A case sensitive APFS volume is a common choice for developers, because some build tools and repositories behave differently on a case insensitive file system. A Mac set up that way, or an external volume formatted that way for a project, cannot host the OneDrive folder. There is no setting that changes it, and converting a volume between the two variants means reformatting.

Checking is not obvious from Finder, which reports both variants as APFS. Disk Utility shows the specific format on the volume, and diskutil info prints it for a named volume in the terminal. Doing that before choosing the sync location saves an install that appears to work and then fails on the first pair of files whose names differ only in case.

Names and files that will not go up

A long list of restrictions applies to what can sync, and most of it exists because OneDrive and SharePoint share a naming model with Windows. The characters not allowed in file and folder names are the double quote, asterisk, colon, less than, greater than, question mark, forward slash, backslash and vertical bar. Leading and trailing spaces are not allowed either.

Two of those hit Mac files specifically. A colon is legal in a macOS filename and reserved in this list. And a trailing space is easy to create by accident when renaming in Finder. Microsoft's page notes that on a Mac a file or folder is renamed by selecting it and pressing return, which is the fix once the offending name is found.

The same page carries a dated note that changes the picture for Mac users: as of 28 January 2025, invalid characters are now supported on OneDrive for Mac. That is a genuine improvement and also a reason to be careful with older advice, since guidance written before that date describes stricter behaviour than the current app has.

Reserved names remain reserved regardless. The list includes .lock, CON, PRN, AUX, NUL, COM0 through COM9, LPT0 through LPT9, _vti_, desktop.ini, and any filename starting with ~$. The string _vti_ cannot appear anywhere in a name, not just at the start.

Three structural limits catch automated setups rather than hand filing. OneDrive does not support syncing through symbolic links or junction points, a network or mapped drive cannot be used as the sync location, and temporary TMP files are not synced. The symbolic link restriction is the one that breaks carefully arranged Mac folders, because a symlinked folder inside the OneDrive directory is a common way to pull a large project in without moving it.

Finally, .DS_Store on macOS is in the category of files used by the local computer that do not normally sync. If such files do get uploaded during a migration, the documented behaviour is that the sync app deletes the cloud copy and leaves the local one.

Size and volume limits worth checking in advance

The published maximum for an individual file is 250 GB, and the same figure applies to upload, download and sync, including files inside a zip archive. Microsoft's note is explicit that these are per file limits rather than total storage limits, and that anything larger than a few gigabytes is better handled by the sync app than by the website upload form.

Item counts matter more than most people expect. Microsoft recommends syncing no more than a total of 300,000 items across cloud storage, and warns that performance problems can appear above that number even when not everything is being synced. A public preview raising the figure to 1,000,000 items exists, and the requirements listed for it are Windows only, so it does not apply to a Mac. Separately, the OneDrive website copies a maximum of 2,500 files at a time.

Two smaller ceilings affect how the account looks rather than whether it works. Thumbnails are not generated for images larger than 100 MB, and PDF previews are not generated for files larger than 100 MB. A folder of large scans will therefore look empty of previews while syncing perfectly.

Sharing has its own ceiling that only shows up on big folders. When a folder is shared, the total number of sub items inside it and its sub folders is limited to 50,000, and the documented way around it is to move some items out to a folder outside the original or to share individual files instead. The supported limit for unique permissions on items in a list or library is also 50,000, with 5,000 given as the recommended general limit because changes above that number take noticeably longer. Outlook .PST files are a separate case: they are supported but synced less frequently than other file types in order to reduce network traffic, which makes a mailbox archive a poor candidate for a folder that needs to be current on two machines.

For anyone moving a large archive in, those numbers turn into a plan: count the items first, split anything over 250 GB, and expect the preview generation to stop being helpful at the top end. A file manager that reports folder item counts and sizes without opening each folder in turn shortens that audit considerably, and the Features page covers the kind of view that makes it a single pass instead of a hunt.

What to change first

Check the macOS version against the 15.8 figure on Microsoft's requirements page rather than the 14.4 figure in the App Store listing, then confirm the target volume is case insensitive APFS before choosing where the OneDrive folder lives. Those two checks prevent the two failures that are expensive to undo. If the sync folder is going to sit alongside local project folders that get driven from the terminal, keeping the file view and the shell in one place removes the window switching that cloud folders tend to multiply; Atriens is built around that, and the FAQ sets out what it does not try to replace.