Short answer: Object storage stores data as objects rather than as files in a folder tree or blocks on a disk. Each object consists of the data itself, metadata that describes it and a unique key, and it’s read and written through an HTTP-based API. The de facto standard for that API is Amazon’s S3 API; “S3-compatible” storage means object storage that works with the same tools.
How Does Object Storage Work?
The S3 model has three core concepts:
- Bucket: the container that holds objects. Access permissions, versioning and lifecycle rules are usually set at bucket level.
- Object: the file itself plus the metadata that describes it. Metadata includes standard fields such as last-modified date and
Content-Type, plus custom fields you add. - Key: the object’s unique name within the bucket, e.g.
photos/2026/cat.jpg. The “/” isn’t a real folder; the structure is flat, and interfaces just display it like folders.
An object is addressed by endpoint + bucket + key: https://bucket-name.s3.region.amazonaws.com/photos/cat.jpg. Uploading uses a PUT request, reading a GET, deleting a DELETE and listing a GET; requests are signed with an access key. Buckets and objects are private by default; public read access is only possible when explicitly granted.
One important difference: objects aren’t modified piece by piece. Changing even a single byte of a file means re-uploading the whole object. In Amazon S3 a single PUT request can upload up to 5 GB; larger objects are sent with multipart upload.
Object vs File vs Block Storage
| Feature | Object storage | File storage | Block storage |
|---|---|---|---|
| Data structure | Objects in a flat structure inside buckets | Folder and file tree | Raw disk made of fixed-size blocks |
| Access | API over HTTP(S) (S3) | Network file protocols such as NFS and SMB | Attached to the OS as a disk (iSCSI, Fibre Channel, virtual disk) |
| Changes | The object is rewritten as a whole | Part of a file can be changed | Individual blocks can be changed |
| Scaling | Very high; no practical limit on objects per bucket | Moderate; management gets harder with huge file counts | Limited by disk/volume size |
| Best for | Backups, archives, media, static files, logs, data lakes | Shared folders, team file sharing | Databases, virtual machine disks, operating systems |
In short, you don’t run a database or an operating system on object storage; those need the server’s own disk (block storage). Object storage shines for data that grows a lot and rarely changes.
What Does S3-Compatible Storage Mean?
Amazon S3 launched in 2006, and its API gradually became the common language of object storage. Today many cloud providers and open-source projects (e.g. MinIO, Ceph RADOS Gateway, Garage) work with the S3 API. That means you can use the same backup software, library or command-line tool with different providers just by changing the endpoint address:
# Upload a file to an S3-compatible provider with the AWS CLI
aws s3 cp backup.tar.gz s3://backup-bucket/2026/ --endpoint-url https://s3.provider.com
# List the bucket contents
aws s3 ls s3://backup-bucket/2026/ --endpoint-url https://s3.provider.comCompatibility isn’t always 100%; if you’ll use features such as versioning, Object Lock or lifecycle rules, check that the provider supports them. For Amazon S3 itself, see what is AWS S3.
Key Features of Object Storage
- Versioning: each new upload under the same key is kept as a separate version, so an object that was deleted or overwritten by mistake can be restored.
- Object Lock: prevents objects from being deleted or changed for a set period (WORM). Used for backups protected against ransomware.
- Lifecycle rules: automatically move old objects to a cheaper storage class or delete them after a set time.
- Storage classes: a standard class for frequently accessed data, and cheaper classes with slower or paid retrieval for infrequently accessed data and archives.
- Consistency: Amazon S3 provides strong read-after-write consistency for writes and deletes in all Regions; a read right after a successful upload returns the new data.
Use Cases
- Off-server backups: the most common use is keeping server and database backups in another location. The “one copy off-site” step of the 3-2-1 rule usually lives here. More: server backup strategies.
- Static files and media: website images, videos and downloadable files; used with a CDN it reduces server load. See best CDN services.
- User uploads: applications that write user files to object storage instead of the server disk are easier to scale.
- Logs and data lakes: large volumes of log and analytics data are stored cheaply and read directly by analytics tools.
How Is Cost Calculated?
With object storage you usually pay for what you use. Three items make up the bill: the amount of data stored (GB/month), the number of requests (PUT, GET, LIST) and data transferred out (egress). For frequently downloaded files, egress can exceed the storage cost; always factor it in when comparing providers.
Frequently Asked Questions
Can object storage be mounted like a disk?
Tools such as rclone or s3fs can mount it like a folder, but every operation is an API request behind the scenes. It isn’t suitable for databases or frequently changing files.
Can I run my own object storage?
Yes. Open-source software such as MinIO, Ceph or Garage lets you build S3-compatible storage on your own servers. Check the licence and community edition terms before installing, and plan for multiple disks and servers for durability.
Does object storage replace backups?
It’s a backup target, but not a backup strategy on its own. Without versioning and Object Lock, data that’s deleted or corrupted is gone from every copy.
Conclusion
Object storage is a scalable, economical solution for growing, rarely changing data such as backups, media and logs, and the S3 API makes it portable between providers. Your application and database, however, should run on a server with fast block storage. For that, see our VDS server and dedicated server options.
Categories
-
CentOS 7 guides
-
cPanel 20 guides
-
CyberPanel 18 guides
-
Operating Systems 81 guides
-
Juniper Networks 18 guides
-
Control Panels 50 guides
-
Linux 17 guides
-
MySQL 29 guides
-
Network 95 guides
-
Plesk Panel 12 guides
-
Virtual Servers 273 guides
-
SEO 3 guides
-
Cyber Security 8 guides
-
Technology 162 guides
-
VMware 36 guides
-
WordPress 20 guides
-
Artificial Intelligence 22 guides