aws s3

9 posts with the tag "aws s3"

Azure Blob Tiers vs AWS S3 Storage Classes (and Google Nearline/Coldline)

Jun 29, 2026

Azure calls them access tiers. Amazon S3 and Google Cloud Storage call them storage classes. Other providers call them tiers, classes, plans, or just pricing. The labels sound interchangeable, but they are not one-to-one.

The biggest trap is the word archive. Azure Archive is offline and must be rehydrated before you can read it. AWS S3 Glacier Flexible Retrieval and Deep Archive are also offline restore workflows. Google Cloud Storage Archive, despite the name, still has millisecond access; it is colder mainly because of retrieval charges and a 365-day minimum storage duration^[1]. If you treat all three as the same thing, your restore plan will be wrong.

This guide maps the intent behind each tier or class: hot data, monthly access, quarterly access, offline archive, automatic tiering, and provider-specific variants.

Tiers and Classes at a Glance

Intent	Azure Blob	AWS S3	Google Cloud Storage	Other provider names
Active, frequently read data	Hot	S3 Standard	Standard	OCI Standard, IBM Standard, Cloudflare R2 Standard, DigitalOcean Spaces Standard, Wasabi Hot, Backblaze B2
Unknown or changing access	Smart tier, where available	S3 Intelligent-Tiering	Autoclass	IBM Smart Tier, OCI Auto-Tiering
Infrequent but online access	Cool	S3 Standard-IA, S3 One Zone-IA	Nearline	OCI Infrequent Access, IBM Vault, Cloudflare R2 Infrequent Access, DigitalOcean Spaces Cold Storage
Rare but still online access	Cold	S3 Glacier Instant Retrieval	Coldline	IBM Cold Vault
Archive with restore delay	Archive	S3 Glacier Flexible Retrieval, S3 Glacier Deep Archive	Not the same: Google Archive is still online	OCI Archive
High-performance special class	No direct Azure access-tier equivalent	S3 Express One Zone	Rapid storage	Provider-specific performance products

That table is a mental map, not a pricing calculator. Always check the current pricing page before committing data, because minimum durations, request charges, retrieval fees, and regional prices can matter more than the storage price.

What the Names Mean Underneath

Storage tiers are usually a trade between four things:

• Storage price: colder classes cost less per GB-month.
• Access price: colder classes usually charge more to read, retrieve, or operate on data.
• Minimum duration: colder classes often bill as if the object stayed for 30, 90, 180, or 365 days.
• Access latency: online classes return data immediately; offline archive classes require a restore or rehydration step.

Azure states the ladder clearly: Hot has the highest storage cost and lowest access cost; Cool and Cold reduce storage cost but increase access and transaction costs; Archive is offline, lowest storage cost, and highest access cost^[2]. AWS frames S3 classes by use case, from Standard for frequent access, to Standard-IA for monthly access, to Glacier classes for archive and restore workflows^[3]. Google keeps every primary storage class online, even Archive, and makes the difference mostly price, availability, retrieval fees, and minimum storage duration^[4].

Minimum Duration and Access Behavior

Provider	Class or tier	Minimum duration	Online read?	Restore or rehydrate behavior
Azure Blob	Hot	None	Yes, milliseconds	None
Azure Blob	Cool	30 days	Yes, milliseconds	None
Azure Blob	Cold	90 days	Yes, milliseconds	None
Azure Blob	Archive	180 days	No	Rehydrate to Hot, Cool, or Cold; can take up to 15 hours[5]
AWS S3	Standard	None	Yes, milliseconds	None
AWS S3	Standard-IA	30 days	Yes, milliseconds	Retrieval fees apply[6]
AWS S3	One Zone-IA	30 days	Yes, milliseconds	Retrieval fees apply; stored in one Availability Zone[7]
AWS S3	Glacier Instant Retrieval	90 days	Yes, milliseconds	Retrieval fees apply[8]
AWS S3	Glacier Flexible Retrieval	90 days	No	Restore first; expedited, standard, or bulk retrieval ranges from minutes to 12 hours[9]
AWS S3	Glacier Deep Archive	180 days	No	Restore first; AWS summarizes average retrieval as 9 to 48 hours[10]
Google Cloud Storage	Standard	None	Yes, milliseconds	None
Google Cloud Storage	Nearline	30 days	Yes, milliseconds	Retrieval fees apply
Google Cloud Storage	Coldline	90 days	Yes, milliseconds	Retrieval fees apply
Google Cloud Storage	Archive	365 days	Yes, milliseconds	No offline restore; higher access/operation costs and 365-day minimum[11]
Oracle Object Storage	Standard	None	Yes	None
Oracle Object Storage	Infrequent Access	31 days	Yes	Retrieval fees apply
Oracle Object Storage	Archive	90 days	No	Restore to Standard for access; Oracle says first byte is available at most an hour after restore request[12]
Cloudflare R2	Standard	None	Yes	No egress bandwidth charge, but operations still bill
Cloudflare R2	Infrequent Access	30 days	Yes	Data retrieval processing fee applies, but egress bandwidth remains free[13]
DigitalOcean Spaces	Standard	None	Yes	Included storage and outbound transfer bundle
DigitalOcean Spaces	Cold Storage	30 days	Yes	Retrieval fee, early deletion/update cost, and 128 KiB minimum billing units[14]

Where They Overlap

Hot / Standard / Active Storage

Azure Hot, AWS S3 Standard, Google Standard, OCI Standard, IBM Standard, Cloudflare R2 Standard, Backblaze B2, and Wasabi Hot are all meant for data that can be read at any time without a restore step. This is where you put application assets, active backups, staging data, media currently in production, and datasets you expect to query often.

The difference is not the meaning. It is the billing model. AWS, Azure, and Google separate storage, requests, retrieval, and transfer in more detail. Wasabi publishes no separate egress or API request charges but applies a 90-day minimum storage duration and a minimum storage amount^[15]. Backblaze B2 positions itself as always-hot storage with no minimum storage duration and free egress up to 3x average monthly stored data^[16].

Monthly Access / Infrequent Access

Azure Cool, AWS S3 Standard-IA, Google Nearline, OCI Infrequent Access, IBM Vault, Cloudflare R2 Infrequent Access, and DigitalOcean Spaces Cold Storage all point at the same general idea: data you do not read often, but still want online when you do.

The common shape is a lower storage price, a 30-ish day minimum, and some cost when you read the data. The names differ: Azure calls it Cool, AWS calls it IA, Google calls it Nearline, Oracle says Infrequent Access, IBM says Vault, and Cloudflare says Infrequent Access. Treat them as cousins, not exact twins.

Quarterly or Rare Online Access

Azure Cold, AWS S3 Glacier Instant Retrieval, Google Coldline, and IBM Cold Vault are closer to each other in intention: data accessed at most a few times a year, but still available quickly. Azure Cold has millisecond access with a 90-day minimum. AWS Glacier Instant Retrieval has millisecond access with a 90-day minimum. Google Coldline has millisecond access with a 90-day minimum and retrieval charges^[17]. IBM Cold Vault is the IBM name for cold workloads where data is accessed every 90 days or less, with larger retrieval charges than Vault^[18].

Offline Archive

Azure Archive, AWS S3 Glacier Flexible Retrieval, AWS S3 Glacier Deep Archive, and Oracle Archive are true archive workflows. The object exists, but you cannot just read it like a hot object. You initiate a restore or rehydration operation first.

This is where restore time becomes a product requirement. Azure Archive can take up to 15 hours to rehydrate. AWS Glacier Flexible Retrieval can restore in minutes to hours depending on retrieval tier. AWS Glacier Deep Archive is designed for hours-long restores, with AWS summarizing average retrieval as 9 to 48 hours. Oracle Archive restores objects to Standard for access.

Google Archive does not belong in this exact group. It is the coldest Google Cloud Storage class, but it remains online with millisecond access. Its archive-like behavior is economic: a 365-day minimum duration plus higher data access and operation costs^[19].

Where They Differ

Difference	Why it matters
Archive can mean offline or online	Azure Archive and AWS Glacier Flexible/Deep Archive require restore. Google Archive does not.
Minimum duration is not always the same	Azure Archive is 180 days; AWS Deep Archive is 180 days; Google Archive is 365 days; Oracle Archive is 90 days.
Retrieval fees are separate from egress	A provider can have free egress but still charge retrieval processing or operations, such as R2 Infrequent Access.
Automatic tiering is implemented differently	S3 Intelligent-Tiering is a storage class. Google Autoclass is a bucket feature. Azure Smart tier is an access-tier automation feature where available. OCI Auto-Tiering moves between Standard and Infrequent Access.
Some providers do not expose a full class ladder	Backblaze B2 and Wasabi focus on simple hot storage economics rather than many storage classes. Lifecycle rules may delete or hide old versions, but that is not the same as a cold storage class.
One-zone classes are about resilience, not just price	S3 One Zone-IA and S3 Express One Zone trade multi-AZ resilience for cost, latency, or locality. Do not map them directly to Azure Cool or Google Nearline without considering failure-domain risk.

S3 vs Azure Tier Changes

Changing the class or tier of existing data is one place where Azure and S3 differ sharply.

Azure Blob has a Set Blob Tier operation. It sets the access tier on a blob, snapshot, or specific blob version by using the comp=tier request and an x-ms-access-tier value^[20]. Azure's versioning docs treat tiering as an operation you can apply to any version of a block blob, while version creation is described around write operations such as Put Blob, Put Block List, Copy Blob, and Set Blob Metadata^[21]. In practical terms, a tier change is not a copy-over-self operation.

Amazon S3 can also change an existing object's storage class without downloading it to your machine, but the mechanism depends on how you do it.

Change method	Azure Blob	AWS S3
Manual immediate change	Set Blob Tier changes the access tier on the blob or version.	Console, CLI, SDK, and API changes are copy-based. AWS documents changing an existing object's class with aws s3 cp object object --storage-class ..., and the CopyObject API accepts x-amz-storage-class[22].
Lifecycle change	Azure lifecycle management can move blobs between tiers by policy.	S3 Lifecycle Transition changes the current object version to the specified storage class; NoncurrentVersionTransition changes noncurrent versions[23].
Versioning impact	A tier change does not create a copied object version the way a write/copy does. Explicitly tiered versions can change how Azure bills shared blocks and full content length[24].	Manual copy-over-self creates a new copied object version when destination bucket versioning is enabled; AWS says CopyObject returns the version ID of the newly created copy[25]. Lifecycle transitions do not create a new current version; they transition the applicable version.
Cost shape	Tier-down is billed as a write operation; tier-up is billed as a read operation for Set Blob Tier[26].	Copy requests are charged based on destination storage class and Region; the request can also trigger source retrieval charges, and cross-Region copies can incur data transfer charges[27]. Lifecycle transitions have transition request costs and minimum-duration rules.

The safe S3 cleanup pattern depends on intent. If you want data to age into colder classes predictably, lifecycle rules are usually cleaner. If you need to change specific objects right now, manual copy-over-self works, but versioned buckets will keep the old version until lifecycle or explicit deletion removes it.

Lifecycle Policies: Azure vs S3 Ease

Both Azure Blob and Amazon S3 can automatically move data to colder storage by rule. The difference is how much the rule system asks you to think about.

Azure Blob lifecycle management is built around access-tier actions. A policy is a JSON document made of rules; each rule has conditions, actions, and filters. Conditions can use creation time, last modified time, and last accessed time if access tracking is enabled. Actions can move current versions, previous versions, or snapshots to cooler tiers, delete them, or move blobs back from Cool to Hot when they are accessed. Filters can include path prefixes and blob index tags^[28]. In the Azure portal, this is exposed under Data management => Lifecycle management, with a list view for common rules and a code view for JSON policies^[29].

Amazon S3 Lifecycle is broader. A bucket lifecycle configuration can have rules that transition objects to other storage classes, expire current versions, transition noncurrent versions, permanently delete noncurrent versions, remove expired delete markers, and abort incomplete multipart uploads. Rules can target all objects or filter by prefix, tags, and object size^[30]. You can create them in the S3 console under the bucket Management tab, or manage them with CLI, SDKs, or the REST API^[31].

Task	Azure Blob lifecycle	S3 Lifecycle	Easier in practice
Move logs or backups to a colder tier after N days	Add a rule for base blobs, set days since modified/created/accessed, choose Cool, Cold, or Archive.	Add a lifecycle rule, filter by prefix/tag/size, choose a storage-class transition and days after creation.	Tie for simple prefix-by-age rules. Azure reads closer to the access-tier model.
Use last-access behavior	Supported if last access tracking is enabled; lifecycle can also move blobs back from Cool to Hot when accessed[32].	S3 Lifecycle is mostly age/filter based. Use S3 Intelligent-Tiering when access pattern is unknown or changing.	Azure for explicit last-access rules; S3 for fully managed Intelligent-Tiering.
Manage old versions	Supports current versions, previous versions, and snapshots as lifecycle targets.	Very explicit current/noncurrent version actions, including transition and expiration of noncurrent versions[33].	S3 gives more version-specific knobs; Azure is simpler if you only need tier/delete policies.
Avoid tiny-object surprises	Fewer class-transition-specific size traps in the lifecycle model.	Objects smaller than 128 KB do not transition by default unless you override with size filters or headers; transition request costs can outweigh storage savings[34].	Azure is easier; S3 is more configurable but easier to misprice.
Rehydrate archived data automatically	Lifecycle policies cannot rehydrate Archive blobs to an online tier[35].	Lifecycle cannot transition Deep Archive back to warm classes; restore/copy workflows are needed for archived objects[36].	Neither. Archive restore is a separate workflow.
Know when it will happen	Policy changes can take up to 24 hours to go into effect and for first execution to start[37].	Lifecycle configuration propagation takes minutes, but actions are asynchronous and can complete later; billing usually changes when the rule is satisfied[38].	Neither is immediate. Use direct tier change/copy when you need right-now changes.

The short version: Azure is usually easier when your rule is "move these blobs by age, prefix, tag, or access time to Hot/Cool/Cold/Archive." S3 is more flexible when you need full object lifecycle management across current versions, noncurrent versions, delete markers, multipart cleanup, object-size filters, and multiple storage-class transitions. That flexibility is useful, but it also makes S3 lifecycle rules easier to misconfigure.

Automatic Tiering: Similar Goal, Different Mechanic

Provider	Feature	What it does	Watch out for
Azure Blob	Smart tier	Automatically moves data between Hot, Cool, and Cold based on usage patterns, where available[39].	It does not include Archive in the same online ladder. Confirm account and API support before designing around it.
AWS S3	Intelligent-Tiering	Keeps the storage class as Intelligent-Tiering while moving objects through Frequent, Infrequent, Archive Instant, and optional Archive/Deep Archive access tiers[40].	Monitoring/automation fees apply; objects under 128 KB are not auto-tiered. Optional archive tiers require restore.
Google Cloud Storage	Autoclass	Moves objects to colder storage classes when not accessed, and back to Standard when read[41].	Management and enablement charges can apply; manual storage class changes are ignored in Autoclass buckets.
Oracle Object Storage	Auto-Tiering	Moves objects larger than 1 MiB from Standard to Infrequent Access and back to Standard based on access patterns[42].	It is a Standard to Infrequent Access optimizer, not a deep archive policy.
IBM Cloud Object Storage	Smart Tier	Bills dynamic workloads by automatically classifying data into hot, cool, and cold tiers based on monthly usage patterns[43].	It is bucket-class pricing, not the same mechanics as S3 Intelligent-Tiering or Google Autoclass.

Azure-to-AWS-to-Google Mapping

If you use Azure...	Closest AWS S3 class	Closest Google class	Practical meaning
Hot	S3 Standard	Standard	Active data; lowest read friction; highest storage cost among general classes.
Cool	S3 Standard-IA	Nearline	Infrequent online data, roughly monthly access, 30-day minimum.
Cold	S3 Glacier Instant Retrieval	Coldline	Rare online data, roughly quarterly access, 90-day minimum.
Archive	S3 Glacier Flexible Retrieval or Deep Archive	No exact equivalent	Offline restore workflow. Google Archive is colder economically but still online.
Smart tier	S3 Intelligent-Tiering	Autoclass	Let the provider move data across warmer and colder classes based on access.

Same Intention, Different Name

If your thought is...	Choose this kind of class	Examples
"This data is active and users or apps read it constantly."	Hot/standard	Azure Hot, S3 Standard, GCS Standard, R2 Standard, IBM Standard, OCI Standard.
"I read this monthly, but it still needs to come back instantly."	Online infrequent access	Azure Cool, S3 Standard-IA, GCS Nearline, R2 Infrequent Access, OCI Infrequent Access, IBM Vault.
"I read this quarterly or rarely, but a restore delay would be painful."	Online cold	Azure Cold, S3 Glacier Instant Retrieval, GCS Coldline, IBM Cold Vault.
"This is compliance/archive data and waiting hours is acceptable."	Offline archive	Azure Archive, S3 Glacier Flexible Retrieval, S3 Glacier Deep Archive, OCI Archive.
"I do not know the access pattern yet."	Auto tiering	Azure Smart tier, S3 Intelligent-Tiering, Google Autoclass, IBM Smart Tier, OCI Auto-Tiering.
"I want simple predictable billing more than fine-grained classes."	Flat hot storage	Backblaze B2, Wasabi, many S3-compatible specialists.

Which One Should You Choose?

Choose Hot / Standard when users, apps, or jobs read the data regularly. If your object is a website asset, current media project, active backup, training dataset, or API payload, keep it online and warm.

Choose Cool / Standard-IA / Nearline when the data is still important but usually sits untouched for weeks. This is a good fit for backups, completed projects, and archives that are still likely to be restored within a month.

Choose Cold / Glacier Instant Retrieval / Coldline when you expect rare access but cannot tolerate a restore delay. These classes are good for quarterly compliance checks, disaster recovery material, and media that might need quick retrieval but not frequent reads.

Choose Archive / Glacier Flexible / Deep Archive / OCI Archive only when restore delay is acceptable. These are not CDN origins, app storage, or active backup targets. They are for data you preserve more than you use.

Choose automatic tiering when you genuinely do not know the access pattern. Do not use it as a substitute for understanding a known workflow. If half a bucket is active data and half is never-read backup data, separate prefixes or buckets plus lifecycle rules may be clearer and cheaper.

Migration Notes

When you move data between clouds, do not just map names. Map behavior.

• Moving Azure Cool to S3 Standard-IA usually preserves the monthly-access intent.
• Moving Azure Cold to S3 Glacier Instant Retrieval preserves fast retrieval better than moving it to Glacier Flexible Retrieval.
• Moving Azure Archive to Google Archive changes behavior: the data becomes online in Google, but with a 365-day minimum and retrieval/operation charges.
• Moving Google Archive to Azure Archive changes behavior the other direction: the data becomes offline until rehydrated.
• Moving AWS Deep Archive to Azure Archive keeps the offline-archive idea, but restore times and minimum durations differ.

Blober can write new Azure Blob uploads directly to Hot, Cool, Cold, or Archive in a workflow, and it can bulk-change existing Azure blobs between those tiers with Azure mutations. For S3-compatible destinations, the generic connector includes a storage-class field, so you can use provider-documented class names where the destination supports x-amz-storage-class.

The Traps to Check Before You Pick a Tier

• Minimum duration. Cool/IA/Nearline usually means 30 days. Cold/Coldline/Glacier Instant often means 90 days. Deep/archive classes can mean 180 or 365 days.
• Online vs offline. Azure Archive and S3 Glacier Flexible/Deep Archive require restore. Google Archive does not.
• Retrieval fees. Cold storage often charges when you read, copy, move, or rewrite data.
• Operation fees. Moving, rewriting, lifecycle transitions, and metadata-heavy workflows can cost more in colder classes.
• Minimum billable object size. S3 IA and Glacier Instant use 128 KB minimums; DigitalOcean Cold Storage also documents 128 KiB minimum billable object/read behavior.
• Auto-tiering eligibility. Small objects may not auto-tier. AWS Intelligent-Tiering and Google Autoclass both document 128 KB/KiB style thresholds for automatic transitions.
• Provider-specific semantics. Some providers set class at the bucket level, some per object, some through lifecycle only, and some avoid classes entirely.

Frequently Asked Questions

Is Azure Cool the same as S3 Standard-IA? Conceptually, yes: both target long-lived, infrequently accessed data that still needs millisecond access and has a 30-day minimum. Pricing, operations, and redundancy details differ.

Is Azure Cold the same as Google Coldline? They are close in intention: rare-access online storage with a 90-day minimum and fast reads. Do not confuse either with Azure Archive or S3 Glacier Deep Archive, which are restore-first archive workflows.

Is Google Archive the same as Azure Archive? No. Google Archive is still online with millisecond access. Azure Archive is offline and must be rehydrated before reading.

Which S3 class maps to Azure Archive? S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive are the closest behavioral matches because they are archived and require restore before normal access. S3 Glacier Instant Retrieval maps more closely to Azure Cold.

Does the cheapest storage class always save money? No. If you read the data more often than expected, retrieval, operation, early deletion, and restore costs can erase the storage savings. The cheapest class is usually only cheapest when the access pattern matches the class.

Related Guides

• How to Bulk Change Azure Blob Storage Access Tiers
• How to Transfer Files from AWS S3 to Azure Blob Storage
• Cloud Storage Ingress vs Egress Fees
• S3-Compatible Storage Providers: The Complete List

Get Blober

Pick the right storage class before you move the data. Blober transfers between S3, S3-compatible storage, Azure Blob, Google Drive, Dropbox, local storage, and more, and can write Azure Blob data straight to the tier you choose.

Download Blober at blober.io

Tags:

• blober
• azure
• azure blob storage
• aws s3
• google cloud storage
• storage tiers
• storage classes
• cost optimization

S3-Compatible Storage Providers: The Complete List (90+ Providers)

Jun 28, 2026

This is a practical list of well-known S3-compatible storage providers. If a service speaks the Amazon S3 API, the same tools, SDKs, and apps that work with AWS S3 usually work with it by changing two things: the endpoint URL and the access keys. That portability is why so many S3-compatible services exist, from global clouds to storage you run on your own hardware.

We have grouped them into six categories so the list stays usable. Each provider below links to a detailed entry with its endpoint format, regions, addressing style, and notes. Whatever S3-compatible store you are searching for, there is a good chance it is on this page.

Every endpoint format here comes from the provider's own documentation, cross-checked against current S3 client references and the per-provider sources in the category pages^[1]. The tables show endpoint hostnames for readability. In Blober, enter the full URL with https:// unless you are connecting to a local/self-hosted server that explicitly uses http://.

What S3-Compatible Means Here

S3-compatible means the service exposes the same HTTP API as Amazon S3, so an S3 client points at it by URL. It does not mean the service is run by Amazon, and it does not promise every advanced feature is identical. For the full explanation, see What S3-Compatible Really Means.

For common S3 operations, the custom endpoint is the portability layer. Once your tool can set that endpoint, the provider becomes much easier to swap.

How Blober Connects to Any of These

Blober has preconfigured connectors for the most common S3 services (Amazon S3, Wasabi, Cloudflare R2, Backblaze B2, DigitalOcean Spaces, and Rabata). For everything else on this list, Blober has a single generic S3-Compatible connector: you paste the endpoint URL and keys, and Blober can use the common browse, upload, download, copy, and delete operations when the provider implements them.

That connector covers both addressing styles (bucket in the subdomain, or bucket in the path), single-bucket or full-account access, a custom region, and a free-text storage class, so it reaches the long tail of providers, self-hosted servers, and local test setups. You point Blober at a source and a destination and it copies between them directly, without staging a full copy on your disk.

The Six Categories

Category	What is in it	Open the list
Cloud object storage	S3 services from large platform clouds (Alibaba, Tencent, Huawei, IBM, Oracle, Google, Yandex, and more)	Cloud providers
Object storage specialists	Independent clouds built only for object storage (Wasabi, Backblaze, Storj, IDrive e2, Cubbit, and more)	Specialists
Hosting and VPS object storage	S3 storage bundled with a hosting or VPS platform (DigitalOcean, Linode, Vultr, OVHcloud, Hetzner, Scaleway, and more)	Hosting and VPS
Self-hosted and open source	S3 servers you run yourself (MinIO, Ceph, SeaweedFS, Garage, and more)	Self-hosted
Enterprise and on-premises	Appliances and enterprise platforms (NetApp StorageGRID, Dell ECS, Cloudian, Pure FlashBlade, and more)	Enterprise
Decentralized and Web3	Object storage backed by decentralized networks (Storj, Filebase, 4everland, and more)	Decentralized

Master Index of S3-Compatible Providers

Every provider, alphabetical, with its endpoint format. The endpoint is the host you give your S3 client; the bucket name is then added either as a subdomain or in the path. Replace any bracketed value (<region>, <account>, <namespace>) with your own. A check in the last column means Blober ships a preconfigured connector; everything else uses the generic S3-Compatible connector. When you enter one of these in Blober, include the URL scheme, for example https://s3.example.com.

Provider	Endpoint format	Preconfigured
Alibaba Cloud OSS	oss-<region>.aliyuncs.com
Amazon S3	s3.<region>.amazonaws.com	Yes
Apache Ozone	self-hosted S3 Gateway
ArvanCloud	s3.<region>.arvanstorage.ir
Backblaze B2	s3.<region>.backblazeb2.com	Yes
Baidu AI Cloud BOS	s3.<region>.bcebos.com
BizflyCloud	<region>.ss.bfcplatform.vn
Ceph (RADOS Gateway)	self-hosted
China Mobile Ecloud EOS	eos-<city>-1.cmecloud.cn
China Telecom CTYun OOS	oos-<region>.ctyunapi.cn
Cloudflare R2	<account>.r2.cloudflarestorage.com	Yes
Cloudian HyperStore	appliance or software
cloudscale.ch	objects.<region>.cloudscale.ch
Contabo Object Storage	<region>.contabostorage.com
Cubbit DS3	s3.cubbit.eu
DataCore Swarm	on-premises
Dell ECS / ObjectScale	on-premises
DigitalOcean Spaces	<region>.digitaloceanspaces.com	Yes
DreamHost DreamObjects	objects-<region>.dream.io
Exaba	self-hosted
Exoscale SOS	sos-<zone>.exo.io
Fastly Object Storage	<region>.object.fastlystorage.app
FileLu S5	s5lu.com
Filebase	s3.filebase.io
4everland	endpoint.4everland.co
Fuga Cloud Object Store	core.fuga.cloud
Garage	self-hosted
Gcore Object Storage	regional endpoint
Google Cloud Storage	storage.googleapis.com
Hitachi Content Platform	on-premises
Hetzner Object Storage	<region>.your-objectstorage.com
Huawei Cloud OBS	obs.<region>.myhuaweicloud.com
IBM Cloud Object Storage	s3.<region>.cloud-object-storage.appdomain.cloud
IDrive e2	<region>.idrivee2-XX.com
Impossible Cloud	<region>.storage.impossibleapi.net
Infomaniak Public Cloud	s3.<region>.infomaniak.cloud
Intercolo Object Storage	de-fra.i3storage.com
IONOS Cloud S3	s3-<region>.ionoscloud.com
JD Cloud Object Storage	s3.<region>.jdcloud-oss.com
Kingsoft Cloud KS3	ks3-<region>.ksyuncloud.com
Leaseweb Object Storage	regional endpoint
Leviia	s3.leviia.com
Liara	storage.iran.liara.space
Linode / Akamai	<region>.linodeobjects.com
MEGA S4	s3.<region>.s4.mega.io
MinIO	self-hosted
NAVER Cloud Object Storage	<region>.object.ncloudstorage.com
NetApp StorageGRID	on-premises
NetApp ONTAP S3	on-premises
Netease NOS	nos-<region>.126.net
Nutanix Objects	on-premises
OpenIO	self-hosted
OpenStack Swift (s3api)	self-hosted
Open Telekom Cloud OBS	obs.<region>.otc.t-systems.com
Oracle Cloud OCI	<namespace>.compat.objectstorage.<region>.oci.customer-oci.com
Outscale OOS	oos.<region>.outscale.com
OVHcloud Object Storage	s3.<region>.io.cloud.ovh.net
Petabox	s3.<region>.petabox.io
Pure Storage FlashBlade	on-premises
Qiniu Kodo	s3-<region>.qiniucs.com
Quantum ActiveScale	on-premises
Rabata	s3.<region>.rabata.io	Yes
RackCorp	<region>.s3.rackcorp.com
Riak CS	self-hosted
Scality RING / ARTESCA	on-premises
Scaleway Object Storage	s3.<region>.scw.cloud
Seagate Lyve Cloud	s3.<region>.<account>.lyve.seagate.com
SeaweedFS	self-hosted
Selectel	s3.<region>.storage.selcloud.ru
Servercore	s3.<region>.storage.selcloud.ru
SberCloud OBS	obs.<region>.hc.sbercloud.ru
Spectra Logic BlackPearl	on-premises
Storadera	<region>.s3.storadera.com
Storj	gateway.storjshare.io
Synology C2	<region>.s3.synologyc2.net
Tebi	s3.tebi.io
Telnyx Cloud Storage	<region>.telnyxcloudstorage.com
Tencent Cloud COS	cos.<region>.myqcloud.com
Tigris	t3.storage.dev
UpCloud Object Storage	<region>.upcloudobjects.com
US3 (UCloud)	s3-<region>.ufileos.com
VAST Data	on-premises
Versity Gateway	self-hosted
VK Cloud Object Storage	hb.bizmrg.com
Vultr Object Storage	<region>.vultrobjects.com
Wasabi	s3.<region>.wasabisys.com	Yes
Yandex Object Storage	storage.yandexcloud.net
Zadara	<vsa-id>.zadarazios.com
Zata	idr01.zata.ai

This index is a starting point. Providers add regions and change hostnames over time, so always confirm the exact endpoint in your provider's console before you connect. The detailed group articles explain each provider's regions, addressing style (path or subdomain), and any quirks.

Subdomain vs Path: The One Setting That Trips People Up

S3 supports two ways of putting the bucket name into the request:

• Virtual-hosted (bucket in the subdomain): https://my-bucket.s3.example.com. This is the AWS default and what most hosted providers expect.
• Path-style (bucket in the path): https://s3.example.com/my-bucket. This is what MinIO, Ceph, and most self-hosted servers expect.

If browsing or uploads fail against a self-hosted server, switch to path-style. In Blober, you pick the style implicitly by which endpoint field you fill in. Everything else is the same.

Frequently Asked Questions

How many S3-compatible storage providers are there? There is no official registry. This page indexes more than ninety well-known hosted providers, hosting platforms, self-hosted servers, enterprise systems, and decentralized gateways across six categories.

Is Azure Blob Storage S3-compatible? Not natively. Azure Blob uses its own API. The concepts map across (a container is like a bucket, a blob like an object), but an S3 tool needs a translation layer to talk to it. See How to Transfer AWS S3 to Azure Blob for moving data between the two.

Can I move data between two different S3-compatible providers? Yes. Because they share the core API, moving between them is usually a straightforward copy. Blober connects to a source and a destination and transfers directly between them. Check provider-specific feature gaps if your workflow depends on object lock, lifecycle, metadata edge cases, or server-side copy.

Do I need a preconfigured connector, or does the generic one work? The generic S3-Compatible connector works with S3-compatible endpoints that support the common operations Blober uses. The preconfigured connectors (S3, Wasabi, R2, B2, Spaces, Rabata) just save you from pasting the endpoint.

Which S3-compatible provider is the cheapest? It depends on your access pattern. Flat-rate, zero-egress providers win for data you read often; the lowest per-GB storage rate wins for cold archives. The pricing model (egress fees and minimum storage duration) usually matters more than the headline storage rate.

Related Guides

• What S3-Compatible Really Means
• Azure Blob Tiers vs AWS S3 Storage Classes
• S3-Compatible Connector Setup
• How to Switch Wasabi to Backblaze B2
• How to Transfer AWS S3 to Azure Blob

Get Blober

Connect to S3-compatible stores on this list and move data between them directly, without filling your local disk. Blober handles S3, Wasabi, R2, B2, Spaces, Rabata, and generic S3 endpoints by URL, plus non-S3 services like Azure Blob, Dropbox, and Google Drive.

Download Blober at blober.io

Tags:

• blober
• object storage
• s3 compatible
• aws s3
• cloud storage
• s3 endpoint
• cloud migration

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 can usually work with it for common object operations by changing endpoint and credentials. 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 a device built for that plug can draw power without caring which utility generated the electricity. S3 compatibility is the plug shape for object storage. Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces all expose an S3-compatible endpoint, so tools such as aws s3, rclone, and desktop transfer apps can point at them by changing the endpoint and the keys.

Why It Matters When You Switch

The real value of S3 compatibility is that it makes providers more swappable. If your app reads and writes through the common S3 operations, 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^[source].
• s3proxy is an open-source proxy that presents an S3 API backed by Azure Blob and other stores^[source].
• VersityGW is an open-source S3 gateway with pluggable backends^[source].
• MinIO is S3-compatible storage that has been used to put an S3 API in front of other backends^[source].

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^[source].

Moving Between S3-Compatible Stores

Because the core API is shared, moving data between S3-compatible providers is usually straightforward. Blober connects to S3, Backblaze B2, Wasabi, Cloudflare R2, and DigitalOcean Spaces, and its generic S3 connector points at other S3-compatible endpoints by URL when they support the common operations Blober uses. 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.

There are dozens of well-known S3-compatible services, plus self-hosted servers and enterprise systems you can run yourself. For a practical roster with endpoints and setup, see The Complete List of S3-Compatible Storage Providers.

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.

Related Guides

• The Complete List of S3-Compatible Storage Providers
• How to Transfer AWS S3 to Azure Blob
• How to Switch Wasabi to Backblaze B2
• How to Move Azure Blob to Cloudflare R2

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

Tags:

• blober
• object storage
• s3 compatible
• aws s3
• cloud storage
• cloud migration

How to Migrate from DigitalOcean Spaces to AWS S3

May 11, 2026

Growing Out of DigitalOcean Spaces

DigitalOcean Spaces is a good starting point for object storage. It is simple, affordable ($5/month for 250 GB + 1 TB transfer), and S3-compatible. For small to mid-size projects, it does the job.

But as your storage needs grow, you run into limitations:

• Region constraints. Spaces are region-scoped. Each region only sees its own Spaces. Cross-region replication is not available.
• No storage tiers. Everything is stored at the same tier. There is no equivalent to S3's Glacier or Intelligent-Tiering for cost optimization.
• Limited ecosystem. AWS S3 integrates with hundreds of services: Lambda, CloudFront, Athena, Step Functions, SageMaker. DigitalOcean's ecosystem is smaller.
• Bandwidth limits. The included 1 TB transfer can be burned through quickly on busy applications.

When a project outgrows Spaces, AWS S3 is the most common destination.

Multi-Region Complexity

DigitalOcean runs Spaces across 7 regions: NYC3, SFO3, AMS3, SGP1, FRA1, SYD1, and BLR1. If you have Spaces in multiple regions, you need to handle each region separately.

Blober detects all your Spaces across all DigitalOcean regions automatically. When you connect your DigitalOcean account, Blober probes all 7 regions in parallel and presents a unified view of all your Spaces. You do not need to configure each region separately.

Tier Detection

DigitalOcean recently introduced cold storage tiers for Spaces. Blober detects whether a Space is using Standard or Cold storage and flags it accordingly. This helps you make informed decisions about which S3 storage class to target.

How to Transfer

Step 1: Connect DigitalOcean Spaces

Add DigitalOcean Spaces as a provider in Blober. You can use either:

• S3-compatible credentials (Access Key + Secret Key) for basic access
• Personal Access Token for richer bucket listing with project metadata

Blober discovers all your Spaces across all regions.

Step 2: Connect AWS S3

Add AWS S3 with your Access Key ID, Secret Access Key, and preferred region. Blober lists your S3 buckets.

Step 3: Map and Transfer

Create a workflow with DigitalOcean as the source and S3 as the destination. Browse your Spaces, select files or entire Spaces, and choose the target S3 bucket and storage class.

Options for the destination:

• Storage class: Standard, Intelligent-Tiering, Standard-IA, Glacier Instant Retrieval, Glacier, or Deep Archive
• Target bucket: Any existing S3 bucket (or create one in the AWS console first)

Step 4: Run

Blober handles the transfer with parallel multipart uploads on both sides. S3-to-S3-compatible transfers are efficient because both services speak the same protocol.

Cost Comparison

	DigitalOcean Spaces	AWS S3 Standard	AWS S3 Standard-IA
Storage (1 TB)	$5/mo (250 GB included) + $20/mo extra	$23/mo	$12.50/mo
Bandwidth (1 TB)	Included	$90/mo	$90/mo
PUT requests (100K)	$0.50	$0.50	$1.00

DigitalOcean is cheaper for simple, low-traffic use cases. S3 is more cost-effective at scale with its tiering options, especially if you use Intelligent-Tiering or Glacier for archival data.

Get Blober

One-time purchase. Transfer as much as you need.

Download Blober at blober.io

Tags:

• blober
• digitalocean
• digitalocean spaces
• aws s3
• cloud migration
• cloud transfer

How to Migrate Google Drive Files to AWS S3

May 11, 2026

When Google Drive Is Not Enough

Google Drive works great as a collaboration tool. Real-time editing, sharing links, 15 GB free storage. But when your data grows past a few hundred gigabytes, or when you need programmatic access, versioning policies, or storage tiering, Google Drive starts showing its limits.

AWS S3 is built for exactly those use cases. It handles petabytes, offers multiple storage classes, integrates with hundreds of AWS services, and gives you full API control. The gap between Google Drive and S3 is not about which is "better." It is about what each one is built for.

Moving from one to the other is where things get complicated.

The Google Drive Export Problem

Google Drive stores some files as native Google formats: Google Docs, Google Sheets, Google Slides. These are not actual files on disk. They are application states stored in Google's cloud. You cannot download a "Google Doc file" the way you download a PDF.

When you export from Google Drive (or use Google Takeout), these files get converted to their Microsoft Office equivalents: DOCX, XLSX, PPTX. But this conversion is often inconsistent with Takeout, and the folder structure gets flattened.

How Blober Handles Google Drive to S3

Blober connects to Google Drive via OAuth and to AWS S3 via access keys. It solves the two biggest pain points of this migration:

Automatic Google Docs Conversion

When Blober encounters a Google Doc, Sheet, or Slide, it automatically converts it to the corresponding Office format (DOCX, XLSX, PPTX) during transfer. This happens on the fly. You do not need to manually export anything.

The converted files land in your S3 bucket in a usable format that any application can read.

Folder Structure Preserved

Blober recreates your Google Drive folder hierarchy in S3. If you have Work/Projects/2025/Proposal.docx in Google Drive, it becomes Work/Projects/2025/Proposal.docx in your S3 bucket. No flat dumps, no reorganization needed.

Shared Files Included

Google Drive has a "Shared with me" section that is separate from your main drive. Blober shows this as a browsable folder, so you can include shared files in your migration if needed.

Steps

1. Connect Google Drive: Add Google Drive as a provider. Blober opens a browser window for OAuth authorization. Sign in and grant access.
2. Connect AWS S3: Add S3 with your Access Key ID, Secret Access Key, and region.
3. Create a workflow: Set Google Drive as source, S3 as destination. Browse your Drive, select files and folders.
4. Choose S3 options: Pick the storage class (Standard, Intelligent-Tiering, Standard-IA, Glacier, etc.) and target bucket.
5. Run: Blober transfers with progress tracking and auto-resume.

S3 Storage Class Selection

One advantage of moving to S3 is choosing the right storage class for your data:

Storage Class	Use Case	Cost (per TB/mo)
Standard	Frequently accessed files	~$23
Intelligent-Tiering	Unknown access patterns	~$23 (auto-optimizes)
Standard-IA	Infrequent access, fast retrieval	~$12.50
Glacier Instant	Archive with instant access	~$4
Glacier Deep Archive	Long-term cold storage	~$1

With Blober, you set the storage class when creating the workflow. All transferred files land on the tier you choose. If you want different tiers for different data, create multiple workflows.

Who Does This

• Startups growing out of Google Workspace who need infrastructure-grade storage
• Data teams that need to run analytics on files currently in Google Drive
• Companies consolidating storage to AWS for compliance or integration reasons
• Developers who want S3's API and event-driven architecture instead of Google Drive's sync model

Get Blober

One-time purchase. No per-GB fees, no subscription.

Download Blober at blober.io

Tags:

• blober
• google drive
• aws s3
• cloud migration
• cloud transfer
• google docs

How to Transfer Files from AWS S3 to Azure Blob Storage

May 11, 2026

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

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

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

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

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

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

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

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

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

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

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.

Related Guides

• Azure Blob Tiers vs AWS S3 Storage Classes for choosing the right destination tier
• How to Bulk Change Azure Blob Storage Access Tiers once your data is on Azure
• How to Move Azure Blob to Cloudflare R2 for moving off Azure later
• Provider setup: AWS S3 and Azure Blob

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

Tags:

• blober
• aws s3
• azure blob storage
• cloud migration
• enterprise
• cloud transfer

Stop Paying Rent to Move Your Own Files

Mar 9, 2026

The Trap

You uploaded 2 TB of photos, videos, and backups to the cloud. Life was good - until you wanted to move them somewhere else.

Suddenly, you're hit with egress fees, per-GB migration charges, and the realization that your cloud provider has been counting on you never leaving. It's your data. But moving it costs real money - every single time.

AWS charges ~$0.09/GB for egress. That's $184 just to download 2 TB of your own files. Want to use a SaaS migration tool? That's another $10-20/month, with transfer caps. Prefer the open-source CLI route? Clear your afternoon - you'll need it for YAML configs, credential files, and provider-specific quirks.

---

The Math

Let's talk real numbers. Over three years, here's what you'll pay using common approaches:

Approach	3-Year Cost	Catch
SaaS Migration Tool	~$360	Monthly sub + data caps
Per-GB Service	~$720+	$0.03/GB, billed every transfer
DIY with CLI	40+ hours	Config per provider, no UI, breaks silently
Blober	One payment	Unlimited transfers. Forever.

The subscription model is designed to extract value from you month after month. The per-GB model punishes you for having more data. The CLI path trades money for your time.

Blober breaks the cycle. Pay once. Transfer as much as you want, as many times as you want. No meter running. No renewal emails. No "upgrade to unlock more."

---

The Escape

Blober is a desktop app - not a SaaS, not a CLI tool, not a cloud service. It runs on your Mac, Windows, or Linux machine and connects directly to your cloud providers:

• AWS S3 - buckets and objects, any region
• Azure Blob Storage - containers and blobs
• Google Drive - files and folders, including shared drives
• GoPro Cloud - back up your action footage locally or to any cloud
• Backblaze B2 - the affordable S3 alternative
• Dropbox - personal and business accounts
• Cloudflare R2 - zero-egress object storage
• Wasabi - hot storage without the cold fees
• DigitalOcean Spaces - all regions, auto-detected
• Local Disk - any folder on your machine

Your files never touch a middleman server. Blober streams directly between your machine and the provider APIs. Browse your cloud storage visually, select what you want, pick a destination - done.

If a transfer gets interrupted (bad WiFi, laptop closed, provider hiccup), Blober picks up where it left off. No re-uploading. No duplicate files.

---

The Move

Here's what switching to Blober actually looks like:

Before: You're juggling browser tabs, CLI sessions, and a spreadsheet tracking which files went where. A SaaS tool emails you that you've hit your 1.2 TB monthly cap. You Google "rclone config azure" for the third time.

After: You open Blober. Connect your accounts. Drag from source to destination. Walk away. It just works.

No internet needed for local-to-local moves. No data ever leaves your machine unless you're sending it to a cloud provider you chose.

---

Who Is This For?

• Photographers & videographers moving terabytes of footage from GoPro Cloud or Google Drive to cheaper archival storage
• Developers & DevOps engineers migrating between S3-compatible providers without writing scripts
• Small businesses consolidating cloud storage without paying an enterprise migration service
• Privacy-conscious users who want their files transferred directly, not through a third-party cloud
• Anyone tired of paying monthly fees to tools that move files you already own

---

Get Blober

Your data. Your machine. Your rules.

One payment. Unlimited transfers. No expiration.

Download Blober => blober.io

Tags:

• blober
• cloud migration
• vendor lock-in
• egress fees
• object storage
• file transfer
• cost comparison
• aws s3
• azure blob
• google drive
• backblaze b2
• dropbox

What Is Blober? Cloud File Transfer Made Simple

Feb 23, 2026

The Problem

Transferring files between cloud providers today means monthly subscriptions, surprise transfer fees, and wrestling with CLI config files. Most tools are either expensive SaaS platforms or developer-only terminals with steep learning curves.

---

The Solution

Blober is a desktop app that connects all your cloud storage in one place. AWS S3, Azure Blob Storage, Google Drive, GoPro Cloud, Backblaze B2, Wasabi, local disk, and more - all supported out of the box. No CLI. No config files. Just a beautiful, intuitive interface.

---

The Value

Buy once, transfer forever. No subscriptions. No transfer fees. Blober runs natively on Mac, Windows, and Linux - and it works offline too.

---

Get Blober

Stop renting your tools. Download Blober =>

Tags:

• blober
• cloud migration
• object storage
• file transfer
• gopro cloud
• aws s3
• azure blob
• google drive
• backblaze b2

Back Up Your GoPro Cloud to Backblaze B2, AWS S3, or Local Storage

Feb 15, 2026

The Problem

GoPro's cloud storage (GoPro Plus / GoPro Premium) offers unlimited storage for GoPro camera media. It's a great perk, until you want your footage somewhere else.

The reality for most GoPro users:

• Painfully limited batch download. GoPro's web portal caps batch downloads at 25 files at a time, bundled into a ZIP. Large batches frequently fail or time out, and metadata like GPS data may be stripped during compression
• No third-party tool support. rclone, MultCloud, Flexify, and every other transfer tool do not support GoPro Cloud
• Subscription dependency. Cancel GoPro Plus and your cloud access disappears. Your footage remains hostage to a recurring charge
• No "Download All" option. If you have hundreds or thousands of files, you're stuck doing dozens of 25-file batch downloads manually, hoping none fail

GoPro community forums are filled with users asking the same question: "How do I download all my GoPro Cloud content at once?" The practical answer is: not without hours of manual work and frequent failures.

Blober changes that.

---

Blober: The Only Tool That Connects to GoPro Cloud

Blober is the only desktop application that integrates with GoPro's cloud storage. No other migration tool, free or paid, supports GoPro Cloud as a source or destination.

With Blober, you can:

• Browse all your GoPro Cloud media: photos and videos, organized by date, camera, and type
• Download everything at once to your local drive, NAS, or external HDD
• Transfer directly to Backblaze B2, AWS S3, Wasabi, Cloudflare R2, Azure Blob Storage, or DigitalOcean Spaces
• Use metadata-based path templates to auto-organize files (e.g., by camera model, capture date, resolution)
• Resume interrupted transfers, with no need to start over if your connection drops

---

Why Back Up GoPro Cloud?

1. Subscription Lock-In

GoPro Plus (now GoPro Premium) costs ~$59.99/year. As long as you pay, your footage stays accessible. The moment you cancel, your cloud media goes offline. For years of footage, that's a dangerous bet on a single subscription.

2. No Redundancy

GoPro Cloud is your only copy in the cloud. There is no built-in backup, no versioning, no geographic replication. If GoPro ever changes their terms, shuts down the service, or experiences data loss, your footage is gone.

3. Cost Optimization

Long-term archival storage costs a fraction of ongoing subscriptions:

Storage Option	Cost for 1 TB/year	Egress Fees
GoPro Plus	~$59.99/year (ongoing)	N/A (limited downloads)
Backblaze B2	~$83/year ($6.95/TB/mo)	Free up to 3x stored
Wasabi	~$83.88/year ($6.99/TB/mo)	Free
AWS S3 (Standard)	~$276/year	$0.09/GB
Local NAS	One-time HDD cost	Free

For most GoPro users, Backblaze B2 or Wasabi combined with a Blober one-time license is the most cost-effective long-term strategy.

4. You Own Your Footage

Your GoPro footage is yours. Keeping it locked behind a single provider's subscription model is not ownership. It is rental. Backing it up to storage you control gives you true data sovereignty.

---

How It Works

Step 1: Connect GoPro Cloud in Blober

1. Open Blober and create a new workflow
2. Select GoPro as the source
3. Click Open GoPro Login - a browser window opens
4. Sign in with your GoPro account
5. Blober captures your session automatically

Step 2: Choose Your Destination

Select where you want your footage to go:

• Local disk: your SSD, HDD, NAS, or external drive
• Backblaze B2: affordable, S3-compatible, free egress
• AWS S3: enterprise-grade, global availability
• Wasabi: hot storage with no egress fees
• Cloudflare R2: zero egress, fast edge delivery
• Any other Blober-supported provider

Step 3: Configure Path Templates (Optional)

Use Blober's metadata-based path templates to auto-organize files as they transfer:

/{camera_model}/{capture_date}/{filename}

This turns a flat GoPro dump into a clean archive:

/HERO13 Black/2026-01-23/GX015742.MP4
/HERO13 Black/2026-01-23/gorp0001.JPG
/HERO12 Black/2025-12-15/GX014521.MP4

Step 4: Run and Monitor

Click Start and Blober handles the rest:

• Parallel downloads for maximum throughput
• Real-time progress tracking
• Automatic resume on interruption
• Full task history logged for every file

---

Supported GoPro Media

Type	Extensions
Videos	.mp4, .mov, .avi, .mkv
Photos	.jpg, .png, .raw, .dng

Blober downloads the highest available quality, with no compression and no re-encoding.

---

Metadata Available

Each GoPro file includes rich metadata that Blober can use for organization:

Field	Example
Camera model	HERO13 Black
Capture date	2026-01-23
Resolution	5312 × 2988
File size	142.5 MB
Duration	0:32 (videos)

---

Frequently Asked Questions

Can I upload to GoPro Cloud with Blober? Yes. Blober supports uploads to GoPro Cloud (up to 5 TB per file) with multipart upload and progress tracking.

Does Blober store my GoPro credentials? No. Blober uses a browser-based login flow. Your session lasts approximately 20 hours, after which Blober prompts you to sign in again. Credentials are never stored or transmitted to any server.

Can rclone, MultCloud, or Flexify do this? No. As of February 2026, Blober is the only transfer tool that supports GoPro Cloud. rclone (70+ providers), MultCloud (30+ services), and Flexify (~25 clouds) do not include GoPro Cloud integration.

What if my transfer is interrupted? Blober saves progress and resumes from the last successfully transferred file. No need to re-download everything.

---

Take Control of Your GoPro Footage

Your footage is irreplaceable: years of adventures, events, and memories sitting in a cloud you can only access through a subscription. Blober gives you a way out: move it all to storage you own and control, in the highest quality, organized exactly how you want.

Get started with Blober =>

Tags:

• blober
• gopro
• gopro cloud
• backup
• backblaze b2
• aws s3
• local storage
• cloud migration
• media archive