How to Transfer GoPro Cloud to Google Drive Without ZIP Files

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

• 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.

1. Open Blober and select Workflows in the left navigation.
2. On the Workflows page, click New Workflow.
3. Enter a Workflow Name, such as GoPro Cloud to Google Drive.
4. Enter a Workflow Description that will help you recognize the backup later.
5. 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.

In the numbered 1 Source Configuration panel:

1. In Search and select a provider, search for and select GoPro Cloud.
2. Under GoPro Account, choose an account you have already connected.
3. To connect another account, click Add account, then Open GoPro Login.
4. 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.

1. Click Browse Files and Folders under Select Source.
2. Use the checkboxes to select the date folders, camera folders, photos, or videos you want to copy.
3. 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

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

1. In Search and select a provider, search for and select Google Drive.
2. Under Google OAuth Credentials, choose the OAuth credentials JSON file created during Google Drive setup.
3. When the instructions appear beneath the field, click Authorize Google Drive Access.
4. Sign in to the Google account that will receive the GoPro backup and approve access.
5. 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.

1. Click Browse Folder under Select Destination Folder.
2. Navigate to the Google Drive folder where the backup should be stored.
3. Select that folder using its checkbox. Google Drive must have one destination folder for the workflow.
4. 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.

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.

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

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

1. Find the new workflow on the Workflows page.
2. Confirm its card shows GoPro Cloud as the source and Google Drive as the destination.
3. Click the green Run button.
4. 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, and the files stream through it from GoPro Cloud to Google Drive without being saved as a permanent local copy first. Your credentials remain on your machine, and the media does not pass through Blober's servers.

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:

1. Reopen Blober.
2. Return to the existing task on the Progress page.
3. Resume that task if it was paused. An active pending or running task can be rediscovered after launch.
4. 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.

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 carries on with the rest of the library, so one unavailable file does not hold up every file after it.

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.

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, which reads the source again. Google Drive allows several files with the same name in one folder, so on a rerun the destination's deduplication setting is what prevents duplicates. With the default, Skip if a file with the same name exists, files already at the destination path are skipped. The check compares names, not contents, so a changed file with the same name is skipped as well; choose Overwrite the existing file if you want it copied again. After an interruption, resuming the original task is still the better route, because it already knows which source paths it has processed.

Does Blober delete the files from GoPro Cloud? Not when the workflow action is Copy. The source media stays 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.

Does Blober have to stay open during the transfer? Yes, because Blober performs the transfer on your computer. It prevents system sleep while a task is active, but the computer must stay powered on and connected to the network.

What happens when the GoPro login expires? Blober asks you to sign in again. Once you have, continue the existing task; its completed-file state is preserved.

Can I cancel GoPro Premium right after starting the transfer? Wait until the task has finished and you have checked the files in Google Drive. The GoPro subscription must stay active while Blober reads the source library.

• GoPro Plus Cloud Media Download and Backup
• Google Drive Setup with OAuth and Transfers
• GoPro Cloud vs Dropbox vs Google Drive
• How to Download All GoPro Cloud Videos