# Migrate from gz compression to zstd for backups

**URL:** https://meta.discourse.org/t/migrate-from-gz-compression-to-zstd-for-backups/309984
**Category:** Feature
**Tags:** pr-welcome
**Created:** [May 30, 2024, 3:10pm UTC](https://meta.discourse.org/t/migrate-from-gz-compression-to-zstd-for-backups/309984 "2024-05-30T15:10:53Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [February 3, 2025, 11:16am UTC](https://meta.discourse.org/t/migrate-from-gz-compression-to-zstd-for-backups/309984/3 "2025-02-03T11:16:13Z")

</div>

> [@Isambard](#):
>
> this could be a big saver in disk and transfer

I’d be curious to know the average weight ratio between compressible and already compressed data in a Discourse backup\[1\], and how much data (in %) would be saved using zstd.

It’s not the same feature request, but it’s also about backup compression so I’m crossposting this:

> [@Reduce local disk space needs by not (redundantly) gzipping backups](https://meta.discourse.org/t/reduce-local-disk-space-needs-by-not-redundantly-gzipping-backups/245763/6):
>
> Development of that feature is currently paused and it isn’t on our current roadmap. I hope we will get to it in 2024.

> [@Reduce local disk space needs by not (redundantly) gzipping backups](https://meta.discourse.org/t/reduce-local-disk-space-needs-by-not-redundantly-gzipping-backups/245763/1):
>
> In my case every upload file is already compressed: gz, gzip, gif, jpeg, png, zip. So the final gzipping gains only 1% of size.

I wouldn’t be surprised if the percentage was about the same on all my Discourse forums.

* * *

1. Of course, some forums rely very much on image uploads, and some won’t even allow file uploads

---

_[View the full topic](https://meta.discourse.org/t/migrate-from-gz-compression-to-zstd-for-backups/309984)._