# Image Compression Methods for Uploads

**URL:** <https://community.nocodb.com/t/image-compression-methods-for-uploads/1237>\
**Category:** APIs\
**Created:** [June 25, 2024, 6:07pm UTC](https://community.nocodb.com/t/image-compression-methods-for-uploads/1237 "2024-06-25T18:07:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Benjifrank](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.nocodb.com/benjifrank/32/485_2.png) [@Benjifrank](https://community.nocodb.com/u/Benjifrank)\
**Post date:** [June 25, 2024, 6:07pm UTC](https://community.nocodb.com/t/image-compression-methods-for-uploads/1237/1 "2024-06-25T18:07:50Z")

</div>

## What

Compression methods for uploaded files.

## Why

-People upload needlessly large files that take a long tim to upload and cost us more money  
-This is especially true with PNG screenshots from macs … they can be compressed to 15% normal size  
-We’re using Backblaze for file attachment storage and looking for a method that compresses after upload if a file is large … we also work to instruct team members to compress before upload but need a method to check files afterwards.  
-Would be cool to have a Nocodb plugin that could handle somehting like this.

---

<div class="post-metadata">

**Author:** ![dstala](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@dstala](https://community.nocodb.com/u/dstala)\
**Post date:** [June 26, 2024, 1:25am UTC](https://community.nocodb.com/t/image-compression-methods-for-uploads/1237/2 "2024-06-26T01:25:21Z")

</div>

If you are using forms to upload images, NocoDB supports size based validations over attachment field. [Form | NocoDB](https://docs.nocodb.com/views/view-types/form/#field-validations-)

Created an issue to track this [🔦 Feature: Image Compression Methods for Uploads · Issue #8865 · nocodb/nocodb · GitHub](https://github.com/nocodb/nocodb/issues/8865)

I still feel though, this could be something that’s more in the blackblaze scope.

Another workaround for now could be - you run a script periodically to fetch records inserted recently (once in a week), retrieve their file size & if found above bounds - you can compress and upload.