> For the complete documentation index, see [llms.txt](https://docs.konnekt.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnekt.io/fr/troubleshooting/what-is-the-maximum-path-and-file-name-length.md).

# Quelle est la longueur maximale du chemin et du nom de fichier ?

KONNEKT doit respecter les limites de longueur du chemin et du nom de fichier dans les deux mondes :

* **SharePoint Online**\
  et
* **Windows**.

La longueur maximale d’un nom de fichier, chemin compris, est **260 caractères** au total.

Il se compose du chemin et du nom de fichier :

* **chemin** est : `\\onedrive-<yourTenant>\<site>\<library>\<foldernames>\`\
  Il est limité à 248 caractères.
* **nom de fichier** est : `<name>.<extension>`\
  12 caractères sont toujours conservés pour le nom de fichier (8.3). Le chemin et le nom de fichier ensemble ne doivent pas dépasser la limite totale de 260 caractères.

Ces limites sont principalement dues aux restrictions de Windows OS et de l’Explorateur de fichiers. Des détails peuvent être trouvés [ici](https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=cmd).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.konnekt.io/fr/troubleshooting/what-is-the-maximum-path-and-file-name-length.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.