There should only ever have 1 autosave file per project as it overwrites previous versions when it autosaves
So this may be of interest to you .... This is the way I work with construct 3
1) I have auto backups set to "Save to Browser" at 10 minute intervals.
This is the best way for the short interval backup IMO as it happens in the background so does not interfere with workflow and gives me the best peace of mind that if anything goes wrong in short term I have a very recent copy.
2) Every , say 30-60 minutes, or after I have made a major change, then I will "Download a Copy"
This is the best for regular saving as it puts a physical copy on my hard drive and due to the nature of "Download" always gives it a new sequential number ( i really love this aspect of using Download) so I am not overwriting any previous file. every save i make will automatically be its own file with a new number suffix.
3) at the end of every session I save a copy to the cloud.
When returning to my project I always use the latest sequentially numbered file in the Downloads folder
This means that my project always has a new file name every time I open it.
This is the filename used when Construct makes the automatic Backup to the Browser.
(Note that I very rarely use the Browser Backups I am just happy knowing that they are there. And yes they have saved my life on a few occasions.)
My project is currently running at about 180MB save
AS the project filename is always different, every time I use Construct the auto backup adds another 180 MB to IndexedDB
So not including anything else like exports etc, using construct 88 times will fill indexeddb >16GB (which appears to be max allowed by chrome)