Skip to content
Blober Blober Download Docs
Articles

Articles

How to Switch from Google Drive to Dropbox

Switch from Google Drive to Dropbox with Blober

Move Google Drive to Dropbox Without the Google Docs Trap

Section titled "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.

MethodGoogle Docs handlingFolder structureLocal disk neededBest for
Manual export, then uploadOpen and export each oneRebuild by handFull library sizeA handful of files
Google TakeoutExports to Office, inside flat zipsLost in date-stamped foldersSpace for every zipA full archive you will sort later
Blober (direct)Auto-converts to .docx, .xlsx, .pptxPreserved automaticallyNone, files stream through memoryMoving your account intact

Google Drive vs Dropbox: Different Strengths

Section titled "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

Section titled "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:

  1. Open each Google Doc, Sheet, or Slide
  2. Download it as DOCX, XLSX, or PPTX
  3. Upload it to Dropbox
  4. 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

Section titled "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

Section titled "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

Section titled "Steps"
  1. Connect Google Drive: OAuth login through your browser
  2. Connect Dropbox: OAuth login (or paste an access token)
  3. Browse and select: Navigate your Google Drive in Blober's file browser, select everything or specific folders
  4. 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

Section titled "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

Section titled "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.

Section titled "Related Guides"

One Move, Not a Monthly Bill

Section titled "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

Section titled "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

Switch from Wasabi to Backblaze B2 with Blober

Two S3-Compatible Providers, Different Tradeoffs

Section titled "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

Section titled "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

Section titled "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

Section titled "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

Section titled "Steps"
  1. 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).
  2. Connect Backblaze B2: Add B2 with your Application Key ID and Application Key. Blober auto-detects your bucket regions.
  3. Create a workflow: Source = Wasabi, Destination = B2. Browse your Wasabi buckets, select what to move.
  4. Run: Blober transfers with parallel multipart uploads and automatic resume.

What Blober Handles

Section titled "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

Section titled "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:

  1. Transfer everything to Backblaze B2
  2. Wait until the oldest files in Wasabi pass the 90-day mark
  3. 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

Section titled "Pricing Side-by-Side"
WasabiBackblaze B2
Storage per TB/mo$6.99$6.95
Egress per GB$0 (with conditions)$0.01 (free via Cloudflare)
Min retention90 daysNone
Free egress allowanceEqual to storage3x storage
CDN partnershipNoneCloudflare Bandwidth Alliance

Get Blober

Section titled "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

Transfer files from AWS S3 to Azure Blob Storage with Blober

Moving Between AWS S3 and Azure Blob

Section titled "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

Section titled "The Usual Approaches"

AzCopy + AWS CLI

Section titled "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

Section titled "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

Section titled "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

Section titled "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

Section titled "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

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

Migrating Buckets in Bulk

Section titled "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

Section titled "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

Section titled "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

Section titled "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.

Section titled "Related Guides"

Get Blober

Section titled "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

Upload to GoPro Cloud 4x Faster with Parallel Transfers

Upload to GoPro Cloud 4x faster with Blober parallel uploads

GoPro's Upload Problem

Section titled "GoPro's Upload Problem"

If you shoot with a GoPro, you know the routine. After a day of riding, diving, or traveling, your camera has anywhere from 20 to 200 GB of footage. You plug your camera in or connect via Wi-Fi, and the GoPro app starts uploading to GoPro Cloud.

The upload is slow. Not because your internet is slow, but because GoPro's app sends files one at a time. It picks a file, uploads it, waits for confirmation, then starts the next one. If you have 100 clips from a weekend trip, each one sits in a queue while the previous clip finishes.

This sequential approach means you are never using your full upload bandwidth. Most internet connections can handle several simultaneous uploads. A connection with 50 Mbps upload speed could be pushing four or five files at once, but GoPro's app uses it for just one.

How Blober Handles GoPro Cloud Uploads

Section titled "How Blober Handles GoPro Cloud Uploads"

Blober uses parallel upload streams when transferring files to GoPro Cloud. Instead of sending one file at a time, Blober opens multiple concurrent connections and uploads several files simultaneously.

The result is straightforward: if your connection can handle four simultaneous uploads (and most can), you finish in roughly a quarter of the time.

This is not a theoretical number. It comes down to basic network utilization. GoPro's sequential uploads leave bandwidth idle between files and during handshake overhead. Blober keeps the pipe full by starting the next upload before the previous one finishes its server-side confirmation.

What This Looks Like in Practice

Section titled "What This Looks Like in Practice"
ScenarioGoPro AppBlober
50 GB weekend trip (100 clips)~4 hours~1 hour
120 GB week-long shoot (300 clips)~10 hours~2.5 hours
8 GB quick session (15 clips)~35 min~8 min

Times based on a typical 30 Mbps upload connection. Actual speeds depend on your connection, file sizes, and GoPro Cloud server conditions.

No 25-File Batch Limit

Section titled "No 25-File Batch Limit"

GoPro's web interface limits downloads to 25 files at a time. If you want to download 500 clips, you need to repeat the process 20 times.

Blober has no batch limit. Select 10 files or 10,000 and start the transfer. Blober works through the entire queue without stopping to ask you to select the next batch.

Auto-Resume When Transfers Fail

Section titled "Auto-Resume When Transfers Fail"

Uploads fail. Connections drop, laptops go to sleep, Wi-Fi switches networks. When a GoPro Cloud upload fails through the app, it often starts the file over from scratch.

Blober tracks progress per file. If a transfer is interrupted, Blober resumes from where it stopped. For large files (GoPro's 5.3K videos can easily be 5-10 GB each), this saves real time. You do not re-upload 4 GB of a 5 GB file because your connection dropped at 80%.

Upload From Anywhere, Not Just Your Camera

Section titled "Upload From Anywhere, Not Just Your Camera"

GoPro's app expects you to upload from the camera or phone. If your footage is on an SD card, a NAS, or already in another cloud provider, you cannot use the app to get it into GoPro Cloud.

Blober lets you upload to GoPro Cloud from any source it supports:

  • Local drives and SD cards: Import footage from your card reader directly to GoPro Cloud
  • NAS devices: Upload from Synology, QNAP, or any network drive
  • Other cloud providers: Move files from Dropbox, Google Drive, or AWS S3 into GoPro Cloud
  • DJI or Insta360 footage: Consolidate action camera media from multiple brands in one cloud

Why GoPro Cloud?

Section titled "Why GoPro Cloud?"

Some people ask why you would upload to GoPro Cloud at all. Fair question. Here is when it makes sense:

  • You already have a GoPro Plus subscription and want to use the cloud highlight reels and editing features
  • You want automatic camera-to-cloud backup but need a faster way to bulk-upload existing footage
  • You shoot with DJI or other cameras and want all your action footage in one place with GoPro's editing tools

If you are moving away from GoPro Cloud, Blober handles that too. Transfer your entire library to Backblaze B2, AWS S3, Dropbox, or a local drive.

Get Blober

Section titled "Get Blober"

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

Download Blober at blober.io

How to Backup Google Photos Without Google Takeout (After rclone Lost Access)

Download all Google Photos without Takeout using Blober desktop app

Google Photos Does Not Have a "Download All" Button

Section titled "Google Photos Does Not Have a "Download All" Button"

If you have 10,000 or 50,000 photos in Google Photos and you want them on your computer, Google gives you two options:

  1. Select photos manually in the web interface. You can select up to 500 at a time, click download, and receive a zip file. Then repeat until you have covered your entire library.
  2. Use Google Takeout to request an export of your entire library. Google will prepare zip archives and email you a download link. This process can take hours or even days depending on library size.

Neither option lets you browse your library, pick a destination, and transfer everything in one step. There is no sync, no resume, and no way to send files directly to another cloud provider.

Google Photos has no download all button, Takeout takes hours, rclone lost library access, and manual download requires selecting photos one by one

Google Takeout: The Problems Nobody Talks About

Section titled "Google Takeout: The Problems Nobody Talks About"

Google Takeout is the official way to export your Google Photos library. On paper it works. In practice, it has real limitations:

  • Wait time. Google creates your archive in the background. For large libraries, this can take 12 to 48 hours.
  • Zip file format. Your photos arrive in multiple zip archives, often split into 2 GB chunks. You have to download each zip and extract them manually.
  • No folder structure. Takeout dumps all photos into flat directories organized by date. If you had albums, those names may appear as metadata JSON files next to the images, not as actual folders.
  • No resume. If a download fails, you start over. There is no incremental sync.
  • No direct cloud transfer. You cannot send Takeout exports directly to Dropbox, Backblaze, or a NAS. Everything goes through your browser first.

For someone with 200 GB of family photos, Google Takeout means hours of waiting followed by hours of downloading and extracting.

Google's official download options compared: manual selection limited to 500 at a time, Takeout takes hours, rclone API access revoked, and other tools do not work

rclone Lost Full Library Access in March 2025

Section titled "rclone Lost Full Library Access in March 2025"

Until early 2025, rclone had a Google Photos backend that could list and download your photo library. Then Google changed their API access policy.

Starting March 31, 2025, rclone can only download photos that were uploaded through the rclone API itself. If you uploaded your photos through the Google Photos app, the web interface, or any other method, rclone cannot access them anymore.

The rclone documentation states it clearly: "From March 31, 2025 rclone can only download photos it uploaded."

This means rclone is no longer a viable tool for backing up or migrating an existing Google Photos library. Other transfer tools like MultCloud, Flexify, and various CLI utilities face the same restriction or never supported Google Photos at all.

Blober downloads your entire Google Photos library without Takeout, with no manual selection, transfer to any cloud or disk, and auto-resume

Blober Downloads Your Entire Google Photos Library

Section titled "Blober Downloads Your Entire Google Photos Library"

Blober is a desktop application that connects to Google Photos and gives you a visual file browser showing your entire library. From there, you can:

  • Download all photos and videos to your local disk, external drive, or NAS
  • Transfer your library to Dropbox, Google Drive, Backblaze B2, AWS S3, or any other supported provider
  • Browse by album, date, or folder with a familiar file manager interface
  • Resume interrupted transfers automatically if your connection drops
  • Optionally skip files with existing filenames by setting Local destination deduplication to Filename

No Google Takeout. No zip files. No manual selection. You connect your Google Photos account, pick a destination, and Blober handles the rest.

How It Compares to Takeout

Section titled "How It Compares to Takeout"
FeatureGoogle TakeoutBlober
Bulk downloadYes, after hours of waitingYes, immediate
Folder structureFlat zip archivesAlbums and dates preserved
Resume on failureNoYes, automatic
Transfer to another cloudNo, browser download onlyYes, direct to any provider
Real-time browsingNoYes, visual file browser
Incremental syncNoOptional filename deduplication for repeat runs

For repeat exports, see how task resume and Local filename deduplication prevent duplicate downloads. Resume an interrupted task to preserve its per-file progress; use the Local Filename option when intentionally starting a new export into the same folder.

Before and after comparison showing Google Takeout workflow versus Blober's direct Google Photos download and transfer

Common Use Cases

Section titled "Common Use Cases"

Back Up Google Photos to a Local Drive

Section titled "Back Up Google Photos to a Local Drive"

Connect Google Photos in Blober, select your local disk as the destination, and transfer. Every photo and video downloads to a folder on your computer. If you have 100 GB of photos, Blober will transfer them without creating zip files or requiring extraction.

Migrate Google Photos to Dropbox or iCloud

Section titled "Migrate Google Photos to Dropbox or iCloud"

If you are leaving Google Photos for another service, Blober lets you transfer your library directly. Connect Google Photos as the source and Dropbox as the destination. Your photos move from one cloud to the other without touching your local disk (or through it, if you prefer a local copy).

Create a Cold Backup on Backblaze B2

Section titled "Create a Cold Backup on Backblaze B2"

Pair Google Photos with Backblaze B2 in Blober. Your entire photo library gets copied to B2 at $6.95/TB/month for storage. This gives you an independent backup that does not depend on Google.

Why This Matters

Section titled "Why This Matters"

Google Photos is not a backup. It is a service that can change its terms, adjust its storage pricing, or restrict access at any time. The March 2025 API change proved that: tools that worked for years stopped working overnight.

Having a local copy of your photos, or a copy in a second cloud provider, means you are not dependent on a single company to access your own memories.

Blober makes that transfer possible without the pain of Google Takeout, without CLI configuration, and without selecting 500 photos at a time.

Who Is This For?

Section titled "Who Is This For?"
  • Anyone with a large Google Photos library who wants a local backup
  • Users leaving Google Photos for Dropbox, iCloud, or another service
  • Parents and families with years of photos who want a second copy on a hard drive
  • Photographers who used Google Photos as a sync target and need to migrate
  • Privacy-conscious users who want their photos on storage they control

Get Blober

Section titled "Get Blober"

Blober is a one-time purchase with a lifetime license. No subscriptions. No transfer fees. No transfer limits. It runs on Mac, Windows, and Linux.

Download Blober at blober.io