# Pricing & Licenses ExpanDrive was purchased by new ownership in 2024 and a transition process occurred during 2024 and early 2025. The prior owner is no longer involved with ExpanDrive as of April 2025. As of April 2025, we have relaunched ExpanDrive under a new licensing and support model. ## Free License The main ExpanDrive application for Windows, Mac, and Linux is free for personal use. Commercial, academic, or government use is also free for enterprises where fewer than 10 people use ExpanDrive across the enterprise during a calendar year. The Free license does not include technical support, the Web Management Console (for managing user configurations remotely), or ExpanDrive Server Edition. ## Paid License (Recurring Subscription Model) Paid Licenses are available to anyone, and required for Commercial, academic, or government use by more than 10 people at an enterprise. Paid Licenses include access to the main ExpanDrive application, the Web Management Console, and ExpanDrive Server Edition. They also include full technical support. A Paid License costs $29/month and covers use by up to 10 people. This limit is based on whichever is higher: your [total user count](/web-management-console#users) or your total [device count](/web-management-console#device-count), since a single user can activate ExpanDrive on more than one device. For larger deployments, contact our Enterprise Sales team. Enterprise site licenses are available. All Paid Licenses are a recurring subscription. This funds the ongoing costs of development, security, and customer support. Lifetime or perpetual licenses are not offered. Systems with a Paid License contact our license server at `teams.expandrive.com` on port 443 to check for license validity. Lifetime or perpetual licenses sold by the prior owner only apply to use of prior versions of ExpanDrive (versions labeled 2023 or earlier), and do not include technical support from us. The prior owner is no longer a going concern. ### A Note About Support Under our new ownership, we have substantially improved the caliber of ExpanDrive technical support. If you were frustrated by ExpanDrive support in the past, give us another try. Technical support is available only to current Paid License ExpanDrive customers. # Installation & System Requirements The following are the system requirements for ExpanDrive. ## Windows ExpanDrive runs on 32 and 64-bit Windows 7 and newer, including Windows 8, Windows 10, and Windows Server Edition (including Terminal Server). You must have Administrator permissions, or somebody who can provide it to you, in order to complete installation. However, once installation is complete you can use ExpanDrive without Administrator permissions and you can also use the built-in auto-updater. [Download the latest Windows build of ExpanDrive.](https://www.expandrive.com/api/download/expandrive?platform=win64) (64-bit Installer .exe) Other Windows packages: * [32-bit Installer .exe](https://www.expandrive.com/api/download/expandrive?platform=win32\&ext=exe) * [32-bit .nupkg](https://www.expandrive.com/api/download/expandrive?platform=win32\&ext=nupkg) * [64-bit .nukpg](https://www.expandrive.com/api/download/expandrive?platform=win64\&ext=nupkg) ### MSI Installer We also provide an MSI-based installer for deployment on multi-user systems. By default, the MSI installs the application into `C:\Program Files`. This installer does not support automatic updates. It is intended for environments that require centralized deployment. We provide two packages for installation: * [64-bit .msi](https://www.expandrive.com/api/download/expandrive?platform=win64\&ext=msi) * [32-bit .msi](https://www.expandrive.com/api/download/expandrive?platform=win32\&ext=msi) ## macOS ExpanDrive supports any macOS environment running OS X 11.0 or newer. [Download the latest macOS Build of ExpanDrive.](https://www.expandrive.com/api/download/expandrive?platform=macos) ## Linux ExpanDrive supports modern 64-bit desktop Linux environments and requires x86-64 (Intel/AMD 64-bit) architecture. We provide 3 types of packages for installation: * [.deb packages](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=deb), for Debian & Ubuntu based distros * [.rpm packages](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=rpm), for RHEL/Fedora/Centos based distros * [.AppImage](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=AppImage), for other types of installs ## Application Updates ExpanDrive checks for updates at the address `updates.expandrive.com` using port 443. You can use the built-in auto-updater for ExpanDrive without Administrator permissions. # Linux Installations ## Debian and Ubuntu Based Distributions ### Simple Installation for Debian and Ubuntu For Debian and Ubuntu based distributions, download the latest [.deb package (64 bit)](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=deb) and install it through the graphical installer or with the following command. ``` sudo apt install ./ExpanDrive_*_amd64.deb ``` Replace the filename with the actual downloaded package name, or use the wildcard pattern shown above. Installing the .deb this way also installs the apt repository and code signing key, so future updates flow through the system package manager. ### Manual Repository Installation for Debian and Ubuntu Manual repository installation lets you troubleshoot each step separately when the simple .deb installation doesn't work. It also helps when automating ExpanDrive installation across multiple systems, or when you want to verify security keys before adding them to your system. Install the repository and key manually with the following commands: ``` curl https://packages.expandrive.com/keys/expandrive.asc | gpg --dearmor > packages.expandrive.gpg sudo install -o root -g root -m 644 packages.expandrive.gpg /usr/share/keyrings/ sudo sh -c 'echo "deb [arch=amd64 signed-by=/usr/share/keyrings/packages.expandrive.gpg] https://packages.expandrive.com/expandrive stable main" > /etc/apt/sources.list.d/expandrive.list' ``` Then update the package cache and install ExpanDrive: ``` sudo apt-get install apt-transport-https sudo apt-get update sudo apt-get install expandrive ``` ## RHEL, Fedora, and CentOS Based Distributions ### Simple Installation for RHEL, Fedora, and CentOS Download the latest [.rpm package (64-bit)](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=deb) and use yum to install ExpanDrive and its required dependencies. ``` sudo yum localinstall ./ExpanDrive-*.x86_64.rpm ``` Replace the filename with the actual downloaded package name, or use the wildcard pattern shown above. Installing the .rpm also configures the yum repository and code signing key, so future updates flow through the system package manager. ### Manual Repository Installation for RHEL, Fedora, and CentOS Manual repository installation lets you troubleshoot each step separately when the simple .rpm installation doesn't work. It also helps when automating ExpanDrive installation across multiple systems, or when you want to verify security keys before adding them to your system. Install the yum repo manually with the following commands: ``` sudo rpm --import https://packages.expandrive.com/keys/expandrive.asc sudo sh -c 'echo -e "[expandrive]\nname=expandrive\nbaseurl=https://packages.expandrive.com/rpm\nenabled=1\ngpgcheck=1\ngpgkey=https://packages.expandrive.com/keys/expandrive.asc" > /etc/yum.repos.d/expandrive.repo' ``` Then update the package cache and install ExpanDrive with `dnf` (Fedora 22 and above): ``` sudo dnf check-update sudo dnf install expandrive ``` or with `yum`: ``` yum check-update sudo yum install expandrive ``` ## AppImage Installation Most Linux distributions, including Ubuntu, Fedora, Debian, and OpenSUSE, can run AppImages. The AppImage is a portable, distribution-agnostic way to run ExpanDrive without a traditional installation. It requires no root permissions and does not modify system files. To install the AppImage, [download the file](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=AppImage). After downloading, make it executable. Replace the filename with the actual downloaded package name, or use the wildcard pattern shown below: ``` chmod +x ExpanDrive-*.AppImage ``` Run ExpanDrive and configure your [Integrations](/integrations). ## Installing or Updating ExpanDrive's Public Key During an update, an error reading `The following signatures were invalid: EXPKEYSIG` means the version of the key on your system has expired. The following commands update the public key stored on your system. ### Debian and Ubuntu Based Distributions ``` curl https://packages.expandrive.com/keys/expandrive.asc | gpg --dearmor > packages.expandrive.gpg sudo install -o root -g root -m 644 packages.expandrive.gpg /usr/share/keyrings/ ``` ### RHEL, Fedora, and CentOS Based Distributions ``` sudo rpm --import https://packages.expandrive.com/keys/expandrive.asc ``` Once the key is updated, rerun the updater and the update completes without error. # Integrations # Managing Connections ## Adding a Connection You can create any combination of connections to different services. New connections are added from the ExpanDrive application settings. When you select the type of your new connection, you are prompted for the parameters needed for the connection. Each connection type has its own page with the parameters it needs — see [SFTP](/integrations/sftp), [Amazon S3](/integrations/amazon-s3), and the other per-service pages in this section. After you save the new connection information, ExpanDrive immediately connects and displays the contents. ### Mapping Windows Drives When you define a connection using ExpanDrive on Windows, you can choose whether to assign a drive letter to the connection, and which drive letter to use for each connection. Assigning a drive letter can make it simpler to interact with multiple connections, or for scripting. Microsoft recommends [using UNC paths rather than drive letters](https://learn.microsoft.com/en-us/windows/win32/services/services-and-redirected-drives) for connecting to remote systems. ## Removing Connections You can remove your defined connections from the ExpanDrive application settings. If you've used the [Offline Sync](/offline-sync-mode) feature to download any files to your local system, the mounted folder with those downloaded files remains on your local device after the connection is removed. Once you delete the downloaded contents, the folder is removed automatically. # Amazon S3 ExpanDrive supports the Amazon S3 API, letting you connect directly to AWS or to S3-compatible storage services including [DreamObjects](#dreamobjects-connection-parameters), [DigitalOcean Spaces](#digitalocean-spaces), and [Akamai Linode Object Storage](#linode-object-storage). On S3, your files and folders are stored inside top-level folders called buckets that are uniquely named throughout all of S3. ## Connection Parameters Each S3 or S3-compatible connection in Expandrive provides parameters to control exactly what you're connecting to along with your credentials. ### Server The address at which the service can be reached. For Amazon S3, use the default value of `https://s3.amazonaws.com`. For other [S3-compatible providers](#connecting-to-s3-compatible-services), use the address for their service. ### Access Key The access key is your unique identifier for authentication. Think of it like a username for your S3 account. It's usually a 20-character alphanumeric string like `AKIAIOSFODNN7EXAMPLE`. You can obtain this from your AWS IAM console (for Amazon S3) or from your storage provider's dashboard. Keep this confidential and never share it publicly. As a best practice, use the access key of a user other than your root account user. The access key and secret key work together as a pair for authentication. Either one alone is not useful; together they provide full access to your S3 resources. ### Secret Key The secret key is your private authentication key that pairs with your access key. This is like a password. When you save your connection info in ExpanDrive, the secret key is [securely stored](/security#authentication) within your local keychain. ### Custom Region The region where your bucket resides, which varies depending on which provider you are using. This field is optional because S3 bucket names are globally unique and can be identified even without the region specified. Providing the correct region improves performance and avoids the extra cost of requests being routed through the default region. ### Bucket This field lets you restrict what buckets the connection can access on your account. [Bucket-level organization](#bucket-level-organization) is a hallmark of S3-compatible services; buckets are top-level folders of your S3 account that you can attach policies to. If your credentials do not have access to list the buckets in your account, provide the bucket name in your connection parameters. ### Nickname The nickname identifies the connection and appears as the volume label on the mounted drive. ## Bucket-Level Organization Amazon S3 is organized into buckets, which are top-level folders that are uniquely named throughout the service. You can [attach policies to a bucket](https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-bucket-policy.html) to [restrict access to particular users](https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html#example-bucket-policies-folders) or [make hosted content available to the public](https://docs.aws.amazon.com/AmazonS3/latest/userguide/example-bucket-policies.html#example-bucket-policies-anonymous-user). If you have permission to list buckets in your S3 account, ExpanDrive can mount the root of the account, showing you all your buckets. You can instead restrict a mount to a specific bucket, or to a particular folder in a bucket, by typing the bucket name in the remote path section. This is useful if you only have access to a particular bucket or don't have permission to list the buckets for an account. ## Connecting to S3-Compatible Services Many object storage services use APIs that behave the same as Amazon S3 APIs, and you can use ExpanDrive to connect to them with the S3 connector by changing the connection parameters. ### DreamObjects Connection Parameters Override the Server parameter with the [hostname for your account](https://help.dreamhost.com/hc/en-us/articles/32254965300372-DreamObjects-cluster-differences), either `objects-us-east-1.dream.io` or `s3.us-east-005.dream.io`. Supply the access key and secret key in the usual fields. This information is [associated with your DreamObjects user](https://help.dreamhost.com/hc/en-us/articles/215986357-DreamObjects-Keys). ### DigitalOcean Spaces The DigitalOcean Spaces endpoint is `https://.digitaloceanspaces.com`, where `` is the DigitalOcean [datacenter region](https://docs.digitalocean.com/products/spaces/details/availability) where your bucket is located. ### Linode Object Storage ExpanDrive can connect to Akamai Linode Object Storage. The server address is `https://.linodeobjects.com`, where `` is the [datacenter region](https://techdocs.akamai.com/cloud-computing/docs/object-storage-product-limits). If you only need to connect to a single bucket, you can use that [bucket's URL](https://techdocs.akamai.com/cloud-computing/docs/access-buckets-and-files-through-urls#bucket-url) instead for the server address. [Create access keys](https://techdocs.akamai.com/cloud-computing/docs/manage-access-keys) for connecting to your bucket, and provide those within the access key and secret key fields. ### OpenStack Swift Object Storage To use the S3 connector with your [Swift Object Storage](https://www.openstack.org/software/releases/dalmatian/components/swift), provide the host name of your OpenStack cloud server. You need to generate credentials from your chosen authentication service to use for the access key and secret key. ### Rackspace Object Storage ExpanDrive supports connecting to Rackspace Object Storage as an Amazon S3 connection by supplying the correct server endpoint and credentials. Check the [Namespace Details](https://docs.rackspace.com/docs/namespace-details) in the Rackspace Portal for your Access URL and username. The Access URL is the server address you will connect to, and you will provide the username as the Access Key for the connection. Create a Secret Key for the user to use as the Secret Key in your ExpanDrive connection. # Amazon S3 with IAM Role ExpanDrive connects to Amazon S3 using temporary security credentials issued via [AWS Security Token Service (STS)](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp.html). For this workflow, you provide the keys to authenticate as a user who can assume a role that has access to your bucket. ExpanDrive uses STS to get temporary credentials for the role that can access the S3 bucket. If the role is configured for MFA, ExpanDrive prompts you for the one-time password and supplies the MFA information to STS. With the temporary credentials in hand, ExpanDrive provides access to the S3 bucket. This is a more secure alternative to long-term access keys. It supports IAM roles, MFA enforcement, and short-lived credentials that automatically expire. ## Connection Parameters Connecting to S3 using temporary security credentials uses many of the same connection parameters as a [conventional S3 connection](/integrations/amazon-s3). The server, custom region, nickname, and bucket behave exactly the same. ### Access Key This is the access key of the user who has permission to assume a role via STS. ### Secret Key The secret key for the user who can assume a role via STS. ### STS Endpoint The endpoint for AWS STS. Use . ### IAM Role The Amazon Resource Name (ARN) of the role to assume. This role must grant access to the target S3 bucket. # SFTP ExpanDrive is the gold standard for mapping SFTP as a network drive on Mac and Windows. It makes the contents of any SSH server available through Finder, Explorer and other apps on your system. ## Connection Parameters ### Server The address of the server you are connecting to. You can use a domain name or an IP address to connect. ### Username This is the username assigned for your access to the SFTP server. ### Authentication ExpanDrive allows multiple methods for authenticating an SFTP connection: password authentication, SSH key and an external SSH agent, such as Pageant (Windows) or ssh-agent (Mac or Linux). #### Password Authentication Providing a username and password is the default authentication option for an SFTP connection. Your password is saved [securely](/security#authentication) in the macOS Keychain or the Windows credentials vault. If you have multi-factor authentication set up, ExpanDrive will prompt you for those inputs during connection. #### SSH Key Authentication You can mount a drive without a password using a public/private key pair. The public portion must be installed on the remote server; the method for doing this may vary depending on your provider. When you select SSH Key authentication, you'll need to specify the path to the private key file. ExpanDrive only supports OpenSSH format keys. If you have a PuTTY ".ppk" file, you must either convert that key to OpenSSH format or use SSH agent authentication. ExpanDrive does not generate SSH keys. You can use a utility such as PuTTYgen/PuTTY Key Generator for Windows or ssh-keygen on Mac or Linux to create a key pair. #### SSH Agent Authentication SSH agents manage ssh key files for you, removing the need to enter a lengthy passphrase each time you want to connect to an SSH server. This is particularly helpful if you use multiple private/public key pairs to connect to different resources. ExpanDrive uses the Pageant SSH authentication agent (a PuTTY utility) on Windows or the built-in ssh-agent on Mac. You must add your keys to the SSH agent in order to connect with ExpanDrive. When you select SSH Agent authentication, ExpanDrive will automatically communicate with your SSH agent (Pageant on Windows, ssh-agent on Linux or Mac) to establish the SFTP connection. ### Port The number of the port for connecting to SFTP. If you do not specify a port, ExpanDrive will connect on port `22`. You can enter a different value if the server requires it. Some organizations are required to use non-default ports for compliance or security policy reasons. ### Remote path The remote path allows you to enter a path on the remote server which limits which directory will be the top-most directory visible through this connection. Specify the absolute path to the directory, such as `/home/user/inbox` . One reason to specify this path is to create a connection to a single specific directory, which can simplify operations on your computer, allowing you to interact directly with the mount folder rather than repeatedly navigating through subfolders. This setting is also useful if your SFTP provider has granted you access to a deeply nested path but does not automatically change your session to that folder. ### Nickname The nickname serves to identify the connection. This name will show up as the volume label on the mounted drive. # FTP FTP, or File Transfer Protocol, is a well-established protocol for sending data using the client/server model. ExpanDrive's FTP connection supports FTPS connections using TLS/SSL. Do not confuse FTPS with SSH (SFTP) which uses the SSH protocol to exchange information securely using private/public key pairs. ## Connection Parameters ### Server The address of the server you are connecting to. You can use a domain name or an IP address to connect. ### Username This is the username assigned for your access to the FTP server. ### Password The password for your access to the FTP server. Your password is saved [securely](/security#authentication) in the macOS Keychain or the Windows credentials vault. ### Security ExpanDrive can create unencrypted FTP sessions, or secure your FTP sessions using TLS/SSL, or TLS/SSL (login only). #### Unencrypted FTP Connection When you select FTP security, you are creating an insecure, unencrypted connection. Any data, including your passwords, are sent in plaintext. Avoid this option unless it is the only type of FTP connection your server can accept. #### FTP with TLS/SSL Connection An FTP connection uses two separate channels: the control connection and the data connection. The control connection is used to send the username and password and other commands. Files are transferred over the data connection. Selecting FTP with TLS/SSL security creates a connection where both the control connection and the data connections are encrypted. This is the most secure FTP connection you can create with ExpanDrive. #### FTP with TLS/SSL (Login Only) An FTP connection uses two separate channels: the control connection and the data connection. The control connection is used to send the username and password and other commands. Files are transferred over the data connection. When you create a connection using TLS/SSL (login only), the control channel of your connection will be encrypted but the data channel of your connection will not be secure. It is rare to find this type of connection, and most servers that support encrypting the control channel will also support encrypting the data channel. If your remote server supports the FTP with TLS/SSL security type, use that instead of this option because the minor performance decrease of additional encryption is greatly outweighed by the increased security. ### Port The number of the port for connecting to FTP. If you do not specify a port, ExpanDrive will connect on port `21`. You can enter a different value if the server requires it. Some organizations are required to use non-default ports for compliance or security policy reasons. ### Remote Path The remote path allows you to enter a path on the remote server which limits which directory will be the top-most directory visible through this connection. Specify the absolute path to the directory, such as `/home/user/inbox`. One reason to specify this path is to create a connection to a single specific directory, which can simplify operations on your computer, allowing you to interact directly with the mount folder rather than repeatedly navigating through subfolders. This setting is also useful if your FTP provider has granted you access to a deeply nested path but does not automatically change your session to that folder. ### Nickname The nickname identifies this connection on your machine. This name is used as the volume label on the mounted drive. # Box You can use ExpanDrive to connect to Box.com using either a Personal account, or a business account. Business accounts support single sign-on (SSO). ExpanDrive uses a standard [OAuth flow](/security#understanding-oauth-2) to authenticate with Box, so ExpanDrive has no access to your account credentials, only the authentication token returned by Box. ## Connection Parameters ### Nickname The nickname identifies this connection on your machine. This name is used as the volume label on the mounted drive. ### Account The account you used for authenticating to Box is displayed. You cannot change this value. # Dropbox You can use ExpanDrive to connect to Dropbox using either a Personal account or a Dropbox Business account. ExpanDrive uses a standard [OAuth flow](/security#understanding-oauth-2) to authenticate, so ExpanDrive has no access to your account credentials, only the authentication token returned by Dropbox. ## Connection Parameters ### Nickname The nickname identifies this connection on your machine. This name is used as the volume label on the mounted drive. ### Account The account you used for authenticating is displayed. You cannot change this value. ## Connecting Multiple Dropbox Accounts If you're connecting to more than one Dropbox account, you may need to sign out of Dropbox in your default web browser to trigger re-authentication before you add the new connection to ExpanDrive. This will not disconnect your existing ExpanDrive connections to Dropbox. # Google Cloud Storage [Google Cloud Storage](https://cloud.google.com/storage) is a file storage service run by Google. It lets you store files on Google's servers rather than on your local machine. Google Cloud Storage is similar in concept to [Amazon S3](/integrations/amazon-s3) or a more technical version of Google Drive: you can store any kind of file, control who has access to it, retrieve it from anywhere, and integrate with the other tools and services provided in Google Cloud. Google Cloud Storage uses [bucket storage](#bucket-storage) to organize the files you save in the storage. ExpanDrive can connect to your Google Cloud Storage so you can interact with the contents of your buckets directly from your desktop. ## Connecting to Google Cloud Storage ExpanDrive connects to Google Cloud Storage using OAuth, which means you won't need to enter a password directly into ExpanDrive. Instead, you'll be redirected to Google's login page, where you'll sign in and grant ExpanDrive permission to access your account. Google handles the authentication, and ExpanDrive receives a token it uses to connect on your behalf rather than your actual credentials. Make sure the user account you are using has access to the bucket(s) you want to connect to in Google Cloud Storage. ExpanDrive only has the permissions granted to your authenticated user account. ### Nickname The nickname is a display name for this connection. This name is used as the volume label on the mounted drive. ### Bucket Name Enter the name of the specific Google Cloud Storage bucket you want to connect to. Bucket names are globally unique across all of Google Cloud, so this is the exact name you set when you created the bucket. If you leave this field blank, ExpanDrive shows you all buckets your account has access to. If you only have access to a particular bucket or don't have the permissions to list the buckets for an account, you must add the *Bucket Name* in the connection setup within ExpanDrive. ### Folder If you want ExpanDrive to connect to a specific folder within your bucket rather than the root, enter the folder path here. Leave it blank to start at the top level of the bucket. # Google Drive ExpanDrive connects to Google's API and turns Drive into a fast network drive, making your entire account available from any app on your desktop. ExpanDrive uses a standard [OAuth flow](/security#understanding-oauth-2) to authenticate, so ExpanDrive has no access to your account credentials, only the authentication token returned by Google. ## Connection Parameters ### Nickname The nickname identifies this connection on your machine. This name is used as the volume label on the mounted drive. ### Account The account you used for authenticating is displayed. You cannot change this value. # Backblaze B2 Backblaze B2 Cloud Storage is an S3-Compatible object storage solution. ## Connection Parameters Enter the connection parameters for your Backblaze B2 Cloud Storage bucket. ### Key ID The B2 Key ID is your unique identifier for authentication. ### Application Key The Application Key is your private authentication key that pairs with your Key ID. Use a generated [Application Key](https://www.backblaze.com/docs/cloud-storage-application-keys), not the Master Application Key. The Master key is not S3-compatible. When you save your connection info in ExpanDrive, the Application Key is [securely stored](/security#authentication) within your local keychain. ### Nickname The nickname identifies the connection. This name will show up as the volume label on the mounted drive. # IDrive e2 IDrive e2 is an S3-Compatible object storage solution. The ExpanDrive integration with IDrive e2 allows you to connect to the service with a minimum of configuration. ## Connection Parameters ### Server This is the address at which the service can be reached. Every user in IDrive e2 has [their own unique region end-point](https://www.idrive.com/s3-storage-e2/region-endpoints) with access keys specific to those region end-points. ### Access Key The access key is your unique identifier for authentication. Keys can be generated from the Access Keys tab of the IDrive e2 account. ### Secret Key The secret key is your private authentication key that pairs with your access key. This is like a password. When you save your connection info in ExpanDrive, the secret key is [securely stored](/security#authentication) within your local keychain. ### Nickname The nickname serves to identify the connection. This name will show up as the volume label on the mounted drive. # Nextcloud ExpanDrive connects to Nextcloud, a fork of Owncloud, so you can manage files on your Nextcloud instance. ## Connection Parameters ### Server The base URL of the Nextcloud installation. This is a domain name, subdomain, or IP address, followed by the path where Nextcloud is installed. The path is typically `/nextcloud`, or the root of the server when Nextcloud is the only application running. For example, `https://example.com/nextcloud` or `https://cloud.example.com`. ### Username The username assigned for your access to the server. ### Password Your password is saved [securely](/security#authentication) in the macOS Keychain or the Windows credentials vault. ### Nickname The nickname identifies this connection on your machine. This name is used as the volume label on the mounted drive. # OneDrive [OneDrive](https://www.microsoft.com/en-us/microsoft-365/onedrive/online-cloud-storage) is Microsoft's consumer-grade cloud storage service. It gives you a place to store documents, photos, videos, and other files online, so they're accessible from any device. If you have a Microsoft account, you likely already have OneDrive storage available. The service works like Google Drive or Dropbox: files live on Microsoft's servers, and you can sync or access them from wherever you are. ExpanDrive lets you connect to your OneDrive storage so you can manage files directly from your desktop. This connector is for personal Microsoft accounts only. If you're connecting to a work or school account, use the [OneDrive for Business](/integrations/onedrive-for-business) connector instead. ## Connecting to OneDrive ExpanDrive connects to OneDrive using a standard [OAuth flow](/security#understanding-oauth-2), which means you won't enter your Microsoft password into ExpanDrive directly. Instead, you'll be redirected to Microsoft's login page, where you'll sign in and grant ExpanDrive permission to access your files. Microsoft handles the authentication and issues a token that ExpanDrive uses to connect on your behalf. ExpanDrive never has access to your Microsoft credentials. ### Nickname The nickname is the name that appears as the mounted volume on your computer. It's what you see in Finder (on Mac) or File Explorer (on Windows). # OneDrive for Business [OneDrive for Business](https://www.microsoft.com/en-us/microsoft-365/onedrive/onedrive-for-business) is Microsoft's cloud storage service for work and school accounts. It functions like personal [OneDrive](/integrations/onedrive), but it's tied to an organization's Microsoft 365 subscription rather than a personal Microsoft account. If you log in with a work or school address, that's the account you'll use here. Storage limits, sharing permissions, and data policies are typically managed by your organization's IT department rather than by you directly. Connecting ExpanDrive to OneDrive for Business lets you manage files directly from your desktop. If you're using a personal Microsoft account, use the [OneDrive](/integrations/onedrive) connector instead. ## Connecting to OneDrive for Business ExpanDrive connects to OneDrive for Business using a standard [OAuth flow](/security#understanding-oauth-2), which means you won't enter your Microsoft password into ExpanDrive directly. Instead, you'll be redirected to Microsoft's login page, where you'll sign in with your work or school account and grant ExpanDrive permission to access your files. Microsoft handles the authentication and issues a token that ExpanDrive uses to connect on your behalf. ExpanDrive never has access to your Microsoft credentials. ### Nickname The nickname is the name that will appear as the mounted volume on your computer. You'll see it in Finder on Mac or File Explorer on Windows. # SharePoint You can use ExpanDrive to connect to any combination of your SharePoint sites within a single connection. ExpanDrive uses a standard [OAuth flow](/security#understanding-oauth-2) to authenticate with SharePoint, so ExpanDrive has no access to your account credentials, only the authentication token returned by SharePoint. ## Connection Parameters ### Server When you add a new SharePoint connection, the OAuth flow will prompt you for your credentials, and automatically populate the server address for you. ### Site Choose one or more of the sites defined within your SharePoint to be accessible through the ExpanDrive connection. ### Account The account you used for authenticating to SharePoint is displayed. You cannot change this value. # Wasabi ExpanDrive offers a Wasabi integration to connect to your Wasabi buckets and manage your files. You only need to provide an access key id and secret access key. ## Connection Parameters The Wasabi connection in Expandrive provides parameters to control exactly what you're connecting to along with your credentials. ### Server This is the address at which the service can be reached. Wasabi provides different addresses [depending on your storage region](https://docs.wasabi.com/docs/what-are-the-service-urls-for-wasabi-s-different-storage-regions). Choose the service URL that matches your bucket location. ### Access Key Access keys are used to make secure requests to the Wasabi service API. The Wasabi Console allows you to [define access keys](https://docs.wasabi.com/docs/creating-a-user-account-and-access-key#assigning-an-access-key) for a user. An account can have only two access keys per user (two per root account and two per sub-user). The access key and secret key authenticate as a pair. Either one alone is not useful; together they grant full access to your S3 resources. ### Secret Key The secret key is your private authentication key that pairs with your access key. This is like a password. When you save your connection info in ExpanDrive, the secret key is [securely stored](/security#authentication) within your local keychain. ### Bucket This field lets you restrict what buckets the connection can access on your account. [Bucket level organization](/integrations/amazon-s3#bucket-level-organization) is a hallmark of S3-compatible services. If your credentials do not have access to list the buckets in your account, provide the bucket name in your connection parameters. ### Nickname The nickname serves to identify the connection. This name will show up as the volume label on the mounted drive. # WebDAV You can use ExpanDrive to connect to a WebDAV server using either HTTP or HTTPs. ## Connection Parameters ### Server The address of the server you are connecting to, including the protocol prefix, either `https://` or in rare circumstances `http://`. Check with your WebDAV provider for the URL to use. ### Username This is the username assigned for your access to the WebDAV server. ### Password Your password is saved [securely](/security#authentication) in the macOS Keychain or the Windows credentials vault. ### Remote path The remote path allows you to enter a path on the remote server which limits which directory will be the top-most directory visible through this connection. Specify the absolute path to the directory in the form `/home/user/inbox`. One reason to specify this path is to create a connection to a single specific directory, which can simplify operations on your computer, allowing you to interact directly with the mount folder rather than repeatedly opening subfolders. ### Nickname The nickname identifies this connection on your machine. This name is used as the volume label on the mounted drive. # Security ExpanDrive versions 2025 and earlier do not store your credentials (passwords, keys, and authentication tokens) in the Cloud. They are always stored on your machine in the [macOS keychain](https://support.apple.com/guide/keychain-access/what-is-keychain-access-kyca1083/mac) or the [Windows Credential Vault](https://support.microsoft.com/en-us/help/4026814/windows-accessing-credential-manager). We never have access to your credentials. We are working on a Web-based client for ExpanDrive that we intend to release in 2026. When we do, we will begin to store your credentials in the Cloud. We will provide clear notice when this transition occurs. ## Encryption ExpanDrive uses Transport Layer Security (TLS) wherever possible to encrypt data in transit. The only exception is plain unencrypted FTP, which transports data and credentials in plain text. Use FTPS or SFTP (SSH transport) instead of unencrypted FTP. ## Understanding OAuth2 Many cloud storage services use the OAuth2 protocol to authenticate users and issue applications like ExpanDrive an API key. ExpanDrive opens an embedded web browser that connects you directly to Microsoft, Google, Box, Dropbox, and others so that you authenticate with them. The ExpanDrive app never sees your credentials. After the embedded web-based authentication, the OAuth2 server issues a key that is stored on your machine. For Mac, this is the system keychain; on Windows, the Microsoft Windows Credential Manager. ExpanDrive never has access to the credentials you supply during the OAuth authentication process. OAuth authentication supports multi-factor authentication (MFA) flows and SSO like ADFS, Okta, Duo, and others with no additional setup. ### OAuth2 Walk-Through This example shows Google Drive, but the process is the same for OneDrive, OneDrive for Business, SharePoint, Dropbox, and Box. ![Authentication is performed using an embedded browser.](https://1753538908-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M1WQstUIV0CAuN58yGb%2F-M1WRQh5U9IrFLnxXHjd%2F-M1WRucvd13C0bM3ZIkj%2Fimage.png?alt=media\&token=3f00fca4-ef72-47d4-89ca-dc80a9ff0df0) ExpanDrive starts the authentication by connecting directly to Google via an embedded web browser view. The ExpanDrive app never captures the user's credentials. ![After authentication a user authorizes ExpanDrive to have API access](https://1753538908-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M1WQstUIV0CAuN58yGb%2F-M1WRQh5U9IrFLnxXHjd%2F-M1WRxvqD1I4ySXdGEEg%2Fimage.png?alt=media\&token=ed731afe-aaeb-4109-a0a6-54fee4333ab6) The web-based authentication grants the ExpanDrive app access to read and write from the user's Google Drive account on behalf of the user. New credentials (tokens or API keys) are created by Google to represent this grant. This is how ExpanDrive transforms a Google Drive account into a virtual drive. # Offline Sync ExpanDrive can perform an offline sync of any mounted drive, so you can keep working with files from your connections when your device isn't connected to the internet. ## How Offline Sync Works ExpanDrive must be running on your computer for Offline Sync to work. With the remote service connected, you can download files or folders from your connections to your local machine while you're online. After you disconnect from the network, you can keep making changes to those downloaded items as long as ExpanDrive is still running. When you reconnect, your changes are automatically synchronized to your remote storage. ## Using Offline Sync on Windows To enable Offline Sync for an item, right-click the file or folder in Windows Explorer (you can select multiple items) and choose **Offline sync > Local**. ![Context menu in Windows Explorer](https://1753538908-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M1WQstUIV0CAuN58yGb%2F-M1WSZOuiSxkEQ9H1dbU%2F-M1WTHBMFDJ4QAcqaqje%2Fimage.png?alt=media\&token=23ce2627-6dbc-44d9-bbf3-6e1a7b04a8ef) By default, all items mounted on ExpanDrive are Online Only, which requires an active connection to the remote service. Editing files and folders that are Online Only changes them directly within your remote connections in real time. To prepare for working offline, change the Offline Sync mode for the items to **Local**. ExpanDrive downloads the selected Local content to your computer. An internet connection is not required while you are working on Local content, but your ExpanDrive application must be running, and the connection must be in the **Connected** state. Any changes you make to Local data while offline are synced when your computer reconnects to the internet. ## Using Offline Sync on macOS ExpanDrive must be running on your system to use Offline Sync. To prepare for working offline, use the **Download Now** option in Finder to store a local copy of the folder or file on your computer. An internet connection is not required to make changes to downloaded items, but ExpanDrive must be running. You can change or remove any of the downloaded files using Finder. When you reconnect to the internet, changes you made while offline are synced to the remote system automatically. # Logs ExpanDrive logs connections and connection attempts to any of the integration types supported. These logs are saved locally and can be useful in troubleshooting connection issues. ## Locating ExpanDrive Logs ExpanDrive logs are stored in the following locations: * Windows: `%AppData%/ExpanDrive/logs` * Linux: `$XDG_CONFIG_HOME/ExpanDrive/logs` OR `~/.config/ExpanDrive/logs` * Mac: `~/Library/Logs/ExpanDrive` When our support team requests log files for troubleshooting, we recommend zipping the requested logs and then sending the zipped file. # Uninstalling ## Windows Uninstall ExpanDrive using the Windows Control Panel's standard methods for removing programs. ## macOS To remove ExpanDrive on your Mac, drag it to your trash can. ## Linux To remove ExpanDrive from a Debian or Ubuntu based distribution, use ``` sudo apt remove expandrive ``` For a RHEL, Fedora, or CentOS based distribution, use ``` sudo yum remove ExpanDrive ``` If you installed with an .AppImage file, remove the AppImage file to uninstall. # Web Management Console Paying customers receive access to the Web Management Console, which lets you manage, configure, and deploy a shared ExpanDrive configuration to large teams and groups of users. Use it when you want every device on a team to mount the same set of drives with the same settings, without configuring each device individually. Sign in to the Web Management Console from the ExpanDrive homepage. ## Configurations In the Web Management Console, a configuration is a pre-defined set of favorites and options for deployment to a group of users. Each configuration has a unique license key that retrieves the defined favorites and settings when activated. When that license key is entered during installation, ExpanDrive is fully configured as soon as installation completes. Each configuration contains a set of drives, app settings, and license settings. Create, update, and publish your configurations within the Web Management Console. Devices already activated with the configuration's license key receive the new published configuration automatically. ### Drive Settings Drive settings are defined the same way as connections within the client program, using the connection parameters of each connection type. When adding a drive to a configuration, you can enable the *Defer Authentication* option to mount a drive even if the user has not yet authenticated with that storage service. The user is prompted to authenticate the first time they interact with the drive. Defer Authentication is useful for services that use OAuth, where the user must complete the sign-in flow themselves. ### App Settings Use the App settings for a configuration to manage application-level options for the end user. OneDrive and SharePoint configurations support a single sign-on option where available. To enable SSO, add the domain of the end user's sign-on email address in the *Domain hint* field. ### License Settings Two global license settings control what users associated with the configuration can change. Enabling *Managed connections* prevents a user from adding or removing drives. Enabling *Managed settings* prevents a user from changing any of the settings you have pre-configured. ## Users The Users list lets you monitor which users are active, when they last used the connection, and which configuration they are assigned. You can manually create users by email address, or they are automatically added to the users list when they activate a configuration key (license key). You can change the configuration a user has assigned at any time, which is useful when a user moves from one team to another. You can also remove a user altogether. ### Device Count Each user in the Users list shows a device count, which is the number of distinct devices that have activated a configuration or license key for that user. Activating ExpanDrive with a configuration or license key on a new device adds one to that user's device count. The number of license seats used is the higher of your total user count or your total device count. If a user activates ExpanDrive on multiple devices, each device counts toward your plan's seat limit, not just the user. The Devices page lists every device that has activated ExpanDrive across your account. The list shows the *Last Seen* date to help you locate stale entries. You can disable any active device on the Devices page. Disabled devices are not included in your total device count. # ExpanDrive Server Edition ExpanDrive Server Edition is a way to run ExpanDrive as a system service for unattended or headless installations on Windows and Linux. Intel-based (x86 and x86\_64) systems are supported. You can mount a drive for all users of the system, including system processes. On Windows, you can also re-share cloud storage via SMB on the network, making your drives available to other users. Server instances are managed through the Server Edition page in the ExpanDrive [web management console](/web-management-console), where you can retrieve your server token, monitor active instances, and deactivate instances you no longer need. Each account supports up to 4 active server instances. ExpanDrive Server Edition requires a valid, current, [Paid License](/), and is not available or supported under our Free License. ## Legacy Licenses for ExpanDrive Server Edition Lifetime or perpetual licenses sold by the prior owner only apply to use of prior versions of ExpanDrive Server Edition (versions labeled 2023 or earlier), and do not include technical support from us. We have no idea where to get copies of those. The prior owner is no longer a going concern. # Installation ExpanDrive Server Edition is available for Windows and Linux. Only Intel-based (x86 and x86\_64) systems are supported. ARM and other architectures are not supported at this time. ## Windows Download the Windows MSI installer from the Server Edition page of the [web management console](/web-management-console). Both 64-bit and 32-bit builds are available. The installer is machine-wide and requires administrative rights. It registers the ExpanDrive Server Edition Windows service and installs the required kernel driver. The web configuration UI at `http://localhost:28080` is available immediately after installation completes. After installation, a setup prompt will ask you to [enter your server token](/expandrive-server-edition/setup#license-activation) to activate the instance. ### Silent Installation The installer is a standard MSI package and supports `msiexec` command-line arguments for unattended deployment: ```powershell msiexec /i windows_server_edition64_.msi ``` A 32-bit build (`windows_server_edition32_.msi`) is also available for systems that require it. Common options: * `/passive`: show progress only, no interactive prompts * `/quiet`: run fully silently * `/norestart`: do not restart automatically * `/l*v `: write a verbose install log For headless or scripted activation after a silent install, see the [CLI activation option in Setup](/expandrive-server-edition/setup#license-activation). ### Windows Explorer Visibility On a fresh Windows system, newly mounted drives may not appear in Windows Explorer for the currently signed-in user until that user signs out and signs back in. ## Linux ExpanDrive Server Edition for Linux is distributed as native packages: `.deb` for Debian and Ubuntu based distributions, and `.rpm` for RHEL, Fedora, and CentOS based distributions. Download the package for your distribution from the Server Edition page of the [web management console](/web-management-console). After installation completes, [activate your instance with your server token](/expandrive-server-edition/setup#license-activation). ### Debian and Ubuntu based distributions Install the downloaded `.deb` package through your graphical installer, or from the command line: ``` sudo apt install ./exfs__amd64.deb ``` ### RHEL, Fedora, and CentOS based distributions Install the downloaded `.rpm` package with `yum`: ``` sudo yum localinstall ./exfs--0.x86_64.rpm ``` Or with `dnf` (Fedora 22 and above): ``` sudo dnf install ./exfs--0.x86_64.rpm ``` # Setup ExpanDrive Server edition is configured through a locally hosted web server running at `http://localhost:28080`. ## Windows The MSI installer registers and starts the ExpanDrive Server Edition Windows service automatically. No manual service start is required. Once installation completes, the web configuration UI is available at `http://localhost:28080`. If you are accessing it remotely, connect via RDP or use SSH port forwarding. ## Linux ExpanDrive Server edition installs to `/opt/local/bin/exfs` and is generally already in the user's path. Start the built-in web server by running: `exfs --config` If you are connecting remotely to a headless instance, connect via SSH port forwarding: `ssh -L 28080:127.0.0.1:28080 yourserver.com` ## License Activation ExpanDrive Server Edition uses a server token for activation. To get your server token, log into the ExpanDrive [web management console](/web-management-console) and open the Server Edition page. To activate using the web management console, enter your server token at `http://localhost:28080/license`, and activate the license. For headless or scripted activation at the command line: ``` exfs --register ``` Once activated, the license refreshes automatically every hour. The server can remain offline for up to approximately 47 hours after the last successful check-in before the license is considered expired. ### Moving an Installation to a Different Machine Your server token is tied to your account and is used only for the first activation of a new server instance. After activation, the server uses a separate key for ongoing license check-ins for that specific machine. To move an installation to a different machine, deactivate the old instance in the web management console and activate the new one with your server token. ### Regenerating Your Server Token To invalidate your existing server token, regenerate it in the [web management console](/web-management-console). Regenerating the token does not affect currently active server instances, but activating new instances requires the new token. ## Remote Configuration ExpanDrive Server edition only listens on `localhost`, as it is not designed as a hardened service exposed to the public internet. Cloud storage providers including Google, Dropbox, Box, and Microsoft all require the OAuth flow to have a well-known redirect URL to land on with an authorization code at the end of the flow. Since `localhost` is the only well-known URL each machine shares, the redirect must land there. Use SSH port forwarding to redirect to your local machine and have the result captured by ExpanDrive running on your server: `ssh -L 28080:127.0.0.1:28080 yourserver.com` ## Drive Setup and Configuration Add each connection as a Drive within the local web interface at `http://localhost:28080`. Choose the type of provider and then authenticate. For providers that perform OAuth authentication, use SSH port forwarding to redirect to your local machine and have the result captured by ExpanDrive running on your server. ### Additional Drive Options for Windows On Windows, ExpanDrive Server Edition offers a few extra configuration options. #### Mount Type Your mount type can be a network drive (default), or a removable disk (appears as a removable storage device). Without a specific reason to change this, leave it as a network drive for the best performance. #### No Drive Letter You can choose not to mount the drive using a drive letter, and instead have it accessible only via UNC. Access the storage by browsing to `\\computername`. #### Share on Network On Windows, ExpanDrive Server Edition can automatically share your mount on the network, so other computers can connect to your machine and access the storage. All connecting computers share the same credentials you configured the drive for, so this isn't always optimal for a multi-user or multi-tenant setup. For Citrix or Terminal Services environments, use the regular installer that installs for all users, which gives each user their own isolated process and drive mappings. Configuration for the group is easier to manage through the [Web Management Console](/web-management-console). # CLI `exfs` is the ExpanDrive Server Edition executable. While it normally runs as a background service, it also accepts command-line invocations for scripted or headless environments. Each of the following is a separate command invocation. ## Help and Configuration `exfs --help` Print help. `exfs --config` Launch the web-based configuration interface on port 28080. ## Server Activation `exfs --register ` Activate Server Edition using a [server token](/expandrive-server-edition/setup#license-activation). ## Drive Management On Windows, admin rights are required for mount and unmount operations. `exfs --list` List all configured connections. `exfs --mount ` Mount a drive by name. `exfs --unmount ` Unmount a drive by name. `exfs --unmount-all` Unmount all drives. ## Service Behavior `exfs --foreground` Keep exfs in the foreground rather than running as a background service. `exfs --sync` Enable sync write operations. Use this when it is important that operations like delete, rename, and write do not complete until they have been propagated to remote storage. This is generally much slower since there is no opportunity to aggregate and parallelize multiple requests. # Strongsync and S3 Pro The functionality of Strongsync and S3 Pro have been merged into the main ExpanDrive application, and the main ExpanDrive application is now completely free for personal use! Read the [Pricing & Licenses](/) page for more information.