Size optimized file format/extension

[TEcHNOpls]

Hi,

since I'm creating a lot of works (~100 this year and counting), and each occupies a lot of space (~0.5-1GB each) it would be nice to have some way of size optimized file format (with lossless compression, and all that stuff).

Preferably with some tool to convert all the files into the more compact format, w/o need to open/save/close each of theme sparely. Like point to directories/drives and recursively convert all files.

[fde101]

In the interim, try periodically doing a "Save As" to save a new copy of the file, to see if it is smaller.  Due to the nature of how the Affinity file format is handled, that can sometimes result in a smaller file.

 

You might also consider leveraging filesystem-level compression:

Mac - https://developercoach.com/file-system-compression-in-hfs-space-savings-and-performance-gain/

Windoze - https://www.howtogeek.com/133264/how-to-use-ntfs-compression-and-when-you-might-want-to/

[TEcHNOpls]

Thanks, that might be a solution, if I keep my files locally, may be of an issue when moving them to NAS. Also, might want to have a better separation fo stareges, since the 'work' drive cannot be a compressed one. But, generally, this is something to think about.

[fde101]

5 hours ago, TEcHNOpls said:

when moving them to NAS

Be aware that the Affinity apps do not play nice with NAS or other remote storage.  I wouldn't expect it to be an issue with linked image files and such but the actual Affinity documents should be kept local while working on them.  Using NAS / DropBox / etc. to transfer files which are not actively open in the applications should be fine, but before someone tries to open them, they should make a local copy, then close that copy and copy it back to the remote storage later on.

Serif has indicated this is something they are working to improve, but currently trying to work with documents directly which are on remote storage can lead to strange behaviors and even data loss or corruption.

 

5 hours ago, TEcHNOpls said:

since the 'work' drive cannot be a compressed one

Why not?