A fully featured, free, and actively maintained Microsoft OneDrive client that seamlessly supports OneDrive Personal, OneDrive for Business, Microsoft 365 (formerly Office 365), and SharePoint document libraries.
Designed for maximum flexibility and reliability, this powerful and highly configurable client works across all major Linux distributions and FreeBSD. It can also be deployed in containerised environments using Docker or Podman. Supporting both one-way and two-way synchronisation modes, the client provides secure and efficient file syncing with Microsoft OneDrive services — tailored to suit both desktop and server environments.
This project originated as a fork of the skilion client in early 2018, after a number of proposed improvements and bug fixes — including Pull Requests #82 and #314 — were not merged and development activity of the skilion client had largely stalled. While it’s unclear whether the original developer was unavailable or had stepped away from the project - bug reports and feature requests remained unanswered for extended periods. In 2020, the original developer (skilion) confirmed they had no intention of maintaining or supporting their work (reference).
The original skilion repository was formally archived and made read-only on GitHub in December 2024. While still publicly accessible as a historical reference, an archived repository is no longer maintained, cannot accept contributions, and reflects a frozen snapshot of the codebase. The last code change to the skilion client was merged in November 2021; however, active development had slowed significantly well before then. As such, the skilion client should no longer be considered current or supported — particularly given the major API changes and evolving Microsoft OneDrive platform requirements since that time.
Under the terms of the GNU General Public License (GPL), forking and continuing development of open source software is fully permitted — provided that derivative works retain the same license. This client complies with the original GPLv3 licensing, ensuring the same freedoms granted by the original project remain intact.
Since forking in early 2018, this client has evolved into a clean re-imagining of the original codebase, resolving long-standing bugs and adding extensive new functionality to better support both personal and enterprise use cases to interact with Microsoft OneDrive from Linux and FreeBSD platforms.
- Works with OneDrive Personal, OneDrive for Business, and Microsoft SharePoint Libraries.
- Full support for shared folders and files across both Personal and Business accounts.
- Supports single-tenant and multi-tenant Microsoft Entra ID environments.
- Compatible with national cloud deployments:
- Microsoft Cloud for US Government
- Microsoft Cloud Germany
- Azure/Office 365 operated by VNET in China
- Bi-directional sync (default) - keeps local and remote data fully aligned.
- Upload-only mode - only uploads local changes; does not download remote changes.
- Download-only mode - only downloads remote changes; does not upload local changes.
- Dry-run mode - test configuration changes safely without modifying files.
- Safe conflict handling minimises data loss by creating local backups whenever this is determined to be the safest conflict-resolution strategy.
- Comprehensive rules-based client-side filtering (inclusions, exclusions, wildcard
*, globbing**). - Filter specific files, folders, or patterns to tailor precisely what is synced with Microsoft OneDrive.
- Efficient cached sync state for fast decision-making during large or complex sync sets.
- Near real-time processing of cloud-side changes using native WebSocket support.
- Webhook support for environments where WebSockets are unsuitable (manual setup).
- Real-time local change monitoring via inotify.
- Implements the FreeDesktop.org Trash specification, enabling recovery of items deleted locally due to online deletion.
- Strong safeguards to prevent accidental remote deletion or overwrite after configuration changes.
- Interruption-tolerant uploads and downloads, automatically resuming transfers.
- Integrity validation for every file transferred.
- Standard OAuth2 Native Client Authorisation Flow (default), supporting browser-based login, multi-factor authentication (MFA), and modern Microsoft account security requirements.
- OAuth2 Device Authorisation Flow for Microsoft Entra ID accounts, ideal for headless systems, servers, and terminal-only environments.
- Intune Single Sign-On (SSO) using the Microsoft Identity Device Broker (IDB) via D-Bus, enabling seamless enterprise authentication without manual credential entry.
- Multi-threaded file transfers for significantly improved sync speeds.
- Bandwidth rate limiting to control network consumption.
- Highly efficient processing with state caching, reducing API traffic and improving performance.
- libnotify desktop notifications for sync events, warnings, and errors.
- Registers the OneDrive folder as a sidebar location in supported file managers, complete with a distinctive icon.
- Works seamlessly in GUI and headless/server environments. A GUI is only required for Intune SSO, notifications, and sidebar integration; all other features function without graphical support.
- Ability to encrypt/decrypt files on-the-fly when uploading/downloading files from OneDrive
- Support for Windows 'On-Demand' functionality so file is only downloaded when accessed locally
- A GUI for configuration management: OneDrive Client for Linux GUI
- Colorful log output terminal modification: OneDrive Client for Linux Colorful log Output
- System Tray Icon: OneDrive Client for Linux System Tray Icon
Refer to Frequently Asked Questions
If you have a question or need something clarified, please raise a new discussion post here
Support is only provided for the current application release version or newer 'master' branch versions.
The current release version is:
To check your version, run: onedrive --version. Ensure you are using the current release or compile the latest version from the master branch if needed.
If you are using an older version, you must upgrade to the current release or newer to receive support.
If you encounter any issues running the application, please follow these steps before raising a bug report:
-
Check the application version
Runonedrive --versionto confirm which version you are using.- Ensure you are running the latest release.
- If you are already on the latest release but still experiencing issues, manually build the client from the
masterbranch to test against the very latest code. This includes fixes for bugs discovered since the last tagged release.
-
Run in verbose mode
Use the--verboseoption to provide greater clarity and detailed logging about the issue you are facing. -
Test with IPv4 only
Configure the application to use IPv4 network connectivity only, then retest. See the'ip_protocol_version'option documentation for assistance. -
Test with HTTP/1.1 and IPv4
Configure the application to use HTTP/1.1 over IPv4 only, then retest. See the'force_http_11'option documentation for assistance. -
Verify cURL and libcurl versions
If the above steps do not resolve your issue, upgrade bothcurlandlibcurlto the latest versions provided by the curl developers.- See Compatibility with curl for details on curl bugs that impact this client.
- Refer to the official cURL Releases page for version information.
-
Open a new issue
If the problem persists after completing the steps above, proceed to Reporting an Issue or Bug below and open a new issue with the requested details and logs.
Important
Please ensure the problem is a software bug. For installation issues, distribution package/version questions, or dependency problems, start a Discussion instead of filing a bug report.
If you encounter a bug, you can report it on GitHub. Before opening a new issue report:
-
Complete the Basic Troubleshooting Steps
Confirm you’ve run through all steps in the section above. -
Search existing issues
Check both Open and Closed issues for a similar problem to avoid duplicates. -
Use the issue template
Open a new bug report using the issue template and fill in all fields. Complete detail helps us reproduce your environment and replicate the issue. -
Generate a debug log
Follow this process to create a debug log.- If you are concerned about personal or business sensitive data in the debug log, you may:
- Create a new OneDrive account, configure the client to use it, use dummy data to simulate your environment, and reproduce the issue; or
- Provide an NDA or confidentiality agreement for signature prior to sharing sensitive logs.
- If you are concerned about personal or business sensitive data in the debug log, you may:
-
Share the debug log securely
- Do not post debug logs publicly. Debug logs can include sensitive details (file paths, filenames, API endpoints, environment info, etc.).
- Send the log via email to support@mynas.com.au using a trusted email account.
- Archive and password-protect the log before sending (e.g.
.zipwith AES or.7z):- Example (zip with password):
zip -e onedrive-debug.zip onedrive-debug.log - Example (7z with password):
7z a -p onedrive-debug.7z onedrive-debug.log
- Example (zip with password):
- Send the password out-of-band (OOB) — not in the same email as the archive. Email support@mynas.com.au to arrange an OOB method (e.g. separate email thread, phone/SMS, or agreed channel).
- If you require an NDA, attach your NDA or confidentiality agreement to your email. It will be reviewed and signed prior to exchanging sensitive data.
When raising a new bug report, please include all details requested in the issue template, such as:
- A clear description of the problem and how to reproduce it
- Your operating system and installation method
- OneDrive account type and client version
- Application configuration and cURL version
- Sync directory location, system mount points, and partition types
- A full debug log, shared securely as described above
Providing complete information makes it much easier to understand, reproduce, and resolve your issue quickly.
Note
Submitting a bug report starts a collaboration. To help us help you, please:
- Stay available to answer questions or provide clarifications if needed
- Test and confirm fixes in your own environment when a pull request (PR) is created for your issue
Tip
Reports with missing details are much harder to investigate. Sharing as much as you can up front gives the best chance of a fast and accurate fix.
Refer to docs/known-issues.md
Refer to docs/install.md
Refer to docs/usage.md
Refer to docs/business-shared-items.md
Refer to docs/sharepoint-libraries.md
Refer to docs/national-cloud-deployments.md
Refer to docs/docker.md
Refer to docs/podman.md
