File Pilot doesn't have full Unicode support yet. Latin and Cyrillic languages should work out of the box, but Asian languages such as Chinese, Korean, and Japanese will not display properly. This will be resolved in the future.

Currently, there is no built-in way to set File Pilot as the default file manager, such as assigning Ctrl+E to open File Pilot or having folders open in File Pilot by default when clicked.

However, some community members have found temporary solutions via registry edits, which are not officially supported by File Pilot yet. Join our Discord server to discuss this topic.

File Pilot supports accessing content through mapped network drives. However, it does not currently support direct access via UNC paths (e.g., \\servername\sharedfolder) or entire NAS devices.

The focus has been and continues to be on providing a solid local experience, but support for these features will be added in the near future.

File Pilot is not tested or guaranteed to run in virtual machines or Wine. It will likely crash due to graphics initialization issues. Running it in these environments is not supported at this time.

Currently, File Pilot does not support proper OS integration for cloud drives like Google Drive, Dropbox, or OneDrive. This feature is not yet available but is planned for future updates.

Ports for Linux and macOS are on the roadmap, but they will only be developed after we reach a stable and solid Windows experience.

File Pilot has been written with portability in mind, meaning that most of the source code (such as rendering and UI) will be reusable, with only platform-specific code, like filesystem indexing, needing to be ported.