In this article, you'll find information about different unsupported characters, file types, attributes, and more.
Skip Ahead to...
File and Folder Names
To maintain compatibility with Windows' file naming conventions, we do not support file and folder names which include the following characters or have any of the specified naming patterns:
\ / " : < > | * ?
- end with period(s)
- begin or end with spaces
- have control characters
- have Unicode characters with 4 or more bytes
When migrating to Egnyte, Migration App offers the option to Sanitize these file names on the source so that they can be migrated. Each unsupported character is replaced by an underscore. Any file name that is changed is recorded in the Migration Job Report.
File or Folder Names That:
- match one of the following exactly: .ds_store, .metadata_never_index, .thumbs.db, powerpoint temp, desktop.ini, icon\r
- end with: ., ~, ._attribs_, ._rights_, ._egn_, _egnmeta, .tmp, -spotlight, .dwl, .dwl1, .dwl2, .ac$, .sv$, *.~vsdx
- start with: ._, .~, word work file, _egn_., .smbdelete
- start with: ~ and end with .idlk, .xlsx, .xlsx (deleted), .pptx, .pptx (deleted)
- start with: ~$ and end with .doc, .docx, .docx (deleted), .rtf, .ppt, .pptx, .pptx (deleted), .xlsm, .xlsm (deleted), .sldlfp, .slddrw, .sldprt, .sldasm
- are AutoCAD temp files starting with atmp and ending with four numbers, e.g. atm3829
- are SAS temp files ending in .sas.b follwed by two numbers, e.g. myFile.sas.b73
- are PDF temp files starting with aa followed by a single letter followed by five numbers, e.g. aau38221
- end with .$$$, e.g. myFile.$$$, and are uploaded from the Desktop App
Folders Names That:
- match one of the following exactly: .data, .tmp
- start with: .spotlight-
Files and folders containing these characters will not upload or sync, and may encounter other restrictions.
Files that have the 'T' (temporary) attribute set in Windows, with the exception of pdf files, will not be uploaded or synced.
Files with Future or Ancient Timestamp
Files with an ancient (ex: July 1, 1601) or future timestamp cannot be uploaded, synced or migrated to Egnyte. If you encounter this, you can do an Internet search for "script to change future timestamps in my files" which should provide guidance on how to resolve it. Once you have resolved the timestamps, you will be able to upload files as usual.
Egnyte Cloud File Service
The limit is 245 bytes (or characters) per path component (e.g., a file or folder name) and 5000 bytes (or characters) for the entire path (including the filename). Microsoft Office imposes a 215 character limit on Office files.
Desktop Sync for Windows
Desktop Sync for Windows is subject to the same path length limitations as Microsoft Windows.
Egnyte Desktop App (Egnyte Drive) for Mac/Windows
When opening files from the Desktop App, Microsoft Excel is still subject to the maximum folder path limit of 218 characters despite the drive being able to handle longer paths.
Uploading active database files is NOT supported e.g. Exchange, Quickbooks, SQL, Oracle, or MS Access. Although these files will upload, they will be throttled after the initial sync of the file due to rapid event patterns that can cause an unnecessarily large amount of bandwidth to be used. Furthermore, syncing active database files may result in corruption of the database file due to the file being uploaded while it is updated by 3rd party software at a high frequency. For example, on the Desktop App, users may find that database files are hidden from view in the drive because they're considered corrupt. Uploading 'at rest' database files is supported but subjected to throttling limits detailed below.
Throttling for the database file uploads varies between a maximum allowed upload rate of once per minute for database files under 100 MB to once per 6 hours for database files over 1 GB in size. Only up to 3 versions of database files are stored in the cloud despite any version retention policy. The aforementioned behavior applies to files with the following extensions:
The Mac file system includes support for Package Files. Packages look like a file in Finder, but are actually a folder with files inside them. When uploaded to Egnyte (and other services) these are uploaded as a folder with files inside them.
Older versions on iWork formats (e.g. Pages) saved their data in Package formats whereas newer versions default to normal files. If you have older iWorks documents you can convert them to the single file format for greater compatibility with Egnyte and other applications.
Resource Forks and Alternative Data Streams
The Mac file system has support for Resource Forks and Windows has support for Alternative Data Streams. Both of these provide a mechanism to capture additional data associated with the file that is separate from the regular file contents and not included as part of the file size.
Some forms of older Mac Postscript font files capture the entire font data as a resource fork with a zero size file. These fonts can be converted to TTF fonts for greater compatibility with Egnyte and other applications.
Egnyte supports relative links, but when migrating to Egnyte, things can get tricky. Talk to our PS team to find the best solution for migration.
Other Unsupported Applications
- OneNote - due to the way OneNote writes information to files, it is possible for data corruption when using the Egnyte Desktop App to open and edit such files. This is because OneNote does not wait for the file to be downloaded in its entirety before writing to it. For this reason, editing OneNote files is not supported in the Desktop App.
User Names and Groups
There are few restrictions when creating a username in Egnyte.
- Must start with an alphanumeric character
- Can only contain alphanumeric, a hyphen, underscore, and period characters
- Cannot end with a period
- Cannot contain spaces
For groups, the same restrictions apply except group names can contain spaces in between but cannot lead or end with a space.