




















mtime with E2EE, but both S3Drive and Rclone (incl. crypt) preserves file mtime which is the file modification time as displayed by your OS.
If your image has already invalid mtime at the time of the upload that's what would end up on S3Drive. (edited)mtime from EXIF data using some simple scripts.
My suggestion would be to try building a script (or ask AI to help you build one) to restore mtime from EXIF.
E.g. exiftool "-FileModifyDate<DateTimeOriginal" *.jpg
or even: exiftool "-FileModifyDate<DateTimeOriginal" "-FileModifyDate<CreateDate" -r .
Bear in mind that it would be good to backup your files just in case you mess up.
Once you have it in place, you can reupload data to S3Drive and see whether it works.
You can preview mtime, as well as EXIF data using S3Drive (please see attached screenshots)

mtime with E2EE, but both S3Drive and Rclone (incl. crypt) preserves file mtime which is the file modification time as displayed by your OS.
If your image has already invalid mtime at the time of the upload that's what would end up on S3Drive. (edited)