but it'd be very interested to here about techniques on this because I have a lot of space eaten up by timelapses myself
When you store multiple images and/or videos inside of a single PQ file, you'll end up keeping fewer files on your server.
I believe Uber store JPEG data in PQ files and Spotify store audio files in PQ or a similar format on their backend.
I'm not sure what the state of lossless algorithms might be for that though.
It'll also take a hell of a long time to do the compression and decompression. It'd probably be better to do some kind of chunking and deduplication instead of compression itself simply because I don't think you're ever going to have enough ram to store any kind of dictionary that would effectively handle so much data. You'd also not want to have to re-read and reconstruct that dictionary to get at some random image too.
I've rarely seen any non-giants with PBs of data properly compressed. For example, small JSON files converted into larger, compressed parquet files will use 10-100x less space. I am not familiar with images but see no reason why encoding batches of similar images should make it hard to get similar or even better compression ratios
Also, if you decide to move off later on, your transfer costs will also be cheaper if you can move it off in a compressed form first.