cost optimization

2 posts with the tag "cost optimization"

The Best Storage for GoPro and Action-Cam Footage in 2026

Jun 9, 2026

Where to Put Terabytes of GoPro Footage

The problem: GoPro Cloud is great for shooting, but its unlimited tier only holds GoPro footage, and only while you keep paying. Once you have a real archive (multiple terabytes of HERO and action-cam video you want to keep for years) you need a cheaper, permanent home that you own.

The short answer: for most people, Backblaze B2 is the best all-round home at $6.95/TB/month with free egress up to 3x what you store. If you download often, Wasabi removes egress math entirely. If you serve footage publicly, Cloudflare R2's zero egress wins. And a local NAS is cheapest over many years if you are willing to maintain it. Here is the full comparison.

The Options at a Glance

Option	Price	Egress	Best for
Backblaze B2	$6.95/TB/mo (about $83/yr per TB)	Free up to 3x stored, then $0.01/GB	The best default for most archives
Wasabi	$6.99/TB/mo, rising to $7.99 on July 1, 2026	Free (no egress or API fees)	Frequent downloads, predictable bills
Cloudflare R2	$15/TB/mo (about $180/yr per TB)	Free (zero egress)	Serving or streaming footage publicly
Local drive or NAS	One-time hardware cost	Free	Largest archives, lowest long-run cost
GoPro Cloud (baseline)	$59.99/yr, unlimited GoPro footage	Bulk download is hard	Capturing and editing, not archiving

Prices are current as of 2026 and change over time. Always confirm before committing a large library.

Backblaze B2: The Best Default

At $6.95 per TB per month, B2 is roughly a quarter of the price of Amazon S3 for storage, and egress is free up to three times the amount you store each month. For a footage archive, where you upload once and download occasionally, that free-egress allowance usually covers normal retrieval, so your bill is essentially just storage.

• Cost for 5 TB: about $35/month, or roughly $417/year.
• Why it fits GoPro footage: you store a lot and read a little, which is exactly what B2 prices for.
• S3-compatible, so it works with standard tools.

For most people archiving GoPro footage, B2 is the recommendation.

Wasabi: No Egress Math

Wasabi charges one flat rate for capacity, with no egress or API request fees at all. The current rate is $6.99/TB/month, increasing to $7.99/TB/month on July 1, 2026. The trade-offs are a 1 TB minimum and a 90-day minimum storage duration per object, so it suits archives you keep rather than data you churn.

• Best when you pull footage back frequently and do not want to think about egress allowances.
• Watch the 90-day minimum retention: deleting footage early still bills for the remainder of the 90 days.

Cloudflare R2: Zero Egress for Public Footage

R2 costs more to store ($15/TB/month) but charges nothing for egress, ever. That is the opposite balance from B2: you pay more to hold the data and nothing to serve it.

• Best when you publish or stream footage to viewers, where egress on other providers would dominate the bill.
• Not the cheapest for a private cold archive you rarely read; B2 or Wasabi wins there.

Local Drive or NAS: Cheapest Over Years

A hard drive or a NAS (Synology, QNAP, TrueNAS) is a one-time purchase. An 8 TB drive is well under the cost of a single year of cloud storage at that size, and a NAS gives you redundancy across multiple drives.

• Best for the largest archives and the lowest cost measured over five or ten years.
• The catch: a single local copy is not a backup. Drives fail, and a fire or theft takes everything. Use a NAS as one leg of a plan, not the whole plan.

There is a full walkthrough in back up cloud storage directly to your NAS.

The 3-2-1 Setup for Footage You Cannot Re-Shoot

Action-cam footage is unrepeatable. The standard rule for irreplaceable data is 3-2-1: three copies, on two kinds of media, with one offsite. A practical version for GoPro footage:

1. Working copy: GoPro Cloud or your editing machine while a project is active.
2. Local archive: a NAS or external drive you own.
3. Offsite copy: Backblaze B2 or Wasabi.

That gives you cheap bulk storage, a fast local copy, and an offsite copy that survives a disaster, for far less than paying a 2 TB consumer plan forever.

How Blober Gets Your Footage There

Whichever destination wins, Blober is what moves the footage into it. It is the only desktop app that connects to GoPro Cloud, so you can:

• Pull your entire GoPro Cloud library out (no 25-file zip limit) and push it to B2, Wasabi, R2, or a NAS
• Copy footage to two destinations to build the 3-2-1 setup
• Organize files on the way in with path templates, so a flat cloud dump lands as a clean camera/date/file archive

Connect GoPro Cloud as the source, pick your storage as the destination, run, and let it resume through any dropped connection.

Frequently Asked Questions

What is the cheapest cloud storage for GoPro videos? For a private archive, Backblaze B2 ($6.95/TB/month) and Wasabi ($6.99/TB/month) are the cheapest credible options, both far below Amazon S3 or consumer plans. A local NAS is cheaper still over several years if you maintain it.

Is GoPro Cloud good for long-term storage? It is good for capturing and editing, not for archiving. It only stores GoPro footage cheaply, you lose access if you cancel, and there is no bulk export. Keep a copy elsewhere for the long term.

How do I move footage from GoPro Cloud to Backblaze B2 or Wasabi? Use Blober. It connects to GoPro Cloud and transfers your library directly to B2, Wasabi, or any supported destination, with no manual batching.

Backblaze B2 or Wasabi, which is better for GoPro footage? B2 if you mostly store and rarely download, thanks to its free 3x egress allowance. Wasabi if you download often and want zero egress math, keeping the 1 TB minimum and 90-day retention in mind.

Related Guides

• GoPro Cloud Storage: The Complete Guide
• GoPro Cloud vs Dropbox vs Google Drive
• Back Up Your GoPro Cloud to Backblaze B2, AWS S3, or Local Storage
• Back Up Cloud Storage Directly to Your NAS

Get Blober

Move your GoPro footage to the storage that actually fits a large archive. 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

Tags:

• blober
• gopro
• gopro cloud
• backblaze b2
• wasabi
• nas
• media archive
• cost optimization

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:

1. Open Blober and add a new provider
2. Select Azure Blob Storage
3. Paste your connection string (the same one you would use with Azure Storage Explorer or the SDK)
4. 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

Tags:

• blober
• azure
• azure blob storage
• storage tiers
• cloud storage
• cost optimization