cloud storage

DJI Osmo and Insta360 Footage: Where It Should Live

Jun 24, 2026

Where Should Action-Cam Footage Live?

Action-cam footage is large, shot in bursts, and rarely needed in a hurry, so it belongs on storage you own or on cheap, durable object storage, with a second copy somewhere else. A camera-maker's own cloud is a fine staging area, not a final home.

This guide is brand-neutral. Whether you shoot on a DJI Osmo, an Insta360, a GoPro, or a mix, the storage problem is the same: a lot of big files and nowhere obvious to put them.

The Honest Problem With Camera-Maker Clouds

Each camera ecosystem nudges you toward its own app and cloud. That is convenient on day one and limiting later. The clouds are tuned for their own footage, the bulk-export tools tend to be weak, and your library ends up split across apps that do not talk to each other.

If you shoot on more than one brand, this gets worse fast. Footage scattered across a DJI account, an Insta360 account, and a GoPro subscription is three separate silos with three separate exit doors.

The Options, Ranked by Job

A NAS or external drive (footage you own, kept close). Best for active projects and anyone who wants the files under their own roof. A Synology or similar NAS turns a stack of drives into one library you control.

Object storage: Backblaze B2, Wasabi, Cloudflare R2 (the long-term archive). Best for footage you want to keep but rarely open. It is durable and built for large files. Compare them on egress model and minimum storage duration rather than on the sticker, since those terms decide the real cost of an archive you read back occasionally.

Dropbox or Google Drive (sharing and collaboration). Best when the point is handing footage to a client, an editor, or family. Easy links, familiar to everyone, not built to be a cheap multi-terabyte vault.

A Simple Setup That Works for Any Brand

Pull footage off the camera the way each brand expects: GoPro to GoPro Cloud, DJI through the Mimo app, Insta360 through its Studio app, or straight off the SD card.
Get a full-quality copy onto storage you own (a NAS or a drive).
Add a second copy on object storage or a second cloud for the off-site leg of a 3-2-1 backup.

That is the whole strategy. One working copy you can edit from, one archive you can fall back on.

Where Blober Fits

Blober moves footage between a broad range of cloud providers and local storage, so it is the piece that gets a library out of one place and onto another without a download-and-reupload detour. For GoPro specifically, it is the only desktop app that connects directly to GoPro Cloud and pulls the whole library out in one pass.

For DJI and Insta360, whose clouds have no open third-party access, the practical path is to bring footage local through their own apps first, then use Blober to move it onward to a NAS, to object storage, or to another cloud, and to keep that archive copy in sync as you add to it.

Frequently Asked Questions

What is the best storage for action-cam footage? Storage you own (a NAS or drive) for active footage, plus durable object storage like Backblaze B2 or Wasabi for the long-term archive. Keep two copies in different places.

Does DJI or Insta360 have a cloud like GoPro? Both have their own apps and cloud features, but none offer open third-party access for bulk export. The reliable approach is to bring footage local through their apps, then move it onto storage you own.

Can Blober connect to DJI or Insta360 cloud? Blober connects directly to GoPro Cloud. For DJI and Insta360, bring footage local first, then use Blober to move it to a NAS, object storage, or another cloud.

How do I keep one library across different camera brands? Land every brand's footage in one owned destination (a NAS or an object-storage bucket), then keep a second copy elsewhere. Blober handles the moves between them.

Get Blober

Get your action-cam footage onto storage you own. Blober moves it between the major cloud providers, local drives, and your NAS, and it is the only app that connects directly to GoPro Cloud.

Download Blober at blober.io

GoPro Cloud, in Plain English: How It Actually Works

Jun 24, 2026

How GoPro Cloud Works, in One Minute

GoPro Cloud is an auto-backup service that comes with a GoPro subscription. When your camera charges on a Wi-Fi network, it uploads the day's footage on its own, at full quality. You then watch, edit, and share those clips from the Quik app on your phone.

The part that trips people up: the cloud copy is a benefit of the subscription, not a permanent locker. While you pay, it is convenient. Stop paying and the access goes with it. The useful way to think about it is "a fast, automatic staging area," not "my one safe copy."

This page walks through each piece in plain terms, then shows how to keep a copy that stays yours.

The Auto-Upload Loop

The whole system is built around one habit: charging the camera.

Plug a GoPro in on a Wi-Fi network it knows, and while it sits there powered up, the new footage uploads itself to the cloud at full resolution. Once a clip is safely up, you can clear the SD card and keep shooting. That loop, shoot then charge then upload, is the reason people like the service. It removes the manual offload step that every action-cam owner used to dread.

Two conditions have to be true for it to run: the camera needs power, and it needs a Wi-Fi network it has been set up to use. On cellular or a strange network, it waits.

What the Quik App Does

Quik is the front end for everything in the cloud. It is where you browse what has uploaded, where the automatic highlight edits appear, and where you share a clip or a finished cut. For most owners, Quik is GoPro Cloud, because it is the only place they ever see the footage.

That is also the catch. Quik streams a compressed preview for fast playback, not the original file. It is fine for picking a moment or sending a quick highlight, and it is frustrating the day you want the full-quality clip on a real editing timeline.

What GoPro Cloud Stores, and What It Does Not

The headline feature, unlimited storage, applies to media captured on a GoPro camera. Footage from other cameras counts against a separate, capped allowance. So the cloud is tuned for the GoPro workflow, not as a general file drive for everything you own.

It keeps your GoPro video and photos, plus media you add through Quik. It does not give you a public way to pull everything back down in one move. The web portal downloads in small zipped batches, and there is no single "download all" button. For a handful of clips that is fine. For a few thousand, it is the weak point of the whole system.

Why People Treat It as Their One Copy, and Why That Is Risky

Because the upload is automatic and the storage is unlimited, it is easy to assume the footage is safe forever. It is one copy, in one company's cloud, reachable only while the subscription is active. There is no second copy and no third-party tool with open access if something goes wrong.

That is not a reason to avoid GoPro Cloud. It is a reason to keep a copy of your own next to it, so a cancelled card, a changed plan, or a new camera does not put your footage out of reach.

How to Keep a Copy You Own

Blober is the only desktop app that connects to GoPro Cloud, because no other transfer tool supports it. You sign in to GoPro through Blober, see your whole library, pick a destination, and let it run in parallel:

A local drive, an external disk, or a NAS you own
Object storage like Backblaze B2, Wasabi, or Cloudflare R2 for a long-term archive
Dropbox, Google Drive, AWS S3, Azure Blob, or DigitalOcean Spaces

No 25-file batches and no scripts. Keep your subscription or cancel it later; either way the footage now also lives somewhere you control.

Frequently Asked Questions

Does GoPro Cloud upload automatically? Yes. When the camera charges on a Wi-Fi network it knows, it uploads new footage at full quality on its own. It needs both power and that Wi-Fi connection to run.

Does GoPro Cloud store full-quality footage? Yes, it stores your originals. The Quik app plays a compressed preview for speed, but the full-resolution file is what was uploaded.

Can I see GoPro Cloud on a computer? You can sign in at gopro.com to view and download media, though the web portal only downloads about 25 files at a time. To pull your whole library to a computer or another cloud in one pass, use Blober.

Is GoPro Cloud a backup? Treat it as one copy, not a full backup. It is a single copy tied to your subscription. A real backup means a second copy on storage you control.

Get Blober

Keep your GoPro footage on storage you own. Blober is the only app that connects to GoPro Cloud, so you can move your whole library out whenever you want.

Download Blober at blober.io

The 3-2-1 Backup Rule for People Who Live in the Cloud

Jun 24, 2026

What the 3-2-1 Rule Says

Keep 3 copies of anything you care about, on 2 different kinds of media, with 1 copy off-site. It is an old rule from the server world, and it still holds. The twist for cloud-first people is that "it is in Google Photos" or "it is in Dropbox" counts as a single copy, not three.

A cloud account feels like safety because the company runs the servers. It is still one copy in one place, subject to one account that can be locked, billed, closed, or simply forgotten. That is exactly the single point of failure 3-2-1 exists to remove.

Why One Cloud Is Only One Copy

Account lockouts happen. Subscriptions lapse. A provider changes terms or sunsets a service. Sync can faithfully replicate a deletion or a corruption to every device before you notice. In each case, having everything in one cloud means having one copy, and one copy is the thing the rule warns against.

This is not an argument against your cloud. It is an argument for two more copies.

Building the Other Two Copies

You do not need a server rack. A workable 3-2-1 for a normal cloud library looks like this:

Copy 1: the cloud you already use. Google Photos, Drive, Dropbox, iCloud, GoPro Cloud, whatever holds the originals today.
Copy 2: storage you own. A NAS or an external drive. Different kind of media, under your own roof, reachable even if an account is not.
Copy 3: a second, off-site cloud. Object storage like Backblaze B2, Wasabi, or Cloudflare R2, or a second consumer cloud. This is the off-site leg that survives a fire, theft, or a drive failure at home.

Two kinds of media, one of them off-site. That is the whole rule.

Keeping the Copies Current

A backup made once and never updated slowly stops matching reality. The practical habit is to refresh the owned copy and the off-site copy on a schedule that matches how often the originals change: monthly for a photo library, after each shoot for a working archive.

Blober is the piece that moves data between these copies. It connects to a broad set of cloud providers plus local storage and copies between them directly, without staging a full copy on your disk. It has skip-existing, so a re-run only carries what is new rather than recopying everything, which is what makes "refresh the backup" a five-minute job instead of an afternoon.

A Quick Reality Check

Run one test before you trust any of this: open a few files from the owned copy and the off-site copy. A backup you have never opened is a hope. Two copies you have actually checked are a backup.

Frequently Asked Questions

What is the 3-2-1 backup rule? Keep 3 copies of your data, on 2 different types of media, with 1 copy stored off-site. It protects you from any single failure, whether a drive, an account, or a location.

Does cloud storage count as a backup? A single cloud account is one copy, not a backup. It becomes part of a real backup once you add a second copy on owned storage and a third copy off-site.

What is the easiest second copy for a cloud library? A NAS or an external drive. It is a different kind of media than the cloud and stays reachable even if an account is locked.

How do I keep my backup copies up to date? Re-run the copy on a schedule. A tool with skip-existing, like Blober, only moves what changed, so refreshing the owned and off-site copies is quick.

Get Blober

Build a real 3-2-1 backup without a weekend of manual uploads. Blober moves data between your clouds, your NAS, and local drives, and only copies what changed on a re-run.

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 work with it without code changes. 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 any device with that plug works in the wall, regardless of which utility generates the electricity. S3 compatibility is the plug shape. Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces all expose an S3-compatible endpoint, so the same aws s3 commands, the same rclone config, and the same desktop tools point at any of them by changing the endpoint and the keys.

Why It Matters When You Switch

This is the quiet superpower of S3 compatibility: it makes providers swappable. If your app reads and writes through the S3 API, 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.
s3proxy is an open-source proxy that presents an S3 API backed by Azure Blob and other stores.
VersityGW is an open-source S3 gateway with pluggable backends.
MinIO is S3-compatible storage that has been used to put an S3 API in front of other backends.

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.

Moving Between S3-Compatible Stores

Because the API is shared, moving data between S3-compatible providers is a clean operation. Blober connects to S3, Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces, and its generic S3 connector points at any other S3-compatible endpoint by URL, so a provider it does not list by name still works. 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.

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

GoPro Cloud Storage: The Complete Guide (Plans, File Types, Sharing, Limits)

Jun 9, 2026

GoPro Cloud Storage, Explained

The short version: GoPro Cloud is the storage that comes with a GoPro Premium or Premium+ subscription. When your camera charges on Wi-Fi, it auto-uploads your footage at full quality, and you edit and share it from the Quik app. Storage for GoPro-captured video and photos is unlimited; storage for footage from other cameras is capped.

The one limit that matters most: your cloud footage is tied to the subscription. Stop paying and you lose access to it. Everything below explains the plans, file types, sharing, and limits in plain terms, and how to keep a copy you own.

This is a reference page. Each section answers one common question, so jump to whichever one you came for.

What Is GoPro Cloud Storage?

GoPro Cloud is an auto-upload and backup service bundled with a GoPro subscription. The idea is simple: plug your camera in to charge, and while it sits on Wi-Fi, the day's footage uploads itself to the cloud at 100% quality. The camera's SD card can then clear, and the Quik app turns your clips into highlight videos you can watch and share from your phone.

It is built around the GoPro workflow, not as a general file locker. The headline feature, unlimited storage, applies only to media captured on a GoPro camera.

GoPro Premium and Premium+: Plans and Features

GoPro sells two subscription tiers (the service was previously called GoPro Plus). Here is what each one includes and how the cloud allowance compares to general storage services.

Plan	Price	GoPro footage	Non-GoPro footage
GoPro Premium	$59.99/yr	Unlimited cloud storage	100 GB
GoPro Premium+	$99.99/yr	Unlimited cloud storage	500 GB
Google One (for comparison)	$99.99/yr	n/a	2 TB total
Apple iCloud+ (for comparison)	$119.88/yr	n/a	2 TB total

Beyond storage, a GoPro Premium subscription also includes:

Auto-upload to the cloud at full quality while the camera charges on Wi-Fi
Automatic highlight videos generated in the Quik app
Guaranteed camera replacement for any reason (subject to GoPro's terms)
Up to 50% off accessories at gopro.com
Up to $150 off two cameras per year
Live streaming

Premium+ adds the larger 500 GB allowance for non-GoPro footage and some advanced editing features in Quik. Prices and inclusions change, so confirm the current numbers on GoPro's subscription page before you buy.

Supported File Types

GoPro Cloud stores what your camera produces, plus media you add through the Quik app.

Source	Typical formats
GoPro video	`.mp4` (HEVC or H.264), `.360` on Max and 360 cameras
GoPro photo	`.jpg`, and `.gpr` RAW (GoPro's DNG-based RAW)
Added through Quik	Photos and videos from your phone or other cameras

The unlimited allowance is for content captured on a GoPro device (Fusion is excluded). Footage from other cameras counts against the 100 GB (Premium) or 500 GB (Premium+) non-GoPro allowance.

Sharing happens mainly through the Quik app and your GoPro account:

Highlight videos. Quik auto-edits your uploaded clips into a shareable video you can post or send as a link.
Shared links. You can share individual media or edits as links to people who do not have a GoPro account.
Social export. Quik exports directly to the usual social platforms at chosen resolutions.

Sharing is designed for finished edits and individual clips, not for handing someone your entire raw library. There is no public API and no bulk export-and-share.

Storage Limits and Upgrades

The limits people run into:

Unlimited is GoPro-only. Non-GoPro footage is capped at 100 GB on Premium and 500 GB on Premium+. To raise that, upgrade from Premium to Premium+.
Auto-upload needs Wi-Fi and power. The camera uploads while charging on a Wi-Fi network. Cellular data fees may apply if you tether.
Downloading in bulk is the weak point. The web portal lets you download roughly 25 files at a time as a zip, and large batches frequently fail. There is no "download everything" button.

Upgrading or downgrading between Premium and Premium+ is done in your account settings.

You manage your subscription and view cloud media by signing in at gopro.com and through the Quik mobile app. From your account you can see your plan, change between Premium and Premium+, update billing, and start or stop auto-renew. The Quik app is where you browse uploaded media, build edits, and share.

How to Cancel GoPro Cloud

You cancel a GoPro subscription from your account settings on gopro.com or in the app, by turning off auto-renew. Two things to know before you do:

You lose access to your cloud footage when the subscription ends. The cloud library is a benefit of the subscription, not a permanent store.
GoPro does not publish an exact retention window for how long already-uploaded media stays on its servers after you cancel. The safe assumption is that you should treat it as gone once your access ends.

The practical takeaway: download or move your footage somewhere you control before you cancel. There is a step-by-step walkthrough in How to Cancel GoPro Plus Without Losing Your Footage.

The Limit Nobody Mentions: Your Footage Lives and Dies With the Subscription

GoPro Cloud is convenient, and for an active shooter the unlimited tier is genuinely a good deal. But it is one copy, in one company's cloud, that you can only reach while you keep paying. There is no second copy, no versioning, and no third-party tool with API access if something goes wrong. If you stop paying, change cameras, or GoPro changes its terms, the footage you cannot easily bulk-download is the footage you can lose.

That is not an argument against GoPro Cloud. It is an argument for having a copy of your own alongside it.

How to Keep a Copy You Own

Blober is the only desktop app that connects to GoPro Cloud, because no other transfer tool (rclone, MultCloud, Flexify, and the rest) supports it. You sign in to GoPro through Blober, browse your entire library, and send it wherever you want:

Your local drive, an external disk, or a NAS
Backblaze B2 or Wasabi for cheap long-term storage
Dropbox, Google Drive, AWS S3, Azure Blob, Cloudflare R2, or DigitalOcean Spaces

No 25-file zip limit, no manual batches. Connect, select everything, pick a destination, and run, with auto-resume if your connection drops. Keep your GoPro subscription or cancel it; either way the footage is now also on storage you control.

Frequently Asked Questions

Is GoPro Cloud storage really unlimited? For content captured on a GoPro camera (Fusion excluded), yes. Footage from other cameras counts against a separate allowance: 100 GB on Premium, 500 GB on Premium+.

What file types does GoPro Cloud store? GoPro video (.mp4, and .360 on 360 cameras), GoPro photos (.jpg and .gpr RAW), and media you add through Quik from your phone or other cameras.

How much does GoPro Cloud cost? GoPro Premium is $59.99/year and Premium+ is $99.99/year. Confirm current pricing on GoPro's site, since it changes.

Can I download all my GoPro Cloud footage at once? Not through GoPro's website, which limits you to small zip batches. Blober is the only tool that can browse your full GoPro Cloud library and download or transfer all of it in one workflow.

What happens to my footage if I cancel? You lose access to the cloud library when the subscription ends, and GoPro does not publish how long the data is retained afterward. Download or move it before cancelling.

Does any tool other than Blober connect to GoPro Cloud? No. As of 2026, GoPro Cloud has no public API, and Blober is the only third-party desktop app that supports it as a source.

Get Blober

Keep your GoPro footage on storage you own. Blober is the only app that connects to GoPro Cloud, and it is a one-time purchase with no subscription and no per-GB fees.

Download Blober at blober.io

GoPro Cloud vs Dropbox vs Google Drive: Where Should Your Footage Live?

Jun 9, 2026

Where Should Your GoPro Footage Live?

The problem: action-cam footage is big. A day of HERO video is tens of gigabytes, and a couple of seasons fills terabytes. GoPro Cloud, Dropbox, and Google Drive all want to hold it, but they are built for different jobs and priced very differently.

The short answer: GoPro Cloud is the best place to capture and edit footage because of auto-upload, but it locks your files to a subscription. Dropbox and Google Drive are better for sharing and mixing footage with other files, but their 2 TB tiers fill up fast and get expensive. For a large archive you rarely touch, none of the three is the cheapest home. Here is the full comparison.

The Three at a Glance

	GoPro Cloud	Dropbox	Google Drive
Typical price	$59.99/yr (Premium)	$119.88/yr (Plus, 2 TB)	$99.99/yr (Google One, 2 TB)
Capacity	Unlimited for GoPro footage	2 TB	2 TB
GoPro auto-upload	Yes, built in	No	No
Works with non-GoPro files	Limited (100 GB on Premium)	Yes, any file	Yes, any file
Bulk download	Hard (25-file zips)	Yes	Yes (or Takeout)
Sharing	Quik edits and links	Strong link sharing	Strong, Workspace-friendly
If you stop paying	Lose cloud access	Account read-only, then limited	Over-quota, read-only

Prices and allowances change; check each provider before deciding.

Cost Per Terabyte Is the First Filter

The math flips depending on how much footage you have.

Under 2 TB, actively shooting GoPro: GoPro Cloud's unlimited tier at $59.99/yr is the cheapest and least hassle, because it also auto-uploads and edits.
Under 2 TB, mixed with other work files: Dropbox or Google Drive at roughly $100 to $120/yr make sense, since your footage sits next to everything else and shares cleanly.
Over 2 TB: all three get awkward. GoPro Cloud stays unlimited but only for GoPro footage and only while you pay. Dropbox and Google Drive push you to pricier tiers. At this size, dedicated object storage is far cheaper, which is the subject of the best storage for GoPro and action-cam footage.

Upload Friction: GoPro Cloud Wins, Until You Want Out

GoPro Cloud is the only one of the three that uploads your footage for you. Plug the camera in on Wi-Fi and the day's clips go up at full quality, then Quik builds a highlight reel. Dropbox and Google Drive have no GoPro integration, so you offload the SD card to a computer first, then upload by hand.

The friction reverses when you want your footage out. GoPro Cloud has no bulk export and caps web downloads at small zip batches. Dropbox and Google Drive both let you pull everything back down (Drive via the app or Takeout). So GoPro Cloud is the smoothest in, and the hardest out.

GoPro Cloud shines for finished edits. Quik turns clips into shareable videos and links without you touching an editor.
Dropbox is the strongest for sending raw files and folders to people, with reliable shared links and large-file support.
Google Drive is best if your collaborators live in Google Workspace, with comments and in-place previews.

If your goal is a polished clip for social, GoPro Cloud is built for it. If your goal is handing a client or editor the raw footage, Dropbox or Drive is easier.

What Happens Long-Term

This is the dimension people forget until it bites.

GoPro Cloud is one copy that disappears when you stop paying, with no easy bulk export. It is a working cache, not an archive.
Dropbox and Google Drive keep your files if you downgrade, but they go read-only or over-quota, and large libraries cost real money every year, forever.

None of the three gives you an owned, offline copy. For footage you want in ten years, you need a copy on storage you control, regardless of which service you shoot into.

The Recommendation

Actively shooting and want zero-effort backup plus quick edits: keep GoPro Cloud. It is cheap and frictionless for that. But pair it with an owned copy so you are not one cancelled subscription away from losing everything.
You want footage alongside other files and easy sharing: Dropbox or Google Drive, as long as you stay under 2 TB. Past that, the price climbs.
You have a large archive you rarely touch: skip all three as the primary home and use cheap object storage or a NAS. See the best storage for GoPro footage.

Whichever you choose for shooting, the smart setup is shoot in one place, archive in another.

Blober Moves Footage Between All of Them

The reason you do not have to marry one service: Blober connects to GoPro Cloud (the only desktop app that does), Dropbox, Google Drive, and cheaper object storage like Backblaze B2 and Wasabi. You can:

Pull your GoPro Cloud library down before cancelling and push it to Dropbox, Drive, B2, or a NAS
Keep shooting into GoPro Cloud and run Blober now and then to copy new footage into an archive you own
Move a Dropbox or Drive video library into cheaper storage when it outgrows the 2 TB tier

Connect a source, pick a destination, run. Auto-resume if the connection drops, no per-GB fee.

Frequently Asked Questions

Is GoPro Cloud cheaper than Dropbox or Google Drive? For GoPro footage under the unlimited tier, yes: $59.99/yr beats Dropbox (about $120/yr) and Google One (about $100/yr) for 2 TB. The catch is that GoPro Cloud only stores GoPro footage cheaply, and you lose access if you cancel.

Can I move my footage from GoPro Cloud to Dropbox or Google Drive? Yes, with Blober. It is the only app that connects to GoPro Cloud, so you can transfer your library straight to Dropbox, Google Drive, or anywhere else.

Which is best for sharing GoPro videos? GoPro Cloud for polished highlight edits, Dropbox for sending raw files and folders, Google Drive if your collaborators use Google Workspace.

What is the best cloud storage for a large GoPro archive? For terabytes of footage you rarely touch, object storage like Backblaze B2 or Wasabi is far cheaper than any of these three. See the best storage for GoPro and action-cam footage.

Get Blober

Shoot wherever you like and keep a copy you own. Blober is the only app that connects to GoPro Cloud, and it moves your footage to Dropbox, Google Drive, or cheaper storage. One-time purchase, no subscription.

Download Blober at blober.io

Rabata.io: Where It Fits and Where It Doesn't

May 14, 2026

What Rabata Actually Is

Rabata.io is an S3-compatible object storage provider from RCS Technologies (UK) with two products: Hot Storage, general-purpose object storage at $0.01/GB/month in us-east-1, designed for applications, media, and frequently accessed data, and Backup, bulk archival storage at $49/10TB flat in eu-west-2, intended for backups, disaster recovery, and cold data. Both use standard AWS SigV4 authentication, work with any S3 SDK or CLI, and require no code changes to migrate from AWS S3. You swap the endpoint and credentials.

That is the entire product. No compute layer, no managed databases, no dashboard file browser: you cannot preview or view objects through Rabata's web UI, so you need an S3 client or a tool like Blober to actually see what's in your buckets. Just storage with an S3 API.

What the Benchmarks Show

Rabata published benchmarks using MinIO warp v1.0.7 (released January 2025, now superseded by v1.5.0) on a Debian 13 VM in us-east-1 with 8 concurrent threads in September 2025. The methodology is public.

According to their numbers, Rabata wins upload speed by a small margin (1,462 MB/s vs AWS's 1,444) and mixed operations by 2.3x over AWS. It loses on downloads to both Backblaze (2,075 MB/s) and AWS (1,816), and loses small object throughput to iDrive e2 (962 ops/s vs 696).

The mixed operations number is the most relevant for production workloads. Real applications read, write, list, stat, and delete concurrently. Rabata scored 2.3x higher than AWS S3 in that test.

These are same-region tests (us-east-1 to us-east-1). Performance from other geographies is unknown, and Rabata only operates in two regions. The runs are 30 seconds to 10 minutes with 8 threads, so they measure burst, not sustained multi-TB daily throughput over months. The warp version used (v1.0.7, January 2025) was already 8 months old at the time of testing and is now over a year outdated, and newer versions may produce different results. AWS S3 publishes 99.999999999% durability. Rabata publishes no durability SLA, and their terms include a broad "as is" disclaimer with zero liability for data loss.

The Real Use Case

Rabata fits a specific profile:

Write-heavy S3 workloads that need to stay cheap. If you're ingesting backup pipelines, media uploads, log aggregation, or AI training data, and your bottleneck is upload throughput plus cost, Rabata's upload speed at $0.01/GB is competitive, roughly 57% less than AWS's $0.023/GB first-tier pricing (AWS discounts at volume).

The Backup tier at $49/10TB ($0.0048/GB) is priced below Backblaze B2 ($6.95/TB, ~$0.007/GB) and Wasabi ($6.99/TB, ~$0.007/GB, increasing to $7.99/TB in July 2026). Wasabi enforces a 90-day minimum retention. Rabata's Backup tier has no documented minimum retention, but note: egress is capped at 2x your storage amount and billing is in 10TB increments rounded up: store 1TB and you pay for 10TB.

GDPR-compliant EU storage. The eu-west-2 Backup tier gives you EU data residency, which Rabata calls out explicitly. Worth noting: Rabata's parent company (RCS Technologies) operates under UK law, not EU law. Hetzner also offers EU-based S3-compatible storage with three EU regions (NBG1, FSN1, HEL1) versus Rabata's single EU region. For European companies that need S3-compatible storage with data residency guarantees, both are worth evaluating.

No-friction evaluation. 30-day trial, no credit card required per Rabata's signup page.

Where It Doesn't Fit

Download-heavy workloads. If you're serving content to users, Backblaze B2 (2,075 MB/s downloads, ~$0.007/GB) or Cloudflare R2 ($0.015/GB storage, zero egress, weak throughput but free delivery) are better choices depending on whether you're optimizing for speed or cost.
Global distribution. Two regions. If you need worldwide low-latency access, this is not the product.
Enterprise compliance requirements. No published durability SLA, no SOC 2 mention, limited public track record, benchmarks not independently verified.
Ecosystem depth. No lifecycle policies, no event notifications, no cross-region replication, no versioning (or at least none documented), no dashboard file browser. AWS S3 has all of these. Rabata does not.

Where It Sits Competitively

Based on Rabata's own benchmarks (no independent verification available), they offer three things at once that no other single provider does:

Fastest mixed workload performance in their published benchmarks
Simple pricing at $0.01/GB with $0.01/GB egress (Backup tier: egress capped at 2x storage)
No-barrier trial with no credit card required

AWS is faster on downloads but 2-3x more expensive. Backblaze is comparable on storage (~$0.007/GB) but slower on uploads. Cloudflare R2 has zero egress but performs 3-8x worse. Wasabi has no egress fees but enforces 90-day minimums. iDrive wins on small objects but falls behind on mixed workloads.

If your workload is "ingest data via S3 API, store it cheaply, occasionally read it back," Rabata is worth testing. If your workload needs more features, more regions, or a long track record, look elsewhere.

Using Rabata with Blober

Blober supports Rabata.io as a native provider. Connect with your access key and secret key, and Blober detects your buckets across both regions (Hot Storage and Backup). You can use Rabata as a source or destination in any workflow: migrate to it from AWS S3, sync from Dropbox, back up from Google Drive, or download files from Rabata to your local machine. Since Rabata's dashboard has no built-in file browser, Blober is one of the easiest ways to actually see and manage what's in your buckets.

What Blober supports with Rabata:

Browse: list buckets and objects across both regions (something Rabata's own dashboard doesn't offer)
Upload: write files to Hot Storage or Backup buckets
Download: pull files from Rabata to local storage or stream to another provider
Copy/Move: transfer objects between buckets
Delete: remove objects

Blober handles the region routing automatically. If a bucket lives in eu-west-2, operations go through the eu-west-2 endpoint. No manual configuration needed.

For setup details, see the Rabata.io provider documentation.

How to Bulk Change Azure Blob Storage Access Tiers (Hot, Cool, Cold, Archive)

May 11, 2026

Azure Storage Tiers and the Problem with Managing Them

Azure Blob Storage offers four access tiers: Hot, Cool, Cold, and Archive. Each tier has different storage and retrieval costs. The idea is straightforward: keep frequently accessed data on Hot, move older data to Cool or Cold, and archive rarely needed files to Archive for the lowest per-GB rate.

In practice, managing tiers is not that simple. Azure Portal lets you change tiers one blob at a time. For bulk changes, Microsoft points you to PowerShell scripts, Azure CLI, or lifecycle management policies. If you want to move 500 blobs from Hot to Archive, you are either clicking through the portal for an hour or writing and testing a script.

Lifecycle policies help with automated transitions, but they operate on rules and schedules. They are not designed for the case where you look at a set of files and decide, right now, that these specific blobs need to be on a different tier.

Hot, Cool, Cold, and Archive: The Tiers at a Glance

Azure Blob Storage has four access tiers. The colder the tier, the less you pay to store data and the more you pay, in both money and time, to read it back. Here is the practical comparison.

Tier	Storage cost	Read cost	Minimum retention	Time to first byte	Best for
Hot	Highest	Lowest	None	Milliseconds	Data in active use
Cool	Lower	Higher	30 days	Milliseconds	Backups, data read about monthly
Cold	Lower still	Higher still	90 days	Milliseconds	Rarely touched data you still want instantly
Archive	Lowest	Highest	180 days	Hours (rehydration)	Long-term archive and compliance copies

Two things catch people out:

Archive is offline. You cannot read an archived blob directly. You first rehydrate it to Hot, Cool, or Cold, which can take up to 15 hours. Plan for that latency before you archive anything you might need quickly.
Early deletion penalty. If you delete, overwrite, or move a blob out of Cool (30 days), Cold (90 days), or Archive (180 days) before its minimum retention elapses, Azure charges a prorated early deletion fee. Moving a blob to Archive and pulling it back two weeks later is not free.

Moving a warmer blob to a cooler tier is instantaneous. Only the reverse, rehydrating from Archive, takes time.

What Blober Does Differently

Blober is a desktop app that connects to Azure Blob Storage as one of its supported providers. Beyond the usual read, write, list, and delete operations, Blober supports something called mutations for Azure Blob. Mutations let you change properties of existing blobs without transferring any data.

Today, Blober supports two types of Azure mutations:

Storage Tier Changes

Select any number of blobs in the Blober file browser, choose a target tier (Hot, Cool, Cold, or Archive), and run the mutation. Every selected blob gets moved to the new tier. No re-upload, no script, no waiting for a lifecycle policy to kick in.

This is useful when you realize a project is finished and its assets should move to Archive, or when you need to bring archived files back to Cool for a review cycle.

Container Access Level Changes

Azure containers can be set to Private, Blob-level public access, or Container-level public access. Changing access levels usually means navigating to each container in the portal and updating the setting. With Blober, you select the containers you want to modify, pick the access level, and apply.

A Real Example: Post-Production Archival

Say you run a media production company. You have a container called project-alpine-2025 with 800 GB of raw footage sitting on Hot storage. The project wrapped three months ago and no one is accessing those files. You are paying Hot rates for storage that should be on Archive.

With Azure CLI, you would write something like:

az storage blob list --container-name project-alpine-2025 --output tsv | \
while read line; do
  az storage blob set-tier --container-name project-alpine-2025 --name "$line" --tier Archive
done

This works, but you need to set up authentication, handle pagination for large containers, deal with blobs that are already archived, and test the script before running it on production data.

With Blober, you open your Azure Blob connection, navigate to the container, select all files, choose "Archive" as the target tier, and click run. Done.

More Mutations Coming

Tier changes and access levels are the first mutations Blober supports for Azure. The architecture is designed to extend this to other providers and other types of modifications. Future mutations could include things like metadata updates, blob tagging, or replication settings. The goal is to give you the same visual, point-and-click control over blob properties that you already have for transfers.

Setting Up Azure Blob Storage in Blober

Connecting Azure to Blober takes about a minute:

Open Blober and add a new provider
Select Azure Blob Storage
Paste your connection string (the same one you would use with Azure Storage Explorer or the SDK)
Blober verifies the connection and lists your containers

From there, you can browse blobs, transfer files to or from Azure, and run mutations on existing blobs.

Configuration Options

When using Azure as a destination, Blober lets you configure:

Storage Tier: Choose which tier new uploads land on (Hot, Cool, Cold, or Archive)
Write Behavior: Overwrite existing blobs, skip if a blob already exists, or skip only if the blob is archived

These options are set per-workflow, so you can have one workflow that uploads to Hot and another that uploads directly to Archive.

Who Needs This

DevOps teams managing storage costs across multiple containers and projects
Media companies archiving completed project assets
Backup administrators moving cold data to cheaper tiers
Anyone who has outgrown Azure Portal's one-blob-at-a-time tier management

Common Questions About Azure Blob Tiers

Does changing a blob's access tier create a new version? No. Changing the tier with the Set Blob Tier operation does not create a new blob version. When versioning is enabled, the operations that create a version are writes: Put Blob, Put Block List, Copy Blob, and Set Blob Metadata. Set Blob Tier is not one of them, so the blob keeps its version ID and only its tier property changes. If you already keep multiple versions, each version holds its own tier, and explicitly tiering a version changes how that version is billed, but no new version is generated.

Can I set the tier per file share or only per storage account? That question is about Azure Files, which is separate from Azure Blob Storage. For Azure Blob, the tier is a property of each blob, so you set it per blob, and Blober changes many at once. For Azure Files, the older standard tiers (transaction optimized, hot, cool) are set per file share rather than per account, but you choose a share's media tier when you create it and cannot move a share between media tiers in place. To change it you create a new share and copy the data over. Blober's bulk tier change applies to Azure Blob blobs.

How long does a tier change take? Moving from a warmer tier to a cooler one, such as Hot to Cool or Cool to Archive, is instantaneous. Bringing a blob back from Archive to an online tier is a rehydration that can take up to 15 hours, depending on the priority you choose.

Can I move blobs to Archive in bulk without PowerShell? Yes. Select the blobs in Blober, choose Archive as the target tier, and run the mutation. No script, no lifecycle policy, no Azure CLI. The same works in reverse to rehydrate selected blobs to Hot, Cool, or Cold.

Will changing tiers re-upload my data? No. A tier change is a property change on the blob in place. Nothing is downloaded or re-uploaded, so there is no egress cost for the change itself.

Get Blober

Blober is a one-time purchase. No subscriptions. No transfer fees. No transfer limits.

Download Blober at blober.io

cloud storage

Where Should Action-Cam Footage Live?

The Honest Problem With Camera-Maker Clouds

The Options, Ranked by Job

A Simple Setup That Works for Any Brand

Where Blober Fits

Frequently Asked Questions

Related Guides

Get Blober

How GoPro Cloud Works, in One Minute

The Auto-Upload Loop

What the Quik App Does

What GoPro Cloud Stores, and What It Does Not

Why People Treat It as Their One Copy, and Why That Is Risky

How to Keep a Copy You Own

Frequently Asked Questions

Related Guides

Get Blober

What the 3-2-1 Rule Says

Why One Cloud Is Only One Copy

Building the Other Two Copies

Keeping the Copies Current

A Quick Reality Check

Frequently Asked Questions

Related Guides

Get Blober

What "S3-Compatible" Actually Means

The API Is the Standard, Not the Company

Why It Matters When You Switch

What Compatibility Does Not Guarantee

A Note on Azure Blob

Moving Between S3-Compatible Stores

Frequently Asked Questions

Related Guides

Get Blober

GoPro Cloud Storage, Explained

What Is GoPro Cloud Storage?

GoPro Premium and Premium+: Plans and Features

Supported File Types

Sharing Options

Storage Limits and Upgrades

Account Management and Login

How to Cancel GoPro Cloud

The Limit Nobody Mentions: Your Footage Lives and Dies With the Subscription

How to Keep a Copy You Own

Frequently Asked Questions

Related Guides

Get Blober

Where Should Your GoPro Footage Live?

The Three at a Glance

Cost Per Terabyte Is the First Filter

Upload Friction: GoPro Cloud Wins, Until You Want Out

Sharing

What Happens Long-Term

The Recommendation

Blober Moves Footage Between All of Them

Frequently Asked Questions

Related Guides

Get Blober

What Rabata Actually Is

What the Benchmarks Show

The Real Use Case

Where It Doesn't Fit

Where It Sits Competitively

Using Rabata with Blober

Azure Storage Tiers and the Problem with Managing Them

Hot, Cool, Cold, and Archive: The Tiers at a Glance

What Blober Does Differently

Storage Tier Changes

Container Access Level Changes

A Real Example: Post-Production Archival

More Mutations Coming

Setting Up Azure Blob Storage in Blober

Configuration Options

Who Needs This

Common Questions About Azure Blob Tiers

Get Blober