# ExpanDrive Overview ExpanDrive mounts cloud storage and remote servers as native drives on macOS, Windows, and Linux. Files appear in Finder, File Explorer, and desktop applications alongside local files, so you can open, edit, save, and move remote content without learning a separate file-management interface. Files stream on demand instead of requiring a complete synchronized copy on your computer. When you need selected files without a network connection, ExpanDrive can keep them in a local offline cache and synchronize your changes after you reconnect. ExpanDrive is a Files.com product. The desktop application is free for personal use and organizations with up to 10 users or devices, while paid plans add team deployment, Server Edition, and support. ## ExpanDrive Basics Start with the product behavior that matters for your workflow: * [How ExpanDrive Works](/how-expandrive-works) explains mounted drives, on-demand file access, and the difference between ordinary online use and Offline Access. * [Installation and System Requirements](/installation-and-system-requirements) covers supported operating systems, downloads, updates, and removal. * [Connections](/connections) groups cloud content platforms, object storage, and file-transfer protocols by the kind of system being mounted. * [Offline Access](/offline-access) explains how to keep selected content available without a network connection. * [ExpanDrive Website](/expandrive-website) explains account registration, subscription and billing controls, Team Deployment, and access to Server Edition. ## One Drive for Cloud Storage and Remote Servers A single ExpanDrive installation can connect to multiple storage providers and servers at the same time. Each connection appears as a mounted drive and uses the provider's native authentication and API or a standard protocol such as SFTP, FTP, or WebDAV. [Connections](/connections) covers Amazon S3, Google Drive, Google Cloud Storage, OneDrive, SharePoint, Dropbox, Box, Backblaze B2, Wasabi, IDrive e2, Nextcloud, SFTP, FTP/FTPS, WebDAV, and other supported connection types. ## Desktop and Server Use Use the desktop application when a person needs remote files in Finder, File Explorer, or another application on a macOS, Windows, or Linux computer. [Offline Access](/offline-access) can keep selected content locally while the rest remains available on demand. Use [Server Edition](/server-edition) for unattended or headless Windows Server and Linux installations. It runs as a system service, can mount storage for system processes, and can re-share a mounted drive over SMB on Windows. The [ExpanDrive Website](/expandrive-website) is the account hub for ExpanDrive. Use it to create or upgrade an account, manage subscription and billing details, configure [Team Deployment](/expandrive-website/team-deployment), and access Server Edition downloads and activation controls. ## Security and Credentials ExpanDrive uses encrypted transport when the connection supports it. OAuth connections send the user to the storage provider for authentication rather than collecting the provider password inside ExpanDrive. [Security](/security) explains authentication, encryption, and the plain-FTP exception. ## Plans and Product Fit The Free license covers the desktop application within the limits described under [Pricing and Licenses](/pricing-and-licenses). The ExpanDrive Website is available for account and subscription management. Paid plans add Team Deployment, Server Edition, and technical support. Choose ExpanDrive when people or server processes need cloud storage to behave like a mounted drive. Choose [Files.com](https://www.files.com/) when you need a managed cloud file-orchestration platform for automations, hosted SFTP or AS2, centralized audit history, compliance reporting, or transfers between systems without mounting them as a local drive. # How ExpanDrive Works ExpanDrive presents remote storage as a mounted drive. The drive appears in Finder, File Explorer, or the Linux file manager, and desktop applications use ordinary file operations to open, edit, save, move, and remove remote content. ## Mounted Drives and Full Synchronization A mounted drive shows the remote directory structure without first copying the entire account, server, or bucket to the computer. ExpanDrive retrieves file data when an application needs it and uses a local cache for active content. It also maintains a separate directory-listing cache for each connection so ordinary browsing does not require a fresh remote listing for every action. This model makes large remote collections available without requiring enough local disk space for a complete mirror. ExpanDrive is therefore different from a conventional synchronization client. The remote service remains the primary location for online-only content, and the computer downloads the working set rather than every file. The mounted volume is available while ExpanDrive is running and the connection is connected. Disconnecting the connection or exiting ExpanDrive makes that volume unavailable until it is connected again. ### Windows Cache Locations ExpanDrive's file and directory-listing caches are per-user on Windows. On a computer used by several people, each Windows user has their own cache locations under their user profile. | Cache | Default location | | ---------------------------------------- | ---------------------------------------------------------------- | | File content | `%LOCALAPPDATA%\ExpanDrive\-\` | | Mounted-drive directory listings | `%LOCALAPPDATA%\ExpanDrive\-\exfs_files.db` | | Built-in file-browser directory listings | `%APPDATA%\ExpanDrive\IndexedDB\` | `` and `` identify the connection type and the individual connection. Each mounted drive's listing database is stored alongside that connection's file cache. The built-in file browser keeps its listings separately in `IndexedDB`, so its listing cache is distinct from the one used by the mounted drive. ## Online File Access When the computer is online, files that have not been selected for Offline Access remain online only. Opening one retrieves its data from the remote service. Changes to online-only items are written to remote storage through the configured provider API or protocol. Network speed, latency, the remote service, and the selected protocol still affect performance. A mounted remote file system does not have the same latency or availability as a local disk. ## Offline Access [Offline Access](/offline-access) downloads selected files or folders and keeps them available locally. You can work with that downloaded content while disconnected as long as ExpanDrive remains running. After the computer reconnects, ExpanDrive synchronizes the offline changes to the remote service. Offline Access is selective. Content that has not been downloaded still requires a connection to the remote service. ## Connections and Credentials Each mounted drive is a [connection](/connections) to one cloud account, object-storage service, or file server. A computer can have multiple connections at the same time, including multiple accounts from the same provider. ExpanDrive connects directly to the remote service. OAuth providers handle sign-in in their own authorization flow, while server and object-storage connections use the credentials required by their protocol. [Security](/security) explains transport encryption and credential storage. Most connection types can use a folder within the remote service as the root of the mounted drive. Connections can also be read-only when users should be able to open and download remote files without uploading, renaming, moving, or deleting them. ## File Browser and Provider Features ExpanDrive also includes a file browser for a connected drive. On a writable connection, the browser can upload, rename, move, and delete items, create folders, and accept files or folders by drag and drop. Some actions depend on capabilities supplied by the remote provider. Where the provider supports shareable links, ExpanDrive can request a link that points directly to the item in that remote service; ExpanDrive does not host the shared file. Where the provider exposes file-version history, ExpanDrive can display the available versions and download a selected version. On Windows, the ExpanDrive right-click menu provides *Copy Link*, *Previous Versions*, and *Offline Sync* where those actions apply. On Windows 11, select *Show more options* to reach that menu. ## Desktop, Team, and Server Operation The desktop application mounts drives for a person working on Windows, macOS, or Linux. [Team Deployment](/expandrive-website/team-deployment) distributes shared desktop configurations through the ExpanDrive Website. [Server Edition](/server-edition) runs as a system service for unattended Windows Server or Linux workloads. # Installation and System Requirements The following are the system requirements for ExpanDrive. ## Windows ExpanDrive supports Windows 10 and 11, and Windows Server 2016 or newer. Installation requires administrator permissions. Ordinary use and most desktop updates do not require administrator permissions. Windows can still display an administrator prompt when an update needs to install or repair the file-system driver or shell integration. [Download the latest 64-bit Windows installer](https://www.expandrive.com/api/download/expandrive?platform=win64) (`.exe`). Other Windows packages: * [32-bit installer](https://www.expandrive.com/api/download/expandrive?platform=win32\&ext=exe) (`.exe`) * [32-bit NuGet package](https://www.expandrive.com/api/download/expandrive?platform=win32\&ext=nupkg) (`.nupkg`) * [64-bit NuGet package](https://www.expandrive.com/api/download/expandrive?platform=win64\&ext=nupkg) (`.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) For a silent installation with a [Team Deployment](/expandrive-website/team-deployment) configuration, pass the configuration license key through the MSI's `LICENSE` property: ```batch msiexec /i "ExpanDrive.msi" /qn /norestart LICENSE="CONFIGURATION-KEY" ``` Replace `CONFIGURATION-KEY` with the key for the published configuration. This command installs ExpanDrive without an installation interface or an automatic restart. When the user does not already have a valid activation, ExpanDrive uses the supplied key to activate and retrieve the assigned drives and settings. The MSI registers ExpanDrive to launch when a user logs on to Windows. A separate logon script is not required for this startup behavior. Each drive mounts automatically when its [Connect Automatically](/connections/connection-creation-and-removal#automatic-connections) setting is enabled, though the user must still complete any required sign-in. The [Hide Window](/expandrive-website/team-deployment#app-settings) setting controls whether the main window appears at startup. ## macOS ExpanDrive supports macOS 11.0 or newer on Intel and Apple silicon Macs. [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. Choose the package format for your distribution: * [`.deb` package](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=deb) for Debian- and Ubuntu-based distributions * [`.rpm` package](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=rpm) for RHEL-, Fedora-, and CentOS-based distributions * [AppImage](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=AppImage) for other distributions [Linux Installation](/installation-and-system-requirements/linux-installation) covers package-manager commands, repository configuration, AppImage use, and signing-key updates. ## Application Updates ExpanDrive checks for updates at `updates.expandrive.com` using port 443. When automatic update checks are enabled, the desktop application checks shortly after startup and periodically while it remains open. You can also check manually from the application settings. Windows and macOS can download and apply a desktop update from the application. Linux notifies you when an update is available and opens the download page; install the new package through the appropriate package manager or replace the AppImage. The Windows MSI installer does not use the desktop automatic updater because it is intended for centrally managed deployments. On macOS, versions earlier than `2025.11.10` cannot complete an automatic update on modern macOS. Download and install the current build manually once; later releases can use the automatic update mechanism. ## Application Removal [Application Removal](/installation-and-system-requirements/application-removal) provides the uninstall procedure for Windows, macOS, and each supported Linux package format. # Linux Installation ## Debian- and Ubuntu-Based Distributions ### Simple Installation for Debian and Ubuntu For Debian- and Ubuntu-based distributions, download the latest [64-bit `.deb` package](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=deb) and install it through the graphical installer or with the following command: ```bash 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 configures the APT repository and code-signing key, so future updates use the system package manager. ### Manual Repository Installation for Debian and Ubuntu Use the manual repository installation when troubleshooting the `.deb` package, automating installation across multiple systems, or verifying the signing key before adding it to your system. Install the repository and key manually with the following commands: ```bash 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: ```bash 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 [64-bit `.rpm` package](https://www.expandrive.com/api/download/expandrive?platform=linux\&ext=rpm) and use YUM to install ExpanDrive and its required dependencies. ```bash 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 use the system package manager. ### Manual Repository Installation for RHEL, Fedora, and CentOS Use the manual repository installation when troubleshooting the `.rpm` package, automating installation across multiple systems, or verifying the signing key before adding it to your system. Install the yum repo manually with the following commands: ```bash 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): ```bash sudo dnf check-update sudo dnf install expandrive ``` or with `yum`: ```bash sudo 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: ```bash chmod +x ExpanDrive-*.AppImage ``` Run ExpanDrive and create a [connection](/connections/connection-creation-and-removal). ## ExpanDrive Signing Key During an update, the error `The following signatures were invalid: EXPKEYSIG` means the signing key on your system has expired. The following commands update the public key stored on your system. ### Debian- and Ubuntu-Based Distributions ```bash 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 ```bash sudo rpm --import https://packages.expandrive.com/keys/expandrive.asc ``` Once the key is updated, rerun the updater and the update completes without error. # Application Removal Remove ExpanDrive using the standard method for your operating system. ## Windows Uninstall ExpanDrive using the Windows Control Panel's standard methods for removing programs. Windows displays an *ExpanDrive Shell Extension Cleanup* administrator prompt while it removes the File Explorer integration. The desktop and taskbar can disappear briefly while Explorer restarts. If another application still has an ExpanDrive shell-extension file open, Windows can leave that locked file behind until the application exits or the computer restarts. ## macOS Drag ExpanDrive to the Trash. ## Linux To remove ExpanDrive from a Debian- or Ubuntu-based distribution, run: ```bash sudo apt remove expandrive ``` For a RHEL-, Fedora-, or CentOS-based distribution, run: ```bash sudo yum remove ExpanDrive ``` If you installed an `.AppImage` file, delete that file to uninstall ExpanDrive. # Connections ExpanDrive connects cloud storage, object storage, and file-transfer servers to your computer as mounted drives. Files remain in the remote service and are streamed on demand, so desktop applications can work with them through Finder, File Explorer, or the Linux file manager. ## Cloud Content Platforms Use [Cloud Content Platforms](/connections/cloud-content-platforms) for Box, Dropbox, Google Drive, Nextcloud, OneDrive, OneDrive for Business, and SharePoint. These services organize files around user or organization accounts and commonly use provider-managed sign-in flows. ## Object Storage Use [Object Storage](/connections/object-storage) for Amazon S3, Backblaze B2, Google Cloud Storage, IDrive e2, Wasabi, and other S3-compatible services. Object-storage connections commonly use buckets, service endpoints, regions, and access keys. ## File Servers and Protocols Use [File Servers and Protocols](/connections/file-servers-and-protocols) for SFTP, FTP/FTPS, and WebDAV. Prefer an encrypted connection whenever the server supports one. Each connection requires the account or server details appropriate to that provider. [Connection Creation and Removal](/connections/connection-creation-and-removal) explains the common lifecycle; the provider pages document the fields for each connection type. # Connection Creation and Removal A connection tells ExpanDrive which remote service to mount and how to authenticate to it. ## Connection Creation You can add multiple connections to the same service or to different services. Add new connections from the ExpanDrive application settings. After you select a connection type, ExpanDrive prompts you for the required settings. Each connection type has its own page with the parameters it needs — see [SFTP](/connections/file-servers-and-protocols/sftp), [Amazon S3](/connections/object-storage/amazon-s3), and the other per-service pages in this section. After you save the connection, ExpanDrive mounts it and displays its contents. ### Automatic Connections Enable *Connect Automatically* for a connection to mount it when ExpanDrive starts. This makes frequently used drives available without manually connecting them each time. The user must still complete any sign-in required by the storage service. On Windows, the [MSI installer](/installation-and-system-requirements#msi-installer) registers ExpanDrive to launch at user logon. With Connect Automatically enabled, configured drives can mount as part of that startup without a separate logon script. ### Starting Folder Most connection types let you choose a folder within the remote service as the root of the mounted drive. Use this setting when the connection should expose only a particular folder, bucket path, or server directory instead of the service's default root. The exact field name varies by connection type. The page for that provider or protocol identifies the applicable setting. ### Read-Only Connections Set a connection to read-only when users should be able to browse, open, and download remote content without changing it. A read-only connection prevents uploads, renames, moves, deletions, and other write operations through both the mounted volume and ExpanDrive's file browser. ### Windows Drive Letters 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. ## Connection Removal You can remove your defined connections from the ExpanDrive application settings. If you've used [Offline Access](/offline-access) 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. # Cloud Content Platforms Cloud content platforms organize files around a personal account, an organization, or a Microsoft 365 site. ExpanDrive mounts the selected account or site as a drive while the provider remains the system that controls access and stores the files. * [Box](/connections/cloud-content-platforms/box) supports personal and business accounts. * [Dropbox](/connections/cloud-content-platforms/dropbox) supports personal and Dropbox Business accounts, including multiple accounts on one computer. * [Google Drive](/connections/cloud-content-platforms/google-drive) mounts a Google Drive account. * [Nextcloud](/connections/cloud-content-platforms/nextcloud) connects to a customer-selected Nextcloud server. * [OneDrive](/connections/cloud-content-platforms/onedrive) is for personal Microsoft accounts. * [OneDrive for Business](/connections/cloud-content-platforms/onedrive-for-business) is for work and school Microsoft accounts. * [SharePoint](/connections/cloud-content-platforms/sharepoint) can expose one or more sites through one connection. Box, Dropbox, Google Drive, OneDrive, OneDrive for Business, and SharePoint use provider-managed OAuth authorization. Nextcloud uses the server address and account credentials for the selected instance. See [Security](/security) for credential storage and OAuth behavior. # Box You can connect ExpanDrive to a personal or business Box account. Business accounts can use the single sign-on flow configured by the organization. ExpanDrive uses [OAuth authentication](/security#oauth-authentication). You sign in with Box, which returns a token that ExpanDrive stores in your operating system's credential store. ## 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 connect ExpanDrive to a personal or Dropbox Business account. ExpanDrive uses [OAuth authentication](/security#oauth-authentication). You sign in with Dropbox, which returns a token that ExpanDrive stores in your operating system's credential store. ## 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. ## 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 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 [OAuth authentication](/security#oauth-authentication). You sign in with Google, which returns a token that ExpanDrive stores in your operating system's credential store. ## 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. # Nextcloud ExpanDrive mounts a Nextcloud instance as a drive so you can work with its files from desktop applications. ## 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 ExpanDrive stores the password in your operating system's [credential store](/security#credential-storage). ### 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 cloud storage service for personal accounts. 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](/connections/cloud-content-platforms/onedrive-for-business) connector instead. ## OneDrive Authentication ExpanDrive uses [OAuth authentication](/security#oauth-authentication). You sign in with Microsoft and authorize ExpanDrive to access your files. Microsoft returns a token that ExpanDrive stores in your operating system's credential store. ### Nickname The nickname appears as the mounted volume name in Finder on macOS 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 is tied to an organization's Microsoft 365 subscription, and the organization's administrators control its storage, sharing, and data policies. 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](/connections/cloud-content-platforms/onedrive) connector instead. ## OneDrive for Business Authentication ExpanDrive uses [OAuth authentication](/security#oauth-authentication). You sign in with your work or school account and authorize ExpanDrive to access your files. Microsoft returns a token that ExpanDrive stores in your operating system's credential store. ### Nickname The nickname appears as the mounted volume name in Finder on macOS 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 [OAuth authentication](/security#oauth-authentication). You sign in with Microsoft, which returns a token that ExpanDrive stores in your operating system's credential store. ## Connection Parameters ### Server When you add a SharePoint connection, the OAuth flow prompts you to sign in and then fills in the server address. ### 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. # Object Storage Object-storage services organize data in buckets and commonly authenticate with access keys, OAuth, or temporary credentials. A connection can expose all accessible buckets or start at a specific bucket or folder when the provider and credentials support that scope. * [Amazon S3](/connections/object-storage/amazon-s3) also documents several services that use the S3 API. * [Backblaze B2](/connections/object-storage/backblaze-b2) uses a B2 Key ID and Application Key. * [Google Cloud Storage](/connections/object-storage/google-cloud-storage) uses Google OAuth and can start at a specific bucket or folder. * [IDrive e2](/connections/object-storage/idrive-e2) uses a regional endpoint and access-key pair. * [Wasabi](/connections/object-storage/wasabi) uses a regional service URL and access-key pair. Use credentials limited to the buckets and actions the mounted drive requires. Supplying a bucket name is also necessary when the credentials can access a bucket but cannot list every bucket in the account. # 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 identifies the service endpoint, credentials, region, and optional bucket to mount. ### 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 the connection, ExpanDrive stores the secret key in your operating system's [credential store](/security#credential-storage). ### 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. ## 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](/connections/object-storage/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. # Backblaze B2 Backblaze B2 Cloud Storage is an S3-compatible object storage service. ## 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 the connection, ExpanDrive stores the Application Key in your operating system's [credential store](/security#credential-storage). ### Nickname The nickname identifies the connection and appears as the volume label on the mounted drive. # Google Cloud Storage [Google Cloud Storage](https://cloud.google.com/storage) is Google's object storage service. Like [Amazon S3](/connections/object-storage/amazon-s3), it organizes objects in buckets and controls access through cloud identities and permissions. ExpanDrive can connect to your Google Cloud Storage so you can interact with the contents of your buckets directly from your desktop. ## Google Cloud Storage Authentication ExpanDrive uses [OAuth authentication](/security#oauth-authentication). You sign in with Google and authorize ExpanDrive to access your storage. Google returns a token that ExpanDrive stores in your operating system's credential store. 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. # IDrive e2 IDrive e2 is an S3-compatible object storage service. ExpanDrive mounts an IDrive e2 bucket using its regional endpoint and access keys. ## Connection Parameters ### Server Enter the [regional endpoint](https://www.idrive.com/s3-storage-e2/region-endpoints) for your IDrive e2 account. Access keys are specific to the endpoint where they were created. ### 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 the connection, ExpanDrive stores the secret key in your operating system's [credential store](/security#credential-storage). ### Nickname The nickname identifies the connection and appears as the volume label on the mounted drive. # Wasabi ExpanDrive connects to Wasabi buckets using an access key ID and secret access key. ## Connection Parameters The connection settings identify the Wasabi endpoint, credentials, and optional bucket to mount. ### 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 the connection, ExpanDrive stores the secret key in your operating system's [credential store](/security#credential-storage). ### Bucket This field lets you restrict which bucket the connection can access. See [Bucket-Level Organization](/connections/object-storage/amazon-s3#bucket-level-organization) for more information. 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. # File Servers and Protocols ExpanDrive can mount a file server through SFTP, FTP/FTPS, or WebDAV. These connections use a server address, account credentials, and optional remote path rather than a cloud provider's account picker. * [SFTP](/connections/file-servers-and-protocols/sftp) uses SSH and supports passwords, OpenSSH private keys, and SSH agents. * [FTP/FTPS](/connections/file-servers-and-protocols/ftp-ftps) supports unencrypted FTP and FTP protected with TLS. * [WebDAV](/connections/file-servers-and-protocols/webdav) supports HTTP and HTTPS endpoints. Use SFTP, fully encrypted FTPS, or HTTPS-based WebDAV when the server offers it. Plain FTP, login-only FTPS, and HTTP WebDAV can leave file contents unencrypted. [Security](/security) explains the transport implications. # SFTP ExpanDrive mounts an SFTP server as a drive on macOS, Windows, or Linux, making its contents available to desktop applications through the operating system's file manager. ## 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 supports passwords, SSH keys, and external SSH agents such as Pageant on Windows or `ssh-agent` on macOS and Linux. #### Password Authentication Providing a username and password is the default authentication option for an SFTP connection. ExpanDrive stores the password in your operating system's [credential store](/security#credential-storage). If the server requires additional authentication, ExpanDrive prompts for it when connecting. #### 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 supports private keys in OpenSSH format. If you have a PuTTY `.ppk` file, convert it to OpenSSH format or use SSH agent authentication. ExpanDrive does not generate SSH keys. Use a utility such as PuTTYgen on Windows or `ssh-keygen` on macOS or Linux to create a key pair. #### SSH Agent Authentication SSH agents manage SSH keys and their passphrases for you. This is particularly helpful when you use multiple key pairs to connect to different servers. ExpanDrive uses Pageant on Windows or the built-in `ssh-agent` on macOS and Linux. Add the required keys to the agent before connecting with ExpanDrive. When you select SSH Agent authentication, ExpanDrive communicates with the agent to establish the SFTP connection. ### Port If you do not specify a port, ExpanDrive connects on port `22`. Enter a different value only when the server requires it. ### Remote Path The remote path sets the top-level directory visible through this connection. Enter an absolute path 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 identifies the connection and appears as the volume label on the mounted drive. # FTP/FTPS FTP, or File Transfer Protocol, transfers files between a client and server. ExpanDrive also supports FTPS, which protects FTP with TLS. FTPS is different from [SFTP](/connections/file-servers-and-protocols/sftp), which transfers files over SSH and supports SSH key authentication. ## 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 Enter the password for the FTP account. ExpanDrive stores it in your operating system's [credential store](/security#credential-storage). ### 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, the connection is unencrypted. Credentials and file contents are sent in plaintext. Avoid this option unless it is the only connection type the server accepts. #### 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 If you do not specify a port, ExpanDrive connects on port `21`. Enter a different value only when the server requires it. ### Remote Path The remote path sets the top-level directory visible through this connection. Enter an absolute path 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. # WebDAV You can connect ExpanDrive to a WebDAV server over HTTP or HTTPS. Use HTTPS whenever the server supports it. ## Connection Parameters ### Server Enter the server address, including the `https://` or `http://` prefix. Check with your WebDAV provider for the correct URL. ### Username This is the username assigned for your access to the WebDAV server. ### Password ExpanDrive stores the password in your operating system's [credential store](/security#credential-storage). ### Remote Path The remote path sets the top-level directory visible through this connection. Enter an absolute path 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 opening subfolders. ### Nickname The nickname identifies this connection on your machine. This name is used as the volume label on the mounted drive. # Offline Access 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. Offline Access is available on Windows and macOS. It is not available in ExpanDrive for Linux. ## Offline Access Behavior 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. ## Windows To enable Offline Sync for an item, right-click the file or folder in File Explorer. You can select multiple items. Choose *Offline sync > Local*. On Windows 11, this action can appear under *Show more options* in the right-click menu. ![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, mounted items are *Online Only* and require an active connection to the remote service. Changes to these items are written directly to remote storage. To prepare for working offline, change the selected items to *Local*. ExpanDrive downloads their contents to your computer. An internet connection is not required while you work on local content, but ExpanDrive must remain running. Any changes you make to Local data while offline are synced when your computer reconnects to the internet. ## macOS ExpanDrive must be running on your system to use Offline Sync. To prepare for working offline, use *Download Now* in Finder to store a local copy of the file or folder. 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. # ExpanDrive Website The [ExpanDrive Website](https://teams.expandrive.com/) is the account hub for ExpanDrive. It is where you create or sign in to an ExpanDrive account, establish or change a subscription, manage billing, configure a team deployment, and access Server Edition downloads and activation controls. Older material may refer to this site as ExpanDrive for Teams or the Web Management Console. The site is not limited to Team Deployment or to customers who already have a paid subscription. You can create an account and use the subscription and billing area before upgrading. Features such as Team Deployment and Server Edition require a current paid license. ## Account and Subscription Create an ExpanDrive account or [sign in to the ExpanDrive Website](https://teams.expandrive.com/). An account administrator can add billing information and upgrade a free account from the website. For a paid account, the website shows the current subscription, account balance, payment history, and downloadable invoice PDFs. Administrators can update the payment method or cancel and resume automatic renewal. See [Subscription and Billing](/expandrive-website/subscription-and-billing). ## Team Deployment [Team Deployment](/expandrive-website/team-deployment) provides shared connection and application configurations for multiple users and devices. Administrators can publish configurations, assign users, review activated devices, and control whether users can change managed connections and settings. ## Server Edition The Server Edition area provides Windows and Linux package downloads, the server token used to activate a new instance, and the list of active instances. Administrators can deactivate an instance that is no longer in use or regenerate the account's server token. See [Server Edition](/server-edition). # Subscription and Billing The [ExpanDrive Website](https://teams.expandrive.com/) is where an account administrator establishes and manages an ExpanDrive subscription. You can create an ExpanDrive account before purchasing a subscription. From the subscription and billing area, an administrator can enter billing details and upgrade the account to a paid plan. Purchasing a paid plan enables the paid features associated with that account; it does not create a separate Team Deployment account or Server Edition account. For a paid account, the subscription and billing area shows: * the current subscription * the account balance * payment history * downloadable invoice PDFs An administrator can also update the payment method or cancel and resume automatic renewal. [Pricing and Licenses](/pricing-and-licenses) explains the Free and paid license boundaries, seat counting, support, and legacy licenses. # Team Deployment Team Deployment gives an organization one place to define ExpanDrive connections and application settings for multiple users and devices. It is available with a [paid license](/pricing-and-licenses) through the [ExpanDrive Website](/expandrive-website). An administrator creates a configuration containing drives, app settings, and license controls, then publishes it. A configuration license key associates an ExpanDrive installation with that configuration. Published changes are applied to devices that use the key. Connections can defer authentication when each user must complete the provider's sign-in flow. Administrators can also prevent users from adding or removing managed drives or changing managed application settings. ## Configurations A configuration is a predefined set of drives and options for a group of users. Each configuration has a unique license key that retrieves those drives and settings when activated. For centrally managed Windows installations, the [MSI installer](/installation-and-system-requirements#msi-installer) accepts the configuration key through its `LICENSE` property, including during a silent installation. ExpanDrive uses that key to activate and retrieve the assigned drives and settings when the user does not already have a valid activation. Each configuration contains drive settings, app settings, and license settings. Create, update, and publish configurations in the ExpanDrive Website. Devices activated with the configuration's license key periodically retrieve the published configuration. Local changes to managed items are temporary and are replaced by the published configuration after a successful check-in. ### Drive Settings Drive settings are defined the same way as connections within the client program, using the parameters of each connection type. Enable [Connect Automatically](/connections/connection-creation-and-removal#automatic-connections) for drives that should mount when ExpanDrive starts. This lets users access their configured drives after logon without manually connecting each one. Any required sign-in still needs to be completed. When adding a drive to a configuration, you can enable *Defer Authentication* to mount a drive before the user has authenticated with that storage service. The user is prompted to authenticate the first time they interact with the drive. Defer Authentication is useful for OAuth services where each user must complete their own sign-in flow. ### App Settings Use the app settings for a configuration to manage application-level options for the end user. The *Hide Window* setting starts ExpanDrive with its main window hidden, so users can work with their mounted drives without the application window opening at each launch. This setting can be supplied through the desktop app's settings file or a Team Deployment configuration. Enable [Managed settings](#license-settings) to prevent users from changing the settings supplied by the configuration. For drives to mount at startup, also enable their *Connect Automatically* setting. OneDrive and SharePoint configurations support a single sign-on option where available. To enable SSO, add the domain of the end user's sign-in 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 settings supplied by the configuration. ## Users The *Users* list shows which users are active, when they last used ExpanDrive, and which configuration they are assigned. You can create users by email address. Users are also added automatically when they activate a configuration license key. You can change a user's assigned configuration or remove the user. ## Devices and Seat Count Each user in the Users list has a device count showing the number of distinct devices that have activated a configuration or license key for that user. Activating ExpanDrive on another device adds that device to the count. The number of license seats used is the higher of the account's total user count or total device count. If one user activates ExpanDrive on multiple devices, each device can count toward the plan's seat limit. The *Devices* page lists active desktop devices, including their assigned user, configuration, platform, and *Last Seen* date. The Last Seen value is informational; inactive devices do not expire from the list automatically. Disable a stale device from this page when it should no longer count as active. The record remains in account history, but the disabled device is not included in the active device count. # Server Edition ExpanDrive Server Edition runs ExpanDrive as a system service for unattended or headless Windows and Linux installations. It supports Intel-based x86 and x86\_64 systems. 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 controlled from the Server Edition area of the [ExpanDrive Website](/expandrive-website). From there, you can download the installers, retrieve the server token, monitor active instances, and deactivate instances you no longer need. Each account supports up to four active server instances. ExpanDrive Server Edition requires a current [paid license](/pricing-and-licenses). It is not available or supported with a Free license. ## Server Operation [Server Installation](/server-edition/server-installation) covers Windows and Linux packages. [Server Configuration](/server-edition/server-configuration) covers activation, remote access to the local configuration interface, connections, and Windows-specific mount options. [Command-Line Interface](/server-edition/command-line-interface) lists the supported `exfs` commands for activation, mount control, foreground operation, and synchronous writes. Server Edition does not update itself automatically. Upgrade it by installing a newer MSI, DEB, or RPM package as described under [Server Installation](/server-edition/server-installation#server-updates). ## Legacy Licenses for ExpanDrive Server Edition Lifetime or perpetual licenses sold by the prior owner apply only to ExpanDrive Server Edition versions labeled 2023 or earlier. The current ExpanDrive team does not distribute those installers or provide technical support for them, and the prior owner is no longer involved with ExpanDrive. # Server Installation ExpanDrive Server Edition is available for Windows and Linux on Intel-based x86 and x86\_64 systems. ARM and other architectures are not supported. ## Windows Download the Windows MSI installer from the Server Edition area of the [ExpanDrive Website](/expandrive-website). Both 64-bit and 32-bit builds are available. The installer is machine-wide, installs into `C:\Program Files\ExpanDrive\Server`, 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 configuration prompt will ask you to [enter your server token](/server-edition/server-configuration#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 [command-line activation option](/server-edition/server-configuration#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 a `.deb` package for Debian- and Ubuntu-based distributions and an `.rpm` package for RHEL-, Fedora-, and CentOS-based distributions. It requires a systemd-based distribution and FUSE 2; a desktop environment is not required. Download the package for your distribution from the Server Edition area of the [ExpanDrive Website](/expandrive-website). After installation completes, [activate your instance with your server token](/server-edition/server-configuration#license-activation). ### Debian- and Ubuntu-Based Distributions Install the downloaded `.deb` package through your graphical installer, or from the command line: ```bash sudo apt install ./linux-server-edition__amd64.deb ``` ### RHEL-, Fedora-, and CentOS-Based Distributions Install the downloaded `.rpm` package with `yum`: ```bash sudo yum localinstall ./linux-server-edition--1.x86_64.rpm ``` Or with `dnf` (Fedora 22 and above): ```bash sudo dnf install ./linux-server-edition--1.x86_64.rpm ``` The package installs the `expandrive_server.service` configuration service and enables it automatically. Each mounted connection runs as an additional `expandrive@.service`. By default, mounted drives appear under `/mnt/expandrive/`. ## Server Updates Server Edition does not have an automatic-update flow. Download a newer package from the ExpanDrive Website and install it over the existing version with the same package method used for the initial installation. On Windows, uninstalling Server Edition removes the Windows services and installed application but intentionally preserves configuration and operational data under `C:\ProgramData\ExpanDrive`. # Server Configuration Configure ExpanDrive Server Edition through its local web interface 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 the executable at `/usr/bin/exfs`. The package enables and starts the `expandrive_server.service` configuration service automatically, so the local web interface is normally available immediately after installation. ```bash sudo systemctl status expandrive_server.service ``` If you are connecting remotely to a headless instance, connect via SSH port forwarding: ```bash ssh -L 28080:127.0.0.1:28080 yourserver.com ``` ## Server Data Server Edition stores its license, drive definitions, and logs in a machine-wide location because it runs as a system service. | Data | Windows | Linux | | ----------------- | ------------------------------------------ | ----------------------------------------- | | License | `C:\ProgramData\ExpanDrive\license.json` | `/root/.config/ExpanDrive/license.json` | | Drive definitions | `C:\ProgramData\ExpanDrive\favorites.json` | `/root/.config/ExpanDrive/favorites.json` | | Logs | `C:\ProgramData\ExpanDrive\logs` | `/root/.config/ExpanDrive/logs` | Create and change drives through the local web interface instead of editing `favorites.json` manually. [Logs](/logs#server-edition-log-locations) describes the daily log files and Linux service diagnostics. ## License Activation ExpanDrive Server Edition uses a server token for activation. To retrieve it, sign in to the [ExpanDrive Website](/expandrive-website) and open the Server Edition area. To activate through the local web interface, open `http://localhost:28080/license`, enter the server token, and activate the license. For headless or scripted activation at the command line: ```bash exfs --register ``` On Linux, run registration with the same system privileges used by the service so the license is written to the machine-wide path: ```bash sudo /usr/bin/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. ### Installation Transfer 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. The activated license is bound to the server hostname. To move an installation to another machine or change the hostname, deactivate the old instance in the ExpanDrive Website and activate the new hostname with your server token. Copying the license file does not transfer the activation. ### Server Token Regeneration To invalidate your existing server token, regenerate it in the [ExpanDrive Website](/expandrive-website). Regenerating the token does not affect currently active server instances, but activating new instances requires the new token. ## Remote Configuration ExpanDrive Server Edition listens only on `localhost`. Do not expose the configuration interface directly to the public internet. When configuring a remote server, forward port `28080` over SSH. This lets you open the server's local interface from your computer and complete OAuth redirects through `localhost` without exposing the interface publicly: ```bash ssh -L 28080:127.0.0.1:28080 yourserver.com ``` ## Drive Configuration Add each connection as a drive in 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 credentials configured for the drive. Do not use this arrangement when each user or tenant needs an isolated identity. 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. For centrally managed desktop installations, use [Team Deployment](/expandrive-website/team-deployment) instead of sharing one Server Edition mount among users who require separate identities. # Command-Line Interface `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 command help. * `exfs --config` — Launch the web configuration interface on port `28080`. ## Server Activation * `exfs --register ` — Activate Server Edition using a [server token](/server-edition/server-configuration#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 instead of running it as a background service. * `exfs --sync` — Enable synchronous write operations. Deletes, renames, and writes do not return as complete until they have reached remote storage. This mode is slower because ExpanDrive cannot aggregate and parallelize as many requests. # Security ExpanDrive connects your computer directly to each storage provider. It does not proxy file traffic through ExpanDrive infrastructure. ## Encryption ExpanDrive uses Transport Layer Security (TLS) or the connection protocol's native encryption when the selected service and connection settings support secure transport. Plain FTP and endpoints configured with `http://` send credentials and file contents without encryption. Use FTPS, SFTP, or HTTPS whenever the server supports them. If an unencrypted protocol is unavoidable, protect the connection with a VPN or another encrypted network layer. ## Credential Storage ExpanDrive stores passwords, SSH keys, and OAuth tokens in the operating system's credential store: [macOS Keychain](https://support.apple.com/guide/keychain-access/what-is-keychain-access-kyca1083/mac), Windows Credential Manager, or the equivalent system credential store on Linux. It does not write these credentials to a plaintext configuration file or transmit them to ExpanDrive servers. ## OAuth Authentication Cloud storage services such as Microsoft, Google, Box, and Dropbox use OAuth 2.0 to authorize applications. ExpanDrive opens the provider's sign-in flow in an embedded browser, so you authenticate directly with the provider and ExpanDrive does not receive your password. After authentication, the provider issues a scoped token that ExpanDrive stores in the operating system's credential store. The provider's sign-in flow can include multi-factor authentication and single sign-on through services such as Microsoft Entra ID, ADFS, Okta, Duo, or Google Workspace. ### OAuth Example 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, the user authorizes ExpanDrive to access Google Drive.](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. Google creates an OAuth token to represent this authorization. This is how ExpanDrive transforms a Google Drive account into a virtual drive. # Logs ExpanDrive records startup events, connection activity, connection attempts, and operational status messages. These human-readable logs are stored locally and can help troubleshoot connection and application problems. Logs rotate daily. The file for the mounted-file-system component is named `exfs-YYYY-MM-DD.log`. The desktop interface can also write `ExpanDrive - YYYY-MM-DD.log`. ## Desktop Log Locations ExpanDrive logs are stored in the following locations: * Windows: `%AppData%/ExpanDrive/logs` * Linux: `$XDG_CONFIG_HOME/ExpanDrive/logs` or `~/.config/ExpanDrive/logs` * macOS: `~/Library/Logs/ExpanDrive` The application includes an option to open the log folder. ## Server Edition Log Locations Server Edition runs as a machine-wide service, so its logs are stored separately from a desktop user's logs: * Windows: `C:\ProgramData\ExpanDrive\logs\exfs-YYYY-MM-DD.log` * Linux: `/root/.config/ExpanDrive/logs/exfs-YYYY-MM-DD.log` On Linux, you can also inspect the configuration service through systemd: ```bash sudo systemctl status expandrive_server.service sudo journalctl -u expandrive_server.service ``` When Support requests logs, reproduce the problem if possible and note the date and approximate time. Compress the requested files into a ZIP archive before sending them. # Pricing and Licenses ExpanDrive changed ownership in 2024. The current licensing and support model launched in April 2025, and the prior owner is no longer involved with ExpanDrive. ## Free License The main ExpanDrive application for Windows, macOS, and Linux is free for personal use and for organizations with up to 10 users or devices. The [ExpanDrive Website](/expandrive-website) is available for account registration and subscription management. The Free license does not include direct technical support, Team Deployment, or ExpanDrive Server Edition. ## Paid Licenses Paid licenses are available to anyone and are required when an organization exceeds 10 users or devices. Paid licenses include access to the main ExpanDrive application, [Team Deployment](/expandrive-website/team-deployment), ExpanDrive Server Edition, and technical support. Subscription and billing controls for the paid account remain in the ExpanDrive Website. A paid license costs $29 per month and includes 10 seats. Used seats are calculated from whichever is higher: your total user count or your [total device count](/expandrive-website/team-deployment#devices-and-seat-count), since one 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 recurring subscriptions. Lifetime or perpetual licenses are not offered under the current licensing model. Systems with a paid license contact the license server at `teams.expandrive.com` on port `443` to check license validity. For the current plan comparison and purchasing options, see [ExpanDrive pricing](https://www.expandrive.com/pricing). [Subscription and Billing](/expandrive-website/subscription-and-billing) explains the account controls for upgrading, invoices, payment methods, and renewal. ## Legacy Licenses Lifetime or perpetual licenses sold by the prior owner apply only to prior versions of ExpanDrive labeled 2023 or earlier. They do not include technical support from the current ExpanDrive team. ## Support Technical support is available to current paid-license customers. The Free license includes community support. # Legacy Strongsync and S3 Pro Strongsync and S3 Pro functionality is now part of the main ExpanDrive application. ExpanDrive is free for personal use. Read [Pricing and Licenses](/pricing-and-licenses) for more information.