File length restriction for access sharepoint files in windows while amking shortcut is very difficult

Nitesh Ghadge 0 Reputation points
2026-09-21T01:59:00.7766667+00:00

As like charecter length in cloud about "400" need increasing with Windows file explorer too, facing challenges after shifting from on prem file server on sharepint by users with ready data.

after regestry setting change still it is not working.

"260" charecter limitation in that already consume root charecters name and file with subdirectory folders are making large name for identification.

Microsoft 365 and Office | SharePoint | Other | Windows
0 comments

3 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Nitesh Ghadge 0 Reputation points
    2026-09-21T03:19:20.1633333+00:00

    Can this fix microsoft because not possible work on two platform, also some design related files and scm projects are longer

    files and folder not able to reducing name sizing.

    Was this answer helpful?

    0 comments
  2. Dora-T 1,130 Reputation points Independent Advisor
    2026-09-21T02:48:35.3366667+00:00

    Hi @Nitesh Ghadge

    First, I recommend referring to the AI-generated answer, as it includes information about the file path length limits across SharePoint, OneDrive, and Windows, as well as some possible workarounds.

    Please note that Windows File Explorer has a 260-character path length limitation for opening, renaming, and moving files. Microsoft also notes that even when the Windows long path policy is enabled, File Explorer does not currently use it. Therefore, changing the Registry setting alone does not remove this restriction in File Explorer.

    You might also consider the following workarounds mentioned in the AI answer that may be applicable to your situation:

    • Shorten file and folder names where possible to reduce the overall path length.
    • Reduce the folder depth by simplifying or flattening deeply nested folder structures.
    • If a path is too long to manage in File Explorer, access the files through the SharePoint website and consider renaming or moving files/folders there to shorten the overall path.

    Since this is a user-to-user community forum, you may also consider submitting your feedback through Microsoft's feedback channels so that the appropriate product team can review your experience.

    Thank you for your understanding.

    Was this answer helpful?

  3. AI answer

    2026-09-21T01:59:20.2566667+00:00

    The limit cannot effectively be increased for Windows File Explorer and Office desktop apps in this scenario.

    Key limits:

    1. Windows File Explorer: 260 characters for opening, renaming, and moving files.
    2. Office desktop apps on Windows: 256 characters (260 UTF16 WCHARs).
    3. OneDrive and SharePoint in the cloud: 400 characters.
    4. OneDrive sync: 520 characters total, which includes the local synced path plus the OneDrive root folder.

    Why the registry change did not help:

    • Windows can support longer paths only when long path support is enabled.
    • But File Explorer and Office desktop apps do not currently opt in, so enabling the policy or registry setting alone does not remove the 260-character limit for most users.

    Practical ways to work around it:

    1. Shorten file and folder names
      • Reduce long descriptive names.
      • Shorter names leave more room for folder depth.
    2. Flatten the folder structure
      • Deep nesting quickly consumes the available path length.
      • Move frequently used files closer to the root.
    3. Use OneDrive Files On-Demand
      • Browse files in File Explorer without downloading everything.
      • When a file has a long path, open it in the browser, where the 400-character cloud limit applies instead of the 260-character desktop limit.
    4. Rename from the web
      • If a file or folder path is too long to manage in File Explorer, rename it in OneDrive on the web or in the SharePoint site.
      • After the path is shortened enough, it can sync normally to the desktop.
    5. Be careful with SharePoint shortcuts and synced libraries
      • Adding a shortcut to a deeply nested shared library or Teams channel folder can quickly exceed the local Windows limit.
      • Sync only a subfolder if possible, or shorten the shortcut name in OneDrive.
    6. Check the OneDrive root folder length
      • A work or school sync path such as C:\Users\Name\OneDrive - Organization Name\... already uses many characters before the actual file path starts.
      • A longer organization name leaves fewer characters for folders and file names.
    7. Use OneDrive sync notifications
      • If OneDrive detects a path that is too long, it shows a notification identifying affected files.

    Important behavior to expect:

    • A file may work in SharePoint or OneDrive on the web but fail in Windows Explorer.
    • If a synced file’s full path exceeds 520 characters, OneDrive shows a path is too long notification and the sync client quits until the over-limit item is fixed.
    • Individual file or folder names can be up to 255 characters, but the full path can still fail because of nesting.

    For migrated on-premises data, the supported fix is usually to shorten names, reduce nesting, sync a smaller subfolder, or use the web for long paths. There is no supported setting that makes File Explorer use the same 400-character limit as SharePoint Online.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.