What is SeaweedFS?
SeaweedFS is an Apache-licensed distributed storage system for object storage, file access and lakehouse tables. One weed binary can expose an S3 endpoint, a filer-backed directory tree, WebDAV, SFTP, FUSE mounts and built-in catalogs for Apache Iceberg or Lance while storing the underlying data in the same cluster.
Read the full overview
The architecture separates placement, content and metadata. Master servers track volumes rather than individual files and stay out of the read path. Volume servers store blobs in append-only volume files with a compact in-memory index. Filer servers add directories and file semantics using a metadata database chosen by the operator, then expose the higher-level protocols and APIs.
SeaweedFS is optimized for large populations of small files while supporting multi-terabyte objects through chunking. Capacity grows by adding volume servers; filer and S3 gateways are stateless and can scale behind a load balancer. Production operation still requires deliberate choices for replication, metadata durability, authentication, maintenance and disaster recovery.
Distributed S3, file and lakehouse storage designed for billions of objects
Key capabilities
- S3-compatible object storageServe bucket, object, IAM, STS and S3 Tables APIs for AWS SDKs, CLI tools, rclone, restic, Spark and Trino, including versioning, Object Lock, lifecycle rules, multipart uploads and presigned URLs.
- File and application protocolsExpose the same data through HTTP, FUSE, WebDAV, SFTP, HDFS and TUS resumable uploads, with a CSI driver and operator available for Kubernetes environments.
- Small-file-oriented storagePack blobs into append-only volume files and locate content through a cacheable volume identifier, avoiding a separate inode and metadata file for every small object.
- Replication, erasure coding and tieringReplicate hot data across racks or data centers, apply erasure coding to warm volumes, place data on different disk types and move or cache content across supported cloud object stores.
- Iceberg and Lance lakehouse tablesUse S3 Table Buckets, an Iceberg REST catalog or Lance namespace with maintenance tasks for compaction, snapshot expiration, orphan cleanup and manifest rewriting.
- Operational interfacesDeploy with one binary, Docker Compose or Helm, then use the Admin UI, Prometheus metrics,
weed shelland maintenance workers for balancing, vacuuming, repair and lifecycle work.
Where SeaweedFS fits
Self-hosted S3 storage
Run a single-node gateway or a multi-node object platform with named credentials, policies, quotas, audit logging and server-side encryption. Test the precise AWS operations and SDK behaviors required by each application.
Distributed file services
Present filer data through FUSE, WebDAV, SFTP, HDFS or HTTP while keeping directory metadata in LevelDB, PostgreSQL, MySQL, Cassandra, Redis, FoundationDB or another documented backend.
Lakehouse infrastructure
Store Iceberg or Lance tables beside regular objects and connect query engines through the built-in catalog. Validate concurrent commits, maintenance policies and credential scope before consolidating an existing data platform.
Cloud cache and tiered storage
Cache remote buckets locally, warm selected content, write back asynchronously or move whole warm volumes to cloud storage. Recovery testing must include both local metadata and the remote object layout.
Positioning and limitations
SeaweedFS fits teams that need self-hosted S3 and file access, expect very large object counts, or want storage and lakehouse tables in one operational stack. Its simple placement model and stateless gateways differ from systems that rebalance data automatically across rigid erasure sets.
The project publishes single-machine benchmark figures for 1 KB objects and mixed S3 traffic, but labels the laptop results unscientific. Hardware, replication, metadata backend, object distribution, durability settings and network topology can change performance materially. Benchmark with the actual object sizes, concurrency and failure conditions you expect.
SeaweedFS is not a managed storage service. Operators own capacity planning, metadata HA, upgrades, monitoring, balancing, repair and restore procedures. Teams wanting vendor-backed features can evaluate the separate enterprise edition, while the community project remains Apache 2.0 licensed.
Small files are expensive for many distributed file systems because each one carries independent filesystem metadata and creates random I/O. SeaweedFS groups blobs into volumes, keeps a compact index and lets clients reach volume servers directly after resolving the placement. The master therefore tracks thousands of volumes instead of billions of files.
The same data can serve object, file and table workloads, reducing the number of storage systems a small platform team must deploy. This consolidation is valuable only when the chosen interfaces meet application semantics and the team can operate the shared failure domain.
The security boundary requires care. SeaweedFS documents master, volume and raw filer components as services for a trusted network. Exposing internal ports to untrusted clients is unsafe unless the appropriate authentication, JWT, TLS or mTLS controls are enabled. Keep public traffic on authenticated S3 or deliberately secured gateways, rotate credentials, test Object Lock behavior and restore both filer metadata and volume data.
“Distributed S3, file and lakehouse storage designed for billions of objects”
Technical details
- Access
- Self-hosted
- Source model
- Open source
- License
- Verify license
- Founded
- 2014
- Data location
- Self-hosted; operator chooses data placement and replication topology
- Pricing model
- Open source
- API
- Available
- API documentation
- Read API documentation ↗
- Version reference
- 4.48 ↗
- Source checked
- October 14, 2026
- Website
- seaweedfs.com ↗
- GitHub
- Source repository ↗
What to verify
Profile audiences: Developers, DevOps Engineers, System Administrators, IT Teams.
- Confirm current features, licensing and support terms.
- Validate deployment, data location and access control.
- Test integrations, exports and recovery workflows.
Reviews of SeaweedFS
No published reviews yet.
Loading review form…
