Uploads that delete themselves

Your bucket does the deleting

Expiring files are uploaded under tmp/1d/, tmp/7d/, tmp/14d/ or tmp/30d/ in front of their usual path, and a lifecycle rule in your bucket deletes everything in that folder when the time is up. Aktar doesn't need to be running for that: files are deleted on schedule even when your Mac is off or Aktar is no longer installed, and temporary shares stop piling up in the bucket.

History, the Library and upload notifications show when each expiring file will be deleted. While a duration is picked, the panel says so under the drop zone, so a file you meant to keep doesn't expire by accident.

One click to set up

Delete after becomes available once the destination's bucket has Aktar's rules. Choose Set Up Auto-Delete… in the Delete after menu, or use the Auto-Delete section of the destination in Settings → Destinations. Aktar adds four rules, aktar-expire-1d, aktar-expire-7d, aktar-expire-14d and aktar-expire-30d, and keeps every other rule in the bucket exactly as it was.

Some keys aren't allowed to change lifecycle rules, for example a Cloudflare R2 token with Object Read & Write permission (Admin Read & Write works). In that case Aktar lists the four rules to add in your provider's dashboard, and you check again once they're there.

Changed your mind? Turn Off… in the same section stops offering Delete after for that destination. You can keep the rules, so files already under tmp/ are still deleted on schedule, or remove them.

Raycast, iPhone, iPad and Android

The local API now takes expires= on uploads, which gives the Aktar extension for Raycast a Delete After option of its own. The iPhone, iPad and Android apps get expiring uploads in version 1.1.0. They use the same folders and rules, so a bucket you use on several devices only needs to be set up once.