Support

Beta · updated 30 August 2026

Common questions

My drives are not showing in Finder

• macOS keeps file provider extensions switched off until you turn them on, and an app is not allowed to do it for you. Look in System Settings → General → Login Items & Extensions → File Providers and switch AllDrives on.
• If AllDrives shows a banner about a leftover folder, use Clear and retry. macOS will not create a drive while a folder of the same name is left over from a previous install, and the leftover goes to your Trash rather than being deleted.
• The menu bar has Re-add drives to Finder if a drive still will not appear. It re-registers everything; already-downloaded files become placeholders again and download when next opened.

Connecting Google Drive is asking for a lot

• That is the cost of there being no middleman. The permission has to belong to you, so Google requires the credentials to be created in your own project. AllDrives links to the exact pages in order.
• If Google says Error 403: access_denied, your project is still in testing — add your own address under Audience → Test users.
• If files never appear after connecting, the Drive API is probably not enabled on the project yet.

A file will not open, or opening is slow

• Files are placeholders until opened, so the first open downloads. A large file takes as long as your connection needs.
• If a drive shows as offline, check the status line at the bottom of the window — the background service may have stopped, and reopening AllDrives restarts it.

I lost my encrypted drive passphrase

• Those files cannot be recovered. Not by us, and not by your provider — nobody else ever had the key. This is what makes the encryption meaningful, and it is why the app asks you to confirm you have saved the passphrase before creating the drive.
• The files still exist on your provider as ciphertext; without the passphrase there is no way to turn them back into documents.

An assistant cannot see my drives

• Nothing is shared by default. Open Assistant access in AllDrives, turn on the master switch, and grant individual drives.
• Reading and writing are separate. A move between drives needs write access on both, because a move deletes the original.
• Everything the assistant did is listed in the same panel, and most of it can be undone there.

Removing AllDrives completely

• Delete the app, then ~/Library/Application Support/AllDrives and the AllDrives group container in ~/Library/Group Containers.
• Your cloud files are untouched by any of this — they were always in your own accounts.

Connecting a specific service

AllDrives supports around seventy storage services. The ones people use most have a guided walkthrough inside the app — S3, Google Drive, Dropbox, OneDrive, Backblaze B2, SFTP and WebDAV among them. For the rest, the app shows the exact fields that service needs and links here.

• Object storage (S3-compatible, Backblaze B2, Wasabi, Cloudflare R2, MinIO, Ceph): you need an access key ID, a secret access key, usually a region, and for non-AWS services an endpoint URL. Create the keys in that provider's console; AllDrives never sees them after they are stored.
• SFTP, SSH and WebDAV: host, port, username, and either a password or a private key. Self-hosted services have no console to link to, so the details come from whoever runs the server.
• Consumer clouds (Google Drive, Dropbox, OneDrive, pCloud, Box): these use OAuth, and because there is no middleman account, the credentials have to be created in your own developer console. The app links to the exact pages in order.

If a service will not connect, the error the provider returned is shown verbatim in the app — sending us that text is the fastest way to get it fixed.

Privacy and terms

Privacy policy · Terms of use