cloud migration

How to back up OneDrive to Backblaze B2

Aug 4, 2026

OneDrive is good at keeping files available across your devices. It is not a separate backup. A deleted folder, a compromised account, or a bad sync can reach every device connected to the same account.

Backblaze B2 gives you a copy outside Microsoft's ecosystem. Blober can now read OneDrive through Microsoft Graph and write those files directly to B2, so you do not need to download the whole library first.

Why the desktop folder is a poor backup source

OneDrive Files On-Demand keeps online-only files as placeholders on your disk. They look like ordinary files in Finder or File Explorer, but the content stays in Microsoft's cloud until something opens the file.

That saves disk space. It also means a backup tool that reads only the local OneDrive folder may see a placeholder instead of the file itself. The usual workaround is to select "Always keep on this device" and wait for OneDrive to download everything. For a large account, that can take hours and may not fit on the computer at all.

Blober avoids the local folder. It requests each file from OneDrive through Microsoft Graph, then streams it to Backblaze B2 through your computer. Files On-Demand does not enter the path.

Why use B2 for a OneDrive backup

The useful part is separation. Your working files stay in OneDrive, while the backup lives under a different provider and account. B2 also uses S3-compatible object storage, which suits archives that you expect to keep longer than you actively edit them.

This transfer copies files and folders. It does not reproduce Microsoft sharing permissions, version history, comments, or recycle-bin contents.

How to copy OneDrive to Backblaze B2

Connect Microsoft OneDrive in Blober.
Connect Backblaze B2 with your key ID, application key, and bucket.
Create a workflow with OneDrive as the source and B2 as the destination.
Choose the OneDrive folder and the destination path in your bucket.
Start the workflow and keep Blober open until it finishes.

Blober recreates the folder structure in B2. The data passes through the computer running Blober, but it is not staged as a second full copy on disk.

What the OneDrive connection can see

Blober reads the signed-in user's default OneDrive. That includes ordinary files and folders in "My files." It does not include "Shared with me," SharePoint or Teams libraries, OneNote notebooks, Personal Vault, or shortcuts to another drive.

If a shared file must be part of the backup, first download it and upload it to your own OneDrive as an ordinary file. An "Add shortcut to My files" shortcut is still a reference to another drive, so Blober skips it.

Frequently asked questions

Do I need to mark every OneDrive file "Always keep on this device"?

No. Blober reads the cloud copy through Microsoft Graph rather than backing up the local OneDrive sync folder.

Does the transfer need free disk space equal to my OneDrive library?

No. Files stream through the computer running Blober and are not stored there as a complete intermediate copy.

Is Backblaze B2 a full OneDrive clone?

No. It receives the files and folder structure. OneDrive permissions, links, comments, version history, and deleted items do not transfer.

Can Blober include files shared with me?

Not from OneDrive. Microsoft's old "Shared with me" Graph endpoint is deprecated, requires broader access to read remote items, and will stop returning data after November 2026. Blober keeps the narrower Files.ReadWrite permission and reads only the signed-in user's drive.

Get Blober

Move your OneDrive files to Backblaze B2 without first filling your disk.

Download Blober at blober.io

OneDrive or Google Drive: moving between Microsoft 365 and Google Workspace

Aug 4, 2026

Changing cloud storage is usually part of a bigger move. A company adopts Google Workspace, a school issues Microsoft 365 accounts, or a family decides it no longer wants to pay for two storage plans. The files are only one part of that decision, but they are the part that has to come with you.

Blober transfers files in either direction between OneDrive and Google Drive. It streams them through your computer, so you do not need enough free disk space to download the entire account first.

When OneDrive to Google Drive makes sense

Google Drive fits best when most work already happens in Gmail, Google Docs, Meet, and Calendar. A move from OneDrive can make sense when:

your company or school has standardized on Google Workspace;
people collaborate mainly in Docs, Sheets, and Slides;
Chromebooks or browser-based work have replaced Windows desktops;
you want storage billed under an existing Google One or Workspace plan.

Office files do not have to be converted during the transfer. Word, Excel, and PowerPoint files arrive in Google Drive as .docx, .xlsx, and .pptx files. Google can open and edit them, and you can choose later whether to convert them to native Google formats.

When Google Drive to OneDrive makes sense

OneDrive is the more natural home when work revolves around Windows, Microsoft 365, Teams, and the desktop versions of Office. People commonly move in this direction because:

their organization has moved to Microsoft 365;
Office formatting needs to survive round trips without surprises;
Teams and SharePoint are now the main places where people collaborate;
OneDrive storage is already included in a Microsoft 365 plan.

The main catch is Google's native file formats. A Google Doc is not a normal .docx file sitting in Drive. When Blober moves native Google files out of Drive, it exports Docs to .docx, Sheets to .xlsx, and Slides to .pptx. Those copies open in Microsoft Office, but Google comments, revision history, sharing rules, and some format-specific features do not come with them.

What moves in each direction

Source	Destination	File behavior
OneDrive	Google Drive	Office files and other regular files keep their existing formats
Google Drive	OneDrive	Native Docs, Sheets, and Slides export to Microsoft Office formats
Either service	The other service	Folder structure is recreated; sharing rules, links, comments, and version history are not

There is one difference around shared files. Blober exposes Google Drive's "Shared with me" list as a read-only source. OneDrive does not offer an equivalent usable root through the narrow permission Blober requests, so its shared items and cross-drive shortcuts are not shown.

How to move from OneDrive to Google Drive

Connect OneDrive with a Microsoft app client ID.
Connect Google Drive.
Create a workflow with OneDrive as the source and Google Drive as the destination.
Select the source folder and destination folder.
Run the workflow and keep Blober open until it finishes.

After the transfer, open a sample of Word, Excel, and PowerPoint files in Google Drive before closing the old account. Decide whether to leave them in Office format or convert the files you still edit.

How to move from Google Drive to OneDrive

Use the same process in reverse: choose Google Drive as the source and OneDrive as the destination. Include "Shared with me" only for files you are allowed to copy and want to keep. Native Google files are exported during the transfer.

Check a few converted documents, spreadsheets, and presentations in Microsoft Office afterward. Complex layouts, formulas, fonts, and embedded Google-only features deserve a manual look.

Before you cancel the old account

Compare file counts and inspect the folders that matter most. Keep the old account available until you have checked converted documents and confirmed that other people can reach the new location.

Then recreate sharing permissions in the destination. File ownership, organization policies, public links, and team memberships belong to the old service and cannot be carried over as ordinary files.

Frequently asked questions

Can I move between OneDrive and Google Drive without downloading everything?

Yes. Blober streams each file through the computer running the app instead of staging the whole library on disk.

Will Google Docs work in OneDrive?

Blober exports Google Docs, Sheets, and Slides to Word, Excel, and PowerPoint formats. Check complex files after conversion because the two editors do not support every feature in exactly the same way.

Will Office files become Google Docs automatically?

No. They arrive in Google Drive as Office files. Google Drive can edit them in that format, or you can convert selected files later.

Does the migration copy shared files?

Google Drive's "Shared with me" items can be selected as a read-only source. OneDrive's "Shared with me" items and shortcuts to other drives are not available in Blober.

Get Blober

Move the files once, check the result, and finish the ecosystem switch without renting a permanent sync service.

Download Blober at blober.io

AzCopy S3 to Azure: How It Works and the Limits to Check

Jul 31, 2026

AzCopy does not download S3 data through your computer

AzCopy's documented AWS S3 transfer uses Azure's Put Block From URL operation. AWS S3 and Azure Storage exchange the object data without using your computer's network bandwidth.^[1]

That makes AzCopy a strong option for teams comfortable with a command line. It can copy one object, a directory, a bucket, or broader groups of AWS buckets.

The migration still needs planning. Server-to-server describes the data route. It does not solve naming, metadata, authentication, or destination-tier decisions.

Authentication is different on each side

The Azure side can use Microsoft Entra ID or a SAS token. The documented AWS flow uses an AWS access key and secret access key supplied through environment variables.

Protect shell history, scripts, logs, and CI output from credentials. Use the narrowest permissions that cover the source and destination.

Bucket names may change

AWS S3 bucket names and Azure container names allow different characters. AzCopy rewrites names that Azure cannot accept.

Periods can become hyphens. Consecutive hyphens can also be rewritten. Two distinct S3 bucket names may therefore map to the same Azure container name, forcing another rename.

Create a bucket-to-container map before a large migration. Do not discover the naming plan from the destination after the copy is complete.

Invalid metadata needs an explicit choice

S3 and Azure also allow different metadata-key characters. AzCopy provides --s2s-handle-invalid-metadata with three behaviors:

ExcludeIfInvalid omits incompatible metadata and logs a warning.
FailIfInvalid fails that object.
RenameIfInvalid changes the metadata key.

The default exclusion behavior can produce a successful object copy with missing metadata. If metadata affects retention, compliance, processing, or ownership, review this flag before running the job.

AWS S3 is not every S3-compatible service

Microsoft's documented S3 flow uses AWS S3 URL formats. Do not assume the same command accepts every Wasabi, Cloudflare R2, MinIO, DigitalOcean Spaces, or private S3-compatible endpoint.

Test the exact provider and endpoint. A tool that supports generic S3 endpoint URLs may be a better fit for non-AWS sources.

When a desktop workflow fits better

Use AzCopy when server-to-server speed, scripting, automation, and repeatable command lines suit the team.

Use a desktop tool when the operator needs visual file selection, browsing, previews, and fewer command flags. Blober connects AWS S3, Azure Blob Storage, and generic S3-compatible endpoints in one local interface. Its data path is different from AzCopy's server-side AWS path, so choose based on network, security, and operational needs rather than calling either design universally better.

AzCopy also supports job resume and restart. Its source code and current release details are published on GitHub.^[2]

Get Blober

AzCopy is a good command-line tool for AWS S3. When you want visual browsing, previews, destination tier selection, and generic S3-compatible endpoints, Blober covers the same move from a desktop app.

Download Blober at blober.io

Dropbox to Google Drive Without Downloading: What That Really Means

Jul 31, 2026

The file bytes still have to move

"Transfer without downloading" usually means "do not make me save the whole library to my disk and upload it again by hand."

It does not mean the file jumps from Dropbox into Google Drive without any computer reading and uploading the bytes.

The Google Drive API supports simple, multipart, and resumable uploads. Each method sends file data to Google in the request body. Google does not provide a Drive endpoint where a migration tool submits a Dropbox URL and asks Drive to fetch it.^[1]

Some computer must read the Dropbox file and push those bytes to Drive.

Three routes

Full local download and upload

The manual method stores a full local copy first:

Dropbox -> local disk -> Google Drive

It is easy to understand and uses no migration service. It also needs free disk space for the library and creates two separate jobs to monitor.

Stream through your computer

A desktop transfer can read part of a Dropbox file and upload that part to Drive while the rest is still arriving:

Dropbox -> your computer's memory -> Google Drive

The data uses your internet connection, but the app does not need to stage the entire library on disk. Blober uses this model.

Stream through a hosted relay

A hosted migration service can run the same read-and-upload work on its own server:

Dropbox -> migration provider -> Google Drive

Your laptop does not need to stay online. The provider's server, credentials, transfer limits, and retention practices become part of the route.

Do not assume every hosted service stores a full second copy. Ask the provider. The relevant question is where the bytes and credentials pass, not whether the marketing page uses the phrase "cloud to cloud."

Streaming does not remove provider limits

A streamed transfer still follows both APIs. Dropbox must allow the download. Google Drive must accept the upload. Rate limits, large-file rules, name conflicts, and provider-native records can still affect the result.

Google Docs, Sheets, and Slides need special handling in the reverse direction because they are not ordinary downloadable files in the same way as a PDF or JPEG.

Migration is not sync

A migration copies or moves a selected set. Two-way sync watches both providers and reconciles later changes.

If you need a one-time provider switch, use a migration workflow and keep the source until the destination is verified. If you need both accounts to mirror every future edit, choose a sync product and define conflict rules before enabling it.

A safer migration sequence

Transfer one representative folder.
Check nested folders and filenames.
Open small documents and large media files.
Review failures and provider-native records.
Copy the rest.
Keep Dropbox unchanged until the Drive copy is trusted.

"Without downloading" can describe a useful convenience. The honest version should always say where the transfer runs and whether a full local copy is stored.

Get Blober

Blober streams each file from Dropbox through your computer to Google Drive without staging the whole library on disk. Your credentials stay local and no Blober server sits in the path.

Download Blober at blober.io

How the Blober file_dir Path Template Variable Really Works

Jul 20, 2026

The Short Definition

{file_dir} is the directory path relative to the folder you selected as the source boundary. It is the part of the path that sits below that folder, not the file's full path and not always its immediate parent folder.

Blober works it out as it scans the files inside a folder you selected:

file_dir = directory containing the file - selected folder path

This distinction determines whether a custom path template preserves nested source structure.

Where You Use It

In a workflow:

Open Source Configuration.
Click Browse Files and Folders.
Select a folder and submit the selection.
Complete Destination Configuration.
Expand Advanced Path Template (Optional).
Add {file_dir} to the Template Pattern.

A common preservation template is:

{file_dir}/{filename}

This produces a clean filename when {file_dir} is empty and adds nested directories when it is not. Blober removes the empty path segment rather than creating a leading slash.

Case 1: You Select an Individual File

Selected item:

Clients/Acme/Final/report.pdf

Because you picked the file itself, Blober has no selected folder to measure it against. Its relative directory is null, which becomes an empty {file_dir} value.

Template: {file_dir}/{filename}
Result: report.pdf

Blober does not produce:

Clients/Acme/Final/report.pdf

The original parent path is not automatically inferred into {file_dir} for a directly selected file.

This matters when several individual files are selected from different folders. A {file_dir}/{filename} template will not recreate each file's original parent folder. If retaining those parent folders matters, select their containing folders instead.

Case 2: You Select a Folder and the File Is at Its Root

Selected folder:

Shoots/Wedding-2026

File:

Shoots/Wedding-2026/cover.jpg

The file's containing directory and the selected folder are the same. The relative path between them is empty.

{file_dir} = ""
Template: {file_dir}/{filename}
Result: cover.jpg

The selected folder name Wedding-2026 is not included in {file_dir}. The selected folder is the boundary, so relative calculation starts inside it.

If you want the selected folder name in the destination, add it as static text:

Wedding-2026/{file_dir}/{filename}

or select the parent folder Shoots, which changes the relative boundary.

Case 3: You Select a Folder and the File Is Nested

Selected folder:

Shoots

Nested file:

Shoots/Wedding-2026/Camera-A/RAW/DSC_4821.ARW

Now the directory between the selected folder and the file is:

Wedding-2026/Camera-A/RAW

Therefore:

{file_dir} = Wedding-2026/Camera-A/RAW

and:

Template: originals/{file_dir}/{filename}
Result: originals/Wedding-2026/Camera-A/RAW/DSC_4821.ARW

{file_dir} can contain several levels. It holds the full relative path between the selected folder and the file, not only the single parent folder directly above it.

Selection Changes the Result

The same physical file can receive different {file_dir} values depending on the source selection.

File:

Archive/2026/Client-A/Final/video.mp4

Selected source	`{file_dir}`
The file itself	empty
`Archive/2026/Client-A/Final`	empty
`Archive/2026/Client-A`	`Final`
`Archive/2026`	`Client-A/Final`
`Archive`	`2026/Client-A/Final`

This is intentional. Selection defines the root that should not be repeated at the destination.

Why file_dir Matters With Custom Templates

Without a custom template, Blober can automatically preserve subdirectories when Include Subdirectories is enabled.

Once a custom template is entered, that automatic path is replaced. Consider:

by-date/{file_created_date}/{filename}

Every qualifying file is grouped by date. Existing source subfolders disappear from the destination path.

To organize by date while retaining relative folders:

by-date/{file_created_date}/{file_dir}/{filename}

For:

Selected folder: Projects
File: Projects/Acme/Final/report.pdf

the result becomes:

by-date/2026-07-18/Acme/Final/report.pdf

Mixed File and Folder Selections

Blober allows multiple source selections. You can select one folder and several individual files.

Their {file_dir} values do not behave identically:

Files discovered inside the folder receive a relative path beneath that folder.
Files directly selected receive an empty value.
Files at the selected folder's root also receive an empty value.

If the destination must retain a meaningful folder for every file, avoid mixing individual-file selection with a template that depends entirely on {file_dir}. Select common parent folders or add another stable prefix such as {file_ext} or {file_created_date}.

Useful Templates

Preserve the relative hierarchy:

{file_dir}/{filename}

Add an archive prefix:

archive/{file_dir}/{filename}

Split by type while preserving hierarchy:

{file_ext}/{file_dir}/{filename}

Group by creation date while preserving hierarchy:

{file_created_date}/{file_dir}/{filename}

Rename while preserving hierarchy:

{file_dir}/{file_created_datetime}_{filename}

Common Mistakes

Expecting the selected folder's name to appear. It will not. {file_dir} starts below the selected folder.

Selecting individual files and expecting parent folders. Directly selected files have no relative selected-folder context, so {file_dir} is empty.

Assuming Include Subdirectories adds folders to a custom template. A custom path expression takes precedence. Add {file_dir} explicitly.

Using {file_dir} without {filename}. The variable describes directories, not the final filename. A template normally needs both.

Verify It in Preview

Use a small test tree containing:

Test/
  root.txt
  Level-1/
    nested.txt
    Level-2/
      deep.txt

Select Test and preview {file_dir}/{filename}. Expected relative results:

root.txt
Level-1/nested.txt
Level-1/Level-2/deep.txt

That one preview demonstrates the complete rule before it is applied to a large archive.

Continue with the complete Blober path-template guide or learn how selection and glob filters define which files reach the template.

How to Transfer GoPro Cloud to Google Drive Without ZIP Files

Jul 19, 2026

Can You Move GoPro Cloud Files Directly to Google Drive?

Yes. Blober connects GoPro Cloud as a source and Google Drive as a destination, then streams each photo or video from one provider to the other. You do not have to select 25 files at a time, wait for ZIP archives, extract them, and upload them again.

This is useful when you want:

A second copy outside your GoPro subscription
GoPro footage beside other project files in Google Drive
Easier sharing with people who already use Google Workspace
A way to transfer a library that is too large for manual browser downloads

What You Need

Blober installed on Windows, macOS, or Linux
A GoPro Premium or GoPro Plus account with media in GoPro Cloud
A Google account with enough available Drive storage
Google Drive OAuth credentials configured for Blober

If Google Drive is not connected yet, follow the Google Drive setup guide. The GoPro provider guide explains GoPro login and media selection.

Step 1: Open a New Workflow

Open Blober and select Workflows in the left navigation.
On the Workflows page, click New Workflow.
Enter a Workflow Name, such as GoPro Cloud to Google Drive.
Enter a Workflow Description that will help you recognize the backup later.
Under Select Action, choose Copy - Duplicate files to destination.

Use Copy, not Move, for a backup. Copy leaves the original media in GoPro Cloud after it reaches Google Drive.

Step 2: Connect the GoPro Source

In the numbered 1 Source Configuration panel:

Open Source Type and choose GoPro Cloud.
Under GoPro Account, choose an account you have already connected.
To connect another account, click Add account, then Open GoPro Login.
Sign in to GoPro in the window that opens. Return to the workflow after authentication finishes.

The Refresh button reloads the account list if a newly connected account does not appear immediately.

Step 3: Select the GoPro Media

Click Browse Files and Folders under Select Source.
Use the checkboxes to select the date folders, camera folders, photos, or videos you want to copy.
Click Submit Selection.

Your selections appear in Source Configuration. Use Add More Files and Folders if you need to include another part of the library, or remove an item from the selection list if it should not be copied.

You can also expand Advanced Filters (Optional) to restrict the transfer by file type, creation date, file size, subdirectories, or include/exclude patterns. Leave these settings unchanged to copy everything inside the selected folders.

GoPro media is organized into paths such as:

/2026-01-23/HERO13 Black/videos/GX015742.MP4
/2026-01-23/HERO13 Black/photos/GOPR0001.JPG

Step 4: Connect Google Drive

The numbered 2 Destination Configuration panel appears after you submit at least one GoPro source selection.

Open Destination Type and choose Google Drive.
Under Google OAuth Credentials, choose the OAuth credentials JSON file created during Google Drive setup.
When the instructions appear beneath the field, click Authorize Google Drive Access.
Sign in to the Google account that will receive the GoPro backup and approve access.
Return to Blober and wait for Authentication successful to appear.

Google Drive has a 750 GB daily upload limit for most accounts. A multi-terabyte GoPro library may therefore take several days even on a fast connection.

Step 5: Choose the Google Drive Folder

Click Browse Folder under Select Destination Folder.
Navigate to the Google Drive folder where the backup should be stored.
Select that folder using its checkbox. Google Drive must have one destination folder for the workflow.
Click Submit Selection.

The chosen folder appears as the Destination Path. You can expand Advanced Path Template (Optional) if you want Blober to build additional paths from variables such as the filename or file date. Leave it closed for a straightforward copy into the selected folder.

Step 6: Review and Save

The numbered 3 Preview & Summary panel appears when both sides are complete. Check that it shows GoPro media going to the intended Google Drive path.

Review the estimated items and size.
Click Save Workflow.
Wait for Workflow created successfully! before closing the editor.

Saving creates the reusable workflow but does not start a transfer.

Step 7: Run and Monitor the Transfer

Find the new workflow on the Workflows page.
Confirm its card shows GoPro Cloud as the source and Google Drive as the destination.
Click the green Run button.
Blober creates a task and opens the Progress page.

The Progress page shows transferred files, bytes moved, current activity, and individual file results.

Blober runs on your computer, but the files stream from GoPro Cloud to Google Drive rather than being saved as a permanent local copy first. Your credentials remain on your machine, and the media does not pass through Blober's servers.

How Long GoPro Transfers Resume

Authentication sessions can expire during a large transfer. Network interruptions, provider throttling, app restarts, and computer restarts are also normal during multi-day jobs.

Blober stores the task and its per-file progress locally. If the transfer is interrupted:

Reopen Blober.
Return to the existing task on the Progress page.
Resume that task if it was paused. An active pending or running task can be rediscovered after launch.
If GoPro asks you to sign in again, complete the login to obtain a fresh session.

Do not create a replacement workflow or start a new task just to recover from an interruption. The existing task knows which source paths it has already processed; a new task has separate progress state.

Installing a newer Blober version also preserves existing workflows, task history, and task state.

For a deeper explanation, see How Blober Handles Duplicate Files in Long-Running Backups.

How Blober Handles Individual File Errors

During a large library transfer, GoPro may occasionally list a file or part that is not ready to download or is temporarily unavailable.

Blober records the affected item and continues with the rest of the library instead of allowing one unavailable file to block every file that follows.

Review skipped and failed items when the task finishes. A skipped item remains in GoPro Cloud and can be checked there or retried later when it becomes available.

Will a Restart Create Duplicate Files in Google Drive?

Not when you continue the same task. Completed source paths are remembered within that task and are not processed again.

A deliberate rerun of the workflow creates a new task. Google Drive allows multiple files with the same name, and the Local destination's Filename deduplication option does not apply to Google Drive. If a transfer stops, resume its original task rather than starting over.

GoPro Cloud to Google Drive vs Manual Download

Step	Manual GoPro download	Blober workflow
Select media	Small browser batches	Individual folders or entire storage
Download format	ZIP archives	Original media stream
Local extraction	Required	Not required
Google Drive upload	Separate manual step	Same workflow
Resume after interruption	Repeat manual work	Continue the existing task
Long-session re-login	Start over or rebuild batches	Sign in and continue the task

Frequently Asked Questions

Does Blober delete the files from GoPro Cloud?

Not when the workflow action is Copy. The source media remains in GoPro Cloud after it reaches Google Drive.

Does the transfer reduce video or photo quality?

No. Blober requests the highest-quality downloadable GoPro variant and transfers the file without transcoding it.

Must Blober remain open?

Yes, Blober performs the transfer on your computer. It prevents system sleep while a task is active, but the computer must remain powered on and connected to the network.

Blober requests a new login. Authenticate again and continue the existing task; its completed-file state is preserved.

Can I cancel GoPro Premium immediately after starting?

Wait until the task is finished and you have verified the files in Google Drive. Your GoPro subscription must remain active while Blober reads the source library.

Get Blober

Move your GoPro Cloud library to Google Drive without browser batches or ZIP files. Blober is a one-time purchase with no per-GB transfer fee.

Download Blober at blober.io

S3-Compatible Cloud Object Storage Providers (Hyperscalers and Regional Clouds)

Jun 28, 2026

The large platform clouds all run object storage, and most expose an Amazon S3-compatible endpoint alongside their native API. That means you can point an S3 client at Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and many regional clouds by changing the endpoint URL and keys. This page lists the cloud S3-compatible services, their endpoint formats, and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. For independent object-storage clouds, hosting platforms, self-hosted servers, enterprise appliances, and decentralized storage, see the other category pages linked at the end.

These services are intended to connect through Blober's generic S3-Compatible connector when they support the common S3 operations Blober uses. Paste the endpoint and keys, then browse to confirm. Confirm the exact endpoint in each provider's console, since regions and hostnames change over time. The endpoint formats below come from each provider's own documentation, cross-checked against current S3 client references^[1].

Each entry notes an addressing style. Virtual-hosted puts the bucket in the subdomain (https://my-bucket.s3.example.com); path-style puts it in the URL path (https://s3.example.com/my-bucket). Almost every cloud here uses virtual-hosted. The endpoint formats below show hostnames; in Blober, include https:// in the endpoint field. The endpoint setup notes explain how Blober picks the right one.

Alibaba Cloud OSS (Object Storage Service)

Alibaba Cloud Object Storage Service, formerly Aliyun OSS, is the dominant object store in China and across Alibaba's global regions.

Endpoint format: oss-<region>.aliyuncs.com (for example oss-cn-hangzhou.aliyuncs.com, oss-us-east-1.aliyuncs.com, oss-eu-central-1.aliyuncs.com).
Regions: dozens across mainland China, plus Singapore, Tokyo, Frankfurt, London, Dubai, Silicon Valley, and Virginia.
Addressing: virtual-hosted (bucket in subdomain).
Notes: OSS offers Standard, Infrequent Access, Archive, and Cold Archive tiers. Use the matching regional endpoint for your bucket^[2].

Tencent Cloud COS (Cloud Object Storage)

Tencent Cloud Object Storage is the object store behind much of China's app ecosystem, with a global region footprint.

Endpoint format: cos.<region>.myqcloud.com (for example cos.ap-guangzhou.myqcloud.com, cos.ap-singapore.myqcloud.com, cos.na-ashburn.myqcloud.com).
Regions: Beijing, Shanghai, Guangzhou, Chengdu, Hong Kong, Singapore, Mumbai, Seoul, Bangkok, Tokyo, Silicon Valley, Virginia, Toronto, Frankfurt.
Addressing: virtual-hosted.
Notes: there is also a Global Acceleration endpoint (cos.accelerate.myqcloud.com). Standard, Infrequent Access, and Archive tiers are available^[3].

Huawei Cloud OBS (Object Storage Service)

Huawei Cloud OBS is a high-capacity object store with an S3-compatible interface, used widely across Asia, Latin America, and EMEA.

Endpoint format: obs.<region>.myhuaweicloud.com (for example obs.af-south-1.myhuaweicloud.com, obs.ap-southeast-3.myhuaweicloud.com).
Regions: Johannesburg, Bangkok, Singapore, Hong Kong, Shanghai, Beijing, Guangzhou, plus Latin America (Sao Paulo, Mexico City, Santiago, Buenos Aires, Lima) and Moscow.
Addressing: virtual-hosted.
Notes: OBS underpins several rebranded regional clouds (Open Telekom Cloud and SberCloud, listed below), so the connection pattern is similar^[4].

IBM Cloud Object Storage (COS)

IBM Cloud Object Storage, descended from Cleversafe, disperses data across locations and is accessed through an S3-compatible API. It is also sold as on-premises software.

Endpoint format: s3.<region>.cloud-object-storage.appdomain.cloud (for example s3.us-east.cloud-object-storage.appdomain.cloud, s3.eu-de.cloud-object-storage.appdomain.cloud).
Regions: US East and South, EU (Frankfurt, Amsterdam, Milan), Great Britain, plus single-site endpoints in many cities. Private endpoints exist for in-cloud traffic.
Addressing: virtual-hosted.
Notes: IBM COS supports IAM API-key authentication in addition to HMAC access keys. Storage classes include Standard, Vault, Cold Vault, and Smart Tier^[5].

Oracle Cloud Infrastructure (OCI) Object Storage

Oracle Cloud Infrastructure Object Storage offers an Amazon S3 Compatibility API in front of its native object store.

Endpoint format: <namespace>.compat.objectstorage.<region>.oci.customer-oci.com for path-style, or <bucket>.vhcompat.objectstorage.<region>.oci.customer-oci.com for virtual-hosted. The <namespace> is your tenancy's unique Object Storage namespace.
Regions: Ashburn, Phoenix, Frankfurt, London, Tokyo, and the rest of OCI's global regions.
Addressing: both path and virtual-hosted are supported.
Notes: authenticate with a Customer Secret Key (an access key and secret pair). If your tool cannot set the region identifier, set it to us-east-1 or leave it blank to use your home region. SigV2 is not supported^[6].

Google Cloud Storage (XML / S3 Interoperability)

Google Cloud Storage is not S3 by default, but its XML API has an S3-compatible interoperability mode that works with HMAC keys.

Endpoint format: storage.googleapis.com.
Regions: global; the endpoint is single, and the bucket's location is set when you create it.
Addressing: virtual-hosted.
Notes: create an HMAC key for a service account to get an access key and secret. Object versioning listing and a few advanced behaviors differ from AWS, so treat GCS as S3-compatible for the common operations (browse, upload, download, copy) rather than a perfect clone^[7].

Yandex Object Storage

Yandex Cloud's object storage is S3-compatible and popular across Russia and the CIS.

Endpoint format: storage.yandexcloud.net.
Regions: ru-central1 and its availability zones; the endpoint is single.
Addressing: virtual-hosted.
Notes: Standard (hot) and Cold storage classes are available. Use static access keys generated for a service account^[8].

VK Cloud Object Storage (formerly Mail.ru Cloud Solutions)

VK Cloud, previously Mail.ru Cloud Solutions, runs Hotbox and Icebox object storage tiers behind an S3-compatible endpoint.

Endpoint format: hb.bizmrg.com (Hotbox) and ib.bizmrg.com (Icebox), with newer hb.<region>.vkcs.cloud hosts.
Regions: Moscow.
Addressing: virtual-hosted.
Notes: Hotbox is the hot tier, Icebox the cold tier. Confirm the current endpoint in the VK Cloud console.

Baidu AI Cloud BOS (Baidu Object Storage)

Baidu Object Storage provides an S3-compatible interface for one of China's major clouds.

Endpoint format: s3.<region>.bcebos.com (for example s3.bj.bcebos.com for Beijing, s3.gz.bcebos.com for Guangzhou).
Regions: Beijing, Baoding, Suzhou, Guangzhou, Hong Kong, and more.
Addressing: virtual-hosted.
Notes: Standard, Infrequent Access, Cold, and Archive tiers are available.

JD Cloud Object Storage (OSS)

JD Cloud, the cloud arm of JD.com, exposes an S3-compatible object storage service.

Endpoint format: s3.<region>.jdcloud-oss.com (for example s3.cn-north-1.jdcloud-oss.com).
Regions: North China, East China, and South China.
Addressing: virtual-hosted.
Notes: confirm the regional endpoint in the JD Cloud console.

China Mobile Ecloud EOS (Elastic Object Storage)

China Mobile's Ecloud Elastic Object Storage is a large, region-dense S3-compatible service across mainland China.

Endpoint format: eos-<city>-1.cmecloud.cn (for example eos-wuxi-1.cmecloud.cn, eos-beijing-1.cmecloud.cn).
Regions: dozens, from Suzhou and Shanghai to Chengdu, Guiyang, and Xian.
Addressing: virtual-hosted.
Notes: the location constraint must match the endpoint when creating buckets^[9].

Kingsoft Cloud KS3

Kingsoft Cloud Standard Storage Service (KS3) is an S3-compatible object store widely used in China.

Endpoint format: ks3-<region>.ksyuncloud.com or ks3-<region>.ksyun.com (for example ks3-cn-beijing.ksyuncloud.com).
Regions: Beijing, Shanghai, Guangzhou, Hong Kong, and international points.
Addressing: virtual-hosted.
Notes: confirm the current endpoint host in the Kingsoft console.

China Telecom CTYun OOS

China Telecom's CTYun (Tianyi Cloud) Object-Oriented Storage is an S3-compatible service across China Telecom's regions.

Endpoint format: oos-<region>.ctyunapi.cn (for example oos-sccd.ctyunapi.cn).
Regions: many across mainland China.
Addressing: virtual-hosted.
Notes: confirm the regional endpoint in the CTYun console.

NAVER Cloud Object Storage

NAVER Cloud Platform, South Korea's major cloud, runs an S3-compatible object storage service.

Endpoint format: <region>.object.ncloudstorage.com (for example kr.object.ncloudstorage.com).
Regions: Korea, plus other NAVER Cloud regions.
Addressing: virtual-hosted.
Notes: generate API keys in the NAVER Cloud console.

Open Telekom Cloud OBS

Open Telekom Cloud, operated by T-Systems on Huawei technology, exposes Huawei OBS under its own endpoints.

Endpoint format: obs.<region>.otc.t-systems.com (for example obs.eu-de.otc.t-systems.com).
Regions: Germany (Biere, Magdeburg), the Netherlands, and Switzerland.
Addressing: virtual-hosted.
Notes: the OBS lineage means it behaves like Huawei OBS, with European data residency.

SberCloud OBS

SberCloud Advanced (Cloud.ru) runs object storage on Huawei OBS technology with Russian endpoints.

Endpoint format: obs.<region>.hc.sbercloud.ru (for example obs.ru-moscow-1.hc.sbercloud.ru).
Regions: Moscow.
Addressing: virtual-hosted.
Notes: behaves like Huawei OBS with Russian data residency.

Netease NOS (Netease Object Storage)

Netease Object Storage offers an S3-compatible interface used by Netease's services and third parties.

Endpoint format: regional NOS endpoints (for example nos-eastchina1.126.net).
Regions: several across China.
Addressing: virtual-hosted (path-style addressing is disabled by the provider).
Notes: confirm the exact endpoint in the Netease console.

A Note on Microsoft Azure Blob Storage

Azure Blob Storage is the obvious omission here, and it is deliberate. Azure Blob uses its own API, not the S3 API, so it is not S3-compatible in the drop-in sense. The concepts line up (a container maps to a bucket, a blob to an object), but an S3 client cannot talk to Azure Blob without a translation gateway. If you need to move data between S3 and Azure, Blober bridges the two directly. See How to Transfer AWS S3 to Azure Blob.

Frequently Asked Questions

Is Google Cloud Storage S3-compatible? Through its XML API interoperability mode, yes, for the common operations. You create an HMAC key and point your S3 client at storage.googleapis.com. A few advanced behaviors differ from AWS S3.

Is Alibaba OSS the same as AWS S3? OSS speaks the S3 API, so S3 tools work against it by changing the endpoint and keys. It is run by Alibaba, not Amazon, and its tier names and some features are its own.

Why do Open Telekom Cloud and SberCloud look like Huawei OBS? Because they are built on Huawei OBS technology and rebranded for their regions. The S3-compatible connection pattern is the same, with different endpoints and data residency.

Can Blober move data from one cloud's object storage to another? Yes. Point Blober at a source endpoint and a destination endpoint and it copies between them directly for normal object transfers. Provider-specific S3 feature gaps can still matter for advanced workflows.

Get Blober

Connect to any cloud's S3-compatible object storage by URL and move data between providers directly, without filling your local disk.

Download Blober at blober.io

S3-Compatible Object Storage from Web Hosts and VPS Providers

Jun 28, 2026

If you already rent servers from a hosting or VPS company, there is a good chance they also sell S3-compatible object storage right next to your droplets, instances, or dedicated boxes. Keeping storage with your compute reduces latency and often avoids cross-provider egress. This page lists the hosting and VPS object-storage services, their endpoint formats, and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. DigitalOcean Spaces has a preconfigured connector in Blober; the rest use the generic S3-Compatible connector. Confirm endpoints in each provider's console, since regions change over time. The endpoint formats below come from each provider's own documentation, cross-checked against current S3 client references^[1].

Each entry notes an addressing style. Virtual-hosted puts the bucket in the subdomain (https://my-bucket.s3.example.com); path-style puts it in the URL path (https://s3.example.com/my-bucket). Almost every host here uses virtual-hosted. The endpoint formats below show hostnames; in Blober, include https:// in the endpoint field. The endpoint setup notes explain how Blober picks the right one.

DigitalOcean Spaces

DigitalOcean Spaces is S3-compatible object storage with a built-in CDN, sold alongside DigitalOcean droplets.

Endpoint format: <region>.digitaloceanspaces.com (for example nyc3.digitaloceanspaces.com, fra1.digitaloceanspaces.com).
Regions: NYC3, SFO2, SFO3, AMS3, FRA1, SGP1, SYD1, BLR1, ATL1, LON1, TOR1, and more.
Addressing: virtual-hosted.
Notes: Blober has a preconfigured DigitalOcean Spaces connector. Spaces has no built-in cross-region replication; see DigitalOcean Spaces Regions, Replication, and Backup^[2].

Linode / Akamai Object Storage

Linode (now part of Akamai) offers S3-compatible object storage across many global regions.

Endpoint format: <region>.linodeobjects.com (for example us-east-1.linodeobjects.com, eu-central-1.linodeobjects.com).
Regions: Newark, Atlanta, Chicago, Los Angeles, Miami, Seattle, Washington DC, Amsterdam, Frankfurt, London, Madrid, Milan, Paris, Stockholm, Chennai, Jakarta, Osaka, Singapore, Sao Paulo, Melbourne.
Addressing: virtual-hosted.
Notes: one of the widest region footprints among VPS providers^[3].

Vultr Object Storage

Vultr Object Storage is S3-compatible storage with a CDN, billed with generous included transfer.

Endpoint format: <region>.vultrobjects.com (for example ewr1.vultrobjects.com, ams1.vultrobjects.com).
Regions: New Jersey, Silicon Valley, Amsterdam, Singapore, Bangalore, Delhi, and more.
Addressing: virtual-hosted.
Notes: includes an archival storage tier with lifecycle policies. Confirm the regional host in the Vultr console^[4].

OVHcloud Object Storage

OVHcloud offers S3-compatible object storage across its European, North American, and Asia-Pacific regions.

Endpoint format: s3.<region>.io.cloud.ovh.net (for example s3.gra.io.cloud.ovh.net for Gravelines, s3.de.io.cloud.ovh.net for Frankfurt). US regions use io.cloud.ovh.us.
Regions: Gravelines, Roubaix, Strasbourg, Paris, Frankfurt, London, Warsaw, Beauharnois, Toronto, Singapore, Sydney, Mumbai, plus US (Virginia, Oregon) and a cold archive region.
Addressing: virtual-hosted.
Notes: storage classes include Standard, High Performance, Standard Infrequent Access, and archive tiers^[5].

Hetzner Object Storage

Hetzner Object Storage is low-cost S3-compatible storage in Hetzner's European data centers.

Endpoint format: <region>.your-objectstorage.com (for example hel1.your-objectstorage.com, fsn1.your-objectstorage.com, nbg1.your-objectstorage.com).
Regions: Helsinki, Falkenstein, Nuremberg.
Addressing: virtual-hosted.
Notes: a popular budget option for European workloads^[6].

Scaleway Object Storage

Scaleway Object Storage is S3-compatible storage from the French cloud provider, with a Glacier cold tier.

Endpoint format: s3.<region>.scw.cloud (for example s3.nl-ams.scw.cloud, s3.fr-par.scw.cloud, s3.pl-waw.scw.cloud).
Regions: Amsterdam, Paris, Warsaw.
Addressing: virtual-hosted.
Notes: the GLACIER storage class uploads directly to Scaleway's cold tier; restore before reading^[7].

Contabo Object Storage

Contabo Object Storage is budget S3-compatible storage (built on Ceph) with included transfer.

Endpoint format: <region>.contabostorage.com (for example eu2.contabostorage.com, usc1.contabostorage.com, sin1.contabostorage.com).
Regions: Europe, United States, and Asia.
Addressing: virtual-hosted.
Notes: unlimited inbound and generous outbound transfer are included in the flat monthly rate. Confirm your exact endpoint in the Contabo console^[8].

Exoscale SOS (Simple Object Storage)

Exoscale Simple Object Storage is S3-compatible storage from the Swiss cloud provider, with European zones.

Endpoint format: sos-<zone>.exo.io (for example sos-ch-gva-2.exo.io, sos-de-fra-1.exo.io).
Regions: Geneva, Zurich, Frankfurt, Munich, Vienna, Sofia.
Addressing: virtual-hosted.
Notes: strong fit for Swiss and EU data residency^[9].

UpCloud Object Storage

UpCloud Object Storage is S3-compatible storage from the Finnish cloud provider.

Endpoint format: <region>.upcloudobjects.com (the exact host is shown in your console).
Regions: several across Europe, the US, and Asia-Pacific.
Addressing: virtual-hosted.
Notes: confirm the per-region endpoint host in the UpCloud control panel.

IONOS Cloud S3 Object Storage

IONOS S3 Object Storage is S3-compatible storage from the German provider IONOS.

Endpoint format: s3-<region>.ionoscloud.com (for example s3-eu-central-1.ionoscloud.com).
Regions: Frankfurt, Berlin, Logrono (Spain), Lenexa (USA).
Addressing: virtual-hosted.
Notes: generate keys in the Data Center Designer under the Object Storage Key Manager^[10].

Gcore Object Storage

Gcore Object Storage is S3-compatible storage from Gcore, with a wide global edge footprint.

Endpoint format: regional S3 endpoint shown in the Gcore console (for example a s3.<region> style host).
Regions: many across Europe, the Americas, Asia, and the Middle East.
Addressing: virtual-hosted.
Notes: confirm the current endpoint host for your region in the Gcore console.

DreamHost DreamObjects

DreamObjects is DreamHost's S3-compatible object storage, built on Ceph.

Endpoint format: objects-<region>.dream.io (for example objects-us-east-1.dream.io).
Regions: US.
Addressing: virtual-hosted.
Notes: leave the region blank and set the endpoint, as with other Ceph-based services^[11].

RackCorp Object Storage

RackCorp Object Storage is an S3-compatible platform with anycast and many regional endpoints.

Endpoint format: <region>.s3.rackcorp.com (for example au-nsw.s3.rackcorp.com), or s3.rackcorp.com for the global anycast endpoint.
Regions: Australia (several), plus Asia, Europe, North America, and New Zealand.
Addressing: virtual-hosted.
Notes: useful where other providers lack a nearby region^[12].

cloudscale.ch

cloudscale.ch is a Swiss provider with S3-compatible object storage and strong data-residency guarantees.

Endpoint format: objects.<region>.cloudscale.ch (for example objects.rma.cloudscale.ch, objects.lpg.cloudscale.ch).
Regions: Rumlang and Lupfig, Switzerland.
Addressing: virtual-hosted.
Notes: all data stays in Switzerland^[13].

Fuga Cloud Object Store

Fuga Cloud is a European OpenStack-based provider with an S3-compatible object store.

Endpoint format: core.fuga.cloud.
Regions: the Netherlands.
Addressing: virtual-hosted.
Notes: confirm the endpoint and any newer hosts in the Fuga console.

Infomaniak Public Cloud

Infomaniak, a Swiss provider, offers S3-compatible object storage on its OpenStack-based Public Cloud.

Endpoint format: s3.<region>.infomaniak.cloud (for example s3.pub1.infomaniak.cloud).
Regions: Switzerland.
Addressing: virtual-hosted.
Notes: Swiss data residency and renewable-energy hosting.

Outscale OOS (Object Storage)

OUTSCALE, a Dassault Systemes brand, offers enterprise-grade S3-compatible object storage.

Endpoint format: oos.<region>.outscale.com (for example oos.eu-west-2.outscale.com).
Regions: Paris, New Jersey, California, SecNumCloud (Paris), Tokyo.
Addressing: virtual-hosted.
Notes: includes a SecNumCloud-qualified region for sensitive French workloads^[14].

Liara Object Storage

Liara is an Iranian platform with S3-compatible object storage.

Endpoint format: storage.iran.liara.space.
Regions: Iran.
Addressing: virtual-hosted.
Notes: leave the region blank and set the endpoint^[15].

ArvanCloud Object Storage

ArvanCloud offers S3-compatible object storage with regions in Iran.

Endpoint format: s3.<region>.arvanstorage.ir (for example s3.ir-thr-at1.arvanstorage.ir), also seen as s3.arvanstorage.com.
Regions: Tehran, Tabriz.
Addressing: virtual-hosted.
Notes: confirm the current endpoint host in the ArvanCloud console^[16].

BizflyCloud Simple Storage

Bizfly Cloud Simple Storage is an S3-compatible service with regions in Vietnam.

Endpoint format: <region>.ss.bfcplatform.vn (hn.ss.bfcplatform.vn for Hanoi, hcm.ss.bfcplatform.vn for Ho Chi Minh City).
Regions: Hanoi, Ho Chi Minh City.
Addressing: virtual-hosted.
Notes: match the region to the endpoint^[17].

Selectel and Servercore Object Storage

Selectel and its international brand Servercore offer S3-compatible object storage with triple-redundant storage.

Endpoint format: s3.<region>.storage.selcloud.ru (for example s3.ru-1.storage.selcloud.ru), plus s3.<region>.srvstorage.uz and s3.<region>.srvstorage.kz for Servercore in Central Asia.
Regions: St. Petersburg, Moscow, Kazakhstan, Uzbekistan.
Addressing: virtual-hosted (the provider recommends vHosted, not path-style).
Notes: confirm the endpoint for your region in the console^[18].

Fastly Object Storage

Fastly Object Storage is S3-compatible storage from the edge-cloud provider Fastly, with mandatory server-side encryption.

Endpoint format: <region>.object.fastlystorage.app (for example us-east.object.fastlystorage.app).
Regions: US East, US West, US Central, EU Central, EU South, EU West, UK East, JP Central, AU East.
Addressing: virtual-hosted.
Notes: server-side encryption is always on^[19].

Leaseweb Object Storage

Leaseweb offers S3-compatible object storage alongside its dedicated and cloud hosting.

Endpoint format: the regional S3 endpoint shown in the Leaseweb customer portal.
Regions: Europe, the US, and Asia-Pacific.
Addressing: virtual-hosted.
Notes: confirm the exact endpoint host in the Leaseweb portal.

Frequently Asked Questions

Why use a host's object storage instead of a specialist? Keeping storage with your compute reduces latency and often avoids cross-provider egress charges. If you already run servers at OVHcloud, Hetzner, or Vultr, their object storage is the path of least resistance.

Do these all use the AWS S3 API? Yes. Every provider here exposes an S3-compatible endpoint, so the same S3 tools and SDKs work by changing the endpoint and keys.

Can I move data from DigitalOcean Spaces to another host's object storage? Yes. Blober copies directly between S3 endpoints that support the normal object operations it uses. Set the source and destination and it transfers without staging a full copy on your disk.

Which of these connect to Blober without setup? DigitalOcean Spaces has a preconfigured connector. Every other provider on this page uses the generic S3-Compatible connector: paste the endpoint and keys.

Get Blober

Connect to any host's S3-compatible object storage by URL and move data between providers directly, without filling your local disk.

Download Blober at blober.io

S3-Compatible Storage Providers: The Complete List (90+ Providers)

Jun 28, 2026

This is a practical list of well-known S3-compatible storage providers. If a service speaks the Amazon S3 API, the same tools, SDKs, and apps that work with AWS S3 usually work with it by changing two things: the endpoint URL and the access keys. That portability is why so many S3-compatible services exist, from global clouds to storage you run on your own hardware.

We have grouped them into six categories so the list stays usable. Each provider below links to a detailed entry with its endpoint format, regions, addressing style, and notes. Whatever S3-compatible store you are searching for, there is a good chance it is on this page.

Every endpoint format here comes from the provider's own documentation, cross-checked against current S3 client references and the per-provider sources in the category pages^[1]. The tables show endpoint hostnames for readability. In Blober, enter the full URL with https:// unless you are connecting to a local/self-hosted server that explicitly uses http://.

What S3-Compatible Means Here

S3-compatible means the service exposes the same HTTP API as Amazon S3, so an S3 client points at it by URL. It does not mean the service is run by Amazon, and it does not promise every advanced feature is identical. For the full explanation, see What S3-Compatible Really Means.

For common S3 operations, the custom endpoint is the portability layer. Once your tool can set that endpoint, the provider becomes much easier to swap.

How Blober Connects to Any of These

Blober has preconfigured connectors for the most common S3 services (Amazon S3, Wasabi, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, and Rabata). For everything else on this list, Blober has a single generic S3-Compatible connector: you paste the endpoint URL and keys, and Blober can use the common browse, upload, download, copy, and delete operations when the provider implements them.

That connector covers both addressing styles (bucket in the subdomain, or bucket in the path), single-bucket or full-account access, a custom region, and a free-text storage class, so it reaches the long tail of providers, self-hosted servers, and local test setups. You point Blober at a source and a destination and it copies between them directly, without staging a full copy on your disk.

The Six Categories

Category	What is in it	Open the list
Cloud object storage	S3 services from large platform clouds (Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and more)	Cloud providers
Object storage specialists	Independent clouds built only for object storage (Wasabi, Backblaze, Storj, IDrive e2, Cubbit, and more)	Specialists
Hosting and VPS object storage	S3 storage bundled with a hosting or VPS platform (DigitalOcean, Linode, Vultr, OVHcloud, Hetzner, Scaleway, and more)	Hosting and VPS
Self-hosted and open source	S3 servers you run yourself (MinIO, Ceph, SeaweedFS, Garage, and more)	Self-hosted
Enterprise and on-premises	Appliances and enterprise platforms (NetApp StorageGRID, Dell ECS, Cloudian, Pure FlashBlade, and more)	Enterprise
Decentralized and Web3	Object storage backed by decentralized networks (Storj, Filebase, 4everland, and more)	Decentralized

Master Index of S3-Compatible Providers

Every provider, alphabetical, with its endpoint format. The endpoint is the host you give your S3 client; the bucket name is then added either as a subdomain or in the path. Replace any bracketed value (<region>, <account>, <namespace>) with your own. A check in the last column means Blober ships a preconfigured connector; everything else uses the generic S3-Compatible connector. When you enter one of these in Blober, include the URL scheme, for example https://s3.example.com.

Provider	Endpoint format	Preconfigured
Alibaba Cloud OSS	`oss-<region>.aliyuncs.com`
Amazon S3	`s3.<region>.amazonaws.com`	Yes
Apache Ozone	self-hosted S3 Gateway
ArvanCloud	`s3.<region>.arvanstorage.ir`
Backblaze B2	`s3.<region>.backblazeb2.com`	Yes
Baidu AI Cloud BOS	`s3.<region>.bcebos.com`
BizflyCloud	`<region>.ss.bfcplatform.vn`
Ceph (RADOS Gateway)	self-hosted
China Mobile Ecloud EOS	`eos-<city>-1.cmecloud.cn`
China Telecom CTYun OOS	`oos-<region>.ctyunapi.cn`
Cloudflare R2	`<account>.r2.cloudflarestorage.com`	Yes
Cloudian HyperStore	appliance or software
cloudscale.ch	`objects.<region>.cloudscale.ch`
Contabo Object Storage	`<region>.contabostorage.com`
Cubbit DS3	`s3.cubbit.eu`
DataCore Swarm	on-premises
Dell ECS / ObjectScale	on-premises
DigitalOcean Spaces	`<region>.digitaloceanspaces.com`	Yes
DreamHost DreamObjects	`objects-<region>.dream.io`
Exaba	self-hosted
Exoscale SOS	`sos-<zone>.exo.io`
Fastly Object Storage	`<region>.object.fastlystorage.app`
FileLu S5	`s5lu.com`
Filebase	`s3.filebase.io`
4everland	`endpoint.4everland.co`
Fuga Cloud Object Store	`core.fuga.cloud`
Garage	self-hosted
Gcore Object Storage	regional endpoint
Google Cloud Storage	`storage.googleapis.com`
Hitachi Content Platform	on-premises
Hetzner Object Storage	`<region>.your-objectstorage.com`
Huawei Cloud OBS	`obs.<region>.myhuaweicloud.com`
IBM Cloud Object Storage	`s3.<region>.cloud-object-storage.appdomain.cloud`
IDrive e2	`<region>.idrivee2-XX.com`
Impossible Cloud	`<region>.storage.impossibleapi.net`
Infomaniak Public Cloud	`s3.<region>.infomaniak.cloud`
Intercolo Object Storage	`de-fra.i3storage.com`
IONOS Cloud S3	`s3-<region>.ionoscloud.com`
JD Cloud Object Storage	`s3.<region>.jdcloud-oss.com`
Kingsoft Cloud KS3	`ks3-<region>.ksyuncloud.com`
Leaseweb Object Storage	regional endpoint
Leviia	`s3.leviia.com`
Liara	`storage.iran.liara.space`
Linode / Akamai	`<region>.linodeobjects.com`
MEGA S4	`s3.<region>.s4.mega.io`
MinIO	self-hosted
NAVER Cloud Object Storage	`<region>.object.ncloudstorage.com`
NetApp StorageGRID	on-premises
NetApp ONTAP S3	on-premises
Netease NOS	`nos-<region>.126.net`
Nutanix Objects	on-premises
OpenIO	self-hosted
OpenStack Swift (s3api)	self-hosted
Open Telekom Cloud OBS	`obs.<region>.otc.t-systems.com`
Oracle Cloud OCI	`<namespace>.compat.objectstorage.<region>.oci.customer-oci.com`
Outscale OOS	`oos.<region>.outscale.com`
OVHcloud Object Storage	`s3.<region>.io.cloud.ovh.net`
Petabox	`s3.<region>.petabox.io`
Pure Storage FlashBlade	on-premises
Qiniu Kodo	`s3-<region>.qiniucs.com`
Quantum ActiveScale	on-premises
Rabata	`s3.<region>.rabata.io`	Yes
RackCorp	`<region>.s3.rackcorp.com`
Riak CS	self-hosted
Scality RING / ARTESCA	on-premises
Scaleway Object Storage	`s3.<region>.scw.cloud`
Seagate Lyve Cloud	`s3.<region>.<account>.lyve.seagate.com`
SeaweedFS	self-hosted
Selectel	`s3.<region>.storage.selcloud.ru`
Servercore	`s3.<region>.storage.selcloud.ru`
SberCloud OBS	`obs.<region>.hc.sbercloud.ru`
Spectra Logic BlackPearl	on-premises
Storadera	`<region>.s3.storadera.com`
Storj	`gateway.storjshare.io`
Synology C2	`<region>.s3.synologyc2.net`
Tebi	`s3.tebi.io`
Telnyx Cloud Storage	`<region>.telnyxcloudstorage.com`
Tencent Cloud COS	`cos.<region>.myqcloud.com`
Tigris	`t3.storage.dev`
UpCloud Object Storage	`<region>.upcloudobjects.com`
US3 (UCloud)	`s3-<region>.ufileos.com`
VAST Data	on-premises
Versity Gateway	self-hosted
VK Cloud Object Storage	`hb.bizmrg.com`
Vultr Object Storage	`<region>.vultrobjects.com`
Wasabi	`s3.<region>.wasabisys.com`	Yes
Yandex Object Storage	`storage.yandexcloud.net`
Zadara	`<vsa-id>.zadarazios.com`
Zata	`idr01.zata.ai`

This index is a starting point. Providers add regions and change hostnames over time, so always confirm the exact endpoint in your provider's console before you connect. The detailed group articles explain each provider's regions, addressing style (path or subdomain), and any quirks.

Subdomain vs Path: The One Setting That Trips People Up

S3 supports two ways of putting the bucket name into the request:

Virtual-hosted (bucket in the subdomain): https://my-bucket.s3.example.com. This is the AWS default and what most hosted providers expect.
Path-style (bucket in the path): https://s3.example.com/my-bucket. This is what MinIO, Ceph, and most self-hosted servers expect.

If browsing or uploads fail against a self-hosted server, switch to path-style. In Blober, you pick the style implicitly by which endpoint field you fill in. Everything else is the same.

Frequently Asked Questions

How many S3-compatible storage providers are there? There is no official registry. This page indexes more than ninety well-known hosted providers, hosting platforms, self-hosted servers, enterprise systems, and decentralized gateways across six categories.

Is Azure Blob Storage S3-compatible? Not natively. Azure Blob uses its own API. The concepts map across (a container is like a bucket, a blob like an object), but an S3 tool needs a translation layer to talk to it. See How to Transfer AWS S3 to Azure Blob for moving data between the two.

Can I move data between two different S3-compatible providers? Yes. Because they share the core API, moving between them is usually a straightforward copy. Blober connects to a source and a destination and transfers directly between them. Check provider-specific feature gaps if your workflow depends on object lock, lifecycle, metadata edge cases, or server-side copy.

Do I need a preconfigured connector, or does the generic one work? The generic S3-Compatible connector works with S3-compatible endpoints that support the common operations Blober uses. The preconfigured connectors (S3, Wasabi, R2, B2, Spaces, Rabata) just save you from pasting the endpoint.

Which S3-compatible provider is the cheapest? It depends on your access pattern. Flat-rate, zero-egress providers win for data you read often; the lowest per-GB storage rate wins for cold archives. The pricing model (egress fees and minimum storage duration) usually matters more than the headline storage rate.

Get Blober

Connect to S3-compatible stores on this list and move data between them directly, without filling your local disk. Blober handles S3, Wasabi, R2, B2, Spaces, Rabata, and generic S3 endpoints by URL, plus non-S3 services like Azure Blob, Dropbox, and Google Drive.

Download Blober at blober.io

Large Cloud Transfers: When a Desktop App Is the Right Tool

Jun 27, 2026

Moving a few files is easy anywhere. Moving terabytes is a question of where the work runs, and the answer depends on the job. For most transfers, a desktop app on your own machine beats a browser-based or hosted tool. For a single bulk move of a very large dataset into one provider, that provider's own migration service can be faster. This page sorts out which is which.

The Ceiling Inside a Browser Tab

A browser-based transfer happens inside a tab, and a tab is a small, supervised space. It has a memory budget, it can be paused or discarded when you switch away, and it usually holds only a handful of connections. For a dozen photos this is invisible. For a media library it is the wall the transfer hits: the tab slows, the laptop heats up, and a job that should run for an hour cannot stay awake long enough to finish.

The Timeout and the Bandwidth Bill

Hosted services move work onto their own machines, which sounds like an upgrade until you look at the path. The data has to travel from the source into their infrastructure, and then back out to the destination. You wait for both legs, and the company pays for the bandwidth in the middle. That cost does not disappear. It comes back as a subscription, a per-GB charge, or a monthly transfer cap.

Server functions also run on a clock. AWS Lambda, for example, documents a maximum function timeout of 900 seconds, or 15 minutes^[1]. Many serverless jobs are designed to finish in seconds or minutes, not the hours a large migration needs. When the clock runs out mid-file, the job has to be broken into pieces and stitched back together; if that orchestration is wrong, gaps and duplicates are the failure mode.

What a Desktop Process Can Actually Do

A desktop app is not boxed in the same way. It can use the memory and processor your machine actually has, open many transfers in parallel, and keep running for as long as the work takes. If the connection drops, Blober can retry failed records; if you stop and rerun a workflow, skip-existing keeps completed files from being sent again.

Blober also streams rather than stages. Instead of saving a full copy of every file to your disk and uploading it again, it flows the data through and writes it straight to the destination, so disk space stops being the limit. The difference between a streamed transfer and download-and-reupload is small for ten files and decisive for ten thousand, which is covered in Server-to-Server vs Download-and-Reupload.

Your Connection, Your Rules

Because the transfer runs from your machine, it uses your own connection and your own IP address. There is no shared relay address for a provider to throttle or block for every user of the tool at once. A hosted service, by contrast, reaches every provider from the same pool of company servers, which is the traffic pattern most likely to attract shared-service limits. Your own account and API limits still apply either way.

When a Provider's Own Migration Wins

For a single move of a very large dataset, tens of terabytes or tens of millions of files, into one destination, the fastest path is often not your machine at all. Some providers run datacenter-to-datacenter migration, where the data never makes the round trip through your home or office connection. Backblaze, for example, lists assisted data migration as available for B2 Cloud Storage^[2], and what can take weeks streaming through your own link can take far less over a datacenter one. If you are doing one big move into one provider and you can grant that service access, start there. There is a worked 25 TB example in Migrating 100M+ Files from DigitalOcean Spaces to Backblaze B2.

This is not a flaw in any one tool. Any client-side transfer, a desktop app or a command-line tool alike, has to pull the data down to your machine and push it back up, which is two trips through your connection. For the very largest one-time moves, skipping those trips is the whole point.

Where a Desktop App Is the Right Tool

A provider migration helps in a narrow case: one big move, into one provider that offers it, when you can hand that provider access. Outside that case, a desktop app like Blober is usually the better fit, and for some teams it is the only acceptable one.

When you cannot share credentials with anyone. Assisted migration means granting a third party access to your storage. For regulated data, client data under NDA, or anything inside a SOC 2 or ISO 27001 boundary, that is often ruled out. A team in that position cannot hand its keys to a destination provider's migration service any more than it could hand them to a relay. Blober keeps your credentials on your own machine and adds no third party to the path, so the transfer stays inside the controls you already have. See How Blober Works.
When the move is ongoing, not one-time. Migration services are built for a single bulk lift. New uploads, folder moves, periodic refreshes, and re-running a saved job are what a desktop tool is for.
When no assisted path exists. Provider migration almost always moves data into that one provider. Moving between two arbitrary providers, or pulling a library out of a consumer cloud like GoPro Cloud or Google Photos, has no assisted option. A desktop app that speaks each provider directly is the practical route.
When the scale is moderate. For gigabytes or a few terabytes, arranging an assisted migration is more trouble than it is worth. A desktop app just runs.
When you want to watch it happen. A desktop transfer stays visible and under your control, so you can pause, resume, and verify on your own machine.

What a Desktop App Does and Does Not Solve

A desktop app is not magic, and it is not always the fastest option. The bytes travel over your own connection, so a slow link is still slow, and for the very largest one-time moves a provider's datacenter migration can beat it outright. What a desktop app gives you is control and privacy: no relay, no third party holding your keys, and the reach to move between any providers you connect, including the ones with no migration service at all.

Frequently Asked Questions

Is a desktop app the fastest way to move a very large dataset? Not always. For a one-time move of tens of terabytes into a single provider that offers datacenter migration, that route is usually faster, because it skips the trip through your connection. A desktop app wins on control, privacy, ongoing use, and moves between providers that have no assisted option.

What if I cannot give a third party access to my storage? Then a desktop app is the right choice. Blober uses your credentials on your own machine and adds no outside party to the transfer, so it fits inside compliance boundaries that rule out both hosted relays and assisted migration services.

Does the data still go through my computer? Yes. A desktop tool streams the data through your machine to the destination. The point is that it does not also route through a separate company's servers, and it does not save a second full copy to your disk.

What happens if my transfer is interrupted? Blober retries failed records during a run. If you stop and rerun the workflow, skip-existing avoids sending files already written at the destination, so the job continues at file level instead of starting the whole migration again.

Next Steps

For a very large one-time move, read Migrating 100M+ Files from DigitalOcean Spaces to Backblaze B2.
See how the pieces fit in How Blober Works.
Read the mechanic behind direct transfers in Server-to-Server vs Download-and-Reupload.
Ready to move your files? Get Blober.

Where Cloud Transfer Tools Actually Send Your Data

Jun 27, 2026

When you move files between clouds, the tool you pick decides the route your data takes. There are three common designs: a hosted service that relays your files through its own servers, a local command-line tool that runs on your machine, and a local desktop app. They differ most in two places you cannot see from the marketing page: where your files travel, and where your credentials live.

The Three Designs

A hosted service

You sign in on a website, connect your clouds, and the service moves the data on its servers. It is convenient and needs nothing installed. In exchange, your files pass through infrastructure you do not control, your credentials are stored on its systems, and the work depends on its uptime, its pricing, and its jurisdiction. Pricing here is usually a subscription or a per-GB transfer fee, sometimes with a monthly cap.

A local command-line tool

Tools like rclone run on your own machine and move data directly between providers. Your files do not detour through anyone else's servers, and your credentials sit in a local file you control; rclone documents cloud authentication in its local configuration file and recommends protecting that file because it contains login information^[1]. The cost is your time: configuration files, keys to manage, and provider-specific flags, all from a terminal.

A local desktop app

A desktop app keeps the direct, on-your-machine route of a command-line tool and adds a visual interface. You connect a provider by signing in, browse your files, pick a destination, and run. Credentials stay in a local store, the data streams straight between your providers and your machine, and there is no Blober account or Blober server in the transfer path. Blober is built this way, with a lifetime licence rather than a subscription.

Side by Side

Question	Hosted service	Local script	Local desktop app
Where do your files travel?	Through the company's servers	Directly, through your machine	Directly, through your machine
Where do your credentials live?	On the company's systems	In a local file you control	In a local store on your machine
Does the tool vendor need to be in the transfer path?	Yes	No	No
Can provider limits still apply?	Yes, and shared company servers can be throttled or blocked for every user at once	Yes, but traffic uses your own IP	Yes, but traffic uses your own IP
What does it cost you over time?	Subscription or per-GB fee	Free tool, your setup time	Lifetime licence, no subscription or per-transfer fees
What does it ask of you?	An account and trust in the relay	Comfort with a terminal	Signing in and clicking

Reachability and Blocking

A hosted service reaches every provider from the same pool of server addresses. That is the pattern most likely to attract shared-service rate limits, geofencing, or blocks, and when it happens, every user of that service is affected at once. A tool on your own machine connects from your own IP address, so there is no company relay address to single out. For services that were never designed for bulk export, that difference can matter, although account-level and API limits still apply.

Which One Fits You

Pick a hosted service if you want nothing installed, you are moving a modest amount, and a shared team dashboard matters more than keeping data and keys on your own side. These services are genuinely convenient, and for the right job that convenience wins.
Pick a local script if you live in the terminal and want maximum control with no interface in the way.
Pick a desktop app if you want the direct, local route without the setup, especially for large libraries or providers that resist bulk transfers.

No Single Design Wins

No single design is best for everyone. A hosted service removes all setup and is easy to share across a team. A script is the most flexible if you are willing to learn it. A desktop app aims at the middle: the privacy and reach of running locally, with the ease of a visual tool. The right choice is the one whose trade-offs you are happy to live with.

Frequently Asked Questions

Does a desktop app still send my data through my computer? Yes, and that is the point. The data streams through your machine to the destination instead of through a separate company's servers, and no second full copy is saved to your disk.

Why can a hosted service get blocked when a desktop app does not? The hosted service connects from shared company servers that a provider can recognize and throttle. A desktop app connects from your own IP, so there is no shared relay address to block for every user at once.

Is a local tool less safe because the credentials are on my machine? Your machine is a single device under your control, not a shared database of many users' keys. For most people, one device they control is a smaller target than a company server holding thousands of accounts' credentials.

Next Steps

See the on-your-machine design in How Blober Works.
Understand the privacy angle in The Zero-Knowledge Illusion in Cloud Transfer Tools.
Ready to keep the route local? Get Blober.

Archiving Large Research and Scientific Datasets Across Clouds

Jun 24, 2026

The Shape of Research Data

Research datasets are large, occasionally needed years later, and often spread across storage paid for by different grants or collaborators. Archiving them well means picking durable storage, moving the data without a scripting project, and using transfers that resume when a multi-day run gets interrupted.

Anyone who has managed a lab's data knows the pattern. A dataset lives on a cluster's object store, a copy sits in a collaborator's account, and the grant that funded the original storage is ending. The data has to move, it is enormous, and nobody wants to own the migration.

Choose Storage That Suits an Archive

Active analysis and long-term archive have different needs. For the archive, the priorities are durability and a cost model that fits data you read back rarely:

Object storage such as Backblaze B2, Wasabi, or Cloudflare R2 is built for exactly this: large objects, high durability, S3-compatible so your existing tools work.
Compare on egress and minimum storage duration, not the headline rate. For an archive you touch a few times a year, those terms decide the real cost far more than the storage price.
Keep a second copy. A single archive is one copy. Durable does not mean infallible, and a second location is what the 3-2-1 rule is for.

Moving the Data Without a Scripting Project

The usual options at this scale are command-line tools and custom scripts, which is fine if you have an engineer to spare and a problem when you do not. The bottleneck is rarely the copy itself. It is listing millions of small files, keeping throughput up with parallelism, and resuming cleanly when a run that takes days gets interrupted.

Blober handles those parts from a desktop app. It connects to S3, B2, Wasabi, R2, DigitalOcean Spaces, Azure Blob, and local storage, copies between them directly without staging a full copy on disk, runs transfers in parallel, and has skip-existing so a paused or failed run picks up where it left off instead of starting over. For a dataset larger than any one machine's disk, that combination is the difference between a finished archive and an abandoned one.

Document What You Moved

An archive nobody can navigate is only half useful. As you move data, keep a simple record: what went where, when, and the rough file count, so a future you or a future student can find a dataset without reverse-engineering the folder tree. A short README in the destination bucket pays for itself the first time someone needs the data after you have moved on.

Frequently Asked Questions

Where should I archive large research datasets? Durable object storage such as Backblaze B2, Wasabi, or Cloudflare R2, chosen on egress and minimum storage duration rather than the headline rate, with a second copy in another location.

How do I move a multi-terabyte dataset between clouds? Use a tool that transfers directly, runs in parallel, and resumes. Blober copies between object stores and local storage from a desktop app, with skip-existing so interrupted runs continue rather than restart.

What makes large transfers fail? At scale, listing millions of small files and surviving interruptions are the hard parts, not the copy. Parallelism and resumable, skip-existing transfers are what get a multi-day run to finish.

Is object storage good for research archives? Yes. It is durable, built for large objects, and usually S3-compatible, so existing tools work. Keep a second copy elsewhere to satisfy 3-2-1.

Get Blober

Move multi-terabyte datasets between object stores and local storage without a scripting project. Blober transfers in parallel, preserves structure, and resumes interrupted runs.

Download Blober at blober.io

Consolidating Multiple Cloud Accounts Into One (Without Losing Folder Structure)

Jun 24, 2026

Merging Scattered Cloud Accounts, Done Right

To consolidate files spread across several clouds, pick one destination, then copy each source into its own folder there so nothing collides, keeping the original folder tree intact. The hard part is not the copying. It is doing it without flattening your structure or creating a thousand duplicates.

Most people accumulate clouds by accident: a personal Dropbox, a work Google Drive, an old S3 bucket from a project, a free account that came with a device. Finding one file means remembering which silo it is in. Consolidating fixes that, if you do it carefully.

Decide the Destination First

Before moving anything, choose where everything will live. Match it to how you work:

Google Drive or Dropbox if you mostly open and share documents and want easy collaboration.
A NAS or external drive if you want the files under your own roof and off a subscription.
Object storage like Backblaze B2 or Wasabi if it is mostly a large archive you rarely touch.

Pick one. Splitting the destination defeats the point.

Preserve the Structure, Avoid Collisions

This is where consolidations go wrong. Two sources both have a folder named "Projects," they merge, and now you cannot tell which file came from where. The fix is simple: give each source its own top-level folder in the destination, for example from-dropbox/, from-drive/, from-old-s3/, and copy each source's tree underneath. You keep every original path, and nothing overwrites anything.

Blober preserves folder structure when it copies, so the tree you had in each source lands intact in the destination. Point it at a source, choose the destination folder, and it recreates the hierarchy rather than dumping files into one flat pile.

Watch for the Native-Format Trap

If one of your sources is Google Drive, remember that Google Docs, Sheets, and Slides are not real files. They are pointers to Google's editor, and copying them without exporting leaves you with empty links. Decide how those should come across before you move them, so your consolidated library holds real documents, not dead shortcuts.

Do It Once, Then Verify

Run the moves source by source rather than all at once, so you can check each as it lands. When everything is in place, open a few files from each from-* folder and confirm the counts look right. Once you trust the consolidated copy, you can retire the old accounts on your own schedule.

Frequently Asked Questions

How do I combine files from different cloud accounts? Choose one destination, then copy each source into its own folder there so nothing collides. A tool like Blober copies between accounts directly and keeps the folder structure intact.

Will consolidating clouds create duplicate files? Not if you give each source its own top-level folder in the destination. That keeps same-named folders from merging and overwriting each other.

Does moving files between clouds keep my folder structure? With Blober, yes. It recreates the source's folder tree in the destination rather than flattening everything into one folder.

What happens to Google Docs when I consolidate? Google Docs, Sheets, and Slides are editor links, not files. Export them to a real format as part of the move, or you will copy empty pointers.

Get Blober

Pull files from every cloud you use into one home, with the folder structure intact. Blober connects to a wide and growing range of cloud providers plus local storage and copies between them directly.

Download Blober at blober.io

Server-to-Server vs Download-and-Reupload: Why the Difference Decides Your Transfer

Jun 24, 2026

The Two Ways to Move Files Between Clouds

There are two ways to move files from one cloud to another. The common way downloads every file to your computer and uploads it again to the destination, which leaves a full copy on your disk and makes your machine the slow part. The other way, often called server-to-server or a direct transfer, streams the data between the two services without staging a full copy on your disk, so local disk space stops being the limit.

The difference is invisible for ten files and decisive for ten thousand. Understanding it saves you from a stalled migration halfway through a terabyte.

A Quick Word on "Server-to-Server"

The label is looser than it sounds. A literal server-to-server copy, where the two providers hand the bytes straight to each other and nothing passes through you, only happens in narrow cases: within a single provider, or between two services that specifically support it. What a desktop tool like Blober gives you instead is a streamed copy. The data flows through the app rather than being staged on your disk, so disk space stops being the limit, though the bytes still travel over your own connection. The win is skipping the second full copy, not escaping your network.

Download-and-Reupload, and Where It Breaks

Drag a cloud folder to your desktop and back into another service, or let a sync client mirror it locally, and you are doing a download-and-reupload. It works, and for small jobs it is fine.

It breaks in three ways at scale. First, disk: a 2 TB move needs 2 TB of free space, which most laptops do not have. Second, time: every byte makes two trips through your machine. Third, fragility: a sync client chewing through thousands of files will choke, duplicate, or stall, and you babysit it.

What a Direct Transfer Changes

A direct transfer connects to both services and streams data from the source to the destination without writing a full local copy to disk. The practical wins:

Disk space stops being the limit. You can move far more than your free disk, because the files are not staged there.
It runs in parallel. Many files move at once instead of one slow queue, which is what actually makes a big library finish.
It skips what is already done. If a transfer drops partway, re-running it carries only the files that did not make it, instead of starting the whole job over.

The Honest Caveats

A direct transfer is not magic, and it helps to know the real boundaries. The data still travels over the connection of wherever the tool runs, so your bandwidth is part of the equation. Egress, what a source provider charges to read your data out, still applies regardless of the tool, so plan the move as one clean pass rather than repeated pulls. What you avoid is the second full copy on your disk and the double handling that comes with it.

Where Your Data Goes (and Does Not)

There is a second axis worth separating from disk: who handles your data. Some cloud-to-cloud services route your files through their own servers, which means a third party touches them. Blober is a desktop app, so it runs on your machine with your credentials, and your data is not parked on someone else's server in the middle. You get the direct-transfer benefit without handing your files to a relay.

Frequently Asked Questions

What is a server-to-server transfer? Strictly, it means the two providers move the data between themselves so it never touches your machine, which only works in specific cases. In practice, most "server-to-server" tools stream the data through the tool instead. Blober does this from your own machine: the files are never staged as a full copy on your disk, though they do travel over your connection.

Do I have to download files to move them between clouds? Not with a direct-transfer tool. Blober streams between the source and destination without writing a full copy to your disk, so disk space is not the limit.

Why is my cloud-to-cloud transfer so slow? A download-and-reupload sends every byte through your machine twice and often runs one file at a time. A parallel direct transfer keeps many files moving at once, which is far faster for large libraries.

Does a direct transfer avoid egress fees? No. Egress is charged by the source provider for reading your data out, no matter which tool you use. A direct transfer avoids the wasted second trip and the local copy, not the provider's egress.

Get Blober

Move large libraries between clouds without filling your disk. Blober streams files directly between a broad, growing set of cloud providers and local storage, in parallel, and runs on your machine rather than a third-party server.

Download Blober at blober.io

What S3-Compatible Really Means (and Why It Matters When You Switch)

Jun 24, 2026

What "S3-Compatible" Actually Means

S3-compatible means a storage service speaks the same API language as Amazon S3. Tools, SDKs, and apps built for S3 can usually work with it for common object operations by changing endpoint and credentials. It does not mean the service is run by Amazon, and it does not promise every feature is identical.

The S3 API became a de facto standard. Once enough tools spoke it, new providers had a choice: invent their own interface and ask everyone to re-tool, or speak S3 and work on day one with the entire existing ecosystem. Most chose S3.

The API Is the Standard, Not the Company

Think of it like a power socket. The plug shape is the standard, and a device built for that plug can draw power without caring which utility generated the electricity. S3 compatibility is the plug shape for object storage. Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces all expose an S3-compatible endpoint, so tools such as aws s3, rclone, and desktop transfer apps can point at them by changing the endpoint and the keys.

Why It Matters When You Switch

The real value of S3 compatibility is that it makes providers more swappable. If your app reads and writes through the common S3 operations, moving from one S3-compatible store to another is mostly a matter of changing the endpoint and the credentials, not rewriting code. That keeps you from being locked in by your tooling, and it means a provider's pricing model or a new egress policy does not trap your data with them.

What Compatibility Does Not Guarantee

Compatible is not identical. A few things still vary between S3-compatible providers, so check them before you commit:

Feature coverage. Lifecycle rules, versioning, object lock, and multipart limits differ. Most common operations are covered; the long tail is not always.
Performance and consistency. Throughput, latency, and edge-case consistency behavior are the provider's own.
Regions and durability. Where your data physically sits, and how many copies are kept, is a provider decision.
The pricing model. Egress and minimum storage duration are where S3-compatible providers differ most, and those terms decide the real cost of an archive far more than the headline storage rate.

A Note on Azure Blob

Azure Blob Storage uses its own API rather than the S3 API, so it is not S3-compatible in the same drop-in way. The concepts line up (an S3 bucket maps to a container, an object to a blob), but a tool pointed at S3 will not talk to Azure Blob without a translation layer. That is worth knowing if your stack assumes S3 everywhere.

When you do need S3-compatible applications to run against Azure, an S3 gateway sits in front of Azure Blob and converts S3 API calls to Azure Blob calls on the fly:

Flexify.IO runs an S3 gateway in front of Azure Blob Storage^[source].
s3proxy is an open-source proxy that presents an S3 API backed by Azure Blob and other stores^[source].
VersityGW is an open-source S3 gateway with pluggable backends^[source].
MinIO is S3-compatible storage that has been used to put an S3 API in front of other backends^[source].

For .NET projects, FluentStorage takes a different route. Rather than a gateway, it is a polymorphic cloud storage abstraction layer, so one codebase targets S3, Azure Blob, and other stores without per-provider code^[source].

Moving Between S3-Compatible Stores

Because the core API is shared, moving data between S3-compatible providers is usually straightforward. Blober connects to S3, Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces, and its generic S3 connector points at other S3-compatible endpoints by URL when they support the common operations Blober uses. It also bridges to non-S3 services like Azure Blob, Dropbox, and Google Drive. You point it at a source and a destination and it copies between them directly, without staging a full copy on your disk.

There are dozens of well-known S3-compatible services, plus self-hosted servers and enterprise systems you can run yourself. For a practical roster with endpoints and setup, see The Complete List of S3-Compatible Storage Providers.

Frequently Asked Questions

Is Backblaze B2 S3-compatible? Yes. B2 exposes an S3-compatible API, so S3 tools and SDKs work against it by changing the endpoint and keys.

Is Azure Blob Storage S3-compatible? Not natively. Azure Blob uses its own API. The concepts map across (container for bucket, blob for object), but S3 tools need a translation layer to talk to it.

Does S3-compatible mean exactly the same as AWS S3? No. It means the same API language. Features like lifecycle rules and versioning, plus performance, regions, and the pricing model, vary by provider.

Can I switch S3-compatible providers without changing my app? Usually yes, if your app uses the S3 API. You change the endpoint and credentials. Check that the specific features you rely on are supported by the new provider first.

Get Blober

Switch object-storage providers without the re-tooling headache. Blober moves data between S3, B2, Wasabi, R2, Spaces, and more, directly and without filling your local disk.

Download Blober at blober.io

DigitalOcean Spaces: Regions, Cross-Region Replication, and Backup

Jun 9, 2026

Spaces Regions and the Replication Question

The problem: people assume DigitalOcean Spaces replicates across regions the way Amazon S3 can, so a single Space feels like a backup. It is not. A Space lives in one region, and DigitalOcean does not copy it to another region for you.

The short answer: pick the region closest to your users when you create a Space, and if you want a second copy in another region or another provider, you have to make it yourself. This page lists the regions, explains what Spaces does and does not replicate, and shows how to create a real backup copy.

DigitalOcean Spaces Regions

Each Space is tied to one datacenter region, chosen at creation and fixed afterward. The current Spaces regions and their locations:

Region code	Location
NYC3	New York City, United States
SFO3	San Francisco, United States
AMS3	Amsterdam, Netherlands
FRA1	Frankfurt, Germany
SGP1	Singapore
SYD1	Sydney, Australia
BLR1	Bangalore, India

DigitalOcean adds regions over time, so check their documentation for the latest availability. The practical rule is unchanged: choose the region nearest the people who read the data most, because a Space only serves from its own region's endpoint.

Does DigitalOcean Spaces Do Cross-Region Replication?

No. DigitalOcean Spaces does not offer built-in cross-region replication. There is no setting that mirrors a Space in NYC3 to a Space in FRA1, and no automatic failover to another region.

This is the main difference from Amazon S3, which has Cross-Region Replication (CRR) as a bucket feature. On Spaces, if you want the same objects in two regions, you copy them there yourself and keep them in sync by re-copying when things change.

A few consequences worth knowing:

A region outage affects a single Space directly. With no replica, you cannot fail over to another region automatically.
Compliance or latency in a second geography means creating a second Space and populating it yourself.
There is no native "backup to another region" button. Backup is something you set up, not something Spaces does for you.

The CDN Is Not a Backup

DigitalOcean Spaces includes a built-in CDN that caches your objects at edge locations for faster delivery. This is easy to mistake for replication, but it is not. The CDN caches copies for performance and can expire them at any time. The authoritative copy still lives in one region, and if that object is lost, the cache does not protect you. Edge caching speeds up reads; it does not give you a durable second copy.

How to Copy a Space to Another Region or Provider

Since Spaces will not replicate for you, the job is a straightforward copy, and Blober handles it without scripts or AWS-CLI loops.

Spaces to another Spaces region. Connect your DigitalOcean account in Blober. It detects every Space across all regions in one view, so you can copy objects from a Space in one region into a Space you create in another. Run it again later to refresh the copy, skipping objects that already exist.
Spaces to another provider. Use the same flow to copy a Space to AWS S3, Backblaze B2, Wasabi, Cloudflare R2, Azure Blob, Google Drive, Dropbox, or local and NAS storage, for an offsite backup that does not depend on DigitalOcean at all.
Resumable. Large copies survive a dropped connection and continue where they stopped.

This gives you the second copy that Spaces does not provide on its own, in whichever region or provider you choose.

Migrating Off DigitalOcean

If the goal is not a backup but a move, the steps are the same, just pointed at one destination. The most common move is to Amazon S3, which has the storage tiers and ecosystem Spaces lacks. There is a full walkthrough in How to Migrate from DigitalOcean Spaces to AWS S3, including how Blober detects Spaces across all seven regions and maps them to S3 storage classes.

For very large Spaces with millions of objects, see Migrating 100 Million Files from DigitalOcean to Backblaze.

Frequently Asked Questions

Does DigitalOcean Spaces support cross-region replication? No. There is no built-in cross-region replication. To have a Space's objects in a second region, you copy them yourself, which Blober can do across all regions in one workflow.

Which regions can I create a Space in? Currently NYC3, SFO3, AMS3, FRA1, SGP1, SYD1, and BLR1. DigitalOcean occasionally adds regions, so confirm on their site.

Can I move a Space from one region to another? Not in place. You create a new Space in the target region and copy the objects over. Blober copies between regions directly without downloading everything to your computer first.

Is the Spaces CDN a backup? No. The CDN caches objects at the edge for faster delivery and can evict them at any time. The durable copy still sits in one region. For a backup, make a separate copy in another region or provider.

How do I migrate from DigitalOcean to AWS? Connect both in Blober, set DigitalOcean as the source and S3 as the destination, and run. The DigitalOcean Spaces to AWS S3 guide covers it step by step.

Get Blober

Make the second copy that DigitalOcean Spaces will not make for you, to another region or another provider. Blober is a one-time purchase with no per-GB fees.

Download Blober at blober.io

Dropbox and Google Drive: Sync, Transfer, or Migrate?

Jun 9, 2026

Sync, Transfer, or Migrate: Which One Do You Need?

The problem: "sync Dropbox to Google Drive," "transfer Dropbox to Google Drive," and "migrate Dropbox to Google Drive" sound like the same task, so people pick the wrong tool and end up with duplicates, a full hard drive, or a subscription they did not need.

The short answer: they are three different jobs. Pick by how often the files need to move.

You want to...	That is called	How often it runs	Right tool
Move everything once and leave Dropbox behind	Migrate	One time	A direct transfer app like Blober
Keep both accounts and copy new files over now and then	Transfer / incremental refresh	On demand, repeated	Blober (re-run the workflow, it skips what already moved)
Keep both accounts mirrored automatically, in the background	Live sync	Continuous, both directions	A dedicated sync service (see below)

Most people who type "sync Dropbox to Google Drive" actually want the first or second one. They are switching providers or making a backup copy, not running a permanent mirror. If that is you, a migration is simpler, cheaper, and leaves nothing running in the background.

Migrate: A Clean One-Time Move

A migration moves your files from Dropbox to Google Drive once. After it finishes, you verify everything arrived, then cancel or downgrade Dropbox. There is no ongoing connection.

This is the right choice when:

Your company moved to Google Workspace and Dropbox is being retired
You are consolidating two accounts into one
You want your files out of a provider you are leaving

The fastest way to do this without filling your local disk is a direct cloud-to-cloud transfer. Blober streams each file from Dropbox straight to Google Drive, so you do not download the whole library to your computer first. Step-by-step guides:

How to Move Dropbox to Google Drive
How to Switch Google Drive to Dropbox for the reverse direction

Transfer (Incremental Refresh): Copy New Files When You Want

Sometimes you keep using both accounts but want one to receive copies of the other. For example, you work in Dropbox but keep a copy of finished projects in Google Drive.

Blober handles this with saved workflows. You set Dropbox as the source and Google Drive as the destination once. When you want to copy the latest files, you open the workflow and run it again. Blober skips any file that already exists at the destination, so a re-run only moves what is new. This gives you a manual, on-demand refresh without re-copying your whole library every time.

What this is not: it does not watch your folders and copy changes the instant they happen, and it does not run on a schedule by itself. You start each run. For many people that is enough, because they refresh the copy once a week or after a project wraps, not every minute.

Live Sync: When You Genuinely Need a Background Mirror

Live sync keeps two locations matched automatically and continuously. Add a file on one side and it appears on the other within minutes, without anyone pressing a button. True two-way sync also handles edits and deletions in both directions.

Blober does not do continuous background sync today. Two-way sync is on the roadmap, but right now Blober is built for migrations and on-demand transfers, not always-on mirroring. If what you need is a real-time mirror between Dropbox and Google Drive, be honest with yourself about that and use a tool built for it:

Dropbox and Google Drive do not sync to each other natively. Neither company offers a built-in bridge to the other.
Dedicated sync services (for example MultCloud or similar cloud-to-cloud sync tools) can run scheduled or near-real-time syncs between the two. They work, but they route your files through their servers, and they charge a recurring subscription, often with a monthly data cap.

If you only need the mirror for a short project, a sync service on a free or trial tier may cover it. If you need it forever, weigh the ongoing cost against simply doing a clean migration and standardizing on one provider.

"Integration" Usually Means Something Else

A lot of "Dropbox Google Drive integration" searches are really about connecting Dropbox or Drive to a third app: pulling a Dropbox file into Google Sheets, or attaching Drive files in another service. That is an app connector or an automation tool (such as a no-code automation platform), not a storage transfer. If that is what you are after, you do not need a migration tool at all. If you want the actual files to live in the other service, you are back to migrate or transfer above.

How to Decide in One Minute

Moving off one provider for good? Migrate. Run a one-time transfer, verify, then cancel the old account.
Keeping both but want copies kept fresh? Use a re-runnable transfer (Blober workflow with skip-existing) and run it when you need it.
Need changes mirrored automatically, both ways, all the time? Use a dedicated live-sync service, and accept the subscription that comes with it.

For the first two, here is the fastest path that does not fill your disk or charge per gigabyte: move Dropbox to Google Drive with a direct transfer.

Frequently Asked Questions

Can I auto-sync Dropbox to Google Drive? Not with Blober today. Blober runs migrations and on-demand transfers: you start each run, and it skips files that already moved. For continuous background sync in both directions you need a dedicated sync service. Two-way sync is on Blober's roadmap, but it is not live yet.

Is there a Dropbox to Google Drive migration tool that does not download everything first? Yes. Blober streams each file from Dropbox to Google Drive through your computer's memory, so you do not need free disk space equal to your whole library. Nothing is saved to your local disk during the transfer.

Will transferring create duplicates? On a first run, every file is copied once. On a re-run, Blober skips files that already exist at the destination, so you do not get duplicates as long as you keep the same source and destination.

Can I move just one folder instead of my whole account? Yes. You browse your Dropbox in Blober and select a single folder, several folders, or everything. The choice is yours per workflow.

Do I need to keep Blober running for the transfer to continue? The transfer runs while Blober is open. If your connection drops, it resumes from where it stopped. Once a migration finishes, you can close the app. There is no background service left running.

How to Move Dropbox to Google Drive
How to Switch Google Drive to Dropbox
Provider setup: Dropbox and Google Drive

Get Blober

For a clean one-time move or a repeatable copy between Dropbox and Google Drive, Blober is a one-time purchase. No subscription, no per-GB fees, no background service.

Download Blober at blober.io

Proton Drive Is Hard to Migrate To or From. Blober Makes It Easy.

May 27, 2026

The Privacy-First Cloud Storage That's Hard to Move Files Into

Proton Drive is one of the most privacy-respecting cloud storage services available. End-to-end PGP encryption. Swiss jurisdiction. Open-source clients. Zero-access architecture, so not even Proton can read your files. Over 100 million accounts trust it. If privacy is your priority, Proton Drive is a strong choice.

But there's a catch: Proton built great sync clients, not transfer tools.

Their official apps sync a folder between your device and Proton Drive. That works perfectly when Proton Drive is your only cloud. The moment you need to move files from Google Drive, from Dropbox, from AWS S3, or to Proton Drive from another provider, you're on your own. Download everything locally, then re-upload. For a few gigabytes, that's fine. For 500 GB of photos across three Google accounts, it's a weekend you don't get back.

Where Proton Drive Is Officially Supported

Proton offers native clients on four platforms, plus web access:

Platform	Client	Sync	File Browser	Bulk Transfer From Other Clouds
Windows	✅ Desktop app	✅ Folder sync	✅ Via web	❌
macOS	✅ Desktop app	✅ Folder sync	✅ Via web	❌
iOS	✅ Mobile app	✅ Photo backup	✅ In-app	❌
Android	✅ Mobile app	✅ Photo backup	✅ In-app	❌
Linux	❌ No client	❌	✅ Web only	❌
Web	✅ Browser	❌	✅	❌

Notice the last column. Across every platform, on every client, there is no built-in way to transfer files from another cloud provider into Proton Drive. The official path is: download to your machine, then let the sync client pick it up. That means you need enough free local storage to hold everything in transit.

And if you're on Linux, there is no desktop client at all. You get the web interface, which works but doesn't support drag-and-drop bulk uploads from other services either.

What The Proton Client Does Well (And What It Doesn't)

The Proton Drive clients are well-built for their intended purpose, which is sync, not migration:

What they do well:

Folder sync between your device and Proton Drive
Automatic photo backup on mobile
End-to-end encryption handled transparently
Proton Docs and Sheets integration

What they're not built for:

Moving files between Proton Drive and another cloud
Browsing or selecting files from another cloud as part of a transfer
Repeatable transfer workflows
Linux without a browser

That's the gap Blober fills.

What About rclone?

rclone is the canonical open-source tool for cloud storage. It supports 70+ backends and is genuinely excellent at what it does. Its Proton Drive backend works, with a couple of things worth knowing up front:

Tier 4 (Experimental). rclone classifies its Proton Drive support as Tier 4, meaning it's community-maintained and flagged as "use with care." Known gaps include unsupported modification times, draft conflicts on retries, and stale caching when other clients touch the same files. The underlying Proton-API-Bridge library notes there are "likely quite a few errors."
Password-based auth. To set up rclone with Proton Drive, you provide your Proton email, password, 2FA, and (if applicable) mailbox password through rclone config. These end up in rclone's config file on disk.

If you're already in the rclone ecosystem and these tradeoffs work for you, rclone is a perfectly good fit. Blober is a different style of tool for a different style of user, and the rest of this article is about that.

How Blober Handles Proton Drive Differently

Blober takes a different approach to Proton Drive: instead of asking for your credentials in a config file, it asks Proton for them.

You Just Log In. Normally.

When you connect Proton Drive in Blober, a browser window opens to account.proton.me, which is Proton's own login page. You sign in with your email, password, and 2FA exactly as you would in any browser. Your password never touches Blober. It stays inside the isolated browser session, the same way it does when you log in at drive.proton.me.

What Blober Supports With Proton Drive

Operation	Supported	Details
Browse	✅	Navigate your full folder tree
Download	✅	Parallel, resumable downloads
Upload	✅	Parallel uploads, auto-creates folders
Delete	✅	Moves to Proton Trash (recoverable)
Metadata	✅	Filename, size, created/modified dates
Multiple accounts	✅	Each account gets its own session. Run transfers in parallel

What Blober Does That Proton's Client Can't

Transfer from any supported provider directly to Proton Drive. Google Drive, Dropbox, AWS S3, Azure Blob, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, Wasabi, Rabata, GoPro Cloud, local disk. No intermediate downloads.
Transfer from Proton Drive to any other provider. Moving away from Proton? Moving a subset of files to cold storage on Backblaze? Blober handles it.
Selective file transfer. Browse your source, pick exactly the files you want, transfer only those. Not a full sync of everything.
Saved workflows. Set up "Dropbox to Proton Drive" once, run it whenever you want. The workflow remembers your source path, destination path, filters, and file naming templates.
Works on Linux. Blober runs on Windows, macOS, and Linux. Since Proton doesn't ship a Linux desktop client, Blober is one of the few ways to get a desktop-native Proton Drive experience on Linux without using a browser.
Resumable transfers. If your session expires mid-transfer, Blober prompts you to re-authenticate and picks up where it left off. No files are lost or duplicated.

The Migration Scenario

Here's the situation Blober is built for:

You're on Google Drive or Dropbox. You've decided to move to Proton Drive for privacy. You have 200 GB of documents and photos spread across folders. Today, your options are:

Option A: Manual download and re-upload

Download 200 GB from Google Drive to your local machine (hours, needs free disk space)
Wait for Proton Drive sync client to upload it all (hours more, CPU-intensive due to encryption)
Repeat for Dropbox
Hope nothing failed silently

Option B: Google Takeout + manual upload

Request a Takeout archive (can take days)
Download the archive(s)
Extract, organize, upload to Proton Drive
Storage used: 3× (source cloud + local archive + Proton)

Option C: rclone

Run rclone config to set up your Google/Dropbox and Proton remotes
Provide your Proton credentials when prompted
Run rclone copy gdrive: protondrive: with the flags that fit your scenario
Drive everything from the CLI, including monitoring and restart

Option D: Blober

Sign in to Google Drive (OAuth) or Dropbox (OAuth)
Sign in to Proton Drive (browser login)
Select the files you want
Start the transfer, then come back and re-run the same workflow whenever you need to

Blober vs rclone for Proton Drive: Side by Side

	Blober	rclone
Auth method	Browser login via Proton's own page	Credentials in `rclone config`
Interface	Native desktop GUI	CLI
Modification times	Preserved from source	Not preserved
Resume on failure	Automatic	Manual restart
Linux	Native desktop app	CLI
Cross-provider transfer	Built-in (select source and destination)	`rclone copy source: dest:`
Multiple Proton accounts	Each one its own session	Separate config remotes
Scriptable automation	Workflows, no cron	Cron-friendly CLI
Mount as filesystem	Not supported	Supported (FUSE)

Who This Is For

Blober is a good fit if:

You're migrating into Proton Drive from Google Drive, Dropbox, or another cloud
You're moving out of Proton Drive to another provider, or shifting a subset to cold storage
You're on Linux and want a desktop-native way to manage Proton Drive files
You'd rather log in through a browser than configure credentials in a file
You want a repeatable, named workflow you can re-run later

rclone is a good fit if:

You're already in the rclone ecosystem and want one tool for everything
You need scriptable, cron-based automation
You want to mount Proton Drive as a filesystem (FUSE)
You prefer CLI control over a GUI

Using Proton Drive with Blober

Proton Drive is a genuine privacy-first storage service. End-to-end PGP. Zero-knowledge architecture. Open clients. The trade-off Proton makes for that privacy is that getting files in or out, at scale, isn't a first-class experience.

That's where Blober comes in. You sign in to Proton Drive through Proton's own login page, pick the cloud you're moving from or to (Google Drive, Dropbox, S3, Backblaze B2, R2, Wasabi, GoPro, NAS, or local disk), choose what you want to move, and let it run. No config files, no CLI, no separate sync clients to install. The same workflow runs on Linux, macOS, and Windows.

If you have files in other clouds and you want them in Proton Drive, or files in Proton Drive you want elsewhere: that's what Blober is for.

How to Migrate from DigitalOcean Spaces to AWS S3

May 11, 2026

Growing Out of DigitalOcean Spaces

DigitalOcean Spaces is a good starting point for object storage. It is simple, affordable ($5/month for 250 GB + 1 TB transfer), and S3-compatible. For small to mid-size projects, it does the job.

But as your storage needs grow, you run into limitations:

Region constraints. Spaces are region-scoped. Each region only sees its own Spaces. Cross-region replication is not available.
No storage tiers. Everything is stored at the same tier. There is no equivalent to S3's Glacier or Intelligent-Tiering for cost optimization.
Limited ecosystem. AWS S3 integrates with hundreds of services: Lambda, CloudFront, Athena, Step Functions, SageMaker. DigitalOcean's ecosystem is smaller.
Bandwidth limits. The included 1 TB transfer can be burned through quickly on busy applications.

When a project outgrows Spaces, AWS S3 is the most common destination.

Multi-Region Complexity

DigitalOcean runs Spaces across 7 regions: NYC3, SFO3, AMS3, SGP1, FRA1, SYD1, and BLR1. If you have Spaces in multiple regions, you need to handle each region separately.

Blober detects all your Spaces across all DigitalOcean regions automatically. When you connect your DigitalOcean account, Blober probes all 7 regions in parallel and presents a unified view of all your Spaces. You do not need to configure each region separately.

Tier Detection

DigitalOcean recently introduced cold storage tiers for Spaces. Blober detects whether a Space is using Standard or Cold storage and flags it accordingly. This helps you make informed decisions about which S3 storage class to target.

How to Transfer

Step 1: Connect DigitalOcean Spaces

Add DigitalOcean Spaces as a provider in Blober. You can use either:

S3-compatible credentials (Access Key + Secret Key) for basic access
Personal Access Token for richer bucket listing with project metadata

Blober discovers all your Spaces across all regions.

Step 2: Connect AWS S3

Add AWS S3 with your Access Key ID, Secret Access Key, and preferred region. Blober lists your S3 buckets.

Step 3: Map and Transfer

Create a workflow with DigitalOcean as the source and S3 as the destination. Browse your Spaces, select files or entire Spaces, and choose the target S3 bucket and storage class.

Options for the destination:

Storage class: Standard, Intelligent-Tiering, Standard-IA, Glacier Instant Retrieval, Glacier, or Deep Archive
Target bucket: Any existing S3 bucket (or create one in the AWS console first)

Step 4: Run

Blober handles the transfer with parallel multipart uploads on both sides. S3-to-S3-compatible transfers are efficient because both services speak the same protocol.

Cost Comparison

	DigitalOcean Spaces	AWS S3 Standard	AWS S3 Standard-IA
Storage (1 TB)	$5/mo (250 GB included) + $20/mo extra	$23/mo	$12.50/mo
Bandwidth (1 TB)	Included	$90/mo	$90/mo
PUT requests (100K)	$0.50	$0.50	$1.00

DigitalOcean is cheaper for simple, low-traffic use cases. S3 is more cost-effective at scale with its tiering options, especially if you use Intelligent-Tiering or Glacier for archival data.

Get Blober

One-time purchase. Transfer as much as you need.

Download Blober at blober.io

How to Migrate from Google Drive to Backblaze B2

May 11, 2026

Why Move from Google Drive to Backblaze B2?

Google Drive is a collaboration tool with storage built in. Backblaze B2 is pure storage built for scale. The reasons people move between them usually come down to one or more of these:

Cost. Google One charges $100/year for 2 TB. Backblaze B2 charges $6.95/TB/month, but for archival or backup data you access rarely, the math works differently. If you are storing 5+ TB of media, raw footage, or project archives, B2 can be significantly cheaper depending on your access patterns.
Control. B2 gives you S3-compatible API access, which means you can integrate it with backup tools, CDNs, media workflows, and custom applications. Google Drive's API is more limited for bulk operations.
Redundancy. Keeping a copy of your Google Drive data in B2 means you are not dependent on a single provider. If Google changes pricing, restricts your account, or has an outage, your files are safe elsewhere.

The Google Drive Challenge

Google Drive stores native files (Docs, Sheets, Slides) as cloud-only application states, not as downloadable files. When you need them outside of Google, they must be converted to Office formats first.

Google Takeout can export your Drive, but it takes hours, produces fragmented zip archives, and flattens your folder structure. For a migration to B2 specifically, Takeout is especially awkward because you would need to download everything locally, extract it, then upload it to B2 using a separate tool.

How Blober Handles It

Blober connects to both Google Drive and Backblaze B2. It handles the tricky parts automatically:

Google Docs become .docx files during transfer
Google Sheets become .xlsx files during transfer
Google Slides become .pptx files during transfer
Regular files (photos, videos, PDFs) transfer as-is
Folder structure is preserved in your B2 bucket
Shared files are accessible through a "Shared with me" virtual folder

Steps

Connect Google Drive: Add Google Drive as a provider in Blober. OAuth login through your browser.
Connect Backblaze B2: Add B2 with your Application Key ID and Application Key. Blober auto-detects your bucket regions.
Create a workflow: Set Google Drive as source, B2 as destination. Browse and select files or folders.
Run: Blober streams files from Google Drive to B2 through your machine. No local storage needed for intermediate files.

Storage Cost Comparison

	Google One (2 TB)	Backblaze B2 (2 TB)
Monthly	$8.33	~$14
Annual	$100	~$167
5 TB	$25/month (Google One Premium)	~$35/month
10 TB+	Not available on consumer plans	~$70/month
Egress	Free (via Drive sync/download)	Free up to 3x stored

For small amounts of active data, Google Drive is the better deal. For large archives, backups, and media libraries that you rarely access, B2's pay-for-what-you-use model wins.

A Common Setup

Many people do not fully leave Google Drive. Instead, they keep it for active collaboration (shared documents, team folders) and move everything else to B2:

Current projects stay in Google Drive for real-time editing
Completed projects, old photos, and archives go to Backblaze B2
Blober handles the transfer once, then you adjust your Google storage plan

This hybrid approach gives you the best of both: Google's collaboration features for active work and B2's affordable storage for everything else.

Get Blober

One-time purchase. No subscription, no per-GB fees.

Download Blober at blober.io

How to Migrate Google Drive Files to AWS S3

May 11, 2026

When Google Drive Is Not Enough

Google Drive works great as a collaboration tool. Real-time editing, sharing links, 15 GB free storage. But when your data grows past a few hundred gigabytes, or when you need programmatic access, versioning policies, or storage tiering, Google Drive starts showing its limits.

AWS S3 is built for exactly those use cases. It handles petabytes, offers multiple storage classes, integrates with hundreds of AWS services, and gives you full API control. The gap between Google Drive and S3 is not about which is "better." It is about what each one is built for.

Moving from one to the other is where things get complicated.

The Google Drive Export Problem

Google Drive stores some files as native Google formats: Google Docs, Google Sheets, Google Slides. These are not actual files on disk. They are application states stored in Google's cloud. You cannot download a "Google Doc file" the way you download a PDF.

When you export from Google Drive (or use Google Takeout), these files get converted to their Microsoft Office equivalents: DOCX, XLSX, PPTX. But this conversion is often inconsistent with Takeout, and the folder structure gets flattened.

How Blober Handles Google Drive to S3

Blober connects to Google Drive via OAuth and to AWS S3 via access keys. It solves the two biggest pain points of this migration:

Automatic Google Docs Conversion

When Blober encounters a Google Doc, Sheet, or Slide, it automatically converts it to the corresponding Office format (DOCX, XLSX, PPTX) during transfer. This happens on the fly. You do not need to manually export anything.

The converted files land in your S3 bucket in a usable format that any application can read.

Folder Structure Preserved

Blober recreates your Google Drive folder hierarchy in S3. If you have Work/Projects/2025/Proposal.docx in Google Drive, it becomes Work/Projects/2025/Proposal.docx in your S3 bucket. No flat dumps, no reorganization needed.

Shared Files Included

Google Drive has a "Shared with me" section that is separate from your main drive. Blober shows this as a browsable folder, so you can include shared files in your migration if needed.

Steps

Connect Google Drive: Add Google Drive as a provider. Blober opens a browser window for OAuth authorization. Sign in and grant access.
Connect AWS S3: Add S3 with your Access Key ID, Secret Access Key, and region.
Create a workflow: Set Google Drive as source, S3 as destination. Browse your Drive, select files and folders.
Choose S3 options: Pick the storage class (Standard, Intelligent-Tiering, Standard-IA, Glacier, etc.) and target bucket.
Run: Blober transfers with progress tracking and auto-resume.

S3 Storage Class Selection

One advantage of moving to S3 is choosing the right storage class for your data:

Storage Class	Use Case	Cost (per TB/mo)
Standard	Frequently accessed files	~$23
Intelligent-Tiering	Unknown access patterns	~$23 (auto-optimizes)
Standard-IA	Infrequent access, fast retrieval	~$12.50
Glacier Instant	Archive with instant access	~$4
Glacier Deep Archive	Long-term cold storage	~$1

With Blober, you set the storage class when creating the workflow. All transferred files land on the tier you choose. If you want different tiers for different data, create multiple workflows.

Who Does This

Startups growing out of Google Workspace who need infrastructure-grade storage
Data teams that need to run analytics on files currently in Google Drive
Companies consolidating storage to AWS for compliance or integration reasons
Developers who want S3's API and event-driven architecture instead of Google Drive's sync model

Get Blober

One-time purchase. No per-GB fees, no subscription.

Download Blober at blober.io

How to Move Data from Azure Blob Storage to Cloudflare R2

May 11, 2026

The Egress Problem

Azure Blob Storage charges $0.087 per GB for data leaving their network. If you serve 1 TB of files per month to users or external systems, that is $87/month in egress alone, on top of storage costs.

Cloudflare R2 charges $0 for egress. Zero. Nothing. You pay for storage ($0.015/GB/month) and operations, but downloading data from R2 is free. For applications that serve files to users, APIs, CDNs, or other services, switching to R2 can cut your cloud bill significantly.

Why People Make This Move

The most common reason is cost. If your Azure Blob account is mostly used for serving static assets, media files, backups that get restored frequently, or API responses, the egress fees can dwarf your storage costs. R2 removes that variable entirely.

Another reason is simplicity. R2 is S3-compatible, meaning any tool or SDK that works with S3 works with R2. If your application already uses the S3 API (many do, even on Azure), the migration is mostly about moving data and updating the endpoint.

How to Transfer with Blober

Blober supports both Azure Blob Storage and Cloudflare R2 as native providers. The transfer works like any other Blober workflow: connect both accounts, select files, run.

Step 1: Connect Azure Blob Storage

Add Azure Blob as a provider with your connection string. Blober lists your containers and their contents.

Step 2: Connect Cloudflare R2

Add Cloudflare R2 as a provider. You will need your Account ID along with an S3-compatible Access Key ID and Secret Access Key from the Cloudflare dashboard. If you also provide a Cloudflare API token, Blober can list your buckets through Cloudflare's native API with server-side pagination, which is more efficient for accounts with many buckets.

Step 3: Create a Workflow

Set Azure Blob as the source and Cloudflare R2 as the destination. Browse your Azure containers, select the files or containers you want to migrate, and choose the destination bucket in R2.

Step 4: Run

Blober streams data from Azure through your machine to R2. It uses parallel uploads on both ends, so large files move efficiently. If the transfer is interrupted, Blober resumes from where it stopped.

What About Azure Egress Fees During Migration?

This is the unavoidable part. Moving data out of Azure means paying egress. For the initial migration, you will pay $0.087/GB to get your data from Azure to your machine (where Blober runs), and from there to R2.

For 1 TB, that is about $87 in egress fees. That is a one-time cost. After the migration, your ongoing egress from R2 is $0.

If you were paying $87/month in Azure egress, the migration pays for itself in the first month.

Migration Cost Estimate

Data Size	Azure Egress Cost (one-time)	Monthly Savings on R2
500 GB	~$43	Depends on egress pattern
1 TB	~$87	Up to $87/month
5 TB	~$435	Up to $435/month
10 TB	~$870	Up to $870/month

R2 Is S3-Compatible

This matters because your application code likely uses the AWS SDK or an S3-compatible client. After migrating data to R2, updating your app is often as simple as changing the endpoint URL and credentials. No SDK changes, no API rewrites.

Blober connects to R2 using the same S3 protocol, so the transfer is seamless.

When Azure Is Still the Right Choice

R2 is excellent for serving files and eliminating egress. But Azure has features that R2 does not:

Storage tiers (Hot, Cool, Cold, Archive) for lifecycle cost optimization
Geo-redundant replication built into the platform
Azure Functions and event triggers tied to blob operations
Enterprise compliance certifications that some industries require

If you need those features, Azure is worth the egress premium. Many teams keep some data on Azure (for processing and compliance) and move the served/public data to R2 (for cost savings).

Get Blober

One-time purchase. Transfer as much data as you need.

Download Blober at blober.io

How to Move Files from Dropbox to Backblaze B2

May 11, 2026

Why People Leave Dropbox for Backblaze B2

Dropbox works well as a file sync tool. You drop files in a folder and they show up on all your devices. But as your data grows, Dropbox gets expensive. The Plus plan costs $120/year for 2 TB. If you have 5 TB or more, you need Dropbox Business at $180/year per user.

Backblaze B2 charges $6.95 per TB per month for storage. For 2 TB, that is about $14/month or $167/year. But here is where it gets interesting: most of the data sitting in Dropbox is not being actively synced. It is old projects, archives, backups, photos from three years ago. That data does not need instant sync to every device. It needs to be stored cheaply and retrieved when needed.

For archival and backup storage, Backblaze B2 is significantly cheaper. And unlike Dropbox, you only pay for what you use. No fixed plans, no storage ceilings.

The Problem with Moving Data Out of Dropbox

The obvious approach is to download everything from Dropbox to your computer, then upload it to Backblaze B2. This works for small amounts of data. For 500 GB or more, it becomes painful:

You need enough free space on your local disk to hold the download
Downloading takes hours or days depending on your connection
Uploading to B2 takes equally long
If anything fails midway, you start over

Some people try rclone for this. rclone works, but you need to configure both remotes in a text file, understand the command syntax, and handle errors yourself. If you are comfortable with the terminal, rclone is a solid choice. If you are not, it is a wall.

How to Transfer with Blober

Blober connects to both Dropbox and Backblaze B2. You set up both providers, select the files you want to move, and Blober handles the transfer. Files stream from Dropbox through your computer to Backblaze B2 without needing to store them locally.

Step 1: Connect Dropbox

Add Dropbox as a provider in Blober. Click the OAuth login button and authorize Blober with your Dropbox account. Blober stores your credentials locally on your machine, not on any server.

Step 2: Connect Backblaze B2

Add Backblaze B2 as a provider. You will need your Application Key ID and Application Key from the Backblaze dashboard. Blober verifies the connection and lists your buckets.

Step 3: Create a Workflow

Create a new workflow with Dropbox as the source and Backblaze B2 as the destination. Browse your Dropbox files, select what you want to transfer, and choose which B2 bucket to send it to.

Step 4: Run

Click run. Blober transfers files with parallel uploads, progress tracking, and automatic resume if your connection drops.

What About Folder Structure?

Blober preserves your folder structure. If you have Projects/2024/Client-A/ in Dropbox, it creates the same path in your B2 bucket. You do not end up with a flat pile of files.

Cost Comparison

	Dropbox Plus	Backblaze B2 (2 TB)
Monthly cost	$10/month	~$14/month
5 TB	Need Business plan ($15/user/mo)	~$35/month
10 TB	Need Business plan	~$70/month
Egress	Free (sync)	Free to Cloudflare partners, $0.01/GB otherwise
API access	OAuth	S3-compatible

For pure storage (not sync), B2 wins at every tier above 2 TB. And if you pair B2 with Cloudflare CDN through the Bandwidth Alliance, egress is free.

When to Keep Dropbox

This is not about abandoning Dropbox entirely. Dropbox is great for active files you need on every device. The move that makes sense for most people is:

Keep Dropbox for current projects and actively used files
Move archives, old projects, and large media to Backblaze B2
Use Blober to transfer the archival data once, then cancel the upgraded Dropbox plan

Get Blober

Blober is a one-time purchase. No subscription, no per-GB transfer fees.

Download Blober at blober.io

How to Move Files from Dropbox to Google Drive

May 11, 2026

Move Dropbox to Google Drive Without Filling Your Disk

The problem: there is no built-in transfer between Dropbox and Google Drive. The manual route makes you download your entire Dropbox to your computer, then upload all of it to Drive. That needs free disk space equal to your whole library and sends every file over the network twice.

The short answer: you have three realistic options. Drag and drop through the desktop apps, upload through the browser, or run a direct cloud-to-cloud transfer with Blober that streams each file from Dropbox to Google Drive without saving it to your disk. Here is how they compare.

Method	Local disk needed	Speed	Folder structure	Best for
Manual (desktop sync, then drag)	Full library size	Slow: download, then upload	You may have to rebuild it	A single small folder
Browser upload	Enough to download first	Slow	Preserved if you recreate folders	A few gigabytes
Blober (direct)	None, files stream through memory	About half the time, single pass	Preserved automatically	Whole-account moves and large libraries

People switch from Dropbox to Google Drive for a few common reasons:

Their company standardized on Google Workspace and needs everything in Drive
Google One pricing is more competitive for their storage needs (2 TB for $100/year vs Dropbox Plus at $120/year)
They want the Google Docs, Sheets, and Slides collaboration features
They are consolidating everything under one Google account

The actual move is where friction shows up.

The Manual Way

Without a migration tool, moving from Dropbox to Google Drive looks like this:

Install the Dropbox desktop client
Wait for all files to sync to your computer
Drag those files into your Google Drive folder (if using the desktop client) or upload them through the browser
Wait for everything to upload
Verify nothing was missed

This requires enough local disk space to hold your entire Dropbox. If you have 500 GB in Dropbox and a 256 GB laptop, you are stuck.

Even with enough space, the process is slow. You are downloading everything from Dropbox's servers to your local disk, then uploading everything from your local disk to Google's servers. That is double the transfer time.

How Blober Does It

Blober connects to both Dropbox and Google Drive. Files stream from Dropbox through your computer to Google Drive without being stored on your local disk. You need just enough memory to buffer the current file being transferred, not enough disk space for your entire library.

What This Means Practically

No disk space worries. A 1 TB Dropbox migrates to Google Drive even on a laptop with 128 GB of storage.
Half the network time. Instead of download + upload (two trips), Blober streams the data through in a single pass. The download from Dropbox and upload to Google Drive happen simultaneously.
Folder structure preserved. Your Dropbox folder hierarchy recreates exactly in Google Drive.

Steps

Connect Dropbox: OAuth login in your browser. Blober supports both long-term OAuth tokens (with refresh) and direct access tokens.
Connect Google Drive: OAuth login in your browser. Blober accesses your Drive files.
Browse and select: Navigate your Dropbox in Blober's file browser. Select specific folders or your entire Dropbox.
Create a workflow: Set Dropbox as source, Google Drive as destination.
Run: Blober transfers with auto-resume and progress tracking.

Moving your whole Dropbox? Blober streams it straight into Google Drive without filling your laptop. Download Blober, connect both accounts, and start the transfer.

Copy and Move Support

Dropbox is one of the providers where Blober supports native copy and move operations. This means:

Copy duplicates files within Dropbox without re-downloading them
Move relocates files within Dropbox without a round-trip transfer

For the cross-cloud transfer to Google Drive, files stream through your machine as described above. But if you also need to reorganize files within Dropbox before or after the migration, Blober handles that natively.

After the Migration

Once your files are in Google Drive:

They are accessible from any device with a Google account
Google automatically indexes content for search
Office files (DOCX, XLSX, PPTX) can be edited natively in Google Docs/Sheets/Slides
Files sync across devices via the Google Drive desktop app

You can keep Dropbox installed alongside Google Drive if you need a transition period. Once you verify everything transferred correctly, you can downgrade or cancel Dropbox.

Frequently Asked Questions

Can I transfer files from Dropbox to Google Drive without downloading them first? Yes. Blober streams each file directly from Dropbox to Google Drive through your computer. Nothing is saved to your local disk, so you do not need free space equal to your library size.

Does Blober preserve my Dropbox folder structure in Google Drive? Yes. Your Dropbox folder hierarchy is recreated exactly in Google Drive, including nested folders.

How long does a Dropbox to Google Drive migration take? It depends on how much data you have and your upload speed. Because Blober downloads and uploads in a single pass instead of two separate trips, it finishes in roughly half the time of a manual download-then-upload.

Can I sync Dropbox to Google Drive automatically? Blober moves and copies files on demand through workflows that you start when you need them. You can re-run a workflow at any time to move newly added files. It is built for migrations and repeat transfers rather than always-on background sync.

Can I move from Dropbox to Google Workspace or a Shared Drive? Yes. Google Workspace accounts and Shared Drives appear in Blober once you connect Google Drive, so you can set either as the destination.

Switch from Google Drive to Dropbox for the reverse direction
Move Dropbox to Backblaze B2 for cheaper long-term storage
Provider setup: Dropbox and Google Drive

One Move, Not a Monthly Bill

Most cloud-to-cloud services bill per gigabyte or charge a monthly fee for as long as you keep them. Blober is a one-time purchase. Moving 50 GB costs the same as moving 5 TB, and there is nothing to cancel once the migration is done. For a one-off move from Dropbox to Google Drive, that is the difference between paying once and renting a tool for a weekend.

Get Blober

Move your Dropbox into Google Drive without filling your disk or paying per gigabyte. One-time purchase, no subscription, no per-GB fees.

Download Blober at blober.io

How to Switch from Google Drive to Dropbox

May 11, 2026

Move Google Drive to Dropbox Without the Google Docs Trap

The problem: Google Docs, Sheets, and Slides are not real files. They live only inside Google, so you cannot drag them into Dropbox, and Google Takeout exports your library as flat date-stamped zips that lose your folder names.

The short answer: you have three realistic options. Export each native file by hand, use Google Takeout and reorganize the zips afterward, or run a direct transfer with Blober that converts Google Docs to Office formats and rebuilds your folders in Dropbox automatically. Here is how they compare.

Method	Google Docs handling	Folder structure	Local disk needed	Best for
Manual export, then upload	Open and export each one	Rebuild by hand	Full library size	A handful of files
Google Takeout	Exports to Office, inside flat zips	Lost in date-stamped folders	Space for every zip	A full archive you will sort later
Blober (direct)	Auto-converts to .docx, .xlsx, .pptx	Preserved automatically	None, files stream through memory	Moving your account intact

Google Drive vs Dropbox: Different Strengths

Google Drive is tightly integrated with Google Workspace. If your team lives in Gmail and Google Docs, Drive is the natural file storage. But if you work with non-Google tools, or you need reliable desktop sync, offline access, and smart file management, Dropbox has a stronger desktop experience.

People switch from Google Drive to Dropbox for a few reasons:

Dropbox's desktop sync is more reliable for large file sets
Better support for non-Google file formats and creative tools
Dropbox Paper, Smart Sync, and team folder management
Moving away from Google Workspace entirely

Whatever the reason, the migration is the part nobody looks forward to.

Why the Switch Is Harder Than It Sounds

Google Drive stores some files as native Google formats. Google Docs, Sheets, and Slides are not files in the traditional sense. They exist only in Google's cloud. You cannot drag a Google Doc into Dropbox.

If you try to move files manually, you need to:

Open each Google Doc, Sheet, or Slide
Download it as DOCX, XLSX, or PPTX
Upload it to Dropbox
Repeat for every native Google file

For regular files (PDFs, images, videos), you download from Google Drive and upload to Dropbox. But you still need enough local disk space to hold everything, and you need to recreate the folder structure manually.

Google Takeout exports everything as flat zip archives. Your carefully organized folder structure disappears into date-stamped directories.

How Blober Makes This Painless

Blober connects to both Google Drive and Dropbox. When it encounters Google Docs, Sheets, or Slides, it automatically converts them to their Office equivalents (DOCX, XLSX, PPTX) during the transfer. Regular files pass through as-is.

What You Get

Google Docs become .docx files that open in Word, Dropbox Paper, or any text editor
Google Sheets become .xlsx files that open in Excel or Numbers
Google Slides become .pptx files that open in PowerPoint or Keynote
Regular files (PDFs, images, videos) transfer without conversion
Folder structure preserved exactly as it appears in Google Drive
Shared files accessible through the "Shared with me" virtual folder

Steps

Connect Google Drive: OAuth login through your browser
Connect Dropbox: OAuth login (or paste an access token)
Browse and select: Navigate your Google Drive in Blober's file browser, select everything or specific folders
Run the transfer: Files move from Google Drive to Dropbox through your computer

No local disk space needed for intermediate storage. Blober streams files directly from one cloud to the other.

Leaving Google Drive? Blober converts your Docs to Office files and rebuilds your folders in Dropbox in one pass. Download Blober, connect both accounts, and run it.

After the Switch

Once your files are in Dropbox, you can:

Install Dropbox on your devices for desktop sync
Share folders and files with Dropbox's sharing tools
Use Smart Sync to keep files in the cloud until you need them locally
Edit Office files directly (Dropbox has built-in Office integration)

The converted Google Docs are fully editable Office files. They are not locked into any format.

Frequently Asked Questions

Can I move Google Drive to Dropbox without downloading everything first? Yes. Blober streams files directly from Google Drive to Dropbox through your computer, so you do not need local disk space for the whole library.

What happens to my Google Docs, Sheets, and Slides? Blober converts them automatically during the transfer. Docs become .docx, Sheets become .xlsx, and Slides become .pptx, all fully editable in Office, Dropbox Paper, or similar tools.

Does Blober transfer files shared with me? Yes. Files shared with your Google account appear under the "Shared with me" folder in Blober and can be included in the transfer.

Can I sync Google Drive to Dropbox automatically? Blober transfers files on demand through workflows that you run when you need them, and you can re-run a workflow to move new files. It is designed for migrations and repeat transfers rather than continuous background sync.

Can I switch from Google Workspace or a Shared Drive to Dropbox? Yes. Workspace accounts and Shared Drives show up in Blober after you connect Google Drive, so you can use either as the source.

Move from Dropbox to Google Drive for the reverse direction
Provider setup: Google Drive and Dropbox

One Move, Not a Monthly Bill

Most cloud-to-cloud services bill per gigabyte or charge a monthly fee for as long as you keep them. Blober is a one-time purchase. Moving 50 GB costs the same as moving 5 TB, and there is nothing to cancel once the switch is done. For a one-off move from Google Drive to Dropbox, that is the difference between paying once and renting a tool for a weekend.

Get Blober

Move your Google Drive into Dropbox with your folders and Office files intact. One-time purchase, no subscription, no per-GB fees.

Download Blober at blober.io

How to Switch from Wasabi to Backblaze B2

May 11, 2026

Two S3-Compatible Providers, Different Tradeoffs

Wasabi and Backblaze B2 both position themselves as affordable alternatives to AWS S3. Both are S3-compatible. Both offer low-cost storage. But they have meaningful differences that lead people to switch from one to the other.

Wasabi's Model

Wasabi charges $6.99/TB/month with no egress fees. Sounds perfect, until you read the fine print:

90-day minimum retention. If you delete or overwrite a file within 90 days, you still pay for the full 90 days of storage.
Egress is "free" with conditions. Your monthly egress cannot exceed your stored data. If you store 1 TB and download 1.5 TB in a month, Wasabi may contact you about their "reasonable use" policy.
No native CDN partnerships. Wasabi does not have bandwidth alliance partnerships like Backblaze does.

Backblaze B2's Model

Backblaze B2 charges $6.95/TB/month for storage and $0.01/GB for egress. But:

Free egress through Cloudflare. Through the Bandwidth Alliance, egress from B2 to Cloudflare is free. If you use Cloudflare as your CDN (many do), egress is effectively $0.
No minimum retention. Store and delete whenever you want.
Free egress allowance. B2 includes 3x your storage amount in free egress each month. If you store 1 TB, you get 3 TB of free downloads.

For most use cases, Backblaze B2 ends up cheaper or equivalent to Wasabi, with fewer restrictions.

Moving the Data

Both Wasabi and Backblaze B2 speak the S3 protocol. This means Blober uses the same underlying S3 operations for both providers, making the transfer clean and predictable.

Steps

Connect Wasabi: Add Wasabi as a provider with your Access Key, Secret Key, and region (Wasabi uses region-specific endpoints like s3.us-east-1.wasabisys.com).
Connect Backblaze B2: Add B2 with your Application Key ID and Application Key. Blober auto-detects your bucket regions.
Create a workflow: Source = Wasabi, Destination = B2. Browse your Wasabi buckets, select what to move.
Run: Blober transfers with parallel multipart uploads and automatic resume.

What Blober Handles

Multi-region detection for B2. Backblaze B2 buckets can be in different regions. Blober fetches all buckets via B2's native API to determine the correct region for each, then configures the S3 endpoint accordingly.
Region-aware endpoints for Wasabi. Wasabi uses different endpoints per region. Blober maps your chosen region to the correct endpoint.
Large file support. Both providers handle multipart uploads. Blober chunks large files and uploads them in parallel.

Watch the 90-Day Window

When migrating from Wasabi, keep in mind the 90-day minimum retention policy. If you uploaded files to Wasabi less than 90 days ago, you will be charged for the full 90 days even after you delete them.

The practical approach:

Transfer everything to Backblaze B2
Wait until the oldest files in Wasabi pass the 90-day mark
Then delete and close the Wasabi account

This avoids paying both Wasabi and B2 for the same data longer than necessary.

Pricing Side-by-Side

	Wasabi	Backblaze B2
Storage per TB/mo	$6.99	$6.95
Egress per GB	$0 (with conditions)	$0.01 (free via Cloudflare)
Min retention	90 days	None
Free egress allowance	Equal to storage	3x storage
CDN partnership	None	Cloudflare Bandwidth Alliance

Get Blober

One-time purchase. No recurring fees, no per-GB charges.

Download Blober at blober.io

How to Transfer Files from AWS S3 to Azure Blob Storage

May 11, 2026

Moving Between AWS S3 and Azure Blob

AWS S3 and Azure Blob Storage are the two most popular object storage services in the world. Companies move data between them for all sorts of reasons: switching primary cloud vendors, setting up multi-cloud redundancy, following compliance requirements, or simply taking advantage of Azure's pricing for certain workloads.

The transfer itself is the hard part. Both providers have their own tools (AWS DataSync, Azure Data Box, AzCopy), but those tools are designed for their own ecosystem. Cross-cloud transfers with native tools usually require intermediate steps, scripting, or third-party managed services that charge per-GB.

The Usual Approaches

AzCopy + AWS CLI

You can download from S3 using the AWS CLI and upload to Azure using AzCopy. This requires local disk space for the intermediate files, separate authentication for each tool, and scripting to coordinate the two.

Managed Migration Services

Services like Flexify charge per-GiB transferred. For large migrations (10 TB+), the fees add up. Your data also routes through their infrastructure, which may not meet compliance requirements.

rclone

rclone supports both S3 and Azure Blob. It works, but you need to configure both remotes, handle multipart upload settings, and manage the transfer from the command line.

How Blober Handles It

Blober connects to both AWS S3 and Azure Blob Storage natively. You configure both providers with their respective credentials, create a workflow, and run the transfer. Files stream from S3 through your machine to Azure without intermediate storage.

What Blober Does That Matters for This Transfer

Parallel uploads to Azure. Blober uses Azure's uploadStream with configurable concurrency. Large files are streamed in parallel chunks, which makes a noticeable difference on fast connections.

S3 streamed reads. On the source side, Blober reads S3 objects as streams through the AWS SDK. Large objects do not need to be staged as full local files before Azure upload begins.

Azure tier selection. When setting up Azure as your destination, you choose which storage tier new blobs land on: Hot, Cool, Cold, or Archive. This means you can migrate directly to the tier that matches your access pattern without a second step to change tiers after upload.

Write behavior options. You can configure Blober to overwrite existing blobs, skip files that already exist at the destination, or skip only archived blobs. This is useful for incremental migrations where you want to resume without re-transferring what is already there.

Step-by-Step

Connect AWS S3: Add S3 as a provider with your Access Key ID, Secret Access Key, and region. Blober lists your buckets.
Connect Azure Blob: Add Azure Blob Storage with your connection string. Blober verifies and lists your containers.
Create a workflow: Set S3 as source, Azure Blob as destination. Browse and select files or entire buckets.
Choose Azure options: Pick the storage tier and write behavior.
Run: Blober transfers with progress tracking. If you stop and rerun later, skip-existing avoids sending blobs that already landed.

Migrating Buckets in Bulk

Most S3-to-Azure jobs are not a single file, they are whole buckets or whole prefixes. Blober is built for that.

Select an entire bucket or prefix. Browse your S3 bucket in Blober, select everything at the top level or drill into a prefix, and queue it all in one workflow. You do not enumerate keys by hand or script a loop.
Mass transfers run in parallel. Blober reads from S3 as streams and uploads to Azure with parallel streams, so a bucket with thousands of objects moves as a continuous pipeline rather than one object at a time.
Repeatable with skip-existing. Set the write behavior to skip blobs that already exist at the destination. If a multi-terabyte run is interrupted, or you stop and continue tomorrow, re-running the workflow picks up only what has not transferred yet. That is what makes a mass migration practical: you are not forced to start the whole job over.
Land directly on the right tier. Pick the Azure tier for the whole job, so a bulk archive migration writes straight to Cool, Cold, or Archive instead of landing on Hot and needing a second pass.

For a move of 5 TB across 200,000 objects from us-east-1 to westeurope, you point Blober at the bucket, choose the destination container and tier, turn on skip-existing, and let it run. Progress is tracked per file, and rerunning the workflow after an interruption skips blobs that already completed.

Cross-Region Awareness

If your S3 bucket is in us-east-1 and your Azure storage account is in westeurope, Blober handles the cross-region transfer. S3's cross-region copy limitations (which affect native S3-to-S3 copies) do not apply here because the data flows through your machine.

The tradeoff is that transfer speed depends on your internet connection. For very large migrations (50 TB+), this is usually slower than a datacenter-to-datacenter transfer. But for gigabytes to a few terabytes, running through Blober on a fast connection can be simpler than coordinating a managed migration service.

Pricing Comparison

For an S3-to-Azure move, price the transfer in parts instead of trusting a single headline number:

AWS S3 source cost: data transfer out, source reads, and any retrieval fees if the source objects are in an infrequent-access or archive class^[1].
Azure destination cost: Blob Storage usually does not charge for inbound data transfer, but new writes, storage tier, redundancy, and operation charges still matter^[2].
Future Azure egress: if the data later leaves Azure, outbound bandwidth is priced separately by route, zone, and volume^[3].

Azure can be cheaper for some storage-heavy workloads, while S3 can be better when the surrounding AWS ecosystem matters. The right choice depends on access pattern, region, redundancy, tier, request volume, and where the data will go next.

Frequently Asked Questions

How do I copy data from S3 to Azure Blob without AzCopy or scripts? Connect both providers in Blober, create a workflow with S3 as the source and Azure Blob as the destination, select your buckets, and run. There is no AzCopy command, no AWS CLI loop, and no intermediate download to your disk. Files stream from S3 straight to Azure.

Can I migrate a whole bucket, or only individual files? Either. Select a single object, a prefix, or an entire bucket. Whole-bucket and mass-data migrations are the common case.

Does the data land on the tier I want? Yes. You choose the Azure access tier (Hot, Cool, Cold, or Archive) for the destination, and new blobs are written to that tier on arrival. There is no second pass to re-tier after upload.

Who pays for the data transfer? AWS charges egress (data transfer out) when data leaves S3, billed per GB. Azure lists data transfer in as free, while outbound bandwidth is priced separately^[4]. So the transfer cost usually sits on the AWS side, the same as it would with any tool that reads from S3. Blober adds no per-GB fee of its own.

How large a migration can this handle? Transfers run through your machine, so speed depends on your connection. For moderate migrations, Blober avoids managed-service setup and can be rerun with skip-existing if interrupted. For datacenter-scale moves of 50 TB and up, a provider appliance or assisted migration may finish sooner.

Azure Blob Tiers vs AWS S3 Storage Classes for choosing the right destination tier
How to Bulk Change Azure Blob Storage Access Tiers once your data is on Azure
How to Move Azure Blob to Cloudflare R2 for moving off Azure later
Provider setup: AWS S3 and Azure Blob

Get Blober

Migrate S3 buckets to Azure Blob in bulk, with no AzCopy scripts and no per-GB transfer fee from us. One-time purchase, no subscription.

Download Blober at blober.io

Transfer GoPro Cloud Files in 45 Seconds with Blober

Apr 7, 2026

45-Second Demo

This video shows the full process of creating a Blober workflow with GoPro Cloud as the source.

What's Shown

1. Connect GoPro Cloud

Select GoPro Cloud as your source, click Open GoPro Login, and sign in. Blober captures your session. No API keys, no config files, no CLI.

2. Browse Your Media

Click Browse Files and Folders. Blober loads your GoPro Cloud library. Files are listed with date and size.

Blober file browser showing GoPro Cloud files with entire storage directory selected

You can select:

Individual files by clicking a single file
Multiple files by checking several files across folders
Entire directory by ticking the / (Entire Storage) checkbox

3. Create the Workflow

Click Submit Selection. The workflow editor shows your GoPro Cloud source with the selected items. Pick your destination (local disk, Backblaze B2, AWS S3, Dropbox, or another supported provider), configure options, and click Save Workflow.

Blober workflow editor with GoPro Cloud as source and entire storage selected

4. Run It

Close the workflow editor with the X button in the top-right corner. On the Workflows page, click the green Run button on your workflow card. Blober starts the transfer with parallel downloads, progress tracking, and automatic resume.

Why It Matters

GoPro's web portal limits batch downloads to 25 files at a time, bundled as ZIPs. Large downloads often fail. There is no bulk export and no "Download All" button.

Blober is the only tool that connects to GoPro Cloud. rclone, MultCloud, and Flexify do not support GoPro as a source.

No manual downloads. Files move directly from GoPro Cloud to your destination.
No file limits. Transfer 10 files or 10,000 in one run.
No subscription. Blober is a one-time purchase.
No middleman. Everything runs on your machine. Your credentials stay local.

Get Started

Download Blober (macOS, Windows, Linux)
Connect your GoPro Cloud account
Create a workflow and run it

Back Up Cloud Storage Directly to Your NAS

Mar 19, 2026

The Problem

You have files in the cloud - GoPro footage, Dropbox archives, Google Drive projects, S3 buckets - and you want them on your NAS. Simple enough in theory. In practice, the available options are all some flavor of painful.

Four pain points of cloud-to-NAS backup: double-copy workflow, CLI config overhead, SaaS routing through third-party servers, and no GoPro Cloud tool support

Download then copy is the default workflow. Download everything from the cloud to your PC, then manually copy it to the NAS. You need enough free space on your PC for the entire dataset, you do every byte twice, and if the NAS connection drops mid-copy you start over.

CLI tools like rclone can mount cloud storage or sync directly, but you need to configure remotes, write YAML, manage credentials, and troubleshoot provider-specific flags. It works - eventually. It's not something most people reach for on a Saturday afternoon.

SaaS migration services like MultCloud or Cloudsfer route your files through their servers. Your data leaves your network, passes through a third party, then comes back down to your NAS. It's slower, it's a privacy concern, and it costs a monthly subscription - usually with transfer caps.

GoPro Cloud has no solution at all. No migration tool supports it. rclone doesn't. MultCloud doesn't. You're stuck batch-downloading 25 files at a time through a web browser, manually.

Blober Streams Directly to Your NAS

Blober is a desktop app that connects to a growing list of cloud providers and transfers files to any local or network destination - including NAS drives.

Blober streams files directly from cloud to NAS: supports Synology, QNAP, TrueNAS, and any SMB share, with auto-resume and path templates

The architecture is straightforward: Blober runs on your computer, pulls data from the cloud API, and writes it to whatever destination you select in the file picker. If that destination is a mapped network drive (\\SYNOLOGY\backup or /Volumes/NAS/media), the files go there.

No intermediate server. No extra copy on your local disk. No subscription.

Supported NAS systems

Blober works with any NAS that your OS can see as a folder:

Synology DiskStation - map via SMB/CIFS (\synology\shared) or mount via NFS
QNAP - same: SMB share or NFS mount
TrueNAS / FreeNAS - SMB, NFS, or iSCSI-backed mount points
Unraid - SMB shares show up as network folders
Western Digital My Cloud - maps as a standard network drive
Any SMB/NFS share - if your OS can browse it, Blober can write to it

There's nothing NAS-specific to configure in Blober. You just pick the folder.

How It Works

Three steps: connect your cloud source, pick your NAS folder, click transfer

Connect your cloud source. Blober supports GoPro Cloud, Dropbox, Google Drive, AWS S3, Azure Blob, Backblaze B2, Cloudflare R2, Wasabi, and DigitalOcean Spaces. Authenticate once.
Pick your NAS folder. The standard OS folder picker shows your mapped network drives. Select the target directory on your NAS.
Transfer. Blober streams the files and writes them directly to the network path. If your connection drops or the NAS goes to sleep, the transfer resumes from where it stopped.

Auto-organize with path templates

Blober supports path templates that sort files as they arrive:

{file_created_date}/{camera_model}/{media_type}/{filename}

This turns a flat cloud dump into an organized library:

2024-12-15/HERO12 Black/videos/GH010432.MP4
2024-12-15/HERO12 Black/photos/GOPR0900.JPG
2025-01-03/HERO7 Black/videos/GH010904.MP4

The template runs before the file is written - files land on your NAS already organized.

Why NAS Users Specifically Benefit

NAS owners tend to be people who care about data ownership, long-term archival, and not paying recurring fees for storage they already bought. Blober aligns with all three.

Buy once, transfer forever. No subscriptions, no per-GB fees, no limits. Files never leave your network.

Your files stay on your network. Unlike SaaS tools that route data through external servers, Blober pulls from the cloud API and writes locally. For NAS users who chose a NAS precisely to keep data under their control, this matters.

One-time payment. NAS users already rejected the subscription model when they bought hardware instead of renting cloud storage. Blober follows the same philosophy: pay once, use forever.

Scale doesn't matter. Whether you're backing up 50 GoPro clips or migrating 10 TB from S3, there are no transfer caps, no per-GB fees, and no throttling.

Common NAS Backup Scenarios

Scenario	Source	NAS destination
GoPro footage archive	GoPro Cloud	`\\NAS\media\gopro\`
Photo library consolidation	Google Drive + Dropbox	`\\NAS\photos\`
S3 cold storage migration	AWS S3	`\\NAS\archive\s3-backup\`
Shared family photo vault	Dropbox	`\\SYNOLOGY\family-photos\`
Video production offload	Backblaze B2	`\\NAS\projects\raw-footage\`

Each of these is a single task in Blober. Set source, set destination, transfer.

The 3-2-1 Rule, Applied to Your Cloud Accounts

The standard rule for data you cannot afford to lose is 3-2-1: keep three copies, on two kinds of media, with one of them offsite. Most people apply it to files on their computer and forget that a cloud account is just one copy, held on someone else's hardware, under someone else's terms.

A cloud account is not a backup. The provider can lock the account, change pricing, suffer an outage, or (as GoPro Cloud and rclone's Google Photos change both showed) alter API access overnight. Pulling your cloud data down to a NAS turns a single rented copy into a real backup you control.

Applied to cloud accounts, 3-2-1 looks like this:

The cloud copy you already have (Google Photos, Drive, Dropbox, S3, GoPro Cloud).
A NAS copy on hardware you own, pulled down with Blober.
An offsite or second-cloud copy, for example a cheap object-storage bucket, so a fire or theft at home does not take the only local copy.

Blober covers steps 2 and 3 from the same workflow: pick a source, pick your NAS or a second provider, run.

Pulling Each Cloud Down to Your NAS

The destination is the same NAS folder in every case. What differs is the source.

Google Photos. Google has no "download all" button, and since March 2025 rclone can only see photos it uploaded. Blober connects to Google Photos directly and writes your whole library to the NAS. See how to back up Google Photos without Takeout.
Google Drive. Native Google Docs, Sheets, and Slides are not real files. Blober converts them to Office formats (.docx, .xlsx, .pptx) as it writes them to your NAS, and keeps your folder structure intact.
Dropbox. Point the source at your Dropbox and the destination at the NAS share. Folder hierarchy is preserved exactly.
AWS S3 and other object storage. Select a bucket or prefix and write it to a NAS archive folder. Useful for pulling cold S3 data onto cheaper local storage.
GoPro Cloud. Blober is the only tool that connects to GoPro Cloud, so a NAS is the natural home for footage you want off a subscription. See the GoPro Cloud guide.

Who Is This For?

NAS owners who want cloud backups on hardware they control
GoPro users who need their footage off GoPro Cloud (Blober is the only tool that connects)
Photographers and videographers archiving years of work to local network storage
Home lab users consolidating data from multiple cloud services onto one NAS
Small businesses migrating away from cloud storage subscriptions to on-premise drives

Frequently Asked Questions

Does Blober copy files to my NAS without storing them on my PC first? Yes. Blober pulls from the cloud provider's API and writes directly to the network path you select. There is no second copy left on your local disk and no double transfer.

Which NAS brands work? Any NAS your operating system can see as a folder: Synology, QNAP, TrueNAS, Unraid, Western Digital My Cloud, or any SMB or NFS share. There is nothing NAS-specific to configure in Blober; you just pick the folder.

Can I back up Google Photos to my NAS without Google Takeout? Yes. Blober connects to Google Photos directly and writes your library to the NAS, with no Takeout zips and no manual selection. See the Google Photos guide.

What happens if the transfer is interrupted? Blober resumes from where it stopped. If the NAS goes to sleep or the connection drops, you do not start over.

Can I back up to a NAS and a second cloud at the same time? Run two workflows: one to the NAS, one to a cheap object-storage provider like Backblaze B2. Together they give you the local and offsite copies of a 3-2-1 setup.

Get Blober

One app. All your clouds. Any NAS.

Download Blober at blober.io

Data Holders: How Blober Fits Your Workflow

Mar 14, 2026

Who Are Data Holders?

Data holders are individuals and organizations that accumulate, manage, and preserve large volumes of digital files as a core part of their work. They aren't just storing files - they're responsible for keeping data accessible, organized, and safe across years and even decades.

Data holders include:

Photographers and videographers with terabytes of RAW footage and project archives
Researchers and academics maintaining datasets, papers, and experimental outputs
Small businesses managing client records, invoices, contracts, and media assets
IT administrators responsible for infrastructure backups and compliance archives
Content creators with libraries of video, audio, and design files across platforms
Legal and medical professionals bound by retention requirements for sensitive records
Personal archivists preserving family photos, home videos, and documents

What unites them is a common problem: data grows, scatters, and becomes harder to manage over time.

The Data Holder's Problem

Most data holders didn't plan to end up with files in five different places. It happens organically:

Files start local - on a laptop, NAS, or external drive
Cloud adoption fragments storage - Google Drive for sharing, Dropbox for syncing, an S3 bucket for backups
Platform lock-in creeps in - GoPro Cloud holds your footage, iCloud holds your photos, OneDrive holds your documents
Manual management breaks down - folder naming conventions drift, backups become inconsistent, some files have three copies while others have none

The result is a scattered, fragile data footprint where no single tool gives you visibility across all your storage.

Symptom	Root Cause
"I know I have that file somewhere"	Files spread across 3-5 providers with no unified view
"My backup is months out of date"	Manual backup processes that require constant attention
"I'm paying for storage I barely use"	Redundant copies in expensive tiers that should be archived
"I can't move my data without paying egress"	Provider lock-in via egress fees and proprietary APIs
"Organizing everything would take weeks"	Flat folder structures with no metadata-driven automation

How Blober Solves This

Blober is a desktop application purpose-built for data holders who need to move, organize, and back up files across cloud providers and local storage - without recurring fees.

1. One Interface for All Your Storage

Blober connects to the storage providers data holders actually use:

Provider	Typical Use Case
AWS S3	Production infrastructure, enterprise backups
Backblaze B2	Affordable long-term archive
Wasabi	Hot storage with no egress fees
Cloudflare R2	CDN-adjacent delivery, zero egress
Google Cloud Storage	Workspace-integrated projects
Azure Blob Storage	Enterprise and compliance workloads
DigitalOcean Spaces	Dev team object storage
GoPro Cloud	Action camera footage (Blober exclusive)
Dropbox	File sharing and synchronization
Local / NAS	On-premise primary storage

No other single tool covers this range - especially GoPro Cloud, which Blober is the only application to support.

2. Direct Cloud-to-Cloud Transfers

Instead of downloading files to your machine and re-uploading them, Blober transfers data directly between providers. This matters for data holders because:

Saves time - a 2 TB migration doesn't bottleneck on your home internet
Saves bandwidth - your ISP data cap stays intact
Reduces failure points - no half-downloaded files sitting on your local disk

3. Metadata-Driven Organization

Data holders accumulate files over years. Manually sorting them into folders is unsustainable. Blober supports path templates that use file metadata to auto-organize during transfer:

/{year}/{month}/{camera_model}/{filename}

A flat dump of 50,000 files becomes a clean archive:

/2025/06/HERO13 Black/GX015742.MP4
/2025/06/Canon EOS R5/IMG_4521.CR3
/2026/01/iPhone 15 Pro/IMG_0032.HEIC

This works for any transfer - cloud-to-cloud, cloud-to-local, or local-to-cloud.

4. Scheduled and Resumable Transfers

Backup workflows for data holders need to be reliable, not heroic. Blober supports:

Resumable transfers - if your connection drops or your machine restarts, pick up where you left off
Incremental syncs - only transfer files that are new or changed since the last run
Large-file handling - multi-part uploads for files in the tens of gigabytes

No babysitting required. Set up a transfer, let it run, and come back to a completed job.

5. One-Time Pricing

Most cloud migration tools charge per-GB or require annual subscriptions with data caps. For data holders who move terabytes regularly, those costs compound:

Tool	Pricing Model	Cost for 10 TB/year
Flexify.io	~$0.03/GiB per migration	~$300+ (plus egress)
MultCloud	$99.98/year for 2.4 TB cap	~$400+ (need multiple renewals)
rclone	Free but manual	$0 (but hours of CLI configuration)
Blober	One-time purchase	One price, unlimited transfers

You buy Blober once. Transfer 1 TB or 100 TB - the price doesn't change.

Real-World Workflows

The Freelance Videographer

Setup: 8 TB of footage across GoPro Cloud, a local NAS, and Google Drive. Delivers finals via Dropbox.

With Blober:

Connects GoPro Cloud and pulls all footage to Backblaze B2 as a cold archive
Moves finished projects from local NAS to Cloudflare R2 for client delivery
Uses path templates to organize by project date and camera model
Runs periodic syncs from Google Drive to B2 to keep a second backup

Result: One tool replaces four manual processes. Total cost: one Blober license.

The Small Business IT Admin

Setup: 500 GB of compliance documents in Azure Blob Storage. Daily operational files in Google Workspace. Regulatory requirement for off-site backup.

With Blober:

Transfers compliance archive from Azure to Backblaze B2 as a secondary backup
Syncs critical Google Drive folders to a local NAS nightly
Uses Blober's incremental sync so only changed files move each day

Result: Meets audit requirements for geographic redundancy without provisioning a second enterprise cloud account.

The Research Lab

Setup: 12 TB of experimental datasets in AWS S3. New data generated weekly. Grants require data preservation for 10 years.

With Blober:

Migrates completed datasets from S3 Standard to Backblaze B2 (80% storage cost reduction)
Keeps active datasets in S3 for compute-adjacent access
Uses metadata templates to organize by experiment ID and date
Resumable transfers handle multi-GB dataset files without corruption

Result: Storage costs drop dramatically while preservation requirements are met.

Why Not Just Use rclone?

rclone is a powerful open-source CLI tool, and many data holders start there. But it has real limitations for ongoing data management:

Capability	rclone	Blober
GUI for browsing files	No (CLI only)	Yes
GoPro Cloud support	No	Yes (exclusive)
Dropbox support	Yes	Yes
Visual transfer progress	Limited	Full progress dashboard
Resumable multi-part uploads	Partial	Built-in
Path template organization	Manual scripting	Visual template builder
Error handling and retry	Config flags	Automatic
Setup time	Hours (config per remote)	Minutes (OAuth flows)

rclone is great for scripted, automated pipelines. Blober is built for data holders who want reliable transfers without writing shell scripts.

Getting Started as a Data Holder

Audit your storage - list every provider and local device where you keep files
Identify your archive tier - choose an affordable destination like Backblaze B2 or Wasabi for long-term storage
Connect everything in Blober - add each provider via OAuth or API key
Set up your first migration - pick a source, pick a destination, configure a path template
Let Blober handle the rest - resumable transfers, incremental syncs, and metadata organization do the heavy lifting

Your Data, Your Infrastructure

Data holders shouldn't need a subscription to manage their own files. Blober runs locally on your machine - your credentials never pass through third-party servers, your transfer bandwidth isn't metered, and your workflow isn't gated by monthly caps.

One license. Unlimited providers. Unlimited data.

Get Blober and take control of your data workflow.

Your Files, Your Machine, No Middleman: Why Local-First Transfers Matter

Mar 14, 2026

The Risk You're Not Thinking About

Every time you use a SaaS cloud transfer tool (MultCloud, Flexify, or any browser-based service), your files pass through someone else's servers. Your vacation photos, your client deliverables, your financial backups: all routed through infrastructure you don't control, operated by companies you've never audited.

Most people don't think about this. They click "transfer," see a progress bar, and assume their files went from A to B. In reality, the path is A to middleman to B. That middleman sees your filenames, your folder structure, and in many cases, the file contents themselves.

The risk of SaaS cloud transfer tools: your files pass through someone else's servers, data is routed through proxies, and you have zero control over the path

How Blober Is Different

Blober is a desktop app. It runs on your machine (Mac, Windows, or Linux) and talks directly to your cloud provider's API. When you transfer files from AWS S3 to Backblaze B2, the data flows from your machine to the provider endpoint. No relay. No proxy. No middleman.

This isn't just a privacy feature. It's a fundamentally different architecture:

SaaS tools: Your Machine > Their Server > Cloud Provider
Blober: Your Machine > Cloud Provider (direct)

Your credentials never leave your device. Your files never touch a server you didn't choose. And because there's no middleman bandwidth to pay for, there are no per-GB transfer charges from the tool itself. You only pay what your cloud provider charges.

Blober runs on your machine with direct API calls. SaaS tools proxy through their servers while Blober connects you directly to your cloud providers

Take Back Control

Blober connects to a growing list of storage providers - AWS S3, Azure Blob Storage, Backblaze B2, Cloudflare R2, DigitalOcean Spaces, Dropbox, Google Drive, GoPro Cloud, Local Disk, Wasabi, and more - all from a single app with a visual file browser.

No subscriptions. No per-transfer fees. One purchase, lifetime access. And every byte stays between you and your cloud provider.

Take back control with Blober. A growing list of cloud providers, 100% local transfers, one-time purchase, available on Mac, Windows, and Linux

Who Is This For?

Privacy-conscious users who don't want their files routed through third-party servers
Photographers and videographers transferring large media libraries between providers
Small businesses that need to move data without compliance headaches
Anyone leaving a cloud provider who wants a clean, direct migration path
GoPro users who want their footage somewhere they actually control

Get Blober

Your files. Your machine. No middleman. Download Blober

How to Move GoPro Cloud Media to Dropbox the Easy Way

Mar 12, 2026

Why Move Your GoPro Footage to Dropbox?

GoPro Cloud (included with GoPro Plus / GoPro Premium) stores your camera footage automatically. It's convenient, until you need to actually do something with it.

The problems with keeping everything in GoPro Cloud:

No easy bulk export. GoPro's web portal limits batch downloads to 25 files at a time, bundled as a ZIP. Large downloads frequently fail or time out.
No third-party integrations. No other file transfer tool (rclone, MultCloud, Flexify) can connect to GoPro Cloud. You're stuck with the GoPro web interface.
Subscription lock-in. Cancel GoPro Plus and you lose access to your footage. Your media is held hostage by a recurring charge.
No redundancy. If GoPro changes their cloud offering or shuts it down, you have no backup unless you've already downloaded everything manually.

Why Dropbox makes a good destination:

Accessible everywhere. Desktop, mobile, web. Dropbox works across all devices.
Selective sync. Keep large video files in the cloud and only download what you need locally.
Sharing built in. Send footage to clients, collaborators, or editors with a link.
Established and reliable. Dropbox has been around since 2007 and isn't going anywhere.
Integration with editing tools. Many video editors and photo apps integrate directly with Dropbox.

Moving your footage from GoPro Cloud to Dropbox gives you a second copy in a provider you control, one that doesn't depend on a GoPro subscription to access.

How Blober Makes It Easy

Blober is the only desktop app that connects directly to GoPro Cloud. No browser extensions, no manual downloads, no CLI config files. You create a workflow, press play, and your media transfers automatically.

Step 1: Create a Workflow

Open Blober, go to the Workflows page, and click New Workflow. Select GoPro as the source and Dropbox as the destination. Pick the folders you want to transfer from and where they should land.

Blober workflow configured to copy media from GoPro Cloud to Dropbox

Step 2: Run It

Click the play button on your workflow. Blober connects to both providers and starts transferring files immediately. Every file (photos, videos, time-lapses) gets moved directly from GoPro Cloud to Dropbox without touching your local disk first (unless you want it to).

Blober task progress showing files transferring from GoPro to Dropbox

Step 3: Monitor Progress

The Progress page shows exactly what's happening: files transferred, bytes moved, current speed, and estimated time remaining. If something goes wrong, you can pause, retry, or cancel at any time.

Blober task logs showing detailed transfer activity

What Makes This Different

No manual work. You don't download ZIPs, unzip them, then re-upload to Dropbox. Blober handles the entire pipeline.
No file limits. Transfer 10 files or 10,000. Blober processes them all in one run.
No subscription. Blober is a one-time purchase. No monthly fees, no per-GB transfer charges, no limits on how many times you run a workflow.
Runs locally. Your credentials stay on your machine. Files transfer directly between providers. Nothing passes through Blober's servers.

When to Use This

Before canceling GoPro Plus. Get your footage out before you lose access.
Regular backups. Set up a workflow now and run it whenever you want a fresh copy in Dropbox.
Switching providers. Moving off GoPro Cloud entirely? Transfer everything to Dropbox first, then cancel.
Sharing with a team. Put footage in a shared Dropbox folder so editors and collaborators can access it immediately.

Get Started

Download Blober (available for macOS, Windows, and Linux)
Connect your GoPro and Dropbox accounts
Create a workflow and press play

That's it. Your GoPro footage in Dropbox in minutes, not hours.

Stop Paying Rent to Move Your Own Files

Mar 9, 2026

The Trap

You uploaded 2 TB of photos, videos, and backups to the cloud. Life was good - until you wanted to move them somewhere else.

Suddenly, you're hit with egress fees, per-GB migration charges, and the realization that your cloud provider has been counting on you never leaving. It's your data. But moving it costs real money - every single time.

AWS charges ~$0.09/GB for egress. That's $184 just to download 2 TB of your own files. Want to use a SaaS migration tool? That's another $10-20/month, with transfer caps. Prefer the open-source CLI route? Clear your afternoon - you'll need it for YAML configs, credential files, and provider-specific quirks.

The trap: cloud providers charge you egress fees, SaaS tools charge subscriptions, and CLI tools cost you hours of setup time

The Math

Let's talk real numbers. Over three years, here's what you'll pay using common approaches:

Approach	3-Year Cost	Catch
SaaS Migration Tool	~$360	Monthly sub + data caps
Per-GB Service	~$720+	$0.03/GB, billed every transfer
DIY with CLI	40+ hours	Config per provider, no UI, breaks silently
Blober	One payment	Unlimited transfers. Forever.

The subscription model is designed to extract value from you month after month. The per-GB model punishes you for having more data. The CLI path trades money for your time.

Blober breaks the cycle. Pay once. Transfer as much as you want, as many times as you want. No meter running. No renewal emails. No "upgrade to unlock more."

$Cost comparison over 3 years: SaaS tools cost $360, per-GB services cost $720+, DIY CLI costs 40+ hours, Blober costs one single payment$

The Escape

Blober is a desktop app - not a SaaS, not a CLI tool, not a cloud service. It runs on your Mac, Windows, or Linux machine and connects directly to your cloud providers:

AWS S3 - buckets and objects, any region
Azure Blob Storage - containers and blobs
Google Drive - files and folders, including shared drives
GoPro Cloud - back up your action footage locally or to any cloud
Backblaze B2 - the affordable S3 alternative
Dropbox - personal and business accounts
Cloudflare R2 - zero-egress object storage
Wasabi - hot storage without the cold fees
DigitalOcean Spaces - all regions, auto-detected
Local Disk - any folder on your machine

Your files never touch a middleman server. Blober streams directly between your machine and the provider APIs. Browse your cloud storage visually, select what you want, pick a destination - done.

If a transfer gets interrupted (bad WiFi, laptop closed, provider hiccup), Blober picks up where it left off. No re-uploading. No duplicate files.

Blober connects many cloud providers in one app: AWS S3, Azure Blob, Google Drive, GoPro Cloud, Backblaze B2, Dropbox, Cloudflare R2, Wasabi, DigitalOcean Spaces, local disk, and more

The Move

Here's what switching to Blober actually looks like:

Before: You're juggling browser tabs, CLI sessions, and a spreadsheet tracking which files went where. A SaaS tool emails you that you've hit your 1.2 TB monthly cap. You Google "rclone config azure" for the third time.

After: You open Blober. Connect your accounts. Drag from source to destination. Walk away. It just works.

No internet needed for local-to-local moves. No data ever leaves your machine unless you're sending it to a cloud provider you chose.

Before and after comparison: monthly subscriptions, data caps, and files routed through servers vs. one-time payment, unlimited transfers, and 100% local execution with Blober

Who Is This For?

Photographers & videographers moving terabytes of footage from GoPro Cloud or Google Drive to cheaper archival storage
Developers & DevOps engineers migrating between S3-compatible providers without writing scripts
Small businesses consolidating cloud storage without paying an enterprise migration service
Privacy-conscious users who want their files transferred directly, not through a third-party cloud
Anyone tired of paying monthly fees to tools that move files you already own

Get Blober

Your data. Your machine. Your rules.

One payment. Unlimited transfers. No expiration.

Download Blober => blober.io

Migrating 100M+ Files from DigitalOcean Spaces to Backblaze B2

Feb 28, 2026

The Scenario

A media company has 25TB of data spread across 120 million files in DigitalOcean Spaces. Monthly bill: roughly $500/month. They want to move everything to Backblaze B2 to cut costs and get more flexibility.

This is a real-world pattern we see a lot. Let's walk through what it actually takes.

What It Costs

Item	Details	Estimated Cost
Blober License	One-time purchase, no subscription	See pricing
DigitalOcean Egress	~24TB billable at $0.01/GiB (first 1TB free)	~$240
Backblaze Ingress	Free. Backblaze never charges for uploads	$0
Backblaze API Calls	Uploads are free Class A calls, minor listing costs	~$2
Total (excluding license)		~$242

After migrating, the monthly bill drops from ~$500 on DigitalOcean to ~$150 on Backblaze B2. With a one-time license and no per-GB transfer fees, the move pays for itself within the first month.

About Egress Fees

This is where it gets interesting. Backblaze actively wants people to switch to their platform and they back that up with real programs:

Free egress up to 3x your average monthly storage on B2, which means once you're on Backblaze, downloading your own data doesn't cost extra in most scenarios.
Unlimited free egress through CDN and compute partners like Cloudflare, Fastly, Bunny.net, and Vultr.
Assisted data migration is listed as a standard B2 feature on their pricing page.
Universal Data Migration is available for larger committed contracts (50TB+ on pay-as-you-go, or included with B2 Reserve annual plans).

Backblaze explains their philosophy well in this blog post: Cloud Egress Fees: What They Are and How to Reduce Them. The short version is that they believe egress fees are vendor lock-in, and they want to make switching easy.

Even if your dataset is under the 50TB threshold, it's worth contacting their sales team. With a 25TB dataset and willingness to commit for 12 months, there's a solid chance they'll help reduce or cover the DigitalOcean egress fees to get you onboarded.

How Long Does It Take

Let's be honest here. 25TB is a lot of data.

Every file needs its own set of API calls: list from the source, download, then upload to the destination. Each round-trip carries network latency regardless of file size. When you multiply that per-object overhead across 120 million files with 25TB of bandwidth on top, the aggregate time adds up fast.

For a client-side migration where data streams through your local machine, you're looking at:

Several weeks of continuous runtime depending on your connection speed and latency
Your machine needs to stay on and connected the entire time
If your ISP has a monthly data cap, 25TB will almost certainly exceed it
16GB+ RAM recommended for handling the file listing at this scale

This isn't a Blober limitation. Any client-side tool (rclone, Cyberduck, whatever) will face the same physics. Data has to travel from DigitalOcean's datacenter to your machine, then from your machine to Backblaze's datacenter. That's two full trips through your ISP.

The Smart Approach: Two Phases

Phase 1: Let the Datacenters Do the Heavy Lifting

Contact Backblaze's sales team and ask about their assisted migration options. For datasets at this scale, they partner with migration services that can move data directly between datacenters at speeds your home connection can't match. What takes weeks on a home connection can take hours on a datacenter link.

Reach out here: Backblaze Sales

Phase 2: Use Blober for Everything After

Once the initial bulk migration is done, Blober becomes your daily tool for managing files across providers. New uploads, folder syncs, log rotations, moving files between buckets, all handled from your desktop with no per-GB fees and no subscriptions. Your credentials stay on your machine and never touch a third-party server.

Monthly Cost Comparison (Post-Migration)

	DigitalOcean Spaces	Backblaze B2
Storage (25TB)	~$500/mo	~$174/mo
Egress (3TB/mo)	~$30/mo	Free (within 3x allowance)
Total	~$530/mo	~$174/mo
Annual	~$6,360/yr	~$2,088/yr

That's about $4,200 saved per year, every year.

Bottom Line

For large-scale one-time migrations, use Backblaze's own migration programs. They want your business and they'll often help you get there.

For everything after that, Blober gives you a one-time license to manage, sync, and move files across any supported provider, with no recurring costs and no third party ever touching your credentials.

What Is Blober? Cloud File Transfer Made Simple

Feb 23, 2026

The Problem

Transferring files between cloud providers today means monthly subscriptions, surprise transfer fees, and wrestling with CLI config files. Most tools are either expensive SaaS platforms or developer-only terminals with steep learning curves.

The Solution

Blober is a desktop app that connects all your cloud storage in one place. AWS S3, Azure Blob Storage, Google Drive, GoPro Cloud, Backblaze B2, Wasabi, local disk, and more - all supported out of the box. No CLI. No config files. Just a beautiful, intuitive interface.

Meet Blober: one app to move files between AWS S3, Azure Blob, Google Drive, GoPro Cloud, Backblaze B2, Wasabi, local disk, and more

The Value

Buy once, transfer forever. No subscriptions. No transfer fees. Blober runs natively on Mac, Windows, and Linux - and it works offline too.

Blober: buy once, transfer forever. No subscriptions, no transfer fees, beautiful UI, works offline, runs on Mac, Windows, and Linux

Get Blober

Stop renting your tools. Download Blober =>

Back Up Your GoPro Cloud to Backblaze B2, AWS S3, or Local Storage

Feb 15, 2026

The Problem

GoPro's cloud storage (GoPro Plus / GoPro Premium) offers unlimited storage for GoPro camera media. It's a great perk, until you want your footage somewhere else.

The reality for most GoPro users:

Painfully limited batch download. GoPro's web portal caps batch downloads at 25 files at a time, bundled into a ZIP. Large batches frequently fail or time out, and metadata like GPS data may be stripped during compression
No third-party tool support. rclone, MultCloud, Flexify, and every other transfer tool do not support GoPro Cloud
Subscription dependency. Cancel GoPro Plus and your cloud access disappears. Your footage remains hostage to a recurring charge
No "Download All" option. If you have hundreds or thousands of files, you're stuck doing dozens of 25-file batch downloads manually, hoping none fail

GoPro community forums are filled with users asking the same question: "How do I download all my GoPro Cloud content at once?" The practical answer is: not without hours of manual work and frequent failures.

Blober changes that.

Blober: The Only Tool That Connects to GoPro Cloud

Blober is the only desktop application that integrates with GoPro's cloud storage. No other migration tool, free or paid, supports GoPro Cloud as a source or destination.

With Blober, you can:

Browse all your GoPro Cloud media: photos and videos, organized by date, camera, and type
Download everything at once to your local drive, NAS, or external HDD
Transfer directly to Backblaze B2, AWS S3, Wasabi, Cloudflare R2, Azure Blob Storage, or DigitalOcean Spaces
Use metadata-based path templates to auto-organize files (e.g., by camera model, capture date, resolution)
Resume interrupted transfers, with no need to start over if your connection drops

Why Back Up GoPro Cloud?

1. Subscription Lock-In

GoPro Plus (now GoPro Premium) costs ~$59.99/year. As long as you pay, your footage stays accessible. The moment you cancel, your cloud media goes offline. For years of footage, that's a dangerous bet on a single subscription.

2. No Redundancy

GoPro Cloud is your only copy in the cloud. There is no built-in backup, no versioning, no geographic replication. If GoPro ever changes their terms, shuts down the service, or experiences data loss, your footage is gone.

3. Cost Optimization

Long-term archival storage costs a fraction of ongoing subscriptions:

Storage Option	Cost for 1 TB/year	Egress Fees
GoPro Plus	~$59.99/year (ongoing)	N/A (limited downloads)
Backblaze B2	~$83/year ($6.95/TB/mo)	Free up to 3x stored
Wasabi	~$83.88/year ($6.99/TB/mo)	Free
AWS S3 (Standard)	~$276/year	$0.09/GB
Local NAS	One-time HDD cost	Free

For most GoPro users, Backblaze B2 or Wasabi combined with a Blober one-time license is the most cost-effective long-term strategy.

4. You Own Your Footage

Your GoPro footage is yours. Keeping it locked behind a single provider's subscription model is not ownership. It is rental. Backing it up to storage you control gives you true data sovereignty.

How It Works

Step 1: Connect GoPro Cloud in Blober

Open Blober and create a new workflow
Select GoPro as the source
Click Open GoPro Login - a browser window opens
Sign in with your GoPro account
Blober captures your session automatically

Step 2: Choose Your Destination

Select where you want your footage to go:

Local disk: your SSD, HDD, NAS, or external drive
Backblaze B2: affordable, S3-compatible, free egress
AWS S3: enterprise-grade, global availability
Wasabi: hot storage with no egress fees
Cloudflare R2: zero egress, fast edge delivery
Any other Blober-supported provider

Step 3: Configure Path Templates (Optional)

Use Blober's metadata-based path templates to auto-organize files as they transfer:

/{camera_model}/{capture_date}/{filename}

This turns a flat GoPro dump into a clean archive:

/HERO13 Black/2026-01-23/GX015742.MP4
/HERO13 Black/2026-01-23/gorp0001.JPG
/HERO12 Black/2025-12-15/GX014521.MP4

Step 4: Run and Monitor

Click Start and Blober handles the rest:

Parallel downloads for maximum throughput
Real-time progress tracking
Automatic resume on interruption
Full task history logged for every file

Supported GoPro Media

Type	Extensions
Videos	`.mp4`, `.mov`, `.avi`, `.mkv`
Photos	`.jpg`, `.png`, `.raw`, `.dng`

Blober downloads the highest available quality, with no compression and no re-encoding.

Metadata Available

Each GoPro file includes rich metadata that Blober can use for organization:

Field	Example
Camera model	HERO13 Black
Capture date	2026-01-23
Resolution	5312 × 2988
File size	142.5 MB
Duration	0:32 (videos)

Frequently Asked Questions

Can I upload to GoPro Cloud with Blober? Yes. Blober supports uploads to GoPro Cloud (up to 5 TB per file) with multipart upload and progress tracking.

Does Blober store my GoPro credentials? No. Blober uses a browser-based login flow. Your session lasts approximately 20 hours, after which Blober prompts you to sign in again. Credentials are never stored or transmitted to any server.

Can rclone, MultCloud, or Flexify do this? No. As of February 2026, Blober is the only transfer tool that supports GoPro Cloud. rclone (70+ providers), MultCloud (30+ services), and Flexify (~25 clouds) do not include GoPro Cloud integration.

What if my transfer is interrupted? Blober saves progress and resumes from the last successfully transferred file. No need to re-download everything.

Take Control of Your GoPro Footage

Your footage is irreplaceable: years of adventures, events, and memories sitting in a cloud you can only access through a subscription. Blober gives you a way out: move it all to storage you own and control, in the highest quality, organized exactly how you want.

Get started with Blober =>

Data Sovereignty: Why Your Cloud Transfer Tool Matters

Feb 15, 2026

Your Transfer Tool Is a Trust Decision

When you move data between cloud providers, your transfer tool has access to everything: your storage credentials, your file contents, your metadata. The architecture of that tool - where it runs, where credentials are stored, where data flows - determines whether you maintain control or hand it to a third party.

Most people evaluate migration tools on speed and features. Few ask the harder question: who else can see my data while it's in transit?

The Three Architectures

1. SaaS (Cloud-Hosted)

Tools like Flexify.io and MultCloud run on their own servers. Your credentials are stored in their infrastructure. Your data routes through their systems during transfer.

Concern	Flexify.io	MultCloud
Credential storage	Flexify servers	MultCloud servers (Hong Kong)
Data path	Through Flexify infrastructure	Through MultCloud servers
Account required	Yes	Yes
OAuth token storage	Server-side	Server-side
Offline operation	No	No
Privacy policy scope	US (Florida)	Hong Kong

This doesn't mean these services are malicious. But it means:

A third party stores your cloud credentials - API keys, OAuth tokens, or access grants
Your data transits infrastructure you don't control - introducing a man-in-the-middle by design
You're subject to their privacy policy and jurisdiction - which may change without notice
A breach of their systems exposes your credentials and potentially your data

For personal photos, this might feel acceptable. For business data, media archives, legal documents, or HIPAA/GDPR-adjacent workloads - it's a serious risk.

2. CLI (Local, But Exposed)

rclone runs locally on your machine. Your data goes directly to and from each cloud provider. This is a genuine trust advantage over SaaS tools.

However, rclone stores credentials in a plaintext configuration file (~/.config/rclone/rclone.conf). Anyone with access to your filesystem - malware, another user, a compromised backup - can read your cloud credentials directly.

rclone does offer an encryption option for the config file, but it's opt-in and requires manual setup. Most users leave it in plaintext.

3. Desktop App (Local + Secured)

Blober runs entirely on your machine with encrypted credential storage. Your data flows directly between your machine and each cloud provider. No intermediary.

Concern	Blober
Credential storage	✅ Local, encrypted
Data path	✅ Direct (no middleman)
Account required	✅ No (license key only)
OAuth token storage	✅ Local only
Offline operation	✅ Yes
Jurisdiction	✅ Your machine, your rules

Why This Matters

Credential Exposure

Your cloud storage credentials are the keys to your kingdom. An AWS access key or a Google OAuth token doesn't just grant transfer access - it grants full access to your storage: read, write, delete, list. If a SaaS provider's database is breached, your credentials are in that breach.

With Blober, credentials never leave your machine. There is no remote database to breach.

Data in Transit

When a SaaS tool transfers your files, those files pass through their servers. Even with SSL encryption in transit, the data is decrypted on their infrastructure before being re-encrypted and sent to the destination. This is not end-to-end encryption - it's hop-by-hop.

With Blober, data flows directly from source to your machine to destination. No hops through third-party infrastructure.

Jurisdiction and Compliance

MultCloud operates from Hong Kong. Flexify.io from Florida, USA. Each jurisdiction has different data protection laws, government access rules, and breach notification requirements. When your data or credentials live on their servers, you're subject to their jurisdiction - not yours.

Blober runs on your hardware, in your jurisdiction. No foreign servers. No cross-border data flow through third parties.

Subscription as Leverage

SaaS tools require active accounts. Cancel your subscription, and you lose access to your workflows, task history, and potentially your configured connections. This creates a soft lock-in that has nothing to do with the quality of the tool.

Blober is a one-time purchase. No account, no subscription, no leverage.

Comparison Summary

Dimension	SaaS (Flexify, MultCloud)	CLI (rclone)	Blober
Credentials	Third-party servers	Plaintext local file	✅ Encrypted local
Data path	Through vendor servers	Direct	✅ Direct
Account required	Yes	No	✅ No
Offline capable	No	Yes	✅ Yes
Risk of vendor breach	Exposes your credentials	N/A	✅ N/A
Jurisdiction	Vendor's country	Your machine	✅ Your machine
Subscription lock-in	Yes	No	✅ No

Who Should Care?

Freelancers and agencies handling client data - you have a professional duty to control where that data flows
Photographers and videographers with irreplaceable media - GoPro footage, wedding archives, production masters
Small businesses without dedicated security teams - reducing your attack surface matters
Anyone under GDPR, HIPAA, or SOC 2 obligations - third-party data processors require disclosure and contractual agreements
Privacy-conscious individuals who simply want to own their data pipeline

So What?

Your migration tool is not a neutral pipe. It's an active participant in your data flow. Its architecture determines whether your credentials are stored remotely, whether your files transit foreign servers, and whether you maintain sovereignty over your data.

Blober is designed around a simple principle: your data, your machine, your rules.

No accounts. No SaaS intermediaries. No credential exposure. One-time purchase, local execution, direct transfers.

Get Blober =>

The True Cost of Cloud Data Migration in 2026

Feb 15, 2026

The Hidden Tax on Moving Your Own Data

Moving data between cloud providers should be simple. You own the files - you just want them somewhere else. But the cloud industry has turned data migration into a profit center, layering fees at every step: egress charges, per-GB migration fees, monthly subscriptions, and data traffic caps.

Here's what cloud data migration actually costs in 2026, and why Blober's one-time pricing model is a fundamentally better deal for anyone who transfers data more than once.

The Three Cost Models

1. Per-GB Fees (Flexify.io)

Flexify charges a per-GiB fee for every migration, on top of your cloud provider's egress charges.

Migration Size	Flexify Fee (~$0.03/GiB)	Provider Egress (AWS ~$0.09/GB)	Total
100 GB	$3	$9	~$12
1 TB	$30	$92	~$122
10 TB	$307	$922	~$1,229
100 TB	$3,072	$9,216	~$12,288

These are per-job costs. Run the same migration next month? Pay again. Sync regularly? The meter never stops.

Flexify does offer managed migrations for 10+ TB where provider egress may be avoided through direct peering - but those require contacting sales and negotiating custom pricing.

2. Annual Subscriptions with Data Caps (MultCloud)

MultCloud charges an annual subscription that includes a fixed amount of transfer traffic:

Plan	Annual Cost	Data Allowance	Cost Per TB Transferred
Free	$0	5 GB/month	N/A (60 GB/year cap)
1,200 GB plan	$59.99/year	1,200 GB/year	~$50/TB
2,400 GB plan	$99.98/year	2,400 GB/year	~$42/TB

Hit the cap? Transfers stop until you renew. Need to move 5 TB? You'll need to buy the top-tier plan and wait over two years to exhaust the quota - or pay for multiple years upfront.

Over three years, MultCloud costs $180-$300 in subscriptions alone, and you're still capped on how much data you can actually move.

3. One-Time License (Blober)

Blober charges a one-time license fee. No per-GB charges. No annual renewal. No data caps.

Migration Size	Blober Cost	Provider Egress (your standard cloud fees)
100 GB	✅ One-time license	Standard egress only
1 TB	✅ Same license	Standard egress only
10 TB	✅ Same license	Standard egress only
100 TB	✅ Same license	Standard egress only

The only variable cost is your cloud provider's standard egress fee - which you'd pay with any tool, including rclone. There is no Blober surcharge.

The Compounding Problem

Per-GB fees and subscriptions compound over time. If you migrate data regularly - monthly syncs, media archives, backup rotations - the cost gap widens fast:

Scenario	Flexify (per-GB)	MultCloud (subscription)	Blober (one-time)
One 1 TB migration	~$122	$59.99/year	✅ One-time
Monthly 500 GB sync	~$732/year	Exceeds cap	✅ One-time
3 years of regular use	$2,196+	$180-$300	✅ One-time

For users who transfer data as part of their regular workflow - not a one-time event - subscription and per-GB models are an ongoing tax. Blober eliminates it.

What About rclone?

rclone is free and open-source. On raw cost, nothing beats free.

But rclone's cost is measured in time, not money:

Setup time - configuring remotes, flags, and cron jobs
Debugging time - when a transfer fails silently or a flag is wrong
Maintenance time - updating scripts when providers change APIs

For engineers who already live in the terminal, rclone is excellent. For everyone else, the time cost is significant and ongoing. Blober trades a one-time purchase for a visual, persistent workflow engine that eliminates scripting overhead entirely.

Egress Fees: The Unavoidable Cost

Regardless of which tool you use, cloud provider egress fees apply when downloading data. These are charged by your cloud provider, not by Blober:

Provider	Storage (TB/mo)	Egress (per GB)	Notes
AWS S3	$26	$0.09	Egress-heavy workloads get expensive
Azure Blob Storage	$20	$0.08	First 100 GB/month free
Google Cloud Storage	$23	$0.11	Varies by region
Backblaze B2	$6.95	Free (up to 3x)	Free egress up to 3x stored
Wasabi	$6.99	Free	No egress fees ever
Cloudflare R2	$15	Free	Zero egress by design
DigitalOcean Spaces	$5 (250 GB)	$0.01	1 TB outbound included

Pro tip: If you're choosing a destination for long-term storage, providers like Backblaze B2 ($6.95/TB/mo, free egress), Wasabi ($6.99/TB/mo, no egress fees), and Cloudflare R2 (zero egress) offer significantly lower total cost of ownership than AWS, Azure, or GCS. Blober supports all of them.

TL;DR

Tool	Cost Model	Best For
Flexify.io	Per-GB + egress	Enterprise one-time migrations
MultCloud	Annual subscription	Light, occasional consumer transfers
rclone	Free (time cost)	Engineers comfortable with CLI
Blober	One-time license	Anyone who transfers data regularly, values simplicity, or needs GoPro Cloud support

If you transfer data more than once - or plan to - a one-time license pays for itself after a single job. No subscriptions. No per-GB surprises. No data caps.

Get Blober =>

Why Photographers and Videographers Choose Blober

Feb 15, 2026

The Creative Storage Problem

Photographers and videographers generate enormous volumes of data. A single shoot can produce hundreds of gigabytes of RAW photos and 4K/5.3K video files. Over months and years, that adds up to terabytes of irreplaceable media scattered across local drives, cloud providers, and camera-specific platforms.

The challenges are consistent:

Files are large - 4K video clips are often 1-5 GB each. 5.3K GoPro footage is even larger.
Storage is fragmented - footage lives on local SSDs, NAS devices, Google Drive, GoPro Cloud, and various object storage providers
Organization is painful - manually sorting files into date/camera/project folders is tedious and error-prone
Backups are inconsistent - some footage has 3 copies, some has 1, some has none
Cloud costs add up - Google Drive, AWS S3, and iCloud storage bills grow every month

Blober is built to solve exactly these problems.

How Blober Fits Into Creative Workflows

1. Consolidate Scattered Storage

Most creators have files spread across multiple providers - intentionally or not. Blober connects to all of them in one interface:

Provider	Use Case
GoPro Cloud	Action camera footage auto-uploaded
Google Drive	Client deliverables and sharing
Local NAS / SSD	Primary working storage
Backblaze B2	Long-term archive (cheap, reliable)
Wasabi	Hot archive (no egress fees)
AWS S3	Production infrastructure
Cloudflare R2	CDN-adjacent delivery

Instead of logging into 4 different dashboards and downloading/uploading manually, Blober lets you build workflows that move files between any of these in a single operation.

2. GoPro Cloud Backup (Blober Exclusive)

If you shoot with GoPro cameras, you likely have footage auto-uploaded to GoPro Cloud. The problem: GoPro's web portal only allows batch downloads of 25 files at a time (as ZIPs that frequently fail), and no third-party tool supports GoPro Cloud as a transfer source.

Blober is the only tool that connects to GoPro Cloud. You can:

Download all GoPro footage to local storage
Transfer directly to Backblaze B2 or Wasabi for long-term archival
Organize files by camera model, date, and resolution automatically

No other tool - not rclone, not MultCloud, not Flexify - supports GoPro Cloud.

3. Metadata-Driven Organization

Blober's path templating system uses file metadata to automatically organize transfers. Instead of dumping files into flat folders, you define a template:

/{camera_model}/{capture_date}/{filename}

And Blober organizes the output:

/HERO13 Black/2026-01-23/GX015742.MP4
/Sony A7IV/2026-01-20/DSC09845.ARW
/DJI Mini 4/2026-01-18/DJI_0042.MP4

This works across all providers - GoPro Cloud to local, Google Drive to B2, or any combination. Months of manual folder sorting, automated in one workflow.

4. Repeatable Workflows

Creative work is cyclical. Shoots happen regularly, and the post-shoot workflow is always the same: ingest => organize => edit => archive => backup.

Blober saves each transfer as a durable workflow:

One-click re-execution - run the same ingest pattern after every shoot
Resumable transfers - if a 500 GB transfer drops at 80%, pick up where it stopped
Task history - see exactly what was transferred, when, and whether it succeeded
No scripting - no cron jobs, no bash scripts, no forgotten flags

5. Cost-Optimized Archival

For long-term storage, the hyperscalers (AWS, Azure, GCS) are expensive. Creative professionals are increasingly moving to budget-friendly alternatives:

Provider	Storage Cost	Egress	Why Creators Choose It
Backblaze B2	$6.95/TB/month	Free (up to 3x)	Cheapest reliable archive
Wasabi	$6.99/TB/month	Free	No egress fees, predictable billing
Cloudflare R2	$15/TB/month	Free	Zero egress, great for delivery

Blober supports all of these, making it trivial to set up an archive workflow: shoot => ingest to local NAS => archive to Backblaze B2 => done. One-time license, no per-GB fees.

Real-World Scenarios

Wedding Photographer

After each wedding: 80 GB of RAW photos + 40 GB of video. Create a Blober workflow that copies everything from your SSD to Backblaze B2, organized by date and event name. Run it after every wedding with one click.

YouTube Creator

Finished projects sit on Google Drive eating into your 2 TB plan. Use Blober to move completed projects to Wasabi for long-term storage at a fraction of the cost, freeing up Google Drive space for active work.

GoPro Adventure Creator

Years of GoPro footage sitting in GoPro Cloud with no easy way out. Use Blober to download everything to a local NAS, organized by camera and date. Cancel GoPro Plus knowing your footage is safe.

Drone Operator

100+ GB per flight day across DJI footage on local cards and backup copies on Google Drive. Use Blober to standardize your archive: everything goes to Backblaze B2, organized by date and location, with a local NAS mirror.

Why Not rclone?

rclone is free and powerful, but it requires terminal expertise. For each new storage provider, you configure a remote. For each workflow, you write a command with precise flags. There's no visual interface, no persistent workflows, and no GoPro support.

If you're a software engineer, rclone might work. If you're a photographer who wants to focus on photography, Blober is what you need.

Get Started

Blober is available for Windows, macOS, and Linux. One-time license, currently at discounted beta pricing. No subscriptions. No per-GB fees. No data caps.

Connect your providers, build your workflows, and take control of your media archive.

Get Blober =>

Blober vs Flexify

Feb 1, 2026

Overview

Both Blober and Flexify.io solve the same core problem: moving large volumes of data between cloud storage providers. They approach the problem from fundamentally different architectural and economic philosophies.

Flexify.io (founded 2015, Tampa FL) is a managed, cloud-based migration and virtualization platform built for enterprises moving tens or hundreds of terabytes in controlled, one-time projects. Blober is a local-first desktop workflow engine designed for continuous, repeatable transfers, with no subscriptions, no per-GB fees, and no third-party servers touching your data.

Architectural Philosophy

Flexify.io

Cloud-hosted migration engines deployed on Flexify-managed infrastructure
Data routes through Flexify servers (or, for managed 10 TB+ migrations, direct cloud-to-cloud)
Usage-based pricing: you pay per GiB transferred
Emphasis on API virtualization: translates Amazon S3 API to Azure Blob Storage on-the-fly
Supports ~25 object-storage providers (S3-compatible, Azure, GCS, Alibaba, etc.)

Blober

Runs entirely on your local machine (Windows, macOS, Linux)
Transfers go directly between your machine and each storage provider - no intermediary servers
All credentials stored locally and never transmitted to a third party
Supports unique providers like GoPro Cloud that no other migration tool covers

This distinction matters for users who care about cost predictability, credential ownership, data sovereignty, and ongoing workflows rather than one-time migrations.

Pricing Model Comparison

Aspect	Blober	Flexify.io
Pricing style	✅ One-time license	Usage-based (per GiB)
Current cost	Discounted beta pricing	~$0.03/GiB Flexify fee + provider egress ($0.05-$0.09/GiB)
Subscription	✅ None	Sign-up required ($20 free credit)
Long-term cost	✅ Fixed forever	Grows with every transfer
1 TB migration	✅ One-time price	~$80 to $120+ in fees

For a single 1 TB migration from AWS S3 to Google Cloud Storage, Flexify's self-service rate is approximately $0.08 to $0.12 per GiB, which works out to $80 to $120+ for that one job. With Blober, only your provider's standard egress fees apply; there is no Blober per-GB charge.

Feature Comparison

Feature	Blober	Flexify.io
Cloud-to-cloud transfer	✅ Yes	Yes
Local filesystem integration	✅ Yes	Limited
GoPro Cloud support	✅ Yes	❌ No
Metadata-based path templating	✅ Yes	No
Persistent task history	✅ Yes	Managed dashboard
Workflow reuse	✅ Yes	Limited
Resumable workflows	✅ Yes	Yes
API access	No	Yes
Virtual S3 endpoint	No	Yes
Credential storage	✅ Local only	Cloud-managed
Data path	✅ Direct	Through Flexify servers

Data Sovereignty and Privacy

With Flexify, your storage credentials are stored on their servers and your data may transit through Flexify-managed infrastructure. For regulated industries, sensitive media archives, or personal data, this introduces a third-party dependency and potential compliance exposure.

Blober eliminates this concern entirely:

Credentials never leave your machine. No third-party vault, no OAuth token stored in a SaaS dashboard
Data flows directly between your local machine and each cloud provider
Blober works offline with a one-time license
Full control over when, where, and how your data moves

Unique Provider Coverage

Blober is the only migration tool that supports GoPro Cloud, letting GoPro users back up or transfer their media archives to any supported provider (AWS S3, Backblaze B2, Wasabi, local disk, etc.). Neither Flexify, rclone, nor MultCloud offer GoPro Cloud integration.

This makes Blober the go-to choice for photographers, videographers, and agencies managing GoPro footage across storage tiers.

Maturity and Risk Tradeoff

Flexify.io is a mature enterprise platform (since 2015) with production-scale deployments and petabytes migrated. Blober is newer and currently in beta, with faster iteration and less operational overhead.

Blober offsets its maturity gap with:

Aggressive beta pricing: lock in your license before prices go up
Rapid feature development with direct community influence on the roadmap
No lock-in to ongoing fees: one purchase, unlimited use
Desktop-native architecture that is inherently simpler and more predictable

When Blober Makes More Sense

Choose Blober if you:

Transfer data regularly, not just once
Want full control over credentials and data flow
Need GoPro Cloud support (only Blober has it)
Prefer a native desktop UI over enterprise SaaS dashboards
Want predictable lifetime pricing with no per-GB surprises
Care about data sovereignty, with no third-party servers touching your files

Download Blober at blober.io

Blober vs Flexify vs rclone

Feb 1, 2026

Overview

Three tools dominate cloud data transfer in 2026 - each solving the problem from a completely different angle. Here's how they compare.

High-Level Comparison Table

Dimension	Blober	Flexify.io	rclone
Architecture	✅ Local-first desktop	Managed SaaS	CLI utility
Pricing	✅ One-time license	Usage-based (~$0.03-$0.04/GiB + egress)	Free
Ease of use	✅ High (native GUI)	Medium (web dashboard)	Low (terminal only)
Provider count	9+ and growing	~25 (object storage)	70+
GoPro Cloud support	✅ Yes (exclusive)	❌ No	❌ No
Credential control	✅ Local only	Cloud-managed	Local config file
Data path	✅ Direct (no middleman)	Through Flexify servers	Direct (local)
Workflow persistence	✅ Built-in	Dashboard-based	None (manual scripts)
Task history & resume	✅ Built-in	Dashboard-based	Logs only
Metadata path templates	✅ Yes	No	Manual scripting
Automation	Limited	High	Very high
API virtualization	No	Yes (S3-to-Azure gateway)	No
Enterprise scale	High	High	High
Open source	No	No	Yes
Best for	Agencies, creators, engineers	Enterprises (petabyte migrations)	Engineers, sysadmins

Pricing at a Glance

Scenario	Blober	Flexify.io	rclone
100 GB migration	✅ One-time	~$8 - $12	Free
1 TB migration	✅ One-time	~$80 - $120+	Free
10 TB migration	✅ One-time	~$800 - $1,200+	Free
Recurring monthly	✅ $0	Compounds every run	Free

Flexify charges per GiB transferred plus cloud provider egress fees. Costs add up fast for recurring workflows. rclone is free but demands engineering time. Blober sits in the sweet spot: pay once, transfer forever.

Data Sovereignty

Concern	Blober	Flexify.io	rclone
Credentials stored	✅ Local only	Flexify servers	Local config file
Data transits 3rd party	✅ No	Yes (Flexify infra)	No
Account required	✅ No	Yes	No
Offline operation	✅ Yes	No	Yes

For regulated industries, sensitive media archives, or personal data - avoiding third-party intermediaries is not a preference, it is a requirement. Both Blober and rclone keep your data path clean. Flexify introduces a managed middleman.

The GoPro Factor

Blober is the only transfer tool that supports GoPro Cloud. Neither Flexify nor rclone can access GoPro's storage. If you manage GoPro footage - whether as a creator, agency, or production house - Blober is the only option for migrating that media to professional storage like Backblaze B2, AWS S3, or your local NAS.

Summary

rclone is the most powerful tool if you are deeply technical, automation-driven, and comfortable with terminal workflows. It is free and supports 70+ providers.
Flexify.io is ideal for enterprises running massive one-time migrations under strict SLAs, especially when virtual S3 endpoints or managed infrastructure are required. Budget accordingly - costs scale with data volume.
Blober fills the gap between them: professional-grade transfers with a native desktop GUI, local credential control, visual workflows, predictable one-time pricing, and exclusive GoPro Cloud support.

Blober's beta pricing locks in a lifetime license at a fraction of the cost competitors charge for a single large migration. For users who value simplicity, sovereignty, and long-term savings - Blober is the clear choice.

Blober vs MultCloud

Feb 1, 2026

Overview

MultCloud (founded 2012, Hong Kong) is a web-based platform for transferring, syncing, and managing files across 30+ cloud services. It is subscription-based and routes all data through MultCloud's servers.

Blober is a local-first desktop application that transfers data directly between your machine and cloud providers, with no middleman, no subscription, and no data caps.

Both tools target non-technical users who want cloud-to-cloud transfers without writing scripts. The difference lies in architecture, pricing, and trust.

Architectural Difference

MultCloud

Web-based SaaS: runs entirely in your browser
All data routes through MultCloud's servers in Hong Kong
Requires an account and OAuth access to your cloud accounts
Subscription required for meaningful use (free tier: 5 GB/month)

Blober

Native desktop application (Windows, macOS, Linux)
Data flows directly between your machine and each cloud provider
No intermediary servers. Your files never touch a third party
Credentials stored locally, never transmitted

Pricing Model Comparison

Aspect	Blober	MultCloud
Pricing style	✅ One-time license	Subscription (annual)
Free tier	N/A (beta pricing)	5 GB/month, 2 transfer threads
Mid-tier plan	-	$59.99/year for 1,200 GB/year
Top-tier plan	-	$99.98/year for 2,400 GB/year
Transfer threads	Automatic parallelism	Free: 2 threads, Paid: 10 threads
Data cap	✅ None	Capped per plan (5 GB to 2,400 GB/year)
Long-term cost (3y)	✅ One-time purchase	$180 to $300+

MultCloud's data traffic limits are a hard ceiling. Once you exhaust your annual quota, transfers stop until you renew. Blober has no transfer caps. Move as much data as your bandwidth allows.

Feature Comparison

Feature	Blober	MultCloud
Cloud-to-cloud transfer	✅ Yes	Yes
Local filesystem integration	✅ Yes	No (web-only)
GoPro Cloud support	✅ Yes (exclusive)	❌ No
Storage-optimized transfers	✅ Yes	Generic
Workflow persistence	✅ Yes	Scheduled tasks
Task history and logs	✅ Yes	Basic dashboard
Metadata path templates	✅ Yes	No
Resumable transfers	✅ Yes	Limited
Sync (two-way)	Planned	Yes
Email-to-cloud (PDF)	No	Yes
Credential storage	✅ Local only	MultCloud servers (OAuth)
Data path	✅ Direct	Through MultCloud servers

Data Sovereignty and Privacy

This is where the difference is starkest. MultCloud requires OAuth access to your cloud accounts and routes all transferred data through its own servers. Their privacy page states data is "temporarily cached" during operations.

Blober takes the opposite approach:

Credentials never leave your machine. No OAuth tokens stored on third-party servers
Data flows directly between your local machine and each cloud provider
No account needed. Blober works with a license key, offline
No data caching. Nothing is stored, buffered, or logged on remote servers

For users transferring personal photos, sensitive business documents, or media archives, the question is simple: do you want your data flowing through servers in Hong Kong, or directly from your machine to your cloud provider?

GoPro Cloud: Only on Blober

MultCloud supports 30+ consumer cloud services (Google Drive, Dropbox, OneDrive, etc.) but does not support GoPro Cloud. If you need to move GoPro footage to professional storage like Backblaze B2, AWS S3, or Wasabi, MultCloud cannot help.

Blober is the only transfer tool with native GoPro Cloud integration, which makes it essential for photographers, videographers, and agencies managing action camera footage.

When Blober is the Sharper Tool

Choose Blober if you:

Need to move large volumes of data without annual caps
Want predictable, one-time pricing, not $60 to $100/year forever
Prefer local execution over web-based SaaS
Require data sovereignty, with no files routing through third-party servers
Need GoPro Cloud support (only Blober has it)
Value detailed task history, resumable workflows, and metadata-based organization
Care about credential security, with no OAuth tokens stored in the cloud

Blober vs rclone

Feb 1, 2026

Overview

rclone is the industry-standard CLI tool for cloud storage automation among developers and sysadmins. It is extremely powerful, supports over 70 storage providers, and is completely free and open-source. Its tradeoff is complexity - every job requires flags, config files, and terminal expertise.

Blober is built for users who want rclone-level capability without managing flags, scripts, or terminal state. It replaces stateless CLI execution with persistent, visual workflows that anyone can set up and repeat.

Interface and Usability

rclone

Command-line only (experimental web GUI exists, but limited)
Configuration files and flags - every job requires manual setup
Excellent for scripting and cron-based automation
Steep learning curve for non-technical users
No built-in workflow persistence - you must manage your own scripts

Blober

Native desktop GUI (Windows, macOS, Linux)
Visual setup of sources, destinations, and filters
Saved workflows with one-click execution
Built-in task history with resumable state
Designed for repeatability and clarity - no terminal required

Feature Comparison

Feature	Blober	rclone
Interface	✅ GUI	CLI
Provider count	Growing	70+
GoPro Cloud support	✅ Yes	❌ No
Local filesystem	✅ Yes	Yes
Cloud-to-cloud	✅ Yes	Yes
Workflow persistence	✅ Yes	No (manual scripts)
Metadata path templates	✅ Yes	Manual scripting
Task history & resume	✅ Yes	Logs only
Encryption	Planned	Built-in
Automation	Limited	Extensive
Open source	No	Yes
Data path	✅ Direct	Direct (local)

GoPro Cloud: A Blober Exclusive

rclone supports over 70 providers - but GoPro Cloud is not one of them. If you shoot with GoPro cameras and want to move your media from GoPro's cloud to Backblaze B2, AWS S3, Wasabi, or your local NAS, rclone simply cannot help.

Blober is the only transfer tool with native GoPro Cloud integration, making it the obvious choice for photographers, videographers, action sports creators, and agencies managing GoPro media libraries.

Workflow Example

rclone requires upfront configuration, careful flag selection, and scripting discipline to safely repeat jobs:

rclone copy remote:bucket/path dest:bucket/path \
  --transfers 4 --checkers 8 --retries 3 \
  --filter-from filters.txt --log-file transfer.log

Forget a flag? Change a path? The job silently behaves differently. There is no built-in history of what ran, when, or whether it succeeded.

Blober stores each workflow as a durable configuration with immutable execution history. If a transfer is interrupted, Blober resumes based on stored state rather than re-running a stateless command.

This difference becomes critical for:

Long-running transfers over unreliable connections
Media archives with thousands of files
Users who run transfers infrequently and forget the exact flags
Teams where multiple people need to trigger the same workflow

Data Sovereignty

Both rclone and Blober are local-first tools - your credentials stay on your machine. This is a shared advantage over SaaS competitors like Flexify and MultCloud where credentials and potentially data flow through third-party servers.

Where Blober adds value over rclone:

No terminal exposure - credentials are managed in a secured desktop app, not plaintext config files
Encrypted credential storage - not a ~/.config/rclone/rclone.conf file on disk
Visual audit trail - every transfer logged with timestamps, file counts, and status

Cost and Support

Aspect	Blober	rclone
Cost	One-time license	Free
Support	Product support	Community forums
Updates	Included with license	Community-driven
Target user	Creators, agencies, engineers	Engineers, sysadmins

rclone being free is a genuine advantage. Blober earns its price by saving time, reducing errors, and opening cloud transfers to users who would never touch a terminal.

When Blober Makes More Sense

Choose Blober if you:

Prefer visual tools over terminal commands
Want repeatable workflows without writing scripts
Need GoPro Cloud support (only Blober has it)
Need clarity, task history, and one-click resumption
Transfer data occasionally but need it to work reliably every time
Value convenience and productivity over maximum flexibility
Want credentials stored securely - not in a plaintext config file

Download Blober at blober.io

cloud migration

Why the desktop folder is a poor backup source

Why use B2 for a OneDrive backup

How to copy OneDrive to Backblaze B2

What the OneDrive connection can see

Frequently asked questions

Related guides

Get Blober

When OneDrive to Google Drive makes sense

When Google Drive to OneDrive makes sense

What moves in each direction

How to move from OneDrive to Google Drive

How to move from Google Drive to OneDrive

Before you cancel the old account

Frequently asked questions

Get Blober

AzCopy does not download S3 data through your computer

Authentication is different on each side

Bucket names may change

Invalid metadata needs an explicit choice

AWS S3 is not every S3-compatible service

When a desktop workflow fits better

Related Guides

Get Blober

The file bytes still have to move

Three routes

Full local download and upload

Stream through your computer

Stream through a hosted relay

Streaming does not remove provider limits

Migration is not sync

A safer migration sequence

Related Guides

Get Blober

The Short Definition

Where You Use It

Case 1: You Select an Individual File

Case 2: You Select a Folder and the File Is at Its Root

Case 3: You Select a Folder and the File Is Nested

Selection Changes the Result

Why file_dir Matters With Custom Templates

Mixed File and Folder Selections

Useful Templates

Common Mistakes

Verify It in Preview

Can You Move GoPro Cloud Files Directly to Google Drive?

What You Need

Step 1: Open a New Workflow

Step 2: Connect the GoPro Source

Step 3: Select the GoPro Media

Step 4: Connect Google Drive

Step 5: Choose the Google Drive Folder

Step 6: Review and Save

Step 7: Run and Monitor the Transfer

How Long GoPro Transfers Resume

How Blober Handles Individual File Errors

Will a Restart Create Duplicate Files in Google Drive?

GoPro Cloud to Google Drive vs Manual Download

Frequently Asked Questions

Does Blober delete the files from GoPro Cloud?

Does the transfer reduce video or photo quality?

Must Blober remain open?

What happens when GoPro login expires?

Can I cancel GoPro Premium immediately after starting?

Related Guides

Get Blober

Alibaba Cloud OSS (Object Storage Service)

Tencent Cloud COS (Cloud Object Storage)

Huawei Cloud OBS (Object Storage Service)

IBM Cloud Object Storage (COS)

Oracle Cloud Infrastructure (OCI) Object Storage

Google Cloud Storage (XML / S3 Interoperability)

Yandex Object Storage

VK Cloud Object Storage (formerly Mail.ru Cloud Solutions)

Baidu AI Cloud BOS (Baidu Object Storage)

JD Cloud Object Storage (OSS)

China Mobile Ecloud EOS (Elastic Object Storage)

Kingsoft Cloud KS3

China Telecom CTYun OOS

NAVER Cloud Object Storage