cloud backup

A cloud library can take hours or days to copy. During that time, a computer may restart, a network may disconnect, or a provider may ask you to sign in again. You may also want to run the same export later to collect newer files.

Those situations sound similar, but they need different tools:

• Resume the existing task after an interruption. Blober keeps that task's progress and does not process its completed records again. This works on every provider and needs no setting.
• Use destination deduplication for a deliberate rerun. When a new task writes to the same destination, deduplication decides whether files that are already there are skipped or overwritten. This depends on the destination supporting it.

Understanding that distinction is the key to avoiding unnecessary transfers.

A workflow is the reusable setup: source, destination, selected folders, filters, and naming rules. Each time you start that workflow, Blober creates a task that records the progress of that run.

Within a task, Blober records each source path as it is processed or skipped. If that task is interrupted and later continues, records already marked complete are not processed again.

This task state is stored locally with your workflows. Closing Blober, restarting the computer, or installing a newer version of Blober preserves the existing workflows and task history.

1. Reopen Blober.
2. Find the existing task on the Progress page.
3. If it was paused, resume that same task.
4. If it was still pending or running when Blober closed, the app can rediscover it after launch and continue it automatically.
5. Complete any provider login prompt that appears.

Do not start a new task merely because the original task stopped. A new run has its own progress records and is not a continuation of the interrupted run.

This matters especially for long cloud transfers. A provider login may expire during a run; signing in again refreshes access, while the existing task keeps its completed-file state.

Deduplication is a destination setting that decides what happens when the exact destination path is already occupied:

• Skip if a file with the same name exists - the default. The file is not written, the record is marked skipped, and the run continues with the next file.
• Overwrite the existing file - the destination copy is replaced.
• Keep both files (rename the new copy) - available on Local destinations, which save the new file as name (1).ext, then name (2).ext.

The comparison is the destination path: destination folder, path template, and filename. File contents are never compared.

The control appears only for destinations that can act on an existing file:

• Source-only providers have nothing to deduplicate.
• GoPro Cloud cannot replace or compare by name, so a rerun writes the file again.

Azure Blob Storage adds one rule of its own: archived blobs are always skipped, whichever policy is selected, because an archived blob cannot be rewritten. Rehydrate the blob first if you want to replace it.

For a repeat export where an exact existing destination path means "already transferred":

1. Open or create the workflow.
2. Select the destination.
3. Open the destination configuration.
4. Set Deduplication to Skip if a file with the same name exists.
5. Save and run the workflow.

Blober checks the destination before it opens the source, and repeats the check when claiming the final filename, which also protects against two concurrent transfers racing to create the same path.

See Deduplication for the policies and the destinations that support them.

Situation	Recommended action
Blober, the computer, or the network stopped during a task	Resume the existing task
A provider asks you to sign in again during a task	Sign in, then continue the existing task
You installed a Blober update during a transfer	Reopen Blober and continue the existing task
You intentionally rerun an export into the same folder	Set Deduplication to Skip if a file with the same name exists
You want the destination copies replaced	Set Deduplication to Overwrite the existing file, where the destination supports it
The source may contain different files with identical names	Choose Keep both files (rename the new copy) on a Local destination
The destination does not offer deduplication	Resume the same interrupted task instead of rerunning; a fresh run transfers the files again

Google Photos is a common case because a large library may take a long time to download and may contain repeated camera filenames.

For an interrupted Google Photos download, continue the existing task. For a deliberate later export into the same local folder, use Skip if a file with the same name exists only when preserving one file per exact destination filename matches your library.

The full setup is covered in How to Back Up Google Photos Without Google Takeout. That guide and the Deduplication reference use the same setting described here.

• Keep the computer connected to power and avoid moving or disconnecting the destination drive.
• Use a stable destination folder and path template for the whole task.
• Pause before intentionally shutting down if you want manual control over when the task continues.
• After an unexpected restart, reopen Blober before creating anything new and check the existing task first.
• Respond to provider login prompts instead of replacing the workflow.
• Review files marked failed or skipped after completion. A provider may temporarily make an individual file unavailable even though the rest of the transfer completed.

No. Installing an update preserves the local database that contains workflows, tasks, and per-record state. Reopen the existing task after the update rather than creating a replacement.

No. It checks whether the exact destination filename already exists. It does not calculate or compare content hashes.

Yes. Blober saves the reason in the task details and continues with the remaining files. This prevents one unavailable source file or an intentional destination duplicate from blocking the rest of the transfer.

Yes, if the destination supports it. Google Drive destinations offer skip and overwrite. Check the destination configuration for the Deduplication control: if it is not shown, that destination cannot act on an existing file, and resuming the original task is the way to avoid transferring the same files twice.

Blober runs on Windows, macOS, and Linux and is built for transfers that are too large to babysit in a browser.

Download Blober at blober.io

GoPro Plus (now sold as GoPro Premium) costs $59.99/year. It gives you unlimited cloud storage for your GoPro footage, camera replacement coverage, and discounts on accessories. For active GoPro users, that's a reasonable deal.

The problem shows up when you want to leave.

GoPro Plus auto-uploads your footage to GoPro Cloud. Over time, you might have hundreds of gigabytes sitting there. When you cancel, you lose access to those files. GoPro does not give you a bulk export tool, there's no API, and the web interface lets you download at most 25 files at a time in zip bundles.

If you have 500 videos from two years of travel, surfing, or family events, downloading them 25 at a time is not practical. And the zip downloads often fail on larger batches.

When your GoPro Plus subscription ends:

• You can no longer view or access your cloud footage
• Your files remain on GoPro's servers for a limited time (the exact retention policy is not published)
• No third-party tool has API access to help you
• You lose camera replacement coverage and store discounts

The footage does not transfer anywhere. It sits in GoPro's cloud until they delete it. If you did not download it before cancelling, it may be gone.

Blober is the only desktop app that connects to GoPro Cloud. It was built specifically because no other tool can access GoPro's proprietary storage system.

Install Blober on your Mac, Windows, or Linux computer. Add GoPro Cloud as a provider and sign in with your GoPro account. Blober captures your session and gives you a visual file browser showing your entire cloud library.

You have several options:

Local hard drive or SSD The simplest option. Select all your GoPro Cloud files, pick a local folder as the destination, and transfer. Your footage downloads to your computer at full quality.

External drive or NAS If your internal drive does not have enough space, point Blober to an external drive, SD card, or network-attached storage (Synology, QNAP, etc.).

Backblaze B2 (cheapest cloud option) If you want your footage in the cloud but do not want to pay $59.99/year, Backblaze B2 stores data at $6.95/TB/month. For 1 TB of GoPro footage, that is about $83/year with no subscription lock-in, no download limits, and full API access.

Dropbox, Google Drive, or AWS S3 If you already use another cloud provider, Blober can transfer your GoPro footage directly there. No double-download needed.

Select your files (or select all), choose the destination, and click run. Blober transfers with parallel streams, auto-resume on failure, and progress tracking. For large libraries, you can leave it running overnight.

Once your footage is safely stored elsewhere, cancel your subscription through the GoPro app or website. Your files are yours, on storage you control.

Storage Option	Cost (1 TB/year)	Download Limits	API Access
GoPro Plus	$59.99/year	25 files at a time	None
Backblaze B2	~$83/year	Unlimited	S3-compatible
Wasabi	~$84/year	Unlimited	S3-compatible
Local hard drive	One-time ~$40 (4TB HDD)	N/A	N/A
Google Drive (2TB)	$100/year	Unlimited	Yes

GoPro Plus is actually the cheapest cloud option per TB, but it comes with restrictions that the others do not have: no bulk downloads, no third-party tool access, and your footage is inaccessible the moment you cancel.

This is not a case of "just use rclone" or "try MultCloud." GoPro Cloud is a proprietary system with no published API. No transfer tool, CLI, or cloud sync service has ever supported it.

• rclone: No GoPro backend. Never had one.
• MultCloud: Does not list GoPro Cloud as a provider.
• Flexify: No GoPro support.
• CloudHQ, Mover, Movebot: None support GoPro Cloud.

Blober connects to GoPro Cloud through the same authentication path as GoPro's own web app. It is the only third-party tool that can read, download, and transfer your GoPro Cloud files.

Not everyone needs to cancel. If you shoot regularly and use GoPro's highlight tools, Plus is a solid deal. But even if you keep your subscription, having a backup somewhere else is just good practice.

Use Blober to mirror your GoPro Cloud to a local drive or Backblaze B2 as a safety net. That way, if GoPro changes their terms, raises prices, or has a service issue, your footage is protected.

Blober is a one-time purchase with a lifetime license. No subscription, no per-GB fees.

Download Blober at blober.io