OneDrive: Path is too long to sync

Hi, it's BlueByte. A file in your OneDrive folder shows a red X instead of the green sync check, and OneDrive tells you Path is too long to sync. Your file is fine and nothing is lost — OneDrive refuses to sync a file whose full path is longer than the limit it enforces. We'll walk through what that message means, the character limits that decide it, how to find which files are over, shorten them safely, and keep your folders under the line.

What "Path is too long to sync" means

OneDrive reports this as a per-item sync error: the file gets a red X in File Explorer and appears in the OneDrive Activity Center with a note like Path is 32 characters too long. The message tells you the overage, not a fixed threshold, and once you shorten enough it flips to Path is short enough to sync with a green check. The file itself is untouched — OneDrive is declining to upload it, not damaging it. That's why you can fix this without deleting anything.

The numbers that decide whether a path syncs — 400, 120, 520

Three limits from Microsoft's documentation govern this:

• The entire decoded file path, including the file name, can't exceed 400 characters for OneDrive (home and work or school) and SharePoint.
• The full local path is the local path (up to 400 characters) plus the OneDrive root folder (up to 120 characters).
• Paths that exceed 520 characters show a sync error, and OneDrive won't sync the item until you bring it back under the limit.

"Decoded" matters here: characters like a space can expand when encoded, and each one counts toward the total. A deeply nested folder with long, descriptive names is the usual way a single file quietly crosses 400 without anyone noticing.

Confirm which files are over the limit

Don't hunt by hand — let PowerShell list the offenders. Open PowerShell, move into your OneDrive folder, and print every path longer than 400 characters:

cd "$env:OneDrive"
Get-ChildItem -Recurse -Force | Where-Object { $_.FullName.Length -gt 400 } |
  Select-Object @{ n = 'Length'; e = { $_.FullName.Length } }, FullName

Length FullName
------ --------
   431 C:\Users\you\OneDrive\Projects\2026\Q3\ClientDeliverables\Draft\final_v3_reviewed.xlsx

Each row is a file whose full path is the problem. Sorting by Length shows how far over you are, which tells you how much to trim.

Shorten the path by renaming or moving

Microsoft gives two fixes, and both keep your content. Rename the file, or a folder above it, to something shorter — the OneDrive notification updates live and reads Path is short enough to sync once you drop under the limit. Or move the item closer to the top of your OneDrive, into a folder that's fewer levels deep:

Move-Item "$env:OneDrive\Projects\2026\Q3\ClientDeliverables\Draft\final_v3_reviewed.xlsx" "$env:OneDrive\Projects\final_v3.xlsx"

Moving an item up even one or two folder levels is often enough to bring the path under 400. You don't need to delete anything, and you won't lose any content — you're only changing where the file sits, not the file itself.

A real case: a deep export from a colleague

A teammate shares a project archive and you drop the whole tree into OneDrive\Projects. One spreadsheet won't sync — red X, Path is too long to sync. You run the scan above and it prints a single path at 431 characters, buried five folders deep with long auto-generated names. Renaming the file alone isn't enough, so you move its parent folder from Projects\2026\Q3\ClientDeliverables\Draft\ up to Projects\Q3-draft\. The scan now returns nothing, the red X turns to a green check, and the spreadsheet uploads.

Verify the file syncs and the client catches up

Watch the file's icon in File Explorer: a green check (or the "available in the cloud" icon) means it synced. Re-run the scan to confirm no path is still over 400:

(Get-ChildItem "$env:OneDrive" -Recurse -Force | Where-Object { $_.FullName.Length -gt 400 }).Count

0

A count of 0, and the OneDrive icon back to a steady "Up to date" rather than "Sync pending," means every path is under the limit and the client has caught up.

Keep paths under the limit

Keep folder trees shallow and names short, especially near the top, where the OneDrive root already spends part of the budget. Sync a specific subfolder rather than a whole deep archive when you only need part of it. When you bring in exports or downloads with long machine-generated names, flatten them into a shorter folder before they land in OneDrive. If you routinely work with long paths, keep the deepest projects nearer the root so a couple of extra subfolders don't push you past 400.

How this differs from invalid-character and storage-full errors

A path-length block is only about total length. It's different from an invalid-character sync error, where a name contains one of " * : < > ? / \ |, a reserved name such as CON or NUL, or a leading or trailing space — there you fix the character, not the depth. And it isn't a storage-full error: if OneDrive says you're out of space, no amount of shortening helps — you free space or add storage. Read the exact message: "too long" means trim the path, "invalid characters" means fix the name, "full" means make room.