Add option to auto-delete original file after it's been converted via automation

This idea is open.

If you like this idea, please share how this would help you, and vote to show your support.

Our top-voted ideas are shared with our product teams to investigate in our regular reviews.

Agree with this. Do people use DB automation just to convert file types? If so, they would want to keep both. I would not do this- I will always want control over file conversion parameters when the file itself is the objective. Instead, in my applications, I want to share a file using a specific format for broad compatibility as the #1 goal, not file content quality. And in this scenario, I don't want the original file to remain- it takes up space, creates a duplicate (if adding this file from another archive), and makes folder browsing, searching messy. I'd prefer this behavior as requested- delete the original file after conversion.

It would support this 100%, but would suggest implementing by adding a "Delete Original File' option in the Automation rule creation process so that it is flexible for different use cases.