# Project File Name Length Restriction Bypass Issue

**URL:** <https://backstage.polyend.com/t/project-file-name-length-restriction-bypass-issue/16552>\
**Category:** Archive\
**Tags:** tracker-plus, by-design\
**Created:** [December 2, 2024, 10:13am UTC](https://backstage.polyend.com/t/project-file-name-length-restriction-bypass-issue/16552 "2024-12-02T10:13:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Sandroid](https://backstage.polyend.com/user_avatar/backstage.polyend.com/sandroid/32/172_2.png) [@Sandroid](https://backstage.polyend.com/u/Sandroid)\
**Post date:** [December 2, 2024, 12:29pm UTC](https://backstage.polyend.com/t/project-file-name-length-restriction-bypass-issue/16552/2 "2024-12-02T12:29:34Z")

</div>

⚠ Careful! This is a FAT32 filesystem limitation and not a bug.

There are a couple things to be aware of here:

- The FAT32 filesystem has a character limit how long filepaths can be.
- Certain characters are not allowed like `\ / : * ? " < > |`
- The maximum filepath can be 255 characters - this is the **entire path** , not a single file.
- The filesystems on computers do not keep this in mind (Windows does, but not correctly either).

Due to this, there are some limitations how long a filepath can be on the device, before it becomes a problem to be read… and there is nothing that can be done _on the device_ once this happens, because the software simply won’t see those paths/folders. Which also means there is no way to alert the user about this.

**Sidenote:**  
Project names are not based on the filename on disk (they are two separate values)

---

_[View the full topic](https://backstage.polyend.com/t/project-file-name-length-restriction-bypass-issue/16552)._
