# Any tips on avoiding high AWS S3 cost when storing Zarr's with lots of objects

**URL:** <https://discourse.pangeo.io/t/any-tips-on-avoiding-high-aws-s3-cost-when-storing-zarrs-with-lots-of-objects/1977>\
**Category:** Data\
**Created:** [November 30, 2021, 10:24pm UTC](https://discourse.pangeo.io/t/any-tips-on-avoiding-high-aws-s3-cost-when-storing-zarrs-with-lots-of-objects/1977 "2021-11-30T22:24:47Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![rabernat](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/rabernat/32/22_2.png) [@rabernat](https://discourse.pangeo.io/u/rabernat)\
**Post date:** [November 28, 2023, 3:31pm UTC](https://discourse.pangeo.io/t/any-tips-on-avoiding-high-aws-s3-cost-when-storing-zarrs-with-lots-of-objects/1977/13 "2023-11-28T15:31:29Z")

</div>

> [@weiji14](#):
>
> Or are there other methods or file formats that are worth looking at to reduce the file/object count?

If you have existing Zarr data you want to expose for read-only use, and you’d like to reduce the file / object count, a great option (which does not require sharding) is to put it all inside a zip file. You can read from this zip file concurrently with no performance penalty.

If you want to continue writing to the store, the sharded Zarr V3 format would probably be a better fit. Support is not fully implemented yet in Zarr python, but it should be here soon.

---

_[View the full topic](https://discourse.pangeo.io/t/any-tips-on-avoiding-high-aws-s3-cost-when-storing-zarrs-with-lots-of-objects/1977)._