Feature suggestion: Compress/encrypt by file extension

[» by]

I'm having some difficulty organizing my local storage, cloud storage, and Syncovery profiles. Part of the difficulty is that Syncovery profiles are all-or-nothing when it comes to enabling/disabling/configuring both compression and encryption.

For example, I don't want to compress or encrypt my huge system image files, because they are already compressed and encrypted, and doing it in Syncovery is a huge waste of time and resources.

On the other hand, I like to encrypt large videos, but trying to compress them would be a pointless waste.

It would be fantastic to be able to choose which file types (extensions) to compress and/or encrypt in a single Syncovery profile, and which settings to apply (e.g. compression level). Without this capability, I find myself organizing my local storage and Syncovery profiles not by what I'm backing up to Google Drive, but rather by how compression/encryption needs to be handled by Syncovery.

Thanks for reading!

[» by]

If I'm missing something, I'd appreciate someone pointing it out. Was this a ridiculous suggestion? Is my entire thought process on this broken?

[spoidyjan]

Great Suggestion.
Flexibility based on file extensions would make Syncovery much more efficient. For example, when handling large image files, I personally use an image compressor tool to optimize them beforehand. It’s always helpful to have tailored solutions for different file types to save time and resources.

[calcu007]

You use 1 option too, Encrytion or compression y you want.

[» by]

You use 1 option too, Encrytion or compression y you want.

I have no idea what you're trying to say.

[calcu007]

I mean you can use 1 option only encrypt or compress.

[» by]

Right, but that doesn't address my issue. Thanks.

[IMTheNachoMan]

I have a hack solution.

Create multiple profiles with their own include/exclude masks.

One profile does everything but system image files and does encrypt. One profile that does just system image files and does not encrypt.

Hacky but it should work?

[» by]

Thanks. That's pretty much what I'm currently doing, except that I need more than two profiles because of having several "categories" of files (based on desired to encrypt and/or compress).