remotes

Manage Cloud Storage

Manage connections to cloud storage providers like Google Drive, OneDrive, Amazon S3, Backblaze B2, and Local storage.

Recommended: Use Your Own OAuth Credentials

For Google Drive and OneDrive, we recommend using remotes add oauth with your own Client ID and Secret. This way FileFortress never handles your tokens, and you control exactly which permissions to grant.

Google Drive OneDrive Amazon S3 Backblaze B2 Local

Subcommands

remotes add oauth RECOMMENDED Bring Your Own OAuth credentials

Connect Google Drive, OneDrive, or any OAuth-based provider using your own Client ID and Client Secret. This is the recommended approach for all OAuth providers.

Why use your own credentials?

  • Zero token exposure — FileFortress never sees your access or refresh tokens. The entire OAuth flow happens between your browser and the provider.
  • Full permission control — You choose exactly which scopes to grant. Need read-only? Done. Need full write access? Your call, no scrutiny.
  • No shared app limits — Your own Client ID has its own API quota, not shared with other FileFortress users.
# Interactive setup — prompts you for all details
filefortress remotes add oauth

# Non-interactive with all options specified
filefortress remotes add oauth --name "My Drive" --provider gdrive --client-id YOUR_ID --client-secret YOUR_SECRET

Options:

--name

Friendly name for this remote

--provider

e.g. gdrive, onedrive

--client-id

Your OAuth Client ID

--client-secret

Your OAuth Client Secret

Encryption Options Pro Tier

--encryption-type - RCloneStandard, RCloneObfuscate, Aes256Cbc, None
--encryption-password - Password for encryption
--encryption-salt - Optional salt for key derivation
remotes add LEGACY Provider-specific commands

Deprecation Notice: gdrive and onedrive

The remotes add gdrive and remotes add onedrive commands will be retired in a future release. Please use remotes add oauth instead — it gives you full control over your credentials and permissions, and FileFortress never touches your tokens.

Add a new cloud storage provider with provider-specific subcommands.

# Deprecated — use remotes add oauth instead
filefortress remotes add gdrive [--name "name"]
filefortress remotes add onedrive [--name "name"]

# Still current — S3-compatible providers
filefortress remotes add s3 --access-key KEY --secret-key SECRET
filefortress remotes add backblaze --key-id ID --application-key KEY
filefortress remotes add local --path PATH

Encryption Options Pro Tier

--encryption-type - RCloneStandard, RCloneObfuscate, Aes256Cbc, None
--encryption-password - Password for encryption
--encryption-salt - Optional salt for key derivation
remotes list List connected storage

Display all connected cloud storage accounts.

filefortress remotes list

Shows name, type, creation date, and last update time for each remote.

remotes show Show remote details

Display detailed information about a specific remote.

filefortress remotes show <remote_name_or_id>
remotes info Comprehensive remote information

Display comprehensive storage information including usage statistics.

filefortress remotes info <remote_name_or_id> [--refresh]

Shows account details, storage statistics, scan status, and cached vs live data.

remotes remove Remove cloud storage

Remove a connected cloud storage account.

filefortress remotes remove <remote_name_or_id>

Requires confirmation unless cancelled.

remotes scan Scan for files

Scan connected storage for files and update the index.

Scan a specific remote:

filefortress remotes scan <remote_name_or_id>

Fetches file information from the specified remote storage.

Scan all configured remotes:

filefortress remotes scan --all

Scans all connected remotes sequentially and displays aggregate statistics.

remotes enrich ENHANCED Enrich file metadata

Enhance file metadata with additional information from cloud providers.

filefortress remotes enrich [options]

Common Options:

--from-query, -q

Use a saved query

--remote, -r

Specific remote

--media-type

Filter by media type

--migrate-metadata NEW

Migrate to structured format

What Gets Extracted:

Identity: ETag, MD5/SHA256 hashes
Storage: Storage class, encryption status
Media: Duration, dimensions, camera info
Links: Web URLs, sharing links

Common Usage Examples

Add Google Drive (recommended): BYO-OAuth

filefortress remotes add oauth

Follow the interactive prompts. You'll provide your own Client ID and Secret — FileFortress never sees your tokens.

Add OneDrive (recommended): BYO-OAuth

filefortress remotes add oauth --provider onedrive --name "My OneDrive"

Connects OneDrive using your own Azure app credentials. You choose the permission scopes.

Add Amazon S3 (scripted):

filefortress remotes add s3 --non-interactive --access-key AKIA... --secret-key secret... --bucket my-bucket

Add encrypted Google Drive: Pro

filefortress remotes add oauth --provider gdrive --name "Encrypted Drive" --encryption-type RCloneStandard --encryption-password "mypassword"

Uses your own OAuth credentials plus rclone-compatible encryption on top.

List all connected storage:

filefortress remotes list

Enrich photos only:

filefortress remotes enrich --media-type Image --extension .jpg --extension .png

Enriches only image files with EXIF data and dimensions.

Migrate metadata: NEW

filefortress remotes enrich --migrate-metadata

Converts existing metadata to structured format without re-fetching.

Related Commands