Skip to main content
Procore (en-GB)

Why are some files missing after downloading from Procore Sync?

 Limited Release
Procore Sync is currently in limited release. Only a subset of customers maintain access to the application. 


You are downloading folders to your Windows computer from Procore Sync and you notice that after downloading, some files or folders are missing.


There are several reasons why files might be missing from Procore Sync. Possible reasons are that the folder or file name:

  • Ends with a period or whitespace.
    • Windows OS does not allow folders with names ending in a period or whitespace to be downloaded and stored on the computer. This is an operating system limitation and Procore has no control over it. A common example of a folder in the Documents tool that cannot be synced is the name of a sub contractor such as “Smith’s Mechanical Inc.”
  • Has more than 260 characters.
  • Contains forbidden characters.
    • < (less than)
    • > (greater than)
    • : (colon)
    • ” (double quote)
    • / (forward slash)
    • \ (backslash)
    • | (vertical bar or pipe)
    • ? (question mark)
    • * (asterisk)
    • “Tab” character
    • Certain special characters with integer value zero, (i.e., ASCII NUL character), or characters whose integer representations are in the range from 1 through 31.
  • Contains Windows reserved device names. 
    • CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8 and LPT9.
      Note: Also avoid using these in names followed immediately by a file name extension. For example, NUL.txt is not recommended.
  • Contains filenames that are not accepted.
    • thumbs.db
    • desktop.ini
    • .ds_store


This problem can be resolved by renaming the file or folder to remove any characters mentioned above. This can be done through the Documents tool in Procore's web application or through Procore Drive. See the following tutorials on renaming files and folders:

For additional information regarding characters in filenames, see Microsoft's support page: Naming Files, Paths and Namespaces.

See Also